Custom Query (122 matches)
Results (91 - 93 of 122)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #54 | duplicate | Viewer has problems reading a log file | michaelhalloran | michelpons |
| Description |
The attached log file was obtained with the scenario of ticket #33 and with COLTT development version 1.08.5 Build June 30, 2010. When opening the file a message box appears stating \"Some problem reading the file\". |
|||
| #62 | duplicate | Simulis crashes when COLTT enabled on Aspen Properties Thermo System | michaelhalloran | michelpons |
| Description |
I am making a simple calculation in Simulis Thermodynamics using an Aspen Properties Property Package: enthalpy calculation at 1 atm and 90°C of a 10% mol / 90% mol ethanol/water mixture. When Aspen Properties Thermo System v24.0 (i.e. aspenONE 7.2) is logged with either COLTT 1.08.4 or 1.08.5, Simulis crashes and exits during the calculation. Results are obtained when COLTT is not enabled on Aspen Properties Thermo System. The problem may be that Aspen Properties Property Package tries to set a phase fraction for a non-existent solid phase on Simulis MO and that the value to be set is wild... |
|||
| #130 | duplicate | Repeated calls by COLTT on persistence interfaces | Michael Halloran | michelpons |
| Description |
I am using COLTT 2.1 Build June 16, 2012 enabled on a TEA Thermo System and a COUSCOUS Mixer in PRO/II 9.1. I start from a case file where the TEA Thermo System and one of its PP has already been declared and two material streams have been defined. Then I drop the COUCOUS Mixer on the flowsheet, connect inlet ports and the outlet ports and then I run the simulation which ends up with no error. Parsing through the log file obtained, I am puzzled by the following sequence: COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Return from QueryInterface - Succeeded COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Return from QueryInterface - Succeeded COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Return from QueryInterface - Succeeded COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Return from QueryInterface - Succeeded COLTT <CO1> : Call to IPersistStream.Save COLTT <CO1> : Return from IPersistStream.Save - Succeeded It seems there are repeated calls on the same interface by COLTT and that the failure to find this or that interface on the UO is not accounted for by COLTT which repeats on and on the same calls. This sequence seems to occur several times and since the overall logging takes quite longer than the simulation wothout any log, I was wondering if unnecessary calls were made by COLTT and if so could be discarded. |
|||