question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement:
Reported phase properties for each of the single scenarios created in Aspen Flare System Analyzer (AFSA) can be exported into an Excel sheet. | Solution:
As is mention in KB How do I use the Export/Import feature in Aspen Flare System Analyzer? AFSA allows you to export your results to any desired format. If you want to export only the property phases form your scenarios , follow the listed steps:
In the step 2 at the Export Wizard window, from the three options available chose Create a new export definition file; this will allows you to define your own set of variables to export.
From the objects list, look for Results and click on it. Once is highlighted on the Target ribbon, check for Export this type of data, do the same for Phase and CompResults,
Click back the Results folder and move to the Field Details ribbon, check for Scenario Name and for all the information you want to export, do the same for Phase and CompResults,
NOTE: you can always chose the option "Export All"
Click finish and all the properties for all the scenarios will show in the Excel file created.
NOTE: These steps apply not only for phase results; can also be use for any other results available in AFSA
Key words:
Export, Properties, Property Phases, Scenarios.
Keywords: None
References: None |
Problem Statement: After changing the original name of the APC Online server, a problem related to the RTE applications can happen and messages like this are showed on PCWS:
Application: '<Name>' terminated unexpectedly on node: 'Online@localhost'; attempting to restore.
Application: '<Name>' removed from node: 'Online@localhost'
Application: '<Name>' added to node: 'Online@localhost'
Application: '<Name>' was restored on node: 'Online@localhost'
The license server can be reached successfully with the SLM License Profiler tool on the server, but in the Event Viewer in the .NET error message seem to be related to licensing issues. | Solution: Follow the next procedure in order:
Stop the RTE controller application using DMC3 Builder on the Online tab.
Delete the RTE controller application.
Stop the AspenTech Production Control RTE Service.
Go to the next path C:\ProgramData\AspenTech\RTE\V11\Clouds\Online\sys and locate the folder, the .2st and the .apc.dataset files of your application and delete them.
Start the AspenTech Production Control RTE Service.
Go to DMC3 Builder to the Controllers tab and Deploy the controller again.
Verify on the APCOnlineLicensing.log file that the license validation of the application has been completed successfully.
Keywords: RTE controller, licensing issue, renaming server
References: None |
Problem Statement: How to create a Read Only ODBC connection for IP21 through AspenTech SQLplus driver? | Solution:
1. First you need to create a Read Only connection for SQLplus, as described on KB "How to create a read only connection for SQLplus users ". From this step, a new TCP port fro Read Only communication will be created.
2. Confirm if the 3rd party application that you are connecting to is a 64-bit or a 32-bit application. If you are connecting an IP21 32-bit to a 64-bit application, make sure that you have installed Aspen ODBC Drivers (64-bit) on the end node, or if you are connecting to a 32-bit application, confirm that you have the corresponding 32-bit driver on the end node. If not, please enable a custom installation by following this KB: "How do I enable an aspenONE custom installation? ".
Depending on the end application (32-bit or 64-bit), open ODBC Data Source Administrator on the end side (If the end application is on a separate server than IP21 server, perform these steps on the 3rd party application server) . In order to do it, please follow these steps:
3. Open ODBC Data Source Administrator (32-bit or 64-bit depending on the 3rd party application) and click on "System DSN" tab (System DSN means that anyone logged into the computer has access to the ODBC string) or on "User DSN" tab (User DSN means only one user will have access to the string), then click on "Add".
4. Click on AspenTech SQLplus, then click on Finish.
5. A new window will be displayed, type a name for that String and a Description, then click on "Advanced" and then uncheck the last option: "Use Aspen Data Sources (ADSA)"
6. Enter the IP address of the IP21 server and the number of the tcp port that was created in step 1.
7. Confirm that the new string was added to the list, either in System DSN or in User DSN.
Third party application may require to use a Windows account, please make sure that that account is on AFW (If AFW is enabled) and it has Read permissions on AFW.
Keywords: ODBC
Read Only
SQLplus
System DSN
References: None |
Problem Statement: This is an example demonstrating the modeling of simple blending mixer in Aspen Custom Modeler | Solution: Fe, C, Cr and Mn are fed to furnace and mixed together to create Stainless Steel.
It does not use Aspen Properties but it uses stringset to define those components.
Detailed code are attached as below.
You can learn how to use For Loop and multiport in this example.
Model Well
comp as stringset(["C","Fe","Mn","Cr"]);
inlet as input multiport of Fport;
outlet as output Fport;
total_mass as mass;
mass(comp) as mass(initial,0.1);
total_mass=sigma(mass);
fraction(comp) as massfraction;
1e4*fraction(comp)*total_mass=1e4*mass(comp);
Opening as percent(fixed,0.001);
for i in comp do
$mass(i)=sigma(inlet.connection.mass*inlet.connection.fraction(i))-outlet.mass*outlet.fraction(i);
endfor
outlet.fraction=fraction;
outlet.mass=Opening/100*total_mass;
End
Keyword
Aspen Custom Modeler, Blending, Mixer
Keywords: None
References: None |
Problem Statement: 이 예제는 Aspen Custom Modeler 를 이용한 간단한 혼합 믹서의 디자인을 설명합니다. | Solution: Fe, C, Cr, Mn 이 혼합되어 용광로로 투입이 되어 스테인레스 스틸이 생산됩니다.
이 예제는 Aspen Properties 를 사용하지 않고, Stringset 를 이용하여 4가지 Components 를 설정하고 있습니다.
이 예제에서 multiport 와 For 구문의 사용법을 익힐 수 있습니다.
아래 코드와 첨부 예제파일을 참고하십시오.
Model Well
comp as stringset(["C","Fe","Mn","Cr"]);
inlet as input multiport of Fport;
outlet as output Fport;
total_mass as mass;
mass(comp) as mass(initial,0.1);
total_mass=sigma(mass);
fraction(comp) as massfraction;
1e4*fraction(comp)*total_mass=1e4*mass(comp);
Opening as percent(fixed,0.001);
for i in comp do
$mass(i)=sigma(inlet.connection.mass*inlet.connection.fraction(i))-outlet.mass*outlet.fraction(i);
endfor
outlet.fraction=fraction;
outlet.mass=Opening/100*total_mass;
End
Keyword
Aspen Custom Modeler, 블렌딩, 혼합
Keywords: None
References: None |
Problem Statement: In Aspen HYSYS, it is possible to open multiple cases inside the same session. This functionality is not supported inside Plant Data and may result in unsaved changes being lost when switching between cases. | Solution: To open multiple cases when using Plant Data, open separate HYSYS instances for each case.
Key Words
Hysys, Plant Data, Case
Keywords: None
References: None |
Problem Statement: Aspen HYSYS V11 Stream Reporter (HSR 1.7.2) | Solution: HYSYS Stream Reporter (HSR) is an Excel spreadsheet utility that allows to import to a spreadsheet the material stream information such as conditions, properties and compositions, and also compare streams from different cases.
HSR can report properties from the following phases: Overall, Vapour, Light and Heavy (Aqueous) Liquid, Combined Liquid and Solid. It also allows stream user variables and property correlations to be reported. It is also possible to create formulae in the output table. The user can save sets of properties or use one of the pre-built property sets. Streams from different HYSYS cases can be reported in the same stream table. Once a stream table has been generated it can be updated by pressing a single button. Stream tables can be moved to another Excel workbook whilst maintaining the ability to be updated.
HSR takes the form of an Excel spreadsheet file with embedded Visual Basic for Applications (VBA) code that demonstrates how HYSYS can be accessed programmatically. The VBA source code is freely accessible and users are encouraged to learn from it and adapt it to their own needs.
For V10.0 please see the KB Article 056331.
For V9.0 please see the KB Article 057415.
For V8.0 - V8.8 please see the KB Article 057412.
For older versions see the KB Article 054553.
Note
This Automation application has been created by AspenTech as an example of what can be achieved through the object architecture of HYSYS. This application is provided for academic purposes only and as such is not subject to the quality and support procedures of officially released AspenTech products. Users are strongly encouraged to check performance and results carefully and, by downloading and using, agree to assume all risk related to the use of this example. We invite any feedback through the normal support channel at [email protected].
KeyWords
HYSYS Stream Reporter, HSR
Keywords: None
References: None |
Problem Statement: After installing V12 in a VM or local desktop which has already had other versions installed (like V11, V10), Aspen Multi-case users may get an error saying "HYSYS Engine not found in: C:\Program Files\AspenTech\Aspen HYSYS V11.0\hysysengine.exe" when they try to load a HYSYS base case. How can this issue be resolved? | Solution: 1. First, run Set Version - Aspen HYSYS V12 as an Administrator (Found in the Start Menu | Aspen HYSYS folder):
Try attaching a base case again. If that doesn't work:
2. Go to the Registry Editor and under HKEY_CLASSES_ROOT, search for the key: {AAAFC3BE-6389-4B14-AE5C-AAE8E3F98615}. Make sure you find one instance that has children. Then, select the child called LocalServer32. Check on the right hand side, there is a default string. Please check to which folder that string is pointing to and make sure it matches the path C:\Program Files\AspenTech\Aspen HYSYS V12.0\HysysEngine.exe per the image below:
3. Try to attach a HYSYS case again. Ensure you are using Google Chrome for optimum performance.
Keywords: Aspen Multi-case, Registry Editor, Google Chrome
References: None |
Problem Statement: In order to run the GDOT applications in the GDOT Console it is necessary for the User of the machine to be part of the GDOT predefined groups that are configured once you install the Aspen Dynamic Optimization (ADO) suite products. These predefined groups are: GDOTUsers, GDOTOperators, and GDOTEngineers. | Solution: Firstly, you need to make sure you are using an Account with Administrator privileges before starting this procedure.
Go to Computer Management and click on Local Users and Groups.
Click on Groups and make sure that the three GDOT predefined (GDOTUsers, GDOTOperators, and GDOTEngineers) exist in the machine. Otherwise, the installation of the ADO suite has not been performed correctly and must be repaired or re-installed.
If all GDOT predefined groups can be found, then go to Users and locate the User ID you want to add to the GDOT predefined groups. For this example, the selected user is Student.
Double-click on the selected user, the <User> Properties window will show up. Then you will need to click on Member Of tab and then click on Add.
The Select Groups window will show up and you can add the desired GDOT predefined groups manually or click on Advanced.
A menu will be displayed, click on Find Now and locate the GDOT predefined groups and click on OK.
Once the GDOT groups are added to the Select Groups window, click on OK.
If you are able to see the new groups have been added to the Member Of tab, click on Apply and then click on OK.
Keywords: GDOT, GDOTUsers, GDOTOperators, GDOTEngineers, Console
References: None |
Problem Statement: Article 13272 shows a method to execute a query from a graphic published on aspenONE Process Explorer using COS activation from a record working as a trigger. However, method described on the case do not allows passing parameters to the query to be executed other than writing those parameters on a temporary record location and modify the query to take values from a dummy record. Article 8165 shows that is possible to use an SQLplus procedure and pass parameter as part of the URL of a web report, but in this case, is necessary to create a report for the procedure to be execute from a graphic.
This article shows a method in which an SQLplus procedure can be executed from a graphic published on aspenONE Process Explorer, passing parameters defined by users on interaction with the objects in the graphics | Solution: Aspen SQLplus Web Service can be used to execute any procedure saved as ProcedureDef on InfpPlus.21 database as called from a web resource. Also, any query command that is ODBC compliant can be executed on this way. The next example shows a step-by-step guide on the creation of an example graphic that will execute a procedure which update the value of a IP_TextDef from a graphic through query execution.
1. Creating the procedure
The procedure to use on this example can be created on SQLplus with next code:
Procedure SetTextTagValue(Val char(60))
update TextRec1
Set IP_INPUT_VALUE = Val;
End;
The query simply write a value given on Val variable on the IP_INPUT_VALUE field for a IP_TextDef record called TextRec1. You can create a text record with same or change the name of the record to on the query.
Save this query as a ProcedureDef using Record / Save menu on SQLplus, and confirm you can call it with a query like:
Verify that procedure has update the value on the text tag.
2. Getting user defined values from a text data box on a graphic
Open Aspen Browser Graphic Studio and create a graphic with an interface like this:
These are two text data object, the on the left will hold a text value set by user. To make this, go to the properties of the left text data box and change the name like:
For this example, the name given is DATAENTRY; based on this name, copy and paste the next code on the Action tab of this object:
DATAENTRY = prompt('Give a text value:', 'Sample text');
Publish the graphic and test it by doing a click over the data text box:
A prompt window will request a text for the data text box, clicking on Ok button will give the write the value to the graphic:
On next step, this text will be used as a value for an IP_TextDef using the procedure created on step 1.
3. Executing the procedure to write the text value on the text tag.
Go to the properties of the data text on the right and set the text tag used on the query on the Data tab:
This box will show the latest value on the tag.
Go to the properties of the button object and copy/paste next code:
var ServerName = '10.36.48.202';
var command = "SetTextTagValue('[1]')";
var param1 = DATAENTRY;
command = command.replace('[1]', DATAENTRY);
var WebServiceURL = 'http://' + ServerName + '/SQLplusWebService/SQLplusWebService.asmx?op=ExecuteSQL';
var soapRequest = '<?xml version="1.0" encoding="utf-8"?>' +
'<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">' +
'<soap:Body><ExecuteSQL xmlns="http://www.aspentech.com/SQLplus.WebService/"><command>' + command + '</command></ExecuteSQL></soap:Body>' +
'</soap:Envelope>';
var webRequest = new XMLHttpRequest();
webRequest.open('POST', WebServiceURL , 'False');
webRequest.setRequestHeader ('Post', '/SQLplusWebService/SQLplusWebService.asmx HTTP/1.1');
webRequest.setRequestHeader('Content-Type', 'text/xml');
if (confirm('Do you want to execute the query?')) {
webRequest.send(soapRequest);
}
Change ServerName for the server in which Aspen Web Application has been installed (this is the same server in which aspenONE Process Explorer is installed).
Publish the graphic again and test it:
Set a value on the left text data:
Click on the Execute button and wait for the graphic to update:
Modification for procedures with multiple variables.
Code provided on step 3 of previous example work for a procedure which have a single parameter. This can be easily extended to use a procedure with multiple parameters as follow:
Having a procedure like:
Procedure OneHourHistory(tagName char(50), starttime timestamp, endtime timestamp)
Set output 'C:\Temp\' || tagName || '.txt';
Select TS, Value From History
Where Name = tagname
And Period = 00:01:00;
End;
Which use three parameters as follow:
OneHourHistory('ATCAI', '21-MAR-17 07:00:00', '21-MAR-17 08:00:00');
And create a text file with 1-minute interpolated values between given dates on C:\Temp folder.
Code on step 3 can be modified as follow:
var ServerName = '10.36.48.202';
var command = "OneHourHistory('[1]', '[2]', '[3]')";
var param1 = DATAENTRY;
command = command.replace('[1]', DATAENTRY1);
command = command.replace('[2]', DATAENTRY2);
command = command.replace('[3]', DATAENTRY3);
alert(command);
var WebServiceURL = 'http://' + ServerName + '/SQLplusWebService/SQLplusWebService.asmx?op=ExecuteSQL';
var soapRequest = '<?xml version="1.0" encoding="utf-8"?>' +
'<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">' +
'<soap:Body><ExecuteSQL xmlns="http://www.aspentech.com/SQLplus.WebService/"><command>' + command + '</command></ExecuteSQL></soap:Body>' +
'</soap:Envelope>';
var webRequest = new XMLHttpRequest();
webRequest.open('POST', WebServiceURL , 'False');
webRequest.setRequestHeader ('Post', '/SQLplusWebService/SQLplusWebService.asmx HTTP/1.1');
webRequest.setRequestHeader('Content-Type', 'text/xml');
if (confirm('Do you want to execute the query?')) {
webRequest.send(soapRequest);
}
Where DATAENTRY1 to 3 are data box on a graphic:
Each one of these data box receives a value following instruction on Step 2 and the button execute the query based on those values:
Keywords: SQLplus web service
aspenONE Process Explorer
Aspen Browser Graphic Studio
References: None |
Problem Statement: Can I see all the additional files stored inside an APWZ file from inside Aspen Plus? | Solution: Compound files (APZW) are a special file format that contain the actual Aspen Plus file and any auxiliary file needed to correctly run the simulation.
These auxiliary files include Excel spreadsheets linked to a Calculator block, PSV information from the Safety Environment, etc.
The simulation file contained inside the APWZ folder can be either a BKP file or an APW file, for information on how to control the file stored inside the APWZ, please check article 26557.
You can see all the additional files that are included in this APWZ, besides the simulation file by loading the file in Aspen Plus and then going to File | Edit Compound File:
In V12, this menu is under File | Tools:
This option will display a new window, which will show the list of additional files that are stored along the simulation file:
This way, you can keep track of all the additional files as well as their size and last modified date.
Keywords: APWZ, compressed, open, contents, extension, compound
References: None |
Problem Statement: Video: Using the Simulation Importer in a Aspen Basic Engineering | Solution: Aspen Basic Engineering Simulation Importer V12
This video covers the description of the Simulation Importer and an example with Aspen HYSYS.
Keywords: Simulation Importer, Aspen Basic Engineering
References: None |
Problem Statement: If you are using a license server, you must upgrade your license server before installing aspenONE V12. | Solution: Before installing V12, do the following:
Download SLM Server V12.
Install SLM Server V12 using our SLM Server Installation instructions.
While installing aspenONE V12
During the installation, if you add a new license server, the installer will verify if the SLM Server is compatible with V12. If a license server already exists, delete the license server and re-add it to invoke compatibility verification.
Additional Resources
How do I check the version of the SLM Server (Sentinel License Manager) software that is installed on the license server?
What is the compatibility policy for Software License Manager (SLM) Server and Client?
Please contact AspenTech Support at [email protected] if you need assistance with upgrading your SLM Server or installing aspenONE V12.
Keywords: Sentinel RMS License Manager
SLM Server
References: None |
Problem Statement: How do I use the Semi-Ideal Cp/Cv option for ISA standard valve sizing? | Solution: On the valve Rating tab, Sizing view of Valve model, there is new option allowing the user to select between Rigorous Cp/Cv and Semi-Ideal Cp/Cv methods. For the relief valve this option is available under Design tab, Parameters view of the unit model. This option determines how mixture's heat capacity is being calculated therefore the specific heat ratio factor [reference: ANSI/ISA-75.01.01-2002 (IEC 60534-2-1 Mod), is evaluated accordingly. When Semi-Ideal Cp/Cv is selected, the specific heat ratio factor is calculated using the approximation, Cv= Cp - R , and Cp is the heat capacity of the process mixture at the atmospheric pressure (1 atm). This new method meets the ANSI/ISA standard and also meets the API 520 standard, for relief and control valves at choked flow.
Meanwhile, Rigorous Cp/Cv is the original HYSYS method, and it uses the process pressure condition, which is dependent on pressures and will then deviate from ANSI/ISA standard. Due to compatibility reason, Rigorous Cp/Cv is the default method in the Valve model.
A screenshot showing the Semi-Ideal Cp/Cv option for control valve
A screenshot showing the Semi-Ideal Cp/Cv option for relief valve:
Keywords: Relief Valve, Control Valve, Semi-Ideal Cp/Cv
References: None |
Problem Statement: When launching an aspenONE V12 client application like Aspen Plus, Aspen HYSYS, etc, you may get an error message stating: "An error has occurred in decrypting (or decoding) a network message. Probably an incompatible or unknown server, or a version mismatch."
Here is an example of the error.
-------------- SLM Common Error Dialog ---------------
Application: AspenHysys.exe
--------------- Information Flags ---------------
Error while checking out license HYSYS_Process
IgnoreLocal
--------------- Sequence of Events ---------------
Server: License Server Name
Bucket: default
Type: Unified License
Code: 25
Description: An error has occurred in decrypting (or decoding) a network message. Probably an incompatible or unknown server, or a version mismatch | Solution: This error occurs if your SLM client software is at a higher version than your SLM license server.
The V12 SLM client tools is at a higher version than the V11 SLM Server. As a result, the SLM license server needs to be updated to V12 to match the SLM client.
You can download SLM Server V12 from the Download Center.
For additional information, please review our compatibility policy for SLM Server and Client.
Please contact AspenTech Support: [email protected] if you have upgraded the license server and you are still getting the above error message.
Keywords: error code 25
SLM error 25
References: None |
Problem Statement: This knowledge base article explains how to check the version of the SLM Server (Sentinel License Manager) software that is installed on the license server. | Solution: To view the SLM Server's version, follow these steps:
1) Log into your SLM License Server.
2) Open Windows Explorer and go to the C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT folder.
3) Right-click lservnt.exe and select Properties from the context menu.
4) Click on the Details tab.
5) Look at File Version. This is the version of your SLM Server.
Keywords: SLM Server, SafeNet Sentinel, RMS License Manager, Version
References: None |
Problem Statement: This is an example demonstrating the modeling of acid gas removal by amine solvent in Aspen Plus Dynamics | Solution: Amine solvent is fed into absorber and used to absorb CO2 gas. Water loss and Amine solvent loss will be made up by following flowsheet constraint.
IF STREAMS("LEAN3").Fm>50000 then
STREAMS("WATER").FmcR("H2O")=0;
else
STREAMS("WATER").FmcR("H2O")=50000-STREAMS("LEAN3").Fm;
endif
STREAMS("AMINE").FmcR("MEA")=STREAMS("CLEANGAS").Fmcn("MEA")+STREAMS("ACIDGAS").Fmcn("MEA");
Keywords: Dynamics, Amine, Acid gas removal
References: None |
Problem Statement: This is an example demonstrating the modeling of acid gas removal by amine solvent in Aspen Plus Dynamics | Solution: Amine solvent is fed into absorber and used to absorb CO2 gas. Water loss and Amine solvent loss will be made up by following flowsheet constraint.
IF STREAMS("LEAN3").Fm>50000 then
STREAMS("WATER").FmcR("H2O")=0;
else
STREAMS("WATER").FmcR("H2O")=50000-STREAMS("LEAN3").Fm;
endif
STREAMS("AMINE").FmcR("MEA")=STREAMS("CLEANGAS").Fmcn("MEA")+STREAMS("ACIDGAS").Fmcn("MEA");
Keywords: Dynamics, Amine, Acid gas removal
References: None |
Problem Statement: Checklist: everything you need to start your V12 aspenONE deployment today | Solution: The checklist below will assist you with adopting aspenONE V12. A PDF version of the checklist is attached to this article.
Review product documentation
Hardware and software requirements- AspenTech Platform Support Page
If deploying in the cloud, review AspenTech Cloud Support Portal
Product Release notes and installation guides
Visit the Upgrade Journey page for best practices to upgrade
Develop V12 deployment plan
Request V12 license using License Request form
Download V12 media from Download Center
Note: If you do not have access to the media when logged into AspenTech Support Website , please submit a Media Upgrade form.
Preparing the deployment
Download and upgrade SLM Server to V12 - This is a requirement for V12
Create a V12 silent deployment package
Note: Starting with V12, aspenONE Engineering or Petroleum Supply Chain products are now supported with Virtual Desktop Infrastructure (VDI) such as Windows Virtual Desktop. You may choose this option over creating a silent deployment package.
aspenONE V12 Desktop Installation, for reference use aspenONE V12 Unattended Installation Guide
Testing and validation
Verify installation is successful with the Aspen Diagnostic Tool
If installing aspenONE Engineering products, run the Aspen Version Comparison Assistant to validate the models.
Other resources
AspenTech offers Remote Upgrade Services and Consulting
AspenTech offers 120+ training courses, check out our Product training offerings.
Keywords: None
References: None |
Problem Statement: What is the SLM? Software License Manager (SLM) | Solution: Software License Manager (SLM) is a software-based security system that controls and tracks the usage of software, components and features from Aspentech and certain third-party software. The SLM provides significantly more flexibility than the old heritage Hyprotech security system. The following is a summary of the major capabilities offered by the SLM:
? The SLM uses a license file that contains the list of software and features you are licensed to run.
? A single license file can contain multiple software packages and a variety of features (i.e. 3 copies of HYSYS Process and 1 Crude Module, 5 copies of Aspen Plus).
? New license files can be e-mailed to you to add new software or features.
? A hardware key is used in conjunction with the license file. Unlike the traditional Hyprotech key it is simply used as a locking device and contains no license information.
Keywords: SLM
definition
References: None |
Problem Statement: Does it allowed to have the incompatible SLM versions between the server and the client machine? | Solution: When you install the SLM on the server and the client machine, make sure they are using the same versions. In case you are using the different SLM versions, the SLM version on the server must be higher than the SLM version on the client machine.
Keywords: incompatible
server
client
SLM
license
SLM version
References: None |
Problem Statement: There is no SLM License server upgrade procedure in Japanese. | Solution: SLM license server upgrade procedure in Japanese is attached.
Keywords: SLM license server
Japanese
References: None |
Problem Statement: This Knowledge Base article provides steps to troubleshoot the following error:
"Unspecified Error"
which may be encountered when opening the bpcmanager web page (http://localhost/bpcmanager) in Internet Explorer. | Solution: It is likely that the "Unspecified Error" error message is returned because the logged in user is trying to perform an operation he/she is not authorized to perform or the the Aspen Operations Domain Model (ODM) application has not been secured in the Aspen Framework (AFW) Security Manager. This would appear to be an AFW security issue. The error message "Unspecified Error" is possibly coming from the AFW component.
Here are some troubleshooting tips and things to check:
? It may be that the current logged in user account does not have permission to add roles to AFW Security Manager. Has access control been applied to the AFW system? In other words, did you configure security on the AFW Snap-in? If so, does the user account under which the ODM Security Administrator is launched have permission to modify AFW security? You need to add the user to the appropriate role in AFW, and then give that role "Open" permission to the AFW snap-in. After granting the permission, it still might not work immediately. This is because the AFW security cache on the client (ODM computer) is not up-to-date with the AFW server, which is due to the cache refresh rate being set to five minutes, by default. You can force a cache refresh by restarting the IIS service (iisreset) or you can increase the cache refresh frequency, if desired.
? Has Aspen ODM application been added to the secured applications list in the AFW Security Manager?
? Is the AFW Security Client Service running and what user account is it running under? This is a Windows service that should be installed on the ODM computer and generally speaking it should run under a domain based account that has full READ access to Active Directory Users and Computers.
? Are you able to launch (and connect to) the AFW Security Manager from the same computer where the ODM Security Administrator is launched?
? Is it possible that the web server (IIS) on the server where AFW Security is installed is down or disconnected from the network, for some reason?
? Is everything running on the same system or there are multiple computers involved? If multiple computers are involved, is it possible that the firewall settings on the ODM computer are restricting access to the AFW server?
? Have you tried launching the AFW Security Client Tool? This tool has a Test window (press the Advanced Options button) that allows you to test the interaction with AFW. Some important tests to try are Get Roles and Check Access Permissions. To activate the buttons, press Refresh Cache button first.
? Can you run the AFW diagnostic tool named "SSTest.hta"? This should be found in folder C:\Program Files\AspenTech\BPE. Did all tests pass?
? As a last resort, if possible, please try rebooting the ODM computer and the AFW server computer.
After you have tried all of the above troubleshooting steps and still have a problem, please contact AspenTech Support hotline at 888-996-7100 or via e-mail at [email protected]
Keywords: bpc manager
References: None |
Problem Statement: When trying to create an object that was previously removed from the ODM database, the Add method fails with a Fault exception stating that the name is duplicated.
This can be replicated by following the steps below:
? Make the call to the 'Add' method to add an object.
? The response says that the object was created successfully.
? After some time, call the 'Cancel' method to mark the object as removed.
? The response says that the object was removed successfully (call the GetList method to confirm).
? Then, use the Add method to try to create the same object again, as it doesn't exist in the system.
? The response is a Fault exception error stating that the name is duplicated.
How to correctly use the Add and Cancel (Delete) commands sent to the WebService to avoid the above-mentioned Fault exception stating that the name is duplicated? | Solution: The behavior described above with the Add and Cancel (Delete) commands sent to the WebService is as designed.
When an ODM object is created, it is given a BeginTime and an EndTime. When the WebService Add command is used to create an object, the Timestamp argument is used to set the BeginTime. The EndTime is set to DateTime.MaxTime which is 12/31/9999.
When the Cancel (Delete) command is sent to the WebService, the Timestamp argument is used as the Delete time. If the DeleteTime is greater than the BeginTime of the object, the object is not actually deleted. The EndTime is just set to the DeleteTime. The lifespan of the object is just shortened.
If you used the View dialogs available in the Bulkload program, you could change the 'Data Viewed At:' field at the top of the dialog to a time earlier than the time you deleted the GenericItem and you would see that it still existed.
If you want to delete the ODM object completely, you need to set the Timestamp value sent in the Cancel command to the .NET DateTime MinValue. The WebService checks to see if the Timestamp argument is equal to the DateTime.MinValue and substitutes the object's BeginTime.
When an ODM object is deleted, the record in the xxxDef is not deleted. The related record in the xxxHist table has its EndTime column set to the value of the BeginTime column. This indicates that the object has been deleted.
The .NET DateTime.MinValue is Jan 1, 0001 00:00:00. You can try using 0001-01-01T00:00:00 as the Timestamp value which should help overcome the fault exception error mentioned above.
Keywords:
References: None |
Problem Statement: Does AspenTech have any clients sending messages via Tibco to .Net framework? Does AspenTech provide an adapter for .NET framework? | Solution: At this time AspenTech does not have an adapter for .NET framework.
Going directly from an application such as BusinessWorks to a .NET based application is best done through the use of SOAP over HTTP messages (or web services).
You can find an example under <tibco_home>\bw\5.4\examples\activities\interop\dotNet
In aspenONE 2006.5 release there will be a fairly easy way to do this, but it is not currently available in version 2004.2 or 2006.0.
"TIBCO Enterprise Message Service" (Tibco EMS) is available in the 2006 release of Integration Infrastructure - it is not available in 2004.2.
Keywords: None
References: None |
Problem Statement: How to add a sub-class to a class definition from the web interface in ODM (Operations Domain Model)? | Solution: Most item types in ODM can be extended with meta-data by applying classes to them. This includes Classes themselves. One must take care not to confuse the intent of the "Classes" tab on the web interface and Advanced Editor interface. This tab is used to apply an instance of a class definition to an item. It is not used to modify a class definition. If you want to modify a class definition by adding an attribute, this should be done from the "Details" tab.
So, to add a sub-class to a class definition from the web interface, you would perform the following steps:
? Select a class to modify
? Navigate to the "Details" tab
? Add a new class attribute
? Set the type to "Class"
? Select a class by picking from the default value list.
? Press Save.
It is possible to apply an instance of a class to an item of type class by using the Classes tab. In this case, you are not affecting the definition of the class, but instead are applying meta-data to the class definition itself. Therefore, though it is rarely done, you can extend a class by applying a class to it, but remember, that in this case, you are not modifying the definition of the class, you are simply adding meta-data to it.
To further clarify, regarding classes, ODM supports two modes, "designing classes" and "applying classes". The intent of the Classes tab in both the web and advanced editor is to allow custom attribute values to be "applied" to ODM objects. This feature is available for most ODM object types including objects of type "Class". Thus, the web editor does indeed follow the "standard" meaning of the Classes tab, which is to apply an instance of a class to an ODM object. In other words, the Classes tab is not intended for "designing" the definition (structure) of a class, but instead is intended for "applying" class instances.
To summarise:
- In the ODM Configuration Editor and Advanced Editor the Classes tab creates meta data that describes the class.
- To create a complex class with sub-classes, the sub-class is defined as an attribute of the parent via the "Details" tab.
Keywords:
References: None |
Problem Statement: Are there any reserved characters in ODM (Aspen Operations Domain Model)? | Solution: The following special characters are reserved in ODM:
. dot/period
@ ampersand
" double quote
The above characters cannot be used when setting up class names for tag aliases.
Keywords:
References: None |
Problem Statement: Currently there is no single guide showing all the parts that need to be configured for S95 tag support to work correctly from the Aspen Tag Browser or within Web.21. | Solution: Attached to this solution are several documents showing examples of the required configuration. It is a prerequisite that the user understands configuration tools like the ODM Manager etc...
Notes: Aspen Tag Browser supports multiple Tag Alias classes if they are named as described in the instructions, but Web.21 Tag Search will only support one class called "TagAlias". All ODM configuration is case sensitive.
Step 1 ODM Setup for S95 Tag Alias Support.
Step 2 Aspen Tag Browser configuration.
Step 3 Web.21 Configuration.
Keywords:
References: None |
Problem Statement: The initial configuration of the Aspen BPC product requires opening the BPC Administrator in order to Create and Test the connection files that are used by the workspace for connecting to a database server. The BPC Administrator is accessed from:
Start | Programs | AspenTech | Operations Manager | Integration Infrastructure | BPC Administrator.
It is possible that when clicking on the 'database' button on the Aspen BPC Administrator, the resultant page is truncated at the bottom. In this case, the options of Encrypting, Creating, Testing and Viewing cannot be seen. | Solution: The problem is that the current 'Font' setting for the PC is set too large for the Gui to be completely seen.
To check your current font size Right-Click on your PC Desktop and select Properties. On the "Display Properties" screen select the Settings tab. Finally, click on the 'Advanced' button and look at the 'DPI setting'
A DPI setting of 'Large size(120 DPI)' will result in the problem described above.
Changing to a DPI setting of 'Normal size(96 DPI)' should resolve the problem.
Keywords:
References: None |
Problem Statement: If a class attribute definition value is set to default, and then no value is assigned to the attribute instance, the viewer (and the API), returns a NULL value, instead of the default.
How is the ClassAttributeDefinition Default value used in ODM? | Solution: Description of how the ClassAttributeDefinition Default value is used.
The DefaultValue is used in two ways:
1. If the ClassAttributeDefinition is marked as ReadOnly, the DefaultValue is always returned as the ClassAttributeValue when the Class has been applied to an ODM item. If the DefaultValue is changed, the ClassAttributeValue read from the ODM item will return the new DefaultValue.
2. If the ClassAttributeDefintion is NOT marked as ReadOnly, the DefaultValue is used to initialize the ClassAttribuateValue when the Class is initially applied to an ODM item. If the DefaultValue is blank when the Class is applied to an ODM item, the ClassAttributeValue is left as a NULL value. This initial ClassAttributeValue can be used or can be changed before the ODM item is saved.
Once a Read/Write ClassAttributeValue has been saved with an ODM item, adding or changing the DefalutValue defined on the ClassAttributeDefinition has no impact on the ClassAttributeValue associated with the ODM item.
If the DefaultValue on a ClassAttributeDefinition is not defined when a Class is applied to an ODM item and later the DefalutValue is defined, it will have no impact on the ClassAttributeValues associated with existing ODM items that have had the Class applied to them.
Keywords:
References: None |
Problem Statement: When Aspen Operations Domain Model (ODM) and Aspen Role Based Visualization (RBV) are installed on separate servers the following link:
http://RBVServerName/VisualizationNavigation/OpsNavBrowser.aspx
can generate this error:
"Could not load file or assembly AspenTech.BPC.Hierarchy_Interface" | Solution: This error is generated because the Aspen Business Process Components (BPC) are not installed on the RBV server. To resolve this error install the BPC client components on the RBV server. When you install BPC choose the 'Standard Install' option to install only the client components.
Keywords: None
References: None |
Problem Statement: This knowledge base article describes how to resolve the following error message which can occur when starting the Aspen Bulk Load utility:
This application has failed to start because MSVCRTD.DLL could not be found. Re-installing the application may fix this problem. | Solution: MSVCRTD.DLL is a Microsoft debugging dll on which many applications have dependencies. This file should reside in
C:\Windows\System32
Attached is a version of MSVCRTD.DLL from a v2004.2 system which can be copied to the path outlined above. This should resolve this particular error message.
The aspenONE installation places log files in the folder pointed to by the TEMP environment variable. You may be able to determine why this dll was not installed and if any other files are missing by examining these log files.
Keywords:
References: None |
Problem Statement: This Knowledge Base article shows how to filter object on inherited class using Aspen ODM WebService. | Solution: There are two ways of filtering Items via the WebService based on the ClassValues assigned to the items and the BaseClasses of those ClassValues.
1. The first one is to use the SupportsClass(int classDefinitionID) method.
This method takes the ID of the ClassDefinition that you are wanting to use in the filter.
Example:
BaseClass ID = 100000
DerivedClass ID = 100001
The Filter would be
SupportsClass(100000) = true
This first filter approach would require two WebService calls. The first would be to lookup the ID of the 'BaseClass'. This could be done once and the ID saved for later calls. The second call would be to return the list of Items that matched the Filter.
(In the Aspen ODM 2006.5 version there is a SupportsClass method that takes a Class Definition Name so it can be used in a single call.)
2. The second filter string would lookup a ClassAttribute that was on the base class.
The filter would be
ClassValues.ClassDefinition.AllClassAttributeDefinitions.!Find("XXXXX").ClassDefinition.Name= YYYYY
where the XXXXX is the name of a ClassAttribute on the base class and the YYYYY is the name of the base class.
This approach needs each class used by this filter to have at least one ClassAttribute defined in it.
Below please see examples using the data from the Bulkload file attached to this solution.
Class Definitions: UBPType
Class Attribute: Code_UBP
Assigned ID 100835
Class Definition: G-UBPSTOCKAGE_AVANT_SECHAGE
Class Attribute ShortName
Assigned ID 100806
Parent Class UBPType
Class Definition UBPSTOCKAGE_AVANT_SECHAGE
No Class Attribute Defined
Assigned ID 100815
Parent Class G-UBPSTOCKAGE_AVANT_SECHAGE
Filter string for UBPType Class
ClassValues.ClassDefinition.AllClassAttributeDefinitions.!Find("CODE_UBP").ClassDefinition.Name= UBPType
Filter string for G-UBPSTOCKAGE_AVANT_SECHAGEClass
ClassValues.ClassDefinition.AllClassAttributeDefinitions.!Find("ShortName").ClassDefinition.Name
= G-UBPSTOCKAGE_AVANT_SECHAGE
In the attached example this filter string does not work for the UBPSTOCKAGE_AVANT_SECHAGE class because it does not have any ClassAttributes defined on it.
SupportsClass filter examples for the three defined classes.
SupportsClass(100835) = true
SupportsClass(100806) = true
SupportsClass(100815) = true
Keywords: None
References: None |
Problem Statement: How do you configure an Aspen SQLplus web-based report to pass parameters in the URL address? | Solution: In order to pass parameters or variables to an Aspen SQLplus web-based report through the URL, a ProcedureDef record must be used. As an example, save the prodcedure below as a ProcedureDef record in Aspen InfoPlus.21 with the name of ShowTrendVals.
procedure ShowTrendVals(TagName Record, StartTime timestamp, EndTime timestamp)
select name, ip_trend_value, ip_trend_time from ip_analogdef where name = tagname
and ip_trend_time between starttime and endtime;
end;
After the ProcedureDef record is created open http://<webservername>/sqlplus in a browser. Configure a new report and be sure to create a SQL Procedure as the Section Type.
Be sure to check the box Enable Parameters.
Edit the SQL Procedure section to look similar to the following, making sure to use same parameter names listed in the ProcedureDef record in the Value field using the format of :parametername.
Save the Report as either a private or public report.
The URL that can be used to open the report will look like the following:
http://<webservername>/SQLplus/ReportResult.aspx?IsPublic=true&ReportName=ShowTrendVals&tagname=atcl101&starttime=11:00&endtime=12:00
The parameters involved in the URL are IsPublic, ReportName,tagname, starttime, and endtime. The IsPublic parameter will need to be set to true or false depending on how the report was saved (either as Public or Private). The ReportName parameter will reference the name of the report created using the procedure. Tagname, starttime, and endtime were the three parameters referenced in the ProcedureDef record. The order in which the parameters are referenced in the URL does not change the result of the report. All parameters are preceded by an & except for the first parameter listed in the URL which is preceded by a ?.
The report generated will look like the following:
Keywords: parameter
variable
URL
web
Web21
SQL
query
References: None |
Problem Statement: Aspen Licensing Center (ALC) unable to create log files after installing ALC upload toolkit. | Solution: There is a pre-requisite of checking that LServOpts environment variable is set in the License Server before log files will be generated. See solution: 126213
However, if after setting that and the problem still persists, checking that no log files are created in the designated folder in ALC configuration setup but instead in C:\Program Files\AspenTech\ALC\FailUploadFiles, it could be due to the company's security policy where for some reason it cannot use the default local administrator account setup on Aspen ALC Auto-upload schedule service
In this case, the User's login account has to be used instead. Go to services under Administrative management, Right click on the service Aspen ALC Auto-upload schedule service and go to "Properties".
Click on the "Stop" button to stop the service from running. Click on the "Log on" tab, and select Log on as "This account", choosing the user account where the ALC upload toolkit was installed on.
Fill up the user name and password and click on "Apply"
After that, click on the "Start" button to restart the service.
Check on file folder C:\Program Files\AspenTech\ALC\FailUploadFiles if the log files are now transferred to the designated log folders and transmitted to Aspen Licensing server via one of the modes which the user had configured in ALC upload toolkit.
Keywords: ALC, Aspen Licensing Center, Auto Upload toolkit, SLM, License server, Log files, Services, Auto Upload Schedule Service
References: None |
Problem Statement: This Knowledge Base article shows how to best integrate Aspen's Enterprise Integration Framework with Microsoft's BizTalk server. | Solution: Please download and review the attached document titled: BizTalk WSAdapter Setup. The second attachment, IWsAdapterServer.zip, contains a sample BizTalk project.
Keywords: Biz Talk
LOB Adapter
WS Adapter
WCF Web Service
References: None |
Problem Statement: This Knowledge Base article answers the following question: Does the Aspen Operations Domain Model (ODM) Web Service in aspenONE v2004.2 support the Bulkload functions? | Solution: The Web Service in 2004.2 does support the Bulkload functions.
The Bulkload Export method takes an Export Time and returns a boolean to indicate the export has been started. The Bulkload Export is processed as an asynchronous operation. You then need to call the BulkloadStatus method to monitor the export activity. When the BulkloadStatus indicates that the export has completed, call the GetBulkloadResults to get the exported xml file.
WebService Bulkload methods used for exporting:
bool BulkloadExport(DateTime exportTime)
BulkloadStatus GetBulkloadStatus()
BulkloadResults GetBulkloadResults()
Keywords: None
References: None |
Problem Statement: The Release Notes for Aspen Operations Domain Model (ODM) contain the statement:
A frequent request was the ability to have calculation support within the Operations Domain Model. This functionality has been added in this release and it allows the user to define calculations defined externally such as in Aspen Calc.
Unfortunately, neither the Release Notes nor the other ODM manuals give any specific details on how to do this. | Solution: This solution contains an attached Word document full of examples on how to set this up.
At this time, it appears that ODM, Aspen Calc and the user setting this up all need to be installed and logged into the same PC. The AspenTech Support group will investigate further and update this article as necessary.
Keywords:
References: None |
Problem Statement: This Knowledge Base article provides steps to resolve the following error message received when trying to install the 2006.0.1 patch for Aspen Operations Domain Model (ODM):
"{B3D3EDD3-FD24-46E1-BEDF-5A24173693A7} is not installed. ProductState returned -1" | Solution: Aspen ODM must be listed as a product in MS Windows Add/Remove product list. If it is not, then you might have gotten the ODM client version installed automatically with another product. As such, the error message is understandable as the ODM patch 2006.0.1 is a server patch. Please install the product using aspenONE DVD 1 (using Server Install option) and make sure you see ODM in Add/Remove Programs list.
NOTE: There are other AspenTech software products that may generate a similar error message during a patch install. Please always verify that the product in question is listed in Add/Remove product list.
Keywords: B3D3EDD3-FD24-46E1-BEDF-5A24173693A7
A741DBBF-0613-4FEB-8FAB-8B8965B86B7C
Product State returned -1
References: None |
Problem Statement: After a new installation, when starting the Aspen BPCManager, the following error appears
Server Error in '/BPCManager' Application.
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Access is denied: 'Aspentech.BPC.WebAdmin_Implementation'.
Source Error:
Line 256: <add assembly="System.EnterpriseServices, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
Line 257: <add assembly="System.Web.Mobile, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
Line 258: <add assembly="*"/>
Line 259: </assemblies>
Line 260:
Source File: c:\windows\microsoft.net\framework\v1.1.4322\Config\machine.config Line: 258
Assembly Load Trace: The following information can be helpful to determine why the assembly 'Aspentech.BPC.WebAdmin_Implementation' could not be loaded.
=== Pre-bind state information ===
LOG: DisplayName = Aspentech.BPC.WebAdmin_Implementation
(Partial)
LOG: Appbase = file:///C:/Program Files/AspenTech/BPCWebManager
LOG: Initial PrivatePath = bin
Calling assembly : (Unknown).
===
LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).
LOG: Post-policy reference: Aspentech.BPC.WebAdmin_Implementation
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/bpcmanager/61560122/83582605/Aspentech.BPC.WebAdmin_Implementation.DLL.
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/bpcmanager/61560122/83582605/Aspentech.BPC.WebAdmin_Implementation/Aspentech.BPC.WebAdmin_Implementation.DLL.
LOG: Attempting download of new URL file:///C:/Program Files/AspenTech/BPCWebManager/bin/Aspentech.BPC.WebAdmin_Implementation.DLL.
Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP | Solution: This kind of problem is usually very difficult to diagnose. It is usually a configuration issue 'only' seen when Microsoft's Sharepoint is installed on the same computer as the BPCManager. This is due to the fact that Sharepoint takes over some of the IIS functionality.
In this case we needed the 'WRITE' property set on the BPCManager virtual directory when run the first time. After accessing BPCManager for the first time, the 'write' property can be removed. IIS needed the proper permissions to access the BPCManager dlls initially, but did not have them, hence the error. The procedures to do this are :
? Open Internet Information Services
? Expand the Default Web Site (under Web Sites) and select BPCManager.
? Right-click on BPCManager, select 'Properties', and then the 'Virtual Directory' tab
? Select the "Write" checkbox and click on 'Apply Changes'
? Go back to the Default Web Site and Stop and then Restart the Default Web Site
? Close Internet Information Services and hopefully successfully now open BPCManager
? Select one of the components to see that the components are registered. Hierarchy is one of the better components to select!
? BPCManager should now display the Hierarchy Definition List Web Page.
? Close BPCManager and then re-open Internet Information Services
? Repeat the above steps but this time un-checking the 'write property
? Confirm that BPCManager still displays correctly
Keywords:
References: None |
Problem Statement: This Knowledge Base article answers the following question:
What is the check box called "Integration Authentication" on the Callback Definition tab in Aspen Integration Designer used for? | Solution: The Integration Authentication check box on the Callback Definition tab in Aspen Integration Designer has the following functionality:
Not having the integration authentication box checked keeps the default messaging security behavior; by checking the box you change the messaging behavior to have transport security. Transport security provides point to point security between endpoints (client and the service) using HTTPS and the service to be configured with SSL certificates. The default behavior doesn't require the configuration of SSL certificates of the service for authentication. If you would want to check the box, make sure both the service and the client are located in an intranet as the message will not go through any intermediate systems. If the message goes through an intermediary system, issues could arise as the intermediary system might not have the same security.
Keywords: None
References: None |
Problem Statement: Are there any consequences of changing the Security Identifier (SID) of a live machine running Aspen InfoPlus.21, Aspen Web.21, Tibco Business Works, and the Aspen InfoPlus.21 adapter? | Solution: When a computer is added to a domain, the PDC assigns a Security Identifier to it. Except for the SLM license server, our software mostly never cares about this. We sometimes have to change the SID when copying a Virtual Machine image for testing and once we get the VM back into the domain IP.21, Web.21, the IP. 21 Adapter and TIBCO work fine.
Keywords: None
References: None |
Problem Statement: Users may receive a message like the following when running tests in the aspenONE Diagnostics Tool:
Invalid settings for BPE Server webserver (PEGASUSBRIDGE). The 'http://PEGASUSBRIDGE/AspenTech/AFW/BPE/AfwServerInfo.asp' file could not be found on the server. The IIS virtual directory path defined in the IIS AspenTech properties must be set to its physical location.
Set correct 'WebServer' parameter using 'AFW Tools' utility. Or correct problem with IIS settings on BPE Server.
In the message above "PEGASUSBRIDGE" is the name of a server. What does "BPE" stand for in this context and what does this message mean? | Solution: "BPE" in the message above stands for "Aspen Business Process Explorer". This is a *different* product from Aspen Process Explorer. If one is not using Aspen Business Process Explorer then one may safely ignore this message. In this case it is just informational.
Aspen Business Process Explorer is a component of the Aspen Framework Server and is covered in the documentation for that product. The documentation is available on the AspenTech Support website.
Keywords: None
References: None |
Problem Statement: Why do I get "An error occurred on the server when processing the URL" when attempting to load Process Manual content?
When you try and load Process Manual content you get an error message: "An error occurred on the server when processing the URL. Please contact the system administrator." | Solution: The solution to resolve this issue is to enable Parent Paths on IIS Manager, which is disabled by Default.
1. Load IIS Manager.
2. Click on Sites
3. Click on AspenTechProMan
4. Click on ASP
5. Under Enable Parent Paths make sure it is says True.
6. Restart IIS Server.
Here is a screenshot to show the option enabled.
Keywords: Enable Parent Path on ISS
Parent Path
Process manual
Process manual error occurred
Enable Parent path on ASP
how do I enable parent path
References: None |
Problem Statement: This knowledge base article describes how to add a license feature to the license server using WLMAdmin in the event that it has been deleted. | Solution: There are two ways to add a license feature back to the SLM server.
Method 1 - Restart the license server service.
1. Go to 'Program Files\Common Files\Safenet Sentinel\Sentinel RMS License Manager\WinNT' or 'Program Files (x86)\Common Files\Safenet Sentinel\Sentinel RMS License Manager\WinNT' folder.
2. Double-click on the file 'loadls.exe'.
3. Select 'Remove'.
4. Double-click on the file 'loadls.exe' once more.
5. Select 'Add'.
6. Check WLMAdmin. The removed license feature should be there again.
Method 2 - Add feature via WLMAdmin
1. In WLMAdmin, right click on the license server (the one from which the license feature was removed).
2. Select: Add Feature | From a File | To Server |.
3. Browse to your 'lservrc' license file and select it.
4. What WLMAdmin will now do is read your 'lservrc' file and add in all the license features from that file to your license server/WLMAdmin. Since your 'lservrc' file will have the same features as what's listed in WLMAdmin (minus the removed feature), it will not be able to add the already existing license features (as shown in WLMAdmin) to itself. Therefore, you will receive an error message for each license feature that already exists in WLMAdim. The error will read as follows:
Error: The feature could not be added.
Click OK to accept the error. Once the process has gone through each license feature in the 'lservrc' file to add into WLMAdmin, you will see your 'missing' license feature back in the list of features for your license server.
Keywords: WLMAdmin
remove
add
feature
license
References: None |
Problem Statement: When commuting a license using SLMCommute, the confirmation message says the license was commuted successfully. But when the 'View commuted licenses button' is clicked, it shows there are no licenses commuted. | Solution: This problem may occur if the dll "strgxi2.dll" becomes unregistered. To re-register strgxi2.dll follow these steps.
1. Go to the Start menu, then go to Run. Type this command in the Open box:
regsvr32 /u "C:\Program Files\Common Files\Hyprotech\Shared\strgxi2.dll" or
regsvr32 /u "C:\Program Files (x86)\Common Files\Hyprotech\Shared\strgxi2.dll" (for 64 bit systems)
2. Click OK. You should then see a window confirming that unregistration succeeded. The go to the Start menu and then Run again and type:
regsvr32 "C:\Program Files\Common Files\Hyprotech\Shared\strgxi2.dll" or
regsvr32 "C:\Program Files (x86)\Common Files\Hyprotech\Shared\strgxi2.dll" (for 64 bit systems)
3. Click OK and you should see a message that confirms the registration succeeded.
You should now be able to commute and view the commuted license.
Keywords: problem commuting
check out
References: None |
Problem Statement: After installing the SLM license manager and license file, when running WLMAdmin, there are no servers under defined servers or subnet servers. | Solution: Ensure the USB dongle is recognized if using a license file locked to a dongle. To check this, run the SLM Configuration Wizard, and click the CONFIG button. The first line of the configuration settings should say 'Sentinel Hardlock'. If it does not, unplug the USB dongle and use solution document 115262 to reload the dongle drivers.
Once the hardlock dongle is recognized, remove and reload the SLM sentinel service using the loadls.exe in the Program Files\Common Files\Safenet Sentinel\Sentinel RMS License Manager\WinNT or Program Files (x86)\Common Files\Safenet Sentinel\Sentinel RMS License Manager\WinNT folder.
Define the SLM server through WLMAdmin. Run WLMAdmin.exe, and go to EDIT - Defined server list. Type in the full computer name when defining a defined server (i.e. sentinel.corp.mycompany.com).....not just the short name, and then click ADD, then click the OK button.
Then, go back to the EDIT menu, and select PREFERENCES.
Check these boxes:
? Discover Subnet servers on startup
? Discover Defined servers on startup
Save these preferences to a file.
Exit out of WLMAdmin, and then run WLMAdmin again.
The defined server will still be listed, and when you open the plus sign next to the defined server, all licenses should show up.
Keywords: Sentinel
SLM error
Defined servers
Subnet servers
WLMAdmin
References: None |
Problem Statement: What is the turnaround time for receiving an Aspen Tech license file? | Solution: Our Distribution department handles three major types of orders:
1. New orders from either new clients or existing clients that require shipment of software and license keys. These orders normally take 10-14 days.
2. Upgrade requests for the newer versions of existing product for existing clients, have a 10-14 day turnaround commitment.
3. Re-host requests which are changes to an existing license key file due to new hardware or where a license key file has been misplaced. In general these requests are accompanied by some sort of down-time on the customer's end, so we at AspenTech treat such requests very seriously. Our committed turnaround on such requests is 1 business day.
Should the customer have any sort of time-critical need for a quicker turnaround, then the order can be given a higher priority by contacting Support or the Sales representative. At certain times of the year (quarter- or year-end close) it maybe difficult to process all orders in a time frame that we would like, but we do try to prioritize the critical needs first.
If the customer is in a critical position and is in immediate need, then when submitting the key request the customer should also request a 2 week temporary license key. This will prevent any significant downtime.
KeyWords
turn-around, turn around, license key, SLM, product upgrades, temporary license
Keywords: None
References: None |
Problem Statement: Unable to run any AspenONE program after successful product installation.
Also, selecting Config from the first screen of SLM Configuration Wizard opens a blank window. | Solution: 1) Using an administrative account, login to the system
2) Select Start | Run and type in cmd.
3) Within the DOS window change the default folder to:
Program Files\Common Files\Hyprotech\Shared or Program Files (x86)\Common Files\Hyprotech\Shared
4) Within the DOS window enter the command: regsvr32 /u strgxi2.dll then press Enter
5) Repeat the above command without the u option: regsvr32 strgxi2.dll then press Enter
6) Close the DOS window and run the application
Keywords: SLM
AspenONE
References: None |
Problem Statement: When opening the Properties -> License Status menu in the Aspen InfoPlus.21 Administrator program, you may see a message indicating License Denied:
Clicking on the details button shows a screen similar to: | Solution: The issue is that in a new installation of Aspen InfoPlus 21 the number of InfoPlus.21 Points is automatically set to 66,000; however, your InfoPlus.21 licensed points key is set to a lower value. There are two possible reasons for this.
Scenario 1: If this is a standalone license key, it defaults to 1 user key, which translates to 4000 InfoPlus.21 Points, and this may be too low for the number of InfoPlus.21 Points you have on the system.
Scenario 2: If this is a token based license key, the problem could be not enough tokens for the number of applications and InfoPlus.21 Points needed.
In either of these scenarios you'll need to:
Stop Aspen InfoPlus.21, open the Aspen InfoPlus.21 Administrator program, open the database, and select the Set Point Count menu
to reduce the number of points being checked out from 66,000 to the number of points licensed for Aspen InfoPlus.21.
-Or-
Request that the InfoPlus 21 Points key be increased in the license.
Contact AspenTech's Customer Care group by following the link Upgrades, Media & Licenses at: http://support.aspentech.com to request a new license.
Keywords: license, error, check out, SLM_InfoPlus21_Points
References: None |
Problem Statement: How to set up a usage log file manually on a License Server machine | Solution: Go to:
1. My computer -> Properties -> Advanced -> Environment Variables -> OK or through Control Panel-> System-> Properties-> Advanced-> Environment Variables.
2. On the server pc, please press New in the 'System variables'.
Note: The System variables 'LServOpts' should be set in the System variables
and not on the user variable accounts.
3. Fill up Name and Value as below.
The variable value is -l "C:\Program Files\AspenTech\SLMServerLogs\lserv.log" -z 2m -lfe 2 or -l "C:\Program Files (x86)\AspenTech\SLMServerLogs\lserv.log" -z 2m -lfe 2
4. Click OK.
5. Create a folder path named C:\Program Files\AspenTech\SLMServerLogs\ or C:\Program Files (x86)\AspenTech\SLMServerLogs\
6. Run the software. (e.g. Aspen HYSYS or Aspen Plus)
7. A log file will be created in C:\Program Files\AspenTech\SLMServerLogs\ folder.
Note: In V7.2 version onwards, the Usage logs will be automatically set up on the system variables when installing the SLM server.
Keywords: SLM
License Manager
LServOpts
Environment Variables
Usage Log
Report Log
Server setup
References: None |
Problem Statement: From the Internet or Intranet Process Manual, some spreadsheets are referred to in the Drying Technical Area, Volume 4 "Rotary Drying", Part 4, Section 4.5 "Operation of spreadsheets ROTDRY and ROTBAS".
These are;
? ROTBAS Scoping design procedure for a cascading rotary dryer
? ROTDRY Slightly expanded and refined version of ROTBAS
? HAMBLCON Heat and mass balances for continuous dryers
? BURNER Calculations on a direct-fired heater for a dryer
? PNEUCONV Scoping design procedure for a pneumatic conveying (flash) dryer
These spreadsheets were not converted to programs within the Process Tools suite, but the Excel spreadsheets can be downloaded from this solution. They were originally issued on the SPS Summer 1992 CD. | Solution: There are five spreadsheets;
1. ROTDRY
The spreadsheet will carry out scoping design calculations for both concurrent and countercurrent cascading rotary dryers. In its present form it is restricted to adiabatic dryers with water being the evaporating solvent and air the drying medium. The method is described in Section 4.3 of DRY 4.4 (Drying Manual Volume 4 Part 4, Rotary Drying) and Sections 4.5.3 and 4.5.4 shown worked examples.
It requires as input
? the solids feed rate, solids inlet and outlet moisture, solids inlet and outlet temperature;
? inlet and outlet temperature of gas and inlet humidity of gas;
? parameters for the characteristic drying curve of the material (i.e. the critical and equilibrium moisture contents and three constants which define the shape of the drying curve) as well as mean particle size, particle density, bulk density and heat capacity of dry solids;
? the absolute pressure in the dryer;
? parameters for a transport model of the material through the dryer (defaults and range of variation provided).
It will calculate
? the drying gas feed rate and outlet humidity;
? the gas temperature, humidity, solids temperature, drying rate and moisture content profiles along the length of the dryer;
? the required dimensions of the dryer (length and diameter) to achieve the drying of the particular feed under consideration, the drum holdup and the type of drum (i.e. under loaded, design-loaded, overloaded).
At a first stage the calculations are carried out with the default values for flight geometry. The spreadsheet will also calculate drum length and holdup for user-specified values for the flight geometry and number of lifting flights.
2. ROTBAS
ROTBAS requires exactly the same input as ROTDRY. The method is described in Section 4.4 of DRY 4.4 (Drying Manual Volume 4 Part 4, Rotary Drying).
It will calculate:-
? the drying gas feed rate and outlet humidity;
? the gas temperature, humidity, solids temperature, drying rate and moisture content profiles along the length of the dryer;
? the required dimensions of a design loaded dryer (length and diameter) to achieve the drying of the particular feed under consideration.
Differences between ROTBAS and ROTDRY:
In ROTBAS:
? The calculations are carried out only with the default values for flight geometry and the dryer is assumed to be design loaded. There is no provision for user-specified values for flight geometry.
? For the case of concurrent dryers the adiabatic saturation temperature of the air after the initial induction period is taken as constant. For the case of countercurrent dryers it is calculated at the following three positions: a) gas exit, b) end of induction period and c) gas inlet. Then during the period of hindered drying it is considered to vary linearly with X between the values at b and c above.
? The heat transfer coefficient and the particle velocity due to air drag are taken as constant throughout the dryer.
3. HAMBLCON
The spreadsheet will solve the mass and heat balance equations for a continuous dryer for any permissible combination of 2 unknown parameters out of the 11 which are involved in these two equations.
It requires as input:-
? at least 4 of the following 5 variables:
o inlet temperature of gas,
o outlet temperature of gas,
o inlet temperature of solids,
o outlet temperature of solids,
o heat losses through the walls;
? 4 or 5 of the following 6 variables:
o gas feed rate,
o solids feed rate,
o solids inlet moisture,
o solids outlet moisture,
o inlet gas humidity,
o outlet gas humidity;
? ambient conditions (defaults provided);
? specific heat capacities of the dry solids, dry gas, solvent (as liquid), solvent (as vapour) and heat of vaporization of solvent at 0C (defaults provided for the air-water system);
? molecular weights of dry gas and solvent (defaults provided for the air-water system).
It will calculate:-
? the two unknown variables;
? the mass flow rates of the four streams on a dry and wet basis, moisture contents and humidities on a dry and wet basis, gas densities and volumetric flow rates at local conditions;
? the evaporation rate, energy used for evaporation in kW and the heat losses in kW;
? the energy input to the drying air in the heater and the percentage of this energy used for evaporation, used to heat the product, lost with the outlet air and lost through the walls. For these calculations an indirect heater is assumed.
4. BURNER
The spreadsheet will carry out combustion calculations for a direct-fired heater with a variety of fuels.
It requires as input:-
? the fuel being used (data for common fuels are supplied);
? estimates of % excess air accompanying the stoichiometric air and heat losses (defaults provided);
? ambient conditions (defaults provided);
? the temperature and mass flowrate of gas required for the dryer downstream
It will calculate:-
? the composition (by mass) of the gas entering the dryer
? the mass flow rates of fuel, primary combustion air and secondary air
? the inlet air humidity for the dryer
5. PNEUCONV
The spreadsheet will carry out scoping design and performance calculations for a pneumatic conveying dryer system. The method is described in Sections 3 and 4 of DRY 6.4 (Drying Manual Volume 6 Part 4, Pneumatic Conveying Drying). The underlying theory is covered in Section 5.5 of DRY 6.3.
The program requires as input:-
? the gas and solids mass flowrates (or equivalent data);
? the gas and solids inlet temperatures;
? size, density and related data for the solids;
? the inlet moisture content;
? drying kinetics data for hindered (falling-rate) drying calculations;
? outlet moisture content (design mode) or duct length (performance mode).
It will calculate:-
? the length of the dryer (design mode);
? the outlet moisture content (performance mode);
? the heat and mass balance over the dryer;
? outlet humidity, gas and solids temperatures.
Keywords: Spreadsheets, Rotdry, Burner, Hamblcon, Pneuconv, Rotbas
References: None |
Problem Statement: The SLM Commute Tool does not work after upgrading the license server.
The license is generating several error messages that it cannot find the license.
The error 6 is related to the license STRGXI2.dll version | Solution: This knowledge base explains how to implement a work around specific to upgrading SLM Server that caused the SLM Commute Tool not to work.
1. First ensure that SLM Server 8.2 or 8.4 is the correct version installed for the supported operating systems and not 8.1 versions because SLM Server 8.1 is ONLY for Windows Vista.
2. To verify the version, go to C:\Program Files\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT. Highlight lservrt.exe to confirm the correct version installed.
Keywords: None
References: None |
Problem Statement: If you are using version 7.2 of the SLM Server, you may encounter a scenarios in which in the Windows Task Manager shows the process Lservnt.exe (this is the process that hosts the license) using up 100% of the CPU usage. The log file keeps reaching the size limit. As a result, the SLM Sentinel service keeps stopping.
This is a known bug regarding the Sentinel Server software versions. 7.1.1 and .7.2.1 and the error.log file it?s filled with the following error message. See solution #124477 on how create the error.log.
VLSEeventhandler
VLSEeventhandler
VLSEeventhandler
VLSEeventhandler
VLSEeventhandler | Solution: This Knowledge Base Article describes the work around in preventing the SLM Service from stopping. The solution is to delete the - f option in the lservopt environment variable and this will disable the error logging.
The picture below shows the location where to change the LServOpts environment variable:
1. Right-click on "My Computer" icon from your Desktop, and then select properties.
2. Click the Advanced tab; then click ?Environment Variables? button
3. Double-click on the environment variable called LServOpts, to modify the value of the variable.
4. Delete the ?f parameter:
eg.
-l c:\serv.log -z 2m -lfe 2 -f (with the feature turned on)
-l c:\serv.log -z 2m -lfe 2 ( without the feature)
5. Stop and then re-start the Sentinel server service and delete the error log file in this example ?serv.log? located at the C drive. To stop the service, go to 'C:\Program Files\Common Files\SentinelLM RMS Manager\WINNT' and double-click on loadls.exe. Select 'Remove' to stop the Sentinel server service. Then, double-click on loadls.exe again, and then select 'Add' to re-start the Sentinel server service.
KeyWords
Lservnt.exe, LServOpts, sentinel, SLM, license manager, CPU, 100
Keywords: None
References: None |
Problem Statement: Part of the pre-requisite software for the Process Manual is the installation of a database to record user information. The Process Manual supports the full version of Microsoft SQL Server or the cut-down database engine MSDE, where MSDE 2000 SP3 is included on the installation DVD.
In the AES2004InstallationGuide.pdf, page 84 - 89 list the detailed notes required for a Process Manual Installation. However, mention is made that MSDE SP3 is available on the installation DVD but no mention of the location is given. | Solution: MSDE SP3 may be installed from either;
The Aspen DVD disc 1, from the folder Atlanta2004DVD1\core\MSDE2KSP3
The Microsoft website at http://www.microsoft.com/downloads/details.aspx?FamilyID=413744D1-A0BC-479F-BAFA-E4B278EB9147&displaylang=en
KeyWords
MSDE, Process Manual
Keywords: None
References: None |
Problem Statement: This knowledge base article describes how to force the release of commuted licenses that have expired, but have not been automatically returned to the license pool. | Solution: From the license server, there are two ways to force the return of expired commuted licenses:
1. Restart the license manager service. This can be done by double-clicking on the file 'Program Files\Common Files\Safenet Sentinel\Sentinel RMS License Manager\WinNT\loadls.exe' or 'Program Files (x86)\Common Files\Safenet Sentinel\Sentinel RMS License Manager\WinNT\loadls.exe' and selecting REMOVE. Double-click on the 'loadls.exe' file once more and this time, select ADD. Check the license server (using WLMAdmin) and see if the 'stuck' license(s) have been 'released'. If they have not, refer to #2.
2. Run the two utilities described in knowledge base article 117723. Send the information into AspenTech Technical Support. The AspenTech support team will issue you a utility to clear off the unreleased license(s) from the server.
Keywords: commute
expire
stuck
release
license server
WlmAdmin
References: None |
Problem Statement: Within the Aspen Process Manual a number of registry keys may be set that allow tracing logs to be generated to help troubleshoot installation issues with the Aspen Process Manual. These log files record the history of the files opened and calls made to the security system, for example.
Sending these log files to Support may aid troubleshooting. | Solution: With Regedit, the keys given below may be set:
Tracing BrowseSupport (authentication) issues:
[HKEY_LOCAL_MACHINE\SOFTWARE\AspenTech\Aspen Process Manual\2004\BrowseSupport]
Document server:
[HKEY_LOCAL_MACHINE\SOFTWARE\AspenTech\Aspen Process Manual\2004\BrowseServer]
SLM authentication service:
[HKEY_LOCAL_MACHINE\SOFTWARE\AspenTech\Aspen Process Manual\2004\ProManAuthentication]
For each key make the string entry:
Tracelog = <filename>[,clear]
where;
<filename> is file or a complete path and file name for the tracelog file. The log files will be saved to the BrowseServer directory where the Process Manual has been installed if file has been used.
[,clear] if present will delete the tracelog file each time a component is created (i.e. web server restarted). This does not need to be set, but if not set it could mean that the log files become quite large in time with usage.
So for example;
TraceLog=file,clear
will create a new tracefile log each time the web server is started, and will store it in the BrowseServer directory where the Aspen Process Manual is installed.
TraceLog=C:\Trace History\trace.log
will create a log file called trace.log in the directory "C:\Trace History" that will append data each time the Aspen Process Manual is accessed. With time this trace file could become large.
The attached Word document shows screen shots from the regedit program for two of the above registry keys.
KeyWords
Log files, Installation, debugging, Trace file
Keywords: None
References: None |
Problem Statement: Can I use Aspen SLM-enabled products with a Windows / Citrix Terminal Server? | Solution: AspenTech products can be run from Citrix or a terminal server using network licensing only (with the Aspen SLM Network License Server installed on the same or another non-terminal server machine); however AspenTech does not support its products on a Citrix or terminal server with standalone license files unless customer has purchased unlimited licenses.
Keywords: Citrix
Terminal server
References: None |
Problem Statement: Can I have my reservation file with a name different from the default name of 'LSRESERV' and/or reside in a folder other than the default 'C:\Program Files\Common Files\Safenet Sentinel\Sentinel RMS License Manager\WinNT' folder? | Solution: You will need to create a system Environment Variable that points to the full path of the reservation file. For example, if you have a reservation file called 'reservations' in the directory 'C:\SLM Stuff', you'd have to setup the following system Environment Variable:
Variable Name: LSRESERV
Variable Value: "C:\SLM Stuff\reservation"
Even if your reservation file is in the default 'WinNT' folder but has a file name other than 'LSRESERV', you will still need to set the Variable Value to point to the full path of the reservation file.
You will need to restart the computer after setting the environment variable if this is the initial creation. You will need to restart the Sentinel RMS License service if you have made an update to an existing entry.
Keywords: reservation file
directory
folder
Environment Variable
References: None |
Problem Statement: Rather than use the virtual directory, could I run the Process Manual from a virtual site? | Solution: We would recommend a virtual directory, but you could set up an automatic redirection from the root site. To do this, create a file "default.htm" in the root site, containing something like:
<html>
<head>
<title>Process Manual</title>
<meta http-equiv="refresh" content="0;URL=http://NAME/proman/proman.asp">
</head>
<body leftmargin=0 rightmargin=0 topmargin=0 bottommargin=0>
<p style="padding:20;background-color:#006699;color:white;font-family:Arial, sans-serif;font-size:20;font-weight:bold;">Internet Process Manual</p> <p style="margin-left:8;margin-right:8;margin-top:8;margin-bottom:8;">You are being redirected to the main site entry point.</p> <p style="margin-left:8;margin-right:8;margin-top:8;margin-bottom:8;">If the redirection does not work, please click on <a href="http://NAME/proman/proman.asp">this link</a>.</p> <hr color=#006699 size=8>
</body>
</html>
Now users going to the default site should be automatically re-directed to the virtual directory.
KeyWords
Process Manual, intranet, virtual, site, directory, root
Keywords: None
References: None |
Problem Statement: We have a network license and the user gets "Error 17. No servers responded to the client broadcast." What do we do? | Solution: 'Error 17' is accompanied by 'Error 18. No such feature is recognized by the server'. Generally this occurs when the license file is not being read properly by the license server software.
Troubleshooting steps:
1. On the server machine, make sure the license file is in the right place ('C:\Program Files\Common Files\Sentinel RMS License Manager\WinNT' or 'C:\Program Files (x86)\Common Files\Sentinel RMS License Manager\WinNT') and that it is named correctly ('LSERVRC' - no file name extension. This is very important.)
2. From the 'WinNT' folder, run the file 'loadls.exe' and select Remove. Run 'loadls.exe' again and select Add. This effectively stops and restarts the license server service.
3. Run WLMAdmin.exe on the server (found in the folder 'C:\Program Files\Common Files\Hyprotech\SLM Admin Tools' or 'C:\Program Files(x86)\Common Files\Hyprotech\SLM Admin Tools'). When you run this program, double-click on the 'Subnet Servers' to search on your sub-network for license servers that are currently running and see if the license server is showing the correct license file.
4. If the licensed features are not listed, check that you have the correct USB dongle on the computer. If you do have the right USB dongle key on the computer, make sure you have the correct license file. If the license file is showing up when you run WLMAdmin on the server, then try running WLMAdmin on the workstation.
If the license features are not listed in the WLMAdmin tool then check the LSHOST environment variable and verify the correct IP Address or computer name of the license server is listed.
KeyWords
network license, Error 17, Error 18, network Error 17
Keywords: None
References: None |
Problem Statement: Why am I unable to view the Aspen Process Manual web browser page? | Solution: If the Aspen Process Manual page or the Process Manual Administrator page will not open and if a repair installation did not resolve the issue, check the following settings:
1) Check to see if the correct Internet Information Services (IIS) features were installed:
a. Open Control Panel > Programs and Features > Turn Windows features on or off.
b. Expand Internet Information Services and make sure all features under World Wide Web Services are checked.
c. Open the Process Manual Administrator page. If it does not open, go to Step 2.
2) Register the Process Manual dll files:
a. Go to Start > All Programs > Accessories and right-click Command Prompt and select Run as Administrator from the context menu.
b. Navigate to the C:\Program Files (x86)\AspenTech\Aspen Process Manuals V8.0\BrowseServer folder.
i. Type cd “C:\Program Files (x86)\AspenTech\Aspen Process Manuals V8.0\BrowseServer” and press Enter.
c. Type regsvr32 BrowseServer03.dll and press Enter.
d. Type regsvr32 browsesupport04.dll and press Enter.
e. Type regsvr32 LiveEqn02.dll and press Enter.
f. Type regsvr32 promanstruct.dll and press Enter.
g. Type regsvr32 BrowseHelp.dll and press Enter.
h. Open the Process Manual Administrator page. If it does not open, go to Step 3.
3) Check the settings in the Internet Information Services (IIS) Manager.
a. Verify that the Process Manual website was created.
i. Under the Connections panel, expand the machine name and navigate to Sites > Default Web Site > AspenTech and verify that the ProMan site is there and all the folders within the ProMan site.
ii. If the ProMan site is not there, then Aspen Process Manual will need to be uninstalled and reinstalled.
b. Check the ASP Tool settings.
i. Under the Connections panel, click the machine name.
ii. In the middle panel, double click the ASP tool.
iii. Make sure the setting Enable Parent Paths is set to True.
c. Check the Application Pools settings.
i. Under the Connections panel, expand the machine name and click on Application Pools.
ii. In the Applications Pools, verify that AspenAppPool is on the list.
iii. Make sure that the AspenAppPool has the status of Started.
1. If not, right-click AspenAppPool and select Start from the context menu.
iv. Right-click AspenAppPool and select Advanced Settings from the context menu.
1. Set Enable 32-Bit Applications to True. Click OK.
d. Open the Process Manual Administrator page.
If none of the above steps resolved the issue, please call AspenTech Support at 1-888-996-7100, select options 2,1.
Keywords: Process Manual
References: None |
Problem Statement: When using the start and end time functions in Aspen IP.21 Process Browser's SQLplus reporting option, an SQL Procedure does not seem to take into account the start and end times that are dictated by the report parameters. This causes the report to not output the correct information. | Solution: Since SQLplus reporting is an older feature of Aspen IP.21 Process Browser, the new contents of Internet Explorer does not process inputs correctly unless compatibility mode is turned on. To display the SQLplus reports that are desired, click the ALT key on the keyboard and select Tools and Compatibility View settings. Add the location of the Web server onto the list of websites to display in compatibility view. Reloading the Aspen IP.21 Process Browser page in a new tab should fix the problem.
Keywords: SQLplus reporting
timestamps
compatibility view
References: None |
Problem Statement: After running the Aspen Properties Database Configuration Tester, step 3 indicates that it is missing the config.aem.
Normally, running the Aspen Properties Database Configuration Tester can re-create the config.aem, but V8.0 install no longer require MS SQL Server as pre-requisite installation. Therefore, the Aspen Properties Database Configuration Tester will not create or re-create the config.aem if no MS SQL Server is installed. | Solution: This knowledge base describe the process of restoring the database when the Aspen Properties Database Configuration Tester result is "..missing the config.aem" Please follow these steps to create the config.aem and restore the database:
1. Install the Microsoft SQL 2008 Server, it is available from AES DVD \aspenONE_V8.0\aspenONEV8.0DVD1\3rd Party Redistributables folder. Then check to make sure that the SQL (SQLEXPRESS) service is started.
2. Launch the Aspen Properties Database Configuration Tester and click Start button from:
a. Start | All Program | AspenTech | Process Modeling V8.0 | Aspen Properties
b. Then go to C:\ProgramData\AspenTech\APED V8.0\Config.aem or
C:\ProgramData\AspenTech\APED V8.0\<username>\Config.aem to confirm that it is missing.
3. Next, launch the Aspen Properties Database Manager.
Start | All Program | AspenTech | Process Modeling V8.0 | Aspen Properties
a. Right click on the Aspen Physical Properties Database V8.0 | All Tasks | Restore Database
b. Enter the username: useraped2 and password Aproperty88#
c. Then restore the databases one at a time. The three Database Names are:
NISTV80, FACTV80, and APV80
d. Click Browse button and go to C:\ProgramData\AspenTech\APED V8.0\NISTV80
Note: After restoring the first database, config.aem will be created.
e. Go back to step 4a and restore FACTV80 next and one more time for APV80
7. Finally, open the Aspen Product to test.
Keywords: Aspen Properties Database V8.0
References: None |
Problem Statement: This knowledge base article describes how to resolve "error 77" that may occur when attempting to commute a license. When this error occurs, it typically occurs when you attempt to commute a license after returning a license to the pool has failed. | Solution: This problem normally occurs when the commute pool needs to be cleaned. Follow these steps to clear the error.
1. Restart the SLM license service. This sometimes clears the error and allows commuting from the affecting computer.
2. If restarting the service does not resolve the problem contact AspenTech support to request that the commute license file be cleaned.
Keywords: commute
license
SLM
77
error 77
References: None |
Problem Statement: How do I find a dongle ID number? | Solution: The dongle number can be checked in three ways:
1. Check the CD received from AspenTech which consists of the Order Number, System Name and the Dongle Number:
2. Check the Dongle as the side of the dongle consists of a sticker which shows the dongle number :
3. Check the License file i.e. the .SLF file > open it with Notepad > on the first line check KEY SERIAL NUMBER: (i.e. your dongle number):
KeyWords
Dongle, Identify dongle, detect, dongle number
Keywords: None
References: None |
Problem Statement: When an AspenTech product application is started several temporary dll's may be created on the computer desktop:
lsprst7.dll
lsprst7.tgz
nsprs.dll
nsprs.tgz
ssprs.dll
ssprs.tgz
sysprs7.dll
sysprs7.tgz
This knowledge base article describes why these files are created and why are they not deleted when the AspenTech application is closed. They are recreated the next time the AspenTech product is run. | Solution: This is usually the result of not having full administrative rights on the local PC when the installation was performed. It can also be caused when a user has had the administrative rights reduced to rights of a restricted user.
These files are temporary files created by the SLM (Software License Manager). They are created by the "foundation" security code written by Safenet.
The default creation location for these files is the "C:\WINDOWS\system32" directory. They are normally created in this folder and will stay there as long as the AspenTech application is running.
The reason why these files may show up in different locations (such as the Desktop) is if an Administrator takes away local administrator rights and replaces it with restricted-users accounts on the machine, the restriction will only allow Sentinel RMS License Manager to write these files into their personal folders or another location it finds that the user can write to.
How to fix the problem:
1. Delete the temporary files from your desktop. If any of the files below exist on your machine, delete them as well:
C:\WINDOWS\SYSTEM32\SYSPRS7.DLL
C:\WINDOWS\SYSTEM32\SYSPRS7.TGZ
C:\WINDOWS\SYSTEM32\LSPRST7.DLL
C:\WINDOWS\SYSTEM32\LSPRST7.TGZ
C:\WINDOWS\SYSTEM32\CLAUTH1.DLL
C:\WINDOWS\SYSTEM32\CLAUTH2.DLL
C:\WINDOWS\SYSTEM32\SSPRS.DLL
C:\WINDOWS\SYSTEM32\SSPRS.TGZ
2. Give back Full Control permissions (Full control, Modify, read & execute, list folder contents, and write) to the user for the following directories:
a. C:\WINDOWS\system32 (all sub-folders and files)
b. C:\Program Files\Aspentech or C:\Program Files (x86)\Aspentech (all sub-folders and files)
3. Go into the registry (using Regedit) and make sure that:
a. The permissions have not changed on HKLM\SOFTWARE\Hyprotech or HKLM\Software\Wow6432Node\Hyprotech. This folder and all subkeys should have the permissions of Full Control and Read.
b. Check to make sure that the PATH has not changed for the location of the temporary file creation. The path is stored under HKLM\SOFTWARE\Hyprotech\SentinelLM\CurrentVersion\Local or HKLM\SOFTWARE\WOW6432Node\SentinelLM\CurrentVersion\Local. The FilePath should read C:\WINDOWS\system32. If it does not point to that, then manually change it to reflect C:\WINDOWS\system32.
Note: If it is undesirable to give full control permissions to the c:\windows\system32 folder, what you might want to consider, is changing the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Hyprotech\SentinelLM\CurrentVersion\Local or HKLM\SOFTWARE\WOW6432Node\SentinelLM\CurrentVersion\Local, to a path on the user?s hard drive that will allow the creation of these files, such as c:\temp.
If these above suggestions do not work, then try the below steps:
1. Delete the following registry entries:
HKLM\SOFTWARE\Hyprdtech\ or HKLM\Software\Wow6432Node\Hyprotech\
HKLM\SOFTWARE\ntpad
HKLM\SOFTWARE\CLSYSTEM
2. Login as an Administrator.
3. Save the attached file (vregtool.exe) to your machine. You can also download the vregtool.zip file and extract it out to your PC.
4. Run the vregtool.exe file from a command prompt (MS-DOS window: Start - Run - cmd) and then by changing directories to where you saved the vregtool.exe file.
Once in the correct directory location, type VREGTOOL and hit enter. You will not see anything happen when this tool runs. When it is complete, exit the MS-DOS prompt.
5. Run the AspenTech product while still logged in as an Administrator, then close out of the AspenTech product.
6. Logout of the Administrator account, and then log back in as your normal user account.
7. Run your AspenTech product again. The temporary files will no longer be created on the desktop.
Keywords: slm
license manager
temporary
desktop
files
dll
tgz
References: None |
Problem Statement: 能否使特定用户禁止使用commute功能？ | Solution: 到SLM Server 8.2版本,我们不支持对特定用户限制commute功能。
但是我们可以使用group reservation file，可以赋予特定的用户或计算机一定的token/单元。此功能可以适用于普通网络许可证的请求以及commute请求。
Keywords: Commute
SLM Server
限制
CN-
References: None |
Problem Statement: If you need to change your MTU setting so that you can use the SLM over VPN then you will be required first to change the MTU at the client side | Solution: · Open a command line window as an Administrator (Right click on All Programs > Accessories > Command Prompt and select Run as administrator)
· Type the command netsh and wait for prompt
· Type the command interface and wait for prompt
· Type the command ipv4 and wait for prompt
· Type the command set subinterface "Local Area Connection" mtu=1500 store=persistent
Keywords: Change MTU setting
SLM over VPN
set MTU
Windows 7 MTU
Windows Vista MTU
MTU
SLM
References: None |
Problem Statement: This happens with SLM 8.2 Server from V7.2 installer disc. After system reboot sometimes license are available and sometimes they are not. License reload resolves the problem. | Solution: Here is what needs to be done so the problem will not occur. Before system shutdown, make sure that SLM 8.2 license service is shut down gracefully, then reboot.
To shutdown SLM 8.2 license server service gracefully browse to:
Program Files\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT or Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT
folder and double click on loadls.exe and select Remove.
This will allow you to reboot and everything should work as expected.
Keywords: SLM Server 8.2, License, Missing, Missing License
References: None |
Problem Statement: Which firewall ports are required for submitting software usage logs via the Auto Upload Tool (AUT)? | Solution: The Auto Upload Tool enables automatic upload of software usage logs to AspenTech using one of the following protocols and required ports:
Log Transmission Protocol
Required Open Port
HTTPS
443
Secure FTP (SFTP)
22
Email
25 (or SMTP server specific port)
In order for the AUT to work with one of the selected protocols, please ensure that your company’s network allows traffic on the corresponding port.
For more information on the AUT, please refer to KB 144316 or KB 130332.
Keywords: HTTPS
SFTP
Secure FTP
AUT Ports
Email
Token Logs
Usage Logs
References: None |
Problem Statement: How to resolve the error, "AspenTech.ALC.MainFrame has stopped working" when opening the ALC Configuration Tool. | Solution: Install .NET Framework 3.5 resolve the issue
NOTE: Before you install SLM V8.4 or higher, you need to install both .NET Framework 3.5 and .NET Framework 4.0 first.
If you don't install .NET Framework 4.0, you will get 'Error 1304 Error writing to file Interopt.SECSERVEROBJECTLib.dll' during the installation.
See KB Solution 139541 for more details.
If you don't install .NET Framework 3.5 , you will get "AspenTech ALC.MainFrame has stopped working" during the installation , but when you close the error window,the installation process will continue.after the installation,once you open ALC you will get "AspenTech.ALC.MainFrame has stopped working" again
Keywords: ALC
MainFrame
SLM
NET Framework 3.5
References: None |
Problem Statement: How do I install the Microsoft ASP.NET component required for the Software License Manager (SLM) Server? | Solution: This knowledge base article describes the steps required to enable the ASP.NET component.
· Click on Start
· Go to Control Panel | Programs and Features
· On the left hand side navigation click on "Turn Windows features on or off"
· Now enable ASP.NET, which can be located under Internet Information Services | World Wide Web Services | Application Development Features
· Click OK.
· Run the aspenONE installation.
Keywords: asp.net, slm server asp.net, slm server, slm server prerequisite
References: None |
Problem Statement: The SLM manuals contain the complete instructions to install an SLM Server and a license on that server (what we call a "Network" type of SLM license). Sometimes you may want to have some brief troubleshooting instructions to double check the installation of your license. | Solution: Some troubleshooting instructions can be found in the attached Word document.
Keywords: Network SLM licenses
SLM license server
dongle, dongles
dongleless
dongle-less
dongle-locked
References: None |
Problem Statement: How to Enable the ASP.Net Microsoft feature through Programs and Features? | Solution: To enable the ASP.Net Microsoft features on a machine, the following steps need to be performed:
1. Go to Start > Control Panel> Search for “Programs & Features” or
go to the following path: Control Panel\All Control Panel Items\Programs and Features
2. Select “Turn Windows Features on or off”
The Windows feature window will open up
3. Select “Internet Information Services” option and Expand it by selecting the + sign.
4. Select the “World Wide Web Services” option and expand it.
5. Under the “Application Development Features” , select the ASP.Net checkbox and press “OK” button to proceed with the enabling of the feature.
Once done the feature has been installed.
KeyWords
ASP.NET, IIS, Microsoft feature
Application Development Features
Keywords: None
References: None |
Problem Statement: The following error appears in the Windows Event viewer when attempting to start the Sentinel service.
Event ID: 32
The Sentinel RMS License Manager was unable to bind to its socket. | Solution: Microsoft has documented a recent case where the installation of patch MS08-037 has resulted in port conflict and connection problems. This is discussed in further detail on Microsoft's website: http://support.microsoft.com/default.aspx?scid=kb;EN-US;953230
The ReservedPorts registry key can be used to exclude ports used by the Sentinel License Manager are reserved. An example of how to reserve ports is provided on Microsoft's support site at the following link: http://support.microsoft.com/kb/812873
Keywords: Sentinel License Manager;
SLM;
License Manager;
Socket error;
Socket;
References: None |
Problem Statement: No Valid License Found
Server "xxxxxxxx" was not contacted successfully due to the following Sentinel error: 57. The licensing system was unable to resolve the specified Host name. Please check that the Host name exists and is configured in the network DNS. | Solution: 1. Verify that the server location has not changed.
A host name must match to an IP address that is located in a DNS server database, or in a Hosts file.
For additional information on understanding host names, click on the link below:
http://www.tech-faq.com/understanding-host-name-resolution.shtml
Keywords: license, Sentinel, error 57, Hostname, DNS, IP, address, server,
References: None |
Problem Statement: How can I have a backup of my SLM license server? | Solution: Option 1 - Tokens are spread across multiple SLM Servers
Main features:
- Splits entitlement across multiple SLM Servers
- Only lose partial capacity if one SLM Server fails
- Applications cycle through SLM Servers to find an active one with tokens
- Ideal for global companies or companies with multiple related business units
Option 2 - Standby SLM with dongle
Main features:
- Move dongle to backup server
- If primary server fails, a backup SLM Server can be powered on
See below a Process Control Network example of this second option in the context of APC (Advanced Process Control applications) but the same principles apply for Business Network applications.
Configuration to Support Back-Up Licensing on Process Control Network:
The license file can be token-bearing keys or non token-bearing. The file is installed on the Production SLM Server and also on the Backup SLM Server (identical license file).
The license file is enabled by a specific dongle (ZZ) which is made available by AspenTech.
The Backup SLM service can be enabled but it will not be able to release keys because its license file cannot be enabled by the ZZ Dongle if the ZZ Dongle is plugged into the Production SLM Server.
The DMCplus and Aspen Watch SLM clients are configured to point to SLM_Prod as their primary source of keys. These same clients are configured to point to SLM_Back as their secondary source of keys.
Of course in regular operation the clients will only be able to get keys from SLM_Prod because only SLM_Prod will be able to release license keys (as it has Dongle ZZ).
If SLM_Prod fails, or its box fails, then Dongle ZZ is removed and placed in the machine running SLM_Back ? all the clients will then immediately get their keys with minimum interruption from SLM_Back instead of SLM_Prod.
Conclusion:
Using Dongles and duplicate license files (whether token-bearing or non token-bearing) AspenTech can provide an efficient mechanism for providing Back-Ups for the SLM licensing applications.
Keywords:
References: None |
Problem Statement: Starting from aspenONE V7.1, most advanced process control (APC) products consume tokens automatically based on the number of MV's (Manipulated Variables). How does that happen exactly? How do you add up MV's to calculate token consumption of an APC product? Is it by DMCplus server or by controller? | Solution: The sharing is by SLM Server. The usual mechanism that we call "global share" for fractionary token consumption is used. If for example we consider a consumption of 1 token every 3 MV's (note that the actual token value is written in the contract, so the numbers used here are just to provide an explanatory example), if one controller has 5 MV's it will check out 2 tokens. If the next controller has 4 MVs it will only check out 1 token. This is because it will use up the spare MV on the second token. So the SLM server is very fair. It does not care where the controllers or MVs come from.
Keywords: Tokens
Global Share
Controllers
MV
References: None |
Problem Statement: How do I switch between the a standalone license and server license? I have access to both, but I need to know how to choose which license I wish to use. | Solution: It's easy to switch between a standalone license and network server license.
Just go into your SLM configuration wizard on your PC (Start - Programs - Aspentech - Common Utilities - SLM Configuration Wizard), and change the very first screen:
If you want to use network license, choose YES for connecting to an SLM server over the network.
If you want to use the Standalone license, choose No for connecting to an SLM server over the network:
Keywords: standalone, network, switch, license, SLM, configure
References: None |
Problem Statement: This knowledge base article describes the purpose of the SLM_Pool and SLM_Suite license keys. | Solution: The SLM_Pool and SLM_Suite license keys determine how many simultaneous AspenTech applications can be used.
- The SLM_Pool key value represents the number of tokens in a license file (if the license is token-based).
- The SLM_Suite string determines the maximum simultaneous users for an AspenTech application
For Example, a Token License will have the number of users for SLM_Pool set to 1 or higher (this is the number of Tokens) and SLM_Suite set to 32766 (this is the maximum number of users allowed by SLM). This allows the maximum number of users to be limited by the available tokens. The SLM License Profiler can be used to examine these two license key values.
A standalone license is a non-token license for a single user to use an AspenTech application on the local computer. A standalone license will have both SLM_Suite and SLM_Pool set to 1.
For a non-token network license the SLM Suite key will be set to the maximum number of allowed users. For example, a 12 user network license will have SLM_Suite set to 12 and SLM_Pool will be set to 1.
Keywords: SLM_Pool, SLM_Suite, Token, Standard, License file, License strings
References: None |
Problem Statement: This knowledge base article describes the license file lock mechanisms. | Solution: License Type
Lock Type
Description of Lock Type
Details
Standalone -
(Standard Customer)
Dongle
License locked to a USB dongle with a unique dongle number. This option is not available to all customers.
Dongles may be required in some cases
Dongles do not work with Virtual Machines.
Must use v8.4 of SLM client tools if using a 64 bit computer
Standalone -
(Standard Customer)
Dongle Free - Locked to Ethernet AddressLicense locked to a unique code given to each computer by the manufacturer (e.g. 00:00:94:ba:0e:CC)
The license will work on a single user's computer.
Will not work if ethernet address is changed. Ethernet address may get changed when connecting to a new wifi source.
Standalone -
(Small Business Package Customer)
Dongle Free - Locked to Disk IDLicense locked to a unique identifier on a hard disk on the local computer
Disk failure will cause license not to work. You will need a new license if disk is changed.
Network
(Users point to a license that is installed on a network SLM license server)
Dongle
License locked to a USB dongle with a unique dongle number.
Dongles may be required in some cases.
Dongles do not work with Virtual Machines.
Must use v8.4 of SLM client tools if using a 64bit system
Standalone -
(Standard Customer)
Dongle Free - Locked to Ethernet AddressLicense locked to a unique code given to each computer by the manufacturer (e.g. 00:00:94:ba:0e:CC)
The license will work on a single user's computer.
Will not work if ethernet address is changed. Ethernet address may get changed when connecting to a new wifi source.
Virtual
(License is installed on a Virtual Machine)
Dongle
Dongles do not work with Virtual Machines
Do not use dongles on Virtual Machines
Dongle Free
Licenses will only work on Virtual Machines if locked to a combination of Hostname and IP address
There is only 1 lock mechanism available. Use the WEchoID tool to obtain unique lock code
Keywords:
References: None |
Problem Statement: What information is contained in SLM usage logs? | Solution: Please find attached a description of the main fields (columns) in an SLM usage log file.
Keywords: lservopts
References: None |
Problem Statement: On a Windows 7 system Aspen Capital Cost Estimator loses fetched commuted license whenever evaluation of a new component is attempted. Program displays License checkout error.
Using a commuted license on a Windows 7 system, start Aspen Capital Cost Estimator and run a model, evaluate cost and create a report without a problem. Then select a different component for running, At this point the program displays "License checkout Failed" error. | Solution: To start Aspen Capital Cost Estimator, right click mouse on the ACCE shortcut and select "Run as Administrator". Running the product in this manner, the system provides all the privileges to the program to re-read the commuted license file without a problem.
This problem does not happen under XP. Nor does it happen if license is fetched directly from the server.
Keywords: Windows 7
Commuting a license
License
Failed to checkout License
References: None |
Problem Statement: Attempting to fetch a network license from SLM server results in Error 88 | Solution: Error 88 usually appears with none Citrix standalone licenses but not with network licenses unless the product license is removed from SLM Server cache or not listed within the license file.
To resolve the issue, Run SLM license profiler and make sure that product license is listed for the program you are trying to run. If profiler does not have an entry for the program you are trying to run then either this feature has been removed after license file was loaded or the license file does not include license for the product.
If you have purchased the product and the original license file does not include the feature, please call AspenTech Customer Care (1-888-996-7100 Option 0) to get a new license file.
If the license file includes the feature you are trying to run, do the following on the SLM server:
Browse to C:\Program Files\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT and run loadls.exe by double clicking on it. A new window will appear, select Remove.
Run loadls.exe program again and select ADD
Keywords: 88
Error 88
SLM
References: None |
Problem Statement: The normal product usage information is missing in the SLM usage log. It only contains the two following types of lines:
# Shutdown Sentinel RMS License Manager v8.2.0.800 Mon Mar 05 14:30:02 2012 1330954202 SLMServerName 4496 ODY1Mg== 472821
# SuspendLog Sentinel RMS License Manager v8.2.0.800 Mon Mar 05 14:30:08 2012 1330954208 SLMServerName 2888 2000180
How to go back to normal logging? | Solution: This can happen when logging has been disabled or the number of log files in the log folder already reached 99 and the old ones are still lying around.
To avoid this problem, you can do any of the following:
- Move old log files away to some backup folder.
- Deploy the Auto Upload Tool, and select the files to be moved automatically.
- Set the file size to be larger, so that the file list doesn't grow too fast.
Keywords: lservopts
usage logging
AUT
References: None |
Problem Statement: How can I monitor Base Load Tokens usage? | Solution: The Aspen Base Load Service was introduced in V7.1 to allow products to consume Base Load Tokens.
For a list of Product that consume Base Load Tokens, see KB 128288. For instructions on how to install this service, please refer to KB 128332.
To monitor and troubleshoot Base Load Token consumption, the Base Load Service Report is provided. This tool can be accessed via Start | Programs | AspenTech| Common Utilities and selecting "Base Load Token Usage Report"
In the example below, the Report shows 100 Tokens being consumed for PIMS (and no tokens being consumed for any other products):
Keywords: Aspen Base Load Service Monitor
Base Load Token Usage Report
References: None |
Problem Statement: How do I install the WLMADMIN Tool? | Solution: WLMAdmin can be installed from the any aspenONE DVD's:
1. Launch setup.exe in the root of the any of the aspenONE DVDs.
2. Select to install the "SLM Tools 7.3 or 8.4"
3. During the install select the "Server Installation" option
4. In the feature selection window, expand and select "Aspen SLM".
5. Select the "Aspen SLM Admin tools" option "Install this feature and all subfeatures".
6. Click "Next" and "Install"
7. Start ? Programs ? AspenTech ? Common Files ? WLMADMIN
Keywords: WLMAdmin
SLM Admin Tools
References: None |
Problem Statement: How to match a USB dongle to the correct license file. | Solution: License file/Dongle pairs can be matched using either 1) the Lock Code or 2) the Key Serial Number of the device.
Dongle Lock Code-to-License File Name
? Aspen Tech license files that are locked to a USB dongle typically include the Lock Code of the dongle in the name of the license file. The dongle Lock Code address should appear on the sticker placed on the dongle.
o A license file that has the name "Lservrc_080_1234.slf" should be paired to a dongle that has the Lock Code 80_1234 stamped on it.
Key Serial Number
? The Key Serial Number is the second number that is assigned to an Aspen USB dongle and a matching Aspen software license file. You may notice the Key Serial number as a sticker on the opposite side of your Aspen USB dongle. Make note of this number.
o To find the Key Serial Number in the license file, use an ASCII text editor (such as Notepad) to open and find the Key Serial Number (normally appearing in the first line of the license file). The Aspen license file should be paired with the Aspen USB dongle of the same Key Serial Number.
*** Important: Do not save the license file when closing out of the ASCII text Editor ***
Keywords: SLM, Dongle, Training
References: None |
Problem Statement: Attempting to run any Aspen product with installed standalone license file results in:
Error 88: Terminal Server Found. Cannot run Any Aspen application with standalone license file | Solution: To resolve the issue you can do either one of the following:
? Disable Terminal services in your system
? Move to a standalone system without terminal active services
? Contact your Aspen Tech account rep and convert your license file from standalone to network type
Keywords: SLM
88
Terminal Server
Terminal
Server
References: None |
Problem Statement: Dongle locked license does not work on Server 2008 R2 64-bit | Solution: 1. Create a folder called aspenoneMedia at the C drive
2. Copy the entire DVD to C:\aspenoneMedia
3. Copy the DVDBroswerWizardDLL.dll (attached to the incident) to C:\aspenoneMedia, but rename or delete the old one copied from the DVD.
4. Copy the <productname>.msi to aspenoneMedia (To find the <product> .msi -You will have to drill down to the folders of the DVD copy image)
5. Run the UpdateDVDBrowserWizardDLL.vbs (attached to the incident)
Keywords: Dongle, Server 2008 R2 (64-BIT), DVDBrowser.dll, and SLM SERVER
References: None |
Problem Statement: This knowledge base article describes how to commute a license from the SLM License Manager Network Server. | Solution: Commuting Licenses
Use Aspen SLM Commute (SLMCommute.exe) to borrow licenses from a network server. These borrowed, or commuted licenses allow a client computer to run the licensed product while disconnected from the network without the use of a SLM dongle.
Note: You must run Aspen SLM Commute when the user is connected to the License Server network to obtain and verify the licenses required.
The commuted time is specified in days, with a maximum of 30 days. The licenses can be returned prior to their expiration date. In order to successfully commute a license, the commutable feature must be activated in the license file.
Checking Out Commuter Licenses
1. Ensure you have an AspenTech product open before you commute. Otherwise the commuting facility can take a long time to start up.
2. Run the commute program by selecting Start | Programs | AspenTech | Common Utilities | SLMCommute command from the desktop menu.
The Aspen SLM Commute dialog box appears.
Aspen SLM Commute displays the servers you have configured using the SLM Configuration Wizard and enables the user to check out licenses from those servers.
Commuter Option Description
===========================================================================
Single Server searches for and displays a specified license
server. Requires you to specify the license server's
computer hostname, or IP address in the field provided.
===========================================================================
Sub-Net Searches for and displays all of the license servers
on your subnet.
===========================================================================
Take License(s) Checks out the licenses selected.
===========================================================================
Return License(s) Returns the specified licenses.
===========================================================================
Return All Licenses Returns all licenses.
3. When the program loads, if you know the server from which you want to commute licenses:
Enter in the Single field either the Server name the or IP Address. Then click Single.
This causes SLM Commute to display the licenses on the server you specified.
Important: Make a note of the server you are using, because you will need to return the
commuted licenses to the same server
Note: To find a server from which to commute licenses, click Sub-Net.
Once the server has been located, all the available commuter licenses are listed. The license list may take some time
to display.
If a server is unavailable, it appears with a red crossed icon.
4. Click the features for which you want to check out licenses. You can choose one or more features. Each feature you choose is marked with a red icon.
Note: It is recommended that you choose only the licenses you will need.
For example, if you are commuting licenses for HYSYS and are unsure of which licenses you will need to run your case, you can use a capability in HYSYS to display the licenses that are in use in the case that is loaded. In HYSYS, select Simulation | Main Properties from the menu bar; then click the Licenses tab.
5. In the Days to check out license(s) from server field, enter the number of days you require the license(s).The number of days can be any integer from 1 through 30.
6. Click Take License(s).
If the commute is successful, SLMCommute displays a message confirming the successful commute.
7. Click OK.
The license or licenses are temporarily released from the server to your hard drive. The license icon changes for the licenses you have commuted.
8. Close Aspen SLM Commute by clicking File | Exit.
You can now run your licensed product away from the network. Your license automatically expires at midnight on the last day of your license period. If you return to the network, you can return the license to the network before the expire date using Aspen SLM Commute.
Important: Commuting licenses and un-commuting licenses must be done with full local administrator rights.
Keywords: License commute
License checkout
License borrowing
License
Commuting
Borrowing
References: None |
Problem Statement: Hyper V virtual machine on a Windows 2008 Server does not have USB support | Solution: Hyper-V virtualization on a Windows 2008 Server does not have USB support, thus a license key that locked to an USB dongle will not work. AspenTech provides a USB driver for dongle but the OS system has no USB support. There are several ways to solve this problem:
· Install a SLM server on the physical machine and point the Hyper V machine to it to get the license. The license key then would have to be a network key and not a standalone key.
· Install a 3rd party USB redirecting software. There are several out in the market place and they all seem to work. AspenTech don't have a recommendation on which software because these are not tested by the AspenTech team.
· Request a dongle free license from AspenTech.
This issue is not a problem with VMWare as VMware virtualization software provides USB support
Keywords: Hyper-V
USB
SLM
References: None |
Problem Statement: Can I block commute option for specific users? | Solution: For SLM Server up to version 8.2, it does not support commute restriction by specific users.
Currently, using the group reservation file, you may reserve tokens/units for specific clients (users/machines). This will work for both normal network license requests and commuter requests.
Keywords: Commute
SLM Server
Restriction
References: None |
Problem Statement: Error 11 when starting Aspen Basic Engineering (formerly Aspen Zyqad) V7.1 | Solution: This is a known issue. Zyqad line within the license file has more than 100 characters in the comment line. Sentinel cannot handle more than 100 characters of comment. SLM ClientTool, STRGXI2.DLL, has to be upgraded to version V7.2.
Here is the procedure to follow:
Make sure you exit all AspenTech programs
Brows to C:\Program Files\Common Files\Hyprotech\Shared
Click on Start | Run and type in CMD - This will open a DOS window
Within the DOS window type the following commands:
CD C:\..\..
CD C:\Program Files\Common Files\Hyprotech\Shared folder
REGSVR32 -U STRGXI2.DLL
Rename STRGXI2.DLL STRGXI2.old
Download STRGXI2.dll file attached to this solution to the shared folder
REGSVR32 STRGXI2.DLL
Exit
Start Aspen Basic Engineering
Keywords: Aspen Basic Engineering
Zyqad
Error 11
V7.1 Zyqad
References: None |
Problem Statement: How do I install a public/private key for use with the Auto-Upload Tool? | Solution: Once you've received the encryption keys, create directory named Keys under \AspenTech\ALC and copy the .acc file.
1. In the Import User Account section's Account path dialog box, browse to the location of the secure key obtained from AspenTech.
2 User name is automatically filled up by the Auto Upload Tool by reading the .acc file.
3 The AspenTech SFTP field is preconfigured with AspenTech's secure FTP server. It should point to
alcftp.aspentech.com.
4 Click the Test Connection button.
Note: If the connection is successful, a Connection Succeeded message is displayed. If an error message is displayed, see the Troubleshooting section of this manual, or refer to support.aspentech.com, Knowledge Base Item 126943, or contact AspenTech Customer Support for additional assistance.
5 If you are finished with all other configuration settings, click Apply.
Keywords: public, private, Auto-Upload, licensing, installation, key
References: None |
Problem Statement: This knowledge base article describes how to use the SLM Test utility to find additional information about licensing failures. | Solution: Sometimes a product may not be able to obtain a license when starting. The utility attached to this knowledge base article will allow you to test the license request without opening an AspenTech product.
Please download the attached executable to the desktop of the client computer where the problem exists and then double click on it to execute the utility. On the left hand side you will need to manually type in the license key names that you wish to test. These entries are case sensitive and need to have the prefix of 'SLM_'. Be sure to uncheck the check boxes for the lines that do not contain license key names.
Click on Start Test. In the bottom section of the display you will be given execution statistics and also the results. This test utility will return the numerical error code that is encountered. Please refer to KB 111597: What do the SLM error codes mean? to look up the error message from the error code returned by this tool.
Below is an example of how the test tool data is populated for the application SLM_TascPlus:
Keywords: SLM_Test
test utility
References: None |
Problem Statement:
You may get “Not authorized to create, modify, delete, copy or rename any type of calculation on this node” while creating calculation on primary node in MES collaborative environment.
When you try to delete the calculation, you may get “Failed to delete on Collaborative node: xxxxx”.
In this case, I have 3 nodes called MES1201, MES1202 and MES1203 in the collaborative environment. | Solution:
1. Configure AFW security for Aspen calc (Primary node is security server in this case)
a. Launch AFW Security Manager on primary node
b. Expand AFW Security Manager | Right-click applications -> All Tasks -> import application… | Browse to C:\Program Files\AspenTech\Aspen Calc\bin\AspenCalc_base_security_install.xml and open it.
c. Right-click Roles | select New -> Role to create the roles such as sysadmin, engineer and operator.
d. Right-click each role | select properties | add the members.
e. Expand Aspen Calc | Right-click Servers | select New -> Securable Object | Add three objects
f. Right-click each of the Securable Object | select properties | grant permission to the role.
g. Highlight Aspen Calc | Right-click on Servers | Select properties | grant permission to the role.
h. Launch AFW tools from non-primary nodes | Point to the security server.
2. Configure DCOM permissions on each node.
a. Configure DCOM settings by launching Component Services from the Server Manager (or Control Panel, Administrative Tools).
Note: Another way to launch the DCOM configuration tool is to press the Windows key + R to get a Run Window, then enter DCOMCNFG.
b. Expand to the My Computer node and select the Properties option.
c. From the Default Properties tab, ensure that DCOM is enabled.
d. From the COM Security tab, configure the following permissions. If a security group list below is not present in the list, then click the Add button to add a new entry, then configure the permissions.
Access Permissions Limits:
Launch and Activation Permissions Limits:
e. Also, ensure the following minimum permissions are configured for the default permissions.
Access Permissions Default:
Launch and Activation Permissions Default:
f. Now the DCOM security settings must be configured for the Aspen Calc Scheduler Service itself. So, select the DCOM Config node, then select the AspenTech Calculator Engine component. Right-click and select Properties.
g. Select the Security tab and enable the Customize option for the Launch and Activation Permissions, then click the Edit button to add the following permissions.
Launch and Activation Permissions Default:
h. For the Access Permissions, leave the Default option selected.
Please Note! After changing any DCOM permissions, you should restart the Aspen Calc Scheduler service, also known as the AspenTech Calculator Engine service.
3. Restart AFW Security Client Service on each node.
4. Re-open Aspen Calc on primary node and try to create calculation again. You should be able to create the calculation and it will be created on non-primary node automatically.
Key Words:
Collaborative
Calc
Calculation
Not authorized to create
Keywords: None
References: None |
Problem Statement:
In MES Collaborative environment, the checksum on each node should keep same. This article provides the steps to synchronize the checksum in case there is any difference. | Solution: :
1. Save a snapshot from primary node.
2. Stop IP.21 on non-primary node.
3. Delete CHECKSUM_RECIDS in the registry on non-primary node.
HKEY_LOCAL_MACHINE\SOFTWARE\AspenTech\Infoplus.21\17.0\group200
Note: If you don't delete CHECKSUM_RECIDS in the registry , IP.21 will not be able to start with the snapshot saved from primary node. You may get below error message in TSK_DBCLOCK.OUT.
InfoPlus21.snp* with err=*The recIds checksum in the snapshot is different from that in the registry *.
4. Start IP21 on non-primary node with the snapshot saved from primary node. CHECKSUM_RECIDS will be created once IP21 is started.
5. Modify the pub and sub record on non-primary node accordingly.
6. Verify the checksum from registry key "CHECKSUM_RECIDS" or the IP_CHECK_SUM field of CooperativeInfo record in IP.21 administrator.
Key Words:
Checksum
Synchronize
Collaborative
CHECKSUM_RECIDS
Keywords: None
References: None |
Problem Statement: After an Aspen Production Execution Manager installation, it is not readily apparent what URLs to use to visit the Order Management or Order Execution web pages. | Solution: First, to successfully visit the pages, make sure all additional configuration tasks beyond the initial installation are done. This is covered in KB 128767. Once that configuration is done, use the following URLs:
Order Management:
http://localhost/aebrs/pages/OrderManagement/OrderList.aspx
Order Execution:
http://localhost/aebrs/pages/OrderExecution/aebrsworkstation.aspx
Update: Note, these pages have been removed from Version 12.2 and later, replaced by ApemMobile.
Keywords: None
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.