Custom Query (122 matches)
Results (16 - 18 of 122)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #18 | fixed | 09-013 COULIS in PROII | Michael Halloran | michelpons |
| Description |
De: Michel Pons [technologyofficer@…] Envoyé: Wednesday, June 24, 2009 9:25 PM À: 'Ahsan Akhtar' Cc: 'Michael Halloran' Objet: COLTT Issue 09-013 COULIS in PROII Pièces jointes: Mylog240609.olg; proii_062409_211137_10802.log Hi, I have tried the following scenario : in PRO/II 8.3 I am creating a new case by inserting a CAPE-OPEN UO in the flowsheet (no thermodynamic model defined yet). PRO/II opens up a message box that lets one choose which CAPE-OPEN UO to select. I select COULIS from AmsterCHEM. With COLTT 1.08.02 enabled on COULIS, I get an immediate crash leading to the attached log file. With COLTT 1.07 I get also a crash but without any log file appearing in the destination folder. Without COLTT enabled on COULIS, I am able to select which UO to log in COULIS, here GLCC. The attached olg file coming from COULIS shows that. This issue has been numbered 09-013. let me know if you need me to install Visual Studio 2008 in the corresponding VM. Best regards Michel |
|||
| #20 | fixed | 09-017 Test3UO in Aspen Plus 7.1.1 | Michael Halloran | michelpons |
| Description |
De: Michel PONS via YouSendIt [delivery@…] Envoyé: Wednesday, August 26, 2009 10:48 AM À: technologyofficer@… Objet: File Sent: COLTT09-017.zip
============================================================== De: Michel Pons [technologyofficer@…] Envoyé: Wednesday, August 26, 2009 10:43 AM À: 'Michael Halloran' Cc: 'malcolm.woodman@…' Objet: COLTT 09-017 Test3 in Aspen Plus v7.1.1 Michael, You may want to log this issue through the bug tracking facility on SourceForge. I have not put yet SHMA in copy since I don’t know what is the on-going status with SHMA at this stage. Within Aspen Plus 2006.5 I had logged an issue labeled 917841 that pertained to the fact that the flow property in Aspen Plus was not correctly implemented. This led to defect CQ00319371. I had documented this defect with a dedicated Fortran made UO that did not much except calling on this flow property to show it did not work properly. This defect has been announced as resolved in Aspen Plus 7.1. So I have reset the case in Aspen Plus 7.1 with Cumulative Patch 1. I will post you through yousendit the accompanying material meaning the installer for the UO, the bkp file used to start the case as well as the log files and the screenshots mentioned hereafter. The scenario is rather simple. I start from an Aspen Plus file that presents two material streams (one for input, one for output). The inlet stream is fully configured. I select the Corentin_version3 UO (the CAPE-OPEN UO mentioned above) within the CAPE-OPEN library of UOs available and I drop it on the flowsheet. In Aspen Plus 2006.5 I was able to connect the streams and to launch calculation. In Aspen Plus 7.1.1 the UO looks dead meaning no ports available on the UO so I don’t get any further. I have relogged an issue with Aspentech Support on that one. To try understanding the issue I first logged the scenario with COLTT 1.07 enabled on the UO. To my surprise, with COLTT enabled on the UO, the ports are appearing on the UO and the calculation is fine. I can even check that indeed the flow property is well returned by the MO. So I have an issue with COLTT: it changes the behaviour in between the PMC and the PME. My next step has been to try COLTT 1.08.02 on this case. Here I have also a change a behaviour between the PMC and the PME since the ports are showing up and I may launch the calculation. However I have, within the Calculate method, a debug assertion failure message (see screenshots for that) that I chose to ignore and I have then Aspen Plus miserably crashing. So there is also a different behaviour between 1.07 and 1.08.02. That does not help. I have defined this as being issue COLTT 09-017 in order to track it on my side for the moment. There may be two issues there. One is making the ports appear and the second is the debug assertion failure in 1.08.02. Best regards Michel |
|||
| #21 | fixed | 09-014 GLCC UO in PRO/II 8.3 | michaelhalloran | michelpons |
| Description |
De: Michel Pons [technologyofficer@…] Envoyé: Wednesday, June 24, 2009 10:50 PM À: 'Ahsan Akhtar' Cc: 'Michael Halloran' Objet: COLTT 09-014 Debug and crash for GLCC in PRO/II Pièces jointes: proii_062409_223724.log Ahsan, I have a scenario showing a strange behaviour on COLTT 1.08.02. It involves a UO PMC (GLCC) and PRO/II 8.3. Without COLTT enabled on GLCC UO, the calculation of the UO does not go well and I wanted to look at the log in order to figure out what was going on. However enabling COLTT 1.08.02 on GLCC leads first to a debug assertion error then a crash a bit after instantiating the GLCC UO within the PRO/II flowsheet. In fact I have two crash messages as follows: Microsoft Visual C++ Debug Library Debug Assertion Failed!
Program: C:
File: d: Line: 154 Expression: p!=0 For information on how your program can cause an assertion failure, see the Visual C++ documentation on asserts. (Press Retry to debug the application) Abandonner Recommencer Ignorer I selected « Ignore » and got : Exception Detected Exception code 0xc0000005: EXCEPTION_ACCESS_VIOLATION The thread tried to read from or write to a virtual address for which it does not have the appropriate access. Select Cancel to debug or OK to save the copy and quit. OK Annuler Exception Detected Exception code 0xc0000005: EXCEPTION_ACCESS_VIOLATION The thread tried to read from or write to a virtual address for which it does not have the appropriate access. Select Cancel to debug or OK to save the copy and quit. OK Annuler There is a short log created. It is attached. I have numbered this issue 09-014. Let me know if you need Visual Studio 2008 installed in the VM dedicated to this issue. Best regards Michel |
|||