/build/static/layout/Breadcrumb_cap_w.png

hi i am getting the following problem while working on hysys application. any one know about this errors? thanks

I spend sometimes on EDR V7.3.2 and win 7 packaging this weekend. I am dealing with two problems which need to be resolved before we can request testing by the users.

 

First problem is the licensing portion. EDR install package from Aspentech installs a version of SLM Client tools that does not work well with WIN 7 64 BIT. On Sunday, I created a ticket with Aspentech to remove the licensing tool from the package and plug in the one we want. I am waiting for a response from Aspentech.  My earlier suggestion of packaging the newer SLM client tool does not resolve the issue.

 

As you know, the 2nd problem is the MS SQL express SP3 install which displays a warning that none of the property data bases are restored and they have to be restored manually after the install.  This week end, I tried this on a clean VM system. If I install SQL SP3, EDR V7.3.2 installer package from Aspentech does not give this warning however if I use COP package, then I get this error.  This problem is being introduced after being packaged. So your group needs to resolve this problem before we can request testing by the users.  I had a meeting with my EDR customer on Friday and he does not want to see any warning which may confuse the users.  Another reason for solving this problem is that, these databases are used with Aspen Plus and Hysys and the same warning will appear on the install for these products so we need to resolve this before we can proceed.

 


0 Comments   [ + ] Show comments

Answers (0)

Be the first to answer this question

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ