Custom Query (122 matches)
Results (40 - 42 of 122)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #55 | fixed | PPM not queried on error returned | michaelhalloran | michelpons |
| Description |
The scenario is based on the one described for ticket #34 and is obtained when there is no PPDS license available. There is a complete process model developed in Aspen Hysys and making use of PPDS. Because the license is not there the PPM returns an error code 0x80040501 and this is logged in the log file. Aspen Hysys does not seem to pursue any further the matter. However I don't see any attempt from COLTT to query the error handling interfaces that should be present on the PPM object. I wonder why. |
|||
| #56 | fixed | Some problem reading a COLTT log file | MichaelHalloran | michelpons |
| Description |
The attached log file has been obtained by reloading a case in Aspen Hysys v7.2. The case involves a Property Package from MultiFlash Property Package Manager. There is a short error message when loading the file in the Viewer saying that some problem occurred when reading the file. The log file has been done with the COLTT build from June 30, 2010. |
|||
| #57 | fixed | UO and PPM/PP logging not on same level in report | MichaelHalloran | michelpons |
| Description |
The attached log has been obtained while enabling simultaneously logging on a UO PMC and on a PPM PMC. The PPM and the PP appears to be logged at the same level in the log through the Viewer while the UO operation calls are below the level of the PP. Normally the UO and the PP should be on the same level at least for the first calls. |
|||