Custom Query (122 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (25 - 27 of 122)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Ticket Resolution Summary Owner Reporter
#71 fixed PMC mentioned instead of PME for COSESimulationContext michaelhalloran michelpons

Reported by michelpons, 14 years ago.

Description

I am using the NOOperation COUSCOUS UO in Aspen Plus 7.2. Early on in the log I see:

Simulation Context <B1> : Call to get_NamedValueList[1304] Simulation Context <B1> : Error returned from get_NamedValueList - 0x80040509[1304]

In that the NamedValueList property is a property of the ICapeCOSEUtilities class that is implemented as an interface on the PME (Aspen Plus). As it is written in the log, one could think that a call is made on an interface that belongs to the PMC (B1) while the call is made by the PMC on the PME. So the log should be something like:

Simulation Context <PME> : Call to get_NamedValueList[1304] Simulation Context <PME> : Error returned from get_NamedValueList - 0x80040509[1304]

If the name of the PME is not available. Still I think it is available since it is used to name the log file so:

Simulation Context <apmain> : Call to get_NamedValueList[1304] Simulation Context <apmain> : Error returned from get_NamedValueList - 0x80040509[1304]

Could be more logical.

#74 fixed Log of error interfaces on Port following Disconnect failing michaelhalloran michelpons

Reported by michelpons, 14 years ago.

Description

I set up a scenario in Aspen Plus 7.2 where I reload a saved case where a COUSCOUS splitter is configured with three outlets. All ports are connected to streams. During the reload of the case, the call to Disconnect on each of the UO Port fails: \"Error returned from Disconnect - 0x80040501\". I don't see COLTT attempting to call the error handling interfaces on the Port. My understanding is that a Port should implement the error handling interfaces and so could be queried for further information. I attach the log file obtained.

#75 worksforme Aspen Hysys crashes when using logged Aspen Properties PP michaelhalloran michelpons

Reported by michelpons, 14 years ago.

Description

I am using a simple Aspen Properties PP in Aspen Hysys. Without COLTT enabled on Aspen Properties Therrmo System, I see no problem. When enabling COLTT on Aspen Properties Thermo System, I have a crash just after selecting the PP from Aspen Properties Thermo System. In the attached log, I see:

MaterialObject <Anonymous> : Call to SetProp :

Property PhaseFraction Vapor mole (null) -179769313486231570000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000.000000000

which may be wrong but does not cause a crash without COLTT.

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