Custom Query (122 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (22 - 24 of 122)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Ticket Resolution Summary Owner Reporter
#42 fixed Change of error message when UO logged Michael Halloran michelpons

Reported by michelpons, 13 years ago.

Description

I am using a UO made at University of Trieste (Trieste HX). The source/installation is provided as attachment. A number of tests had been made with this UO in the past in ProSimPlus, PRO/II or UniSim Design. I think I have a problem getting the UO properly registered. The RegUnit.bat does not work or rather it is RegUnitAsm.exe that seems to fail (folder bin). However, I double-clicked on the RegistrationInfo.reg file and the registry was updated. The HeatExchanger UO appears in COLTT Controller as well as in the list of UOs available to the PME, here ProSimPlus.

When the UO is not logged, when trying to instantiate the UO in ProSimPlus I get the following error message:


ProSimPlus - Sans nom.pmp3


Le module spécifié est introuvable.


OK


I would translate that as \"the specified module can't be found\". Now, when I enable COLTT on the HeatExchanger UO, I get as error message for the same step:


ProSimPlus - Sans nom.pmp3


Access violation at address 774D1404 in module 'ole32.dll'. Read of address 00000000.


OK


while the log file contains:

LOG FORMAT

  • Call on a given Object is indicated by 'Object<[Object Name]>: Call to [method name]'. *
  • Input arguments and returned values(if any) are then indicated. *
  • End of the call is indicated by 'Object<[Object Name]>: Return from [method name] - <Success Status>.' *

Log generated by C:
Program Files
ProSimPlus3
ProSimPlus.exe Using configuration from C:
Program Files
CAPE-OPEN
COLTT
CAPE-OPENLogs.ini COLTT Version is 1.08.4

ClassFactory : Loading HeatExchanger implemented by mscoree.dll ClassFactory : Failed to load mscoree.dll

For sure, the UO is not properly installed. However is it right to have a different error message with COLTT enabled on the UO and with the UO on its own?

#43 fixed PME aborts in get_Reports Michael Halloran michelpons

Reported by michelpons, 13 years ago.

Description

I am using a UO built by IFP within COFE 1.15. The UO is a 3-phase separator. When the UO is not logged, the calculation goes to its end but COFE displays warnings about properties not set. So I enabled COLTT on the UO and reran the case. With COLTT enabled on the UO, I can drop the UO in the flowsheet, I can connect the inlet port and the three outlet ports to streams, but COFE aborts when I double-click on the icon representing the UO. The Edit method of the UO is not implemented and normally the generic UO interface from COFE should have appeared so that I may give values to the UO parameters.

The attached COLTT log shows that the logging stops in get_Reports. I attach also the COFE document from where I start. The installer for the UO is too large to be attached and will be delivered through a file server.

#44 fixed Location in logfile of message from Validate method Michael Halloran michelpons

Reported by michelpons, 13 years ago.

Description

I am using ChemSep Lite UO in COFE. The COFE flowsheet case will be provided as an attachment. I used this case to check how COLTT was behaving. My only minor concern is with the logging of Validate:

Unit <HPC> : Return from Validate - Succeeded, isValid=false

Message returned from Validate was: not all ports are connected Checking validation status after the call...

It seems to me that the message returned from Validate could be placed before :

Unit <HPC> : Return from Validate - Succeeded, isValid=false

Something like:

Validate returns : isValid : false Message : not all ports are connected Unit <HPC> : Return from Validate - Succeeded

I don't know from where:

Checking validation status after the call...

comes from. If it is an action taken by COLTT, there should be an appropriate way to mention that, oterwise there should be another way.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Note: See TracQuery for help on using queries.