Custom Query (122 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (16 - 18 of 122)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Ticket Resolution Summary Owner Reporter
#17 fixed 09-011 GLCC UO in Aspen Hysys 7.1 Michael Halloran michelpons

Reported by michelpons, 13 years ago.

Description

De: Michel Pons [technologyofficer@…] Envoyé: Sunday, April 26, 2009 10:26 PM À: 'Michael Halloran' Cc: 'Ahsan Akhtar' Objet: RE: GLCC UO In Aspen Hysys v7.1

Pièces jointes: COLTT09_011_Screenshots.doc

Michael,

Please find attached a Word file with screenshots obtained with the scenario of COLTT issue 09-011. I ignore the assertion failed error and then Aspen Hysys crashes.

Best regards

Michel ======================================================= De: Michael Halloran [michaeljhalloran@…] Envoyé: Saturday, April 25, 2009 11:35 PM À: Michel Pons Cc: Ahsan Akhtar Objet: Re: GLCC UO In Aspen Hysys v7.1 Michael,

Can you add information about the assertion? When you get an assertion do you try to ignore it and continue the run?

I don't understand the logs here. The 1.07 log should show the calls to get_ComponentName in the same places as the 1.08 log. The 1.07 logger is logging them and they must have been called or the name shown in the log wouldn't have changed to Check for the 1st parameter. So that looks like a 1.07 problem to me; the 1.08 log is what I would expect.

Regards Michael ========================================================== De: Michel Pons [technologyofficer@…] Envoyé: Thursday, April 23, 2009 10:15 PM À: 'Ahsan Akhtar' Cc: 'Michael Halloran' Objet: GLCC UO In Aspen Hysys v7.1

Pièces jointes: hysys_042309_215826v107.log; hysys_042309_215412v1082.log

Ahsan,

I have ran a combination involving a CAPE-OPEN UO using Thermo 1.0 and Aspen Hysys v7.1. The UO comes from TOTAL and has been made with the Visual Basic Wizard.

The scenario starts from an Unconnected case file that displays three streams, one to be used as inlet and two as outlets to the UO. I use “Add Operation” then Extensions the CAPE-OPEN 1.0 and select GLCC UO. Then I accept this choice. Things are differing from then on with/wothout COLTT and between COLTT versions.

Without COLTT enabled on the GLCC UO, I get message boxes from Aspen Hysys of the type “Error in ExposeCOParstoHysys(13)”. This has been documented to Aspentech Support and is in the process of being solved. Several of these message boxes have to be Okeyed before arriving at the point where connections between ports and material streams can be made. I stop the scenario here.

With COLTT v1.07 enabled on the GLCC UO, I get first the same error message as above and then I have a message box repeated quite a number of times “ActiveXtender Error setting cell color (SetFontCellColor).

With COLTT v1.08.02 (after changing the COLoggersST.dll file) I get, after accepting the UO, a debug assertion failed message and then Aspen Hysys crashes.

I have joined to this message the two log files obtained. I am surprised that the two logs do not show exactly the same sequence.

COLTT v1.07

Parameter Collection <Unnamed> : Call to Item requesting Item 1 Parameter Collection Item returns : 0x569a84 Parameter Collection <Unnamed> : Return from Item - No Error Parameter <Check> : Call to get_Specification

get_specification returns: 0x56e97c

Parameter <Check> : Return from get_Specification - No Error

COLTT v1.08.02 ParameterCollection <Anonymous> : Call to Item requesting Item 1 ParameterCollection Item returns : 0x5698ec ParameterCollection <Anonymous> : Return from Item - No Error Parameter <Anonymous> : Call to ICapeIdentification.get_ComponentName Parameter <Anonymous> : Return from ICapeIdentification.get_ComponentName - No Error Parameter <Check> : Call to get_Specification

get_specification returns: 0x56ccfc

Parameter <Check> : Return from get_Specification - No Error

I have logged this issue as 09-011 in the meantime.

Best regards

Michel

#18 fixed 09-013 COULIS in PROII Michael Halloran michelpons

Reported by michelpons, 13 years ago.

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

#19 worksforme 09-016 COMThermo PP 1.0 in Simulis Thermodynamics Michael Halloran michelpons

Reported by michelpons, 13 years ago.

Description

De: Michael Halloran [michaeljhalloran@…] Envoyé: Monday, August 17, 2009 11:03 PM À: technologyofficer@… Cc: Ahsan Akhtar; malcolm.woodman@… Objet: Re: COLTT 09-016 COMThermo in Simulis Thermodynamics Michel,

Since the logs are so similar I think the debug messages are harmless. I agree they shouldn't be there but I think they are a consequence of you running a debug build. I think the first step is to re-run the test with a release build of 1.08.2 (or .3?) and to compare with 1.07 again.

Regards Michael ==================================================== De: technologyofficer@… Envoyé: Wednesday, August 12, 2009 7:46 AM À: Michael Halloran Cc: Ahsan Akhtar; malcolm.woodman@… Objet: Re: COLTT 09-016 COMThermo in Simulis Thermodynamics

Michael,

I have not made any calculations in both examples. I just selected the Property Package and stopped there. Things may be fine with calculations afterwards but my point is that debug assertion failed messages should not pop up. By clicking on Ignore at each debug assertion failed message I am moving on. There is no such message with COLTT 1.07 enabled on COMThermo Thermo System.

Best regards

Michel =================================================== De: Ahsan Akhtar [ahsan.akhtar@…] Envoyé: Wednesday, August 12, 2009 6:17 AM À: 'Michael Halloran'; 'Michel Pons' Cc: malcolm.woodman@… Objet: RE: COLTT 09-016 COMThermo in Simulis Thermodynamics

Michael,

Yes, you are right, it is a debug build.

Best Regards

Ahsan ==================================================== De: Michael Halloran [michaeljhalloran@…] Envoyé: Wednesday, August 12, 2009 12:01 AM À: Michel Pons Cc: Ahsan Akhtar; malcolm.woodman@… Objet: Re: COLTT 09-016 COMThermo in Simulis Thermodynamics Michel,

The two logs look very similar, so it seems that the calculations proceed in both examples. Is that correct? Are you continuing through the debug messages?

Ahsan, do you know whether 1.08.2 is a debug build or a release build? Presumably 1.07 is a release build?

Regards Michael ================================================== De: Michel Pons [technologyofficer@…] Envoyé: Tuesday, August 11, 2009 11:32 AM À: 'Ahsan Akhtar'; 'Michael Halloran' Cc: 'malcolm.woodman@…' Objet: COLTT 09-016 COMThermo in Simulis Thermodynamics

Pièces jointes: excel_081109_105634_v107.log; excel_081109_110300_v1082.log; Screencopy110809.doc

Hi,

I get « Debug Assertion Failed » messages while making the selection of a COMThermo PP in Simulis Thermodynamics. This occurs with COLTT 1.08.02 while it does not occur with COLTT v1.07. You will find attached a Word document made of screen copies of the scenario performed as well as the log files obtained both with 1.07 and 1.08.02.

I have given number 09-016 to this issue.

Best regards

Michel

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