question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: After running the DBUpdate.sql script on my database to upgrade it to V8.7, I get the following error:
Incorrect syntax near '='
How can I fix it? | Solution: This happens only if the Olefins DB has been upgraded to V8.5.
To fix it:
1. Delete _LINEFILL table manually.
2. Run DBUpdate.exe to generate the DBUpdate.sql script.
3. Execute DBUpdate.sql on the database to update the schema.
Keywords: None
References: None |
Problem Statement: Getting an error "Retrieving the COM class factory for component with CLSID {1460FDB4-752B-11d4-B067-0090271CF383} failed due to the following error: 80070005" when opening the Aspen InfoPlus.21 Mobile web page. | Solution: This error message indicates that a COM library that has a class ID {1460FDB4-752B-11d4-B067-0090271CF383} is not found. In order to know which dll this class ID correspond to search for this ID in the registry editor under HKEY_CLASSES_ROOT | CLSID. Once you find out the library the class ID corresponds to re-register the library following these steps. In this case class ID belongs to the library strgxi2.dll.
1- Open a DOS command window and go to C:\Program Files\Common Files\Hyprotech\Shared\
2- Un-register the library using the following command: regsvr32 /u strgxi2.dll and
3- Re-register it using the command: regsvr32 strgxi2.dll.
once this is registered the user should see a message that the dll has been successfully registered.
Please note that this solution can be applied to other products when getting similar error messages as the STRGXI2.dll is used by the SLM client which is our licensing component .
Keywords: STRGXI2.dll
COM
SLM Client
Aspen InfoPlus.21 Mobile
References: None |
Problem Statement: How do I create dynamic tag list in aspenONE Process Explorer? | Solution: In InfoPlus.21, there is a record called "IP_AlarmSummary" which has a repeat area that populates Tag Names dynamically into the SUMMARY_LINE attribute of the repeat area, as shown below:
First, create a graphic using IP.21 Browser Graphic Studio and then add the Grid Component in the graphic, as shown below:
In the properties of the Grid component go to the data tab and configure the data to "List" type.
- Select the Data Source, enter the Record Name as the InfoPlus.21 Record
- Select the Attribute that has the Dynamic Tag List and
- Select the columns that you would like to see in the Dynamic Tag List. These are attributes of the tag itself
- Publish the Graphic to AspenOne Process Explorer
- Open AspenOne Process Explorer and open the graphic. You will see that the dynamic tags get populate in the Grid.
Keywords: AspenOne Process Explorer
Dynamic Tag list
IP.21 Browser Graphic Studio
Graphic
Dynamic List
A1PE
References: None |
Problem Statement: When opening Sparkline in Aspen InfoPlus.21 mobile the trends appears to be loading but the trends never come up. This solution documents how this can be resolved so that users can see Sparkline. | Solution: In order to resolve this issue use the following procedure
1. To resolve this issue change the "AspenIP21MobileAppPool" Application Pool in IIS to run with an account that has permissions to communicate with Aspen InfoPlus.21 database. We recommend to use the same account as the one that is being used by "Aspen InfoPlus.21 Task Service".
2. Once the account was changed restart the Application pool followed by resetting IIS using 'IISRESET' command from a command prompt.
After this verify to see if you can see the Sparkline.
Keywords: IP.21 Mobile
Sparkline
References: None |
Problem Statement: When aspenONE Process Explorer is loaded and you select the 'Menu Tree' it will load all of the plots and graphics in the tree. If several hundred graphics/plots that have been published to the aspenONE Process Explorer server then this may cause the page to load slowly or become non responsive. | Solution: The menu Tree in aspenONE Process Explorer will remember what location a user was last at or if a folder is open with many Graphics/Plots then the page may become slow or non responsive as shown below.
To work around this issue ensure that in the Aspen IP.21 Browser Graphics studio has approximately 100 graphics per folder. You may need to adjust the amount and depends on individual environments.
To create a Folder you need to have the aspenONE Process Explorer Administrator open the Project in Aspen IP.21 Graphics Studio. Right click and select 'Add Folder' then move your Graphics into the folders. Once Completed the project will need to be saved and Published.
Keywords: Graphics
Slow
freezing.
not responding
References: None |
Problem Statement: Overview of Aspen Dock Scheduler Token consumption. | Solution: An Aspen Petroleum Scheduler model with a Dock Screen will not consume Dock license unless Dock screen has been enabled \ Viewed once. The token consumption can be summarized below:
Product Name
Product Feature Key
Tokens
Aspen Petroleum Scheduler
SLM_ORION_XT
X Tokens
Aspen Dock Scheduler
SLM_RN_PNS_DSS
Y Tokens
Total consumption.
X+Y
To release Dock Scheduling Token, user will need to close Aspen Petroleum Scheduler.
Note: Aspen Petroleum Scheduler will always reopen last viewed screen, therefore if you keep the Dock Screen as your last viewed then when reopening Aspen Petroleum Scheduler it will consume Dock Scheduling Token. If you do not want to consume Dock Scheduling tokens, change the view to any other Event screen and then close Aspen Petroleum Scheduler.
Keywords: APS
Aspen Petroleum Scheduler
Orion
DSS
Dock Scheduling
SLM_RN_PNS_DSS
References: None |
Problem Statement: Having created a Cim-IO Interface for your Ignition OPC-UA Server, you find all your attempts to read data from a device using Test API are met with either of these responses:
Status is 'Request Failed'
Facility=78
Driver Status=1002
-or-
Status is 'Bad Tag'
Facility=78
Driver Status=1006 | Solution: Perhaps the best way to demonstrate the correct syntax to use is by way of an example of reading data from Ignition Generic Simulator.
Assuming that the Ignition device you have created is called SIMDEV, you can read the current RandomDouble1 value using the OPC Quick Client. The syntax of the tagname is: [SIMDEV]_Meta:ReadOnly/ReadOnlyDouble1
To read data from the same tag when using Test API utility program it is necessary to "escape" the colon character following the _Meta portion of the name: _Meta&:Random/1:RandomDouble1
The complete tagname in this example would be:
/Objects/1:Devices/1:[SIMDEV]/1:_Meta&:Random/1:RandomDouble1
Using IP.21 Administrator, the same tagname could then be successfully used for the IO_TAGNAME in a transfer with long tag record.
Keywords: inductive automation
References: None |
Problem Statement: An IQF file fails to load online with the error message "CIMIO_USR_GET_CONVSZ." | Solution: The error message CIMIO_USR_GET_CONVSZ signifies that the cimio communication failed because the get request was trying to get data from a tag of the wrong data type. For example, the above error message will be displayed for situation where a tag that is supposed to be of DBVL (real) data type is read in as a ASC (Text) instead. In such situations, the cimio get request is unable to resolve the data type.
To fix this problem, the user needs to open the faulting IQ application in IQconfig and search through the tag names to locate the tag name with the incorrect data type format and fix this issue.
Keywords: IQ application
CIMIO_USR_GET_CONVSZ
References: None |
Problem Statement: If an IQ has a variable validation module, can it be accessed from the Web Server? | Solution: The below example shows you how to access the IQ variable validation module from the Web Server.
In this example, we added the following data validation modules to an IQ called "TEST".
For the PREDBIAS and LBIASNEW; this example has minimum and maximum limits set as 0 and 100, respectively.
After loading and starting controller, we opened a new instance of the Web server, and opened the TEST IQ. Go to the Engineering “sub-tab”.
PREDBIAS and UAZ can be found by clicking in Operate in the Prediction module.
LBIASNEW is also in Operate for the Lab module
For instance, let’s say we want to modify a validation parameter for PREDBIAS. Click in Operate for Prediction.
Scroll down and you will find that in PREDBIAS and UAZ have Good hyperlink next to the value.
Click on the Good link for PREDBIAS. PCWS displays a pop up window that allows to modify the Validation parameters. Since from the beginning it was only specified the maximum and minimum limits, then those are the only parameters available to modify.
Keywords: Variable validation module, Production Control Web Server, PCWS
References: None |
Problem Statement: While using the new Process Data Add-In available in V7.3 and later, unable to get Current Value in Microsoft Excel 2010.
Error Message: FAILED:Could not connect to net.tcp://<IP.21 Server> Name:52007/PME/ProcessData/IDataService. The connection attempt lasted for a time span of 00:00:01:0184395. TCP error code 10061: No connection could be made because the target machine actively refused it 10.148.32.63:52007. | Solution: Start Aspen Process Data Service. This Service, also new in V7.3 and later, is a requirement for the new Add-In.
Keywords: Excel 2010
Add-In
net.tcp://
IDataService
TCP error code 10061
References: None |
Problem Statement: Aspen Role-Based Visualization Administration Tool - How to connect to a remote Sharepoint configuration database to deploy Aspen Role-Based Visualization content solutions.
What information is required for the connection?
What authentication method is used connecting to the MS-SQL Server database? | Solution: The "RBV Administration Tool" allows deploying Aspen Role-Based Visualization's core and content solutions to the SharePoint portal.
The details needed to establish the connection to the SharePoint Configuration Database must be entered in the "Server Information" frame.
Select Use Local Server when the Sharepoint datasource is installed on the same machine as the RBV server.
Select Use Remote Server to connect to a remote Sharepoint datasource. In that case the following information is also required :
DataSource : Syntax = <ServerName> or <ServerName\InstanceName>.
Username : SQL authentication is used (required) connecting to the SQL server
Password
Initial Catalog : This MS-SQL term refers to <<the name of the initial database (also known as the catalog) of a datasource during connection>>. The database here is the SharePoint Configuration database (not the content database.)
If you did not configure the Sharepoint server yourself or don't remember the datasource and configuration database names, this information can still be retrieved from the Sharepoint 2007 Central Administration under "Operations\Servers in Farm."
Important notes :
1. The core solution (Aspentech.RBV.Core.wsp) must be deployed before any other content solution.
2. The user account used to run the RBV administration tools must have enough privileges to write to the remote database. Errors like "Object reference not set to an instance of an object" have been observed when these privileges are missing.
Keywords: Administrator tools
.wsp
remote server
deploying SharePoint
References: None |
Problem Statement: How can I reset the unbiased prediction to a reasonable value? | Solution: Use LBUINIT to reset the lab bias. It will accept the next lab sample as ?perfect? and set the bias so that the unbiased prediction plus the bias equals the lab sample.
If you are using analyzer updates, there is an AZUINIT that behaves in a similar way. I can?t recall if it is in 2006.5, but he should be able to find both in the respective LBU and AZU sections in IQconfig.
Keywords:
References: None |
Problem Statement: How does SUSPEND mode works for Aspen Smart Step? | Solution: Aspen Smart Step tester is a software package intended for automated step testing of process units. It can be used during throughout the life cycle of a DMCplus controller. The project team can use SmartStep for pre-test activities, step testing, and commissioning support during the DMCplus project. Customer engineers can use SmartStep for periodic performance audits and controller revamp work.
Smart Step has 4 different modes- Control, SingeTest, Multitest, Suspend.
SUSPEND mode in V7.3 and onwards also works in a similar way, i.e. SmartStep will only make a move if CV drifts outside the defined operator limits. The size of the step will be decided by test margin. It will work just like the DMCplus controller but without Linear Programing calculation (minimum move DMCPlus controller). The correcting moves will use the move tolerance- MOVRES (that is internally calculated) so that the correcting moves will be accumulated and they be sent to the independent variable set point - VINDSP, when the accumulated value is above the MOVRES. This way the feedback correlation is “broken”.
Keywords: Suspend
References: None |
Problem Statement: Is it possible to add comments in a CIMIO csd file? | Solution: It is not possible to add comment to CIMIO csd file because anything enter into the csd manually will be overwritten by the CimIo manager.
Keywords: CIMIO
CSD
file
Comment
References: None |
Problem Statement: After installing Aspen Role-Based Visualization, the Operations Navigator web page is blank (you cannot see the Operations Navigator webpart on the page). | Solution: Please make sure that your proxy server doesn't block the JQuery Library used by Aspen Operations Navigator. The Library is maintained by Google to ensure the best user experience when browsing the Internet content using both the full version browsers and their mobile versions. The link that needs to be unblocked is shown below:
http://ajax.aspnetcdn.com/ajax/jQuery/jquery-1.7.2.min.js
Important note:
To troubleshoot the issue please use a JavaScript debugger. In Chrome, use the Chrome DevTools. In Firefox, you can use the built-in Firefox DevTools. In IE, you can use the F12 developer tools.
Keywords: Unable to see Operations Navigator
Operations Navigator missing
Unable to see OpsNav
OpsNav missing
References: None |
Problem Statement: DMCplus Simulate crashes with an "unrecoverable floating point error." | Solution: Simulate has a limitation when using an imported model as a plant: it requires that the total number of model coefficients are the same for the controller model and the plant model. In case this condition is not satisfied, DMCplus Simulate would crash when in the middle of a simulation with an "unrecoverable floating point error."
This issue typically occurs when the user deletes a curve from the plant model and the curve exists in the controller model and visa-versa. If the user wishes to simulate a situation where the plant model does not have a curve, it is advisable to keep the curve in the plant model and use curve operation to change the gain to a very small number (nearly zero).
Keywords: DMCplus Simulate
Floating Point Error
Model Mismatch
References: None |
Problem Statement: What is the default setting used for the normal and fast frequency of PID loops added using PID Wizard on the Production Control Web Server (PCWS)? | Solution: Any PID loop added through PID Wizard will take the default settings for normal and fast scan of 60 and 15 second respectively. To change the frequency of the fast scan for any PID loop, access the loop settings through AspenWatch Maker Tools>Tag Maintenance>PID and double click the loop to bring up the detail page and the fast scan rate can be adjusted there. Once it is changed there, it will retain the same scan rate from that point forward.
Notice the normal scan rate can not be changed from the detail page. To change the normal scan rate, you need to re-import the loop through Tag maintenance>Import using a text file. Only then the normal scan rate can be changed. On this step, the previous IOGetDef entry will be removed and new IOGetDef entry with the new/corrected scan rate will be added without removing any PID loops history.
Keywords: PIDWatch
Aspen Watch
PID Loop
References: None |
Problem Statement: How is an APC project folder structured? What are those object.000000x? | Solution: Aspen Process Controller Builder (aka APC Builder) is the newest interface and technology developed by APC R&D. It was introduced in V7.2 release. APC Builder wraps up legacy DMCplus products (Such as Model, Build, Simulate, Smart Audit; along with Extract and Collect commands and APC Manage for online deploying), making this product a single environment.
APC Builder differs from the DMCplus legacy products since the APC Builder creates a folder which contains all the project information. So, the question here is what is the file structure of an APC Project?
Let’s start by opening a test project folder using APC Builder.
As you may see in the navigation panel, this project has 2 applications (col5x3local and Master), one dataset (MaytoOct2014) and one model (3TRC); while in the workspace we have MaytoOct2014 dataset, 3TRC model and col5x3local application.
Now, let’s open the TEST project folder using Windows Explorer.
You see there are three.folder. 000000000x folders., one .recycle folder, one .temp folder and one .workspaces folder.
APC folder structure is as follows:
· folder. 0000000001 contains all the information of the APPLICATIONS on the navigation panel
· folder. 0000000002 contains all the information of the DATASETS on the navigation panel
· folder. 0000000003 contains all the information of the MODELS on the navigation panel
· .recycle contains all the information of the Recycle Bin (Deleted items from workspace)
· .temp contains all temporal files that are created when working with the project
· .workspaces contains all information of the WORKSPACE. This includes datasets, models and applications that may be there.
Let’s start with folder.0000000001 entity.
This folder has two object.000000000x subfolders. These subfolders are the two applications (Col5x3local and Master, respectively)
When we go to object.0000000001, you can see .data.000000000x, .info.000000000x and .raw.000000000x files. These files contain the information of Col5x3local application.
Now, if we go back to the root folder, and open .folder.0000000002 folder, we see there is only one object entity, which is the MaytoOct2014 dataset.
Digging in MaytoOct2014 dataset (.object.0000000002 folder), we see it has a new folder called .raw.0000000006. This folder contains all information of the vectors inside this dataset.
Going back to the root folder and opening .folder.0000000003 folder, we see it has only one object which is the 3TRC model.
So far, this is all for the navigation panel items. Let’s move on to the workspace items.
.workspaces also has .folder.0000000001 entity. APC Builder future roadmap includes the possibility of having several workspaces, each .folder.000000000x would be a workspace. Since at this moment, APC Builder can only handle one workspace, let’s open .folder.0000000001
You see .folder.0000000001 (Workspace one) has the same structure of the project root folder. . folder.000000000x subfolders are for applications, datasets and models accordingly.
Note: Do not attempt to manipulate any of these files/folders outside of APC Builder. It will most likely corrupt your project.
Keywords: APC project, APC Builder, APC project structure
References: None |
Problem Statement: What is the significance of the warning messages displayed when opening a CCF file edited with newer version of DMCplus Build in an older version of the software? | Solution: Every time a newer version of the software is released, it is possible that some of the CCF parameters from the older version have been deleted or some new CCF parameters have been added to the file structure. The warning message advices the users to check the CCF configurations and confirm that any specific parameter that is important to the DMCplus controller has not been deleted. An example of this would be the STAUTOPAIR feature. This feature is not available in V7.1 and was only added to DMCplus in V7.3. Therefore when the use converts a CCF file from V7.1 to V7.3 or higher, and the controller has SmartStep/Calibrate enabled, this parameter will be automatically added to the CCF file. Now, if the user opens the CCF in V7.1 again, DMCplus Build will not recognize the STAUTOPAIR parameter and delete this parameter.
It is also possible that some parameters important in V7.1 might have been made obsolete and deleted in the newer versions. For example, the SmartStep Single testing option with Pulse and without Pulse (this option was deleted in V7.3CP3). This parameter would be deleted from the CCF when it is opened in a version higher than V7.3CP3. Therefore, when you reopen the CCF from newer version in V7.1, the parameters would be recreated. However, their setting will revert back to defaults instead of the values that were originally used. The warning message is just to ensure that the user know this will happen.
Keywords: CCF
Build
Version Compatibility
References: None |
Problem Statement: aspenONE automatic configuration fails during installation if the domain account password includes special characters. The password is not correctly processed and services cannot be automatically started. | Solution: /Workaround
1. Read all instructions before executing the instructions.
a. IMPORTANT: If the administrative access popup displays during any of the instructions, the access will have to be allowed for a successful upgrade to be performed.
2. Open a Windows Command prompt.
a. Change directories to the C:\Program Files\Common Files\AspenTech Shared\Tomcat<version>\appdata\solr\conf directory.
b. Execute the command (replace myPa$$word with your own password):
password “myPa$$word”
c. The utility will return a result similar to the following:
myPa$$word:aasd989su7f
d. Copy everything after the :
3. Edit the C:\Program Files\Common Files\AspenTech Shared\Tomcat<version>\appdata\solr\conf\AspenSearchSolrSecurity.xml file.
a. Replace the value of the password entry with the value copied.
b. Save the file.
4. Restart the Tomcat service.
5. Verify aspenONE is functioning correctly.
Fixed in Version
CQ00561790: To be announced
Keywords: aspenONE, Search, SOLR, Security
References: None |
Problem Statement: How does the controller handle steady state (SS) limit ranks of 9999 when in SmartStep or Calibrate mode? | Solution: When an APC application is in Control mode, any CV or ET limit that has a SS rank of 9999 is excluded from the Steady State feasibility and optimization calculations. However, when the controller is switched to SmartStep or Calibrate mode, all 9999 ranks will be changed to the highest available numerical value rank (less than 999) in the application. For example, it the highest existing ranking is 300, then the 9999 ranking will be changed to 301 internally.
As a result, the engine will include these ranks in the SS feasibility and optimization calculations. Thus, it may be necessary to widen those limits out when the application is in SmartStep or Calibrate mode so that the engine does not try to bring them back to within limits. If it is not possible to do so, consider turning it OFF these ETs and CVs in order to prevent the engine from taking undesirable actions.
Keywords: SmartStep
Calibrate
Ranking
References: None |
Problem Statement: What type of error is displayed in the Bounded Derivative Network (BDN) training interface in APC Builder? | Solution: The error value calculated and displayed during BDN training in APC Builder is the standard deviation of the normalized model prediction error for the regression. The error is defined as-
Where, n is the number of samples in the dataset and norm_e is the normalized error and is defined as-
Keywords: Nonlinear controller
Apollo
Bounded Derivative Network (BDN)
References: None |
Problem Statement: What causes the MES Cluster Wizard to display the message:
"Failed to open cluster "clustername". Could not contact the specified cluster. Please ensure the name refers to a valid existing cluster. Also ensure that at least one of the cluster components is running and properly connected to the network.
Retrieving the COM class factory for component with CLSID {F2E606E5-2631-11D1-89F1-00A0C90D061E} failed due to the following error: 80040154 Class not registered (exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)" | Solution: Enable the options Failover Cluster Automation Server and Failover Cluster Command Interface in the Microsoft Failover Clustering Tools.
Keywords:
References: None |
Problem Statement: Unable to start TSK_PV task in IP.21 Manager. The following error message is received:
"Error advancing to the end of output file, error code=131, dwCurrentPos=$d" when trying to start TSK_PV task" | Solution: The external task TSK_PV is unable to start due to the output file being too large in size. In order to resolve this issue, browse to Group200 folder, either rename or delete TSK_PV.OUT. It is recommended to perform a search in the computer for the file.
Keywords:
References: None |
Problem Statement: Before installing the 64-bit version of the Aspen InfoPlus.21 product family, users mistakenly may install the 64-bit version of Java 1.7.0_45 instead of the required 32-bit version of Java. As a result, the installation kit complains that 32-bit version of Java is not installed; however before installing the 32-bit version of Java, you first have to remove the 64-bit version of Java. This article explains how to remove the 64-bit version of Java. | Solution: In order to uninstall Java 64 bit go to Start\Control Panel\All Control Panel Items\Programs and Features. Select the Java component and click Uninstall.
Make sure you uninstall all Java Programs (Java X Update and the Java Development kit).
You may choose to use a third-party tool to verify there are no Java related keys left in the registry.
Reboot the server.
Go to http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase7-521261.html and download the Java SE Development Kit 7u45.
After installing the 32-bit version of Java, continue with the Aspen installation process.
Keywords: Java version
JRE
JDK
32 bits
64 bits
References: None |
Problem Statement: In V8.5 when you enable Store and Forward in the Device Record and set IO_STORE_ENABLE to 'Yes' and then turn on IO_DEVICE_PROCESSING to 'ON' the notice that the IO_STORE_ENABLE automatically changes to 'NO' | Solution: This is caused when Cim-IO has been configured manually instead of using the I/O wizard/Connection Manager in the Infoplus.21 Administrator.
To resolve this issue, install the latest Aspen Cim-IO patches and use the I/O Wizard to recreate the logical device.
Keywords: IO_STORE_ENABLE
Store and Forward
Cim-IO
Cimio
References: None |
Problem Statement: After upgrading Aspen Infoplus.21, the Aspen Configuration Excel add-in will not update records or create new ones and produces a message like the following:
'Invalid RECORD value "<name of a record>" | AspenTech.SQLplus.DataProvider'
How can this be fixed? | Solution: The Aspen Configuration Excel Add-In leverages some Aspen SQLplus Stored Procedures (records defined against ProcedureDef). The record names begin with AtXl, and some examples include AtXl_DbSchema and AtXl_UpdateTags. Save a snapshot of the database (for safety reasons) and then delete the ProcedureDef records that begin with AtXl. The next person who uses the Aspen Configuration Excel Add-In will cause the Stored Procedures to be automatically recreated, and this will eliminate the problem.
Keywords:
References: None |
Problem Statement: How do you create a dump file for a process that is hanging or is frozen? | Solution: Recent versions of Microsoft's Windows operating systems simplify the collection of dump files.
Using the Windows Task Manager highlight the process with the problem in the Processes tab, right-click, and select Create Dump File from the menu.
This generates a file named process.dmp file to the folder C:\Users\<user>\AppData\Local\Temp; where <user> is the name of the user running the program.
Make sure you use the right type of Windows Task Manager(Taskmgr,exe) to collect the dump of the program you intend to analyze, depending if the program is 32 or 64 bit.
If the program is 32 bit then use the Taskmgr,exe n the C:\Windows\SysWOW64 folder to capture the crash dump.
If the program is 64 bit then use the Taskmgr,exe in the C:\Windows\System32 folder to capture the crash dump.
To find out what if the program is 32 or 64 bit add the Platform column in the View -> Select columns menu in Task Manager, like:
This will show you if the process you're interested in is 32 or 64 bit, for example for iexplore.exe task manager would show this is a 64 bit application.
Collect this process.dmp file and send it to Aspen for analysis.
Keywords: process, freeze, troubleshoot, dump
References: None |
Problem Statement: After installing AMS Desktop Applications you discover that the Aspen Process Data tab appears in the Excel Ribbon bar but Aspen Configuration tab is either missing or does not have the InfoPlus.21 tool bar. | Solution: Aspen InfoPlus.21 Configuration Add-in is an administration tool and is not installed as part of the Desktop Applications products.
Before v8.7 you must select "Aspen InfoPlus.21 Administrator" (under the Administration Tools) in the installer in order to get the Aspen InfoPlus.21 Configuration add-in.
In v8.7+ you must select Aspen Administration Tools in the installer in order to get the Aspen InfoPlus.21 Configuration add-in:
Keywords: Office
Ribbon
Desktop Applications
Configuration Wizard
absent missing not there
References: None |
Problem Statement: What is the difference between Web service and DCOM protocols used in Aspen ADSA? | Solution: ADSA has two available protocols to be used for connecting Aspen Info plus 21 server to its clients. The two protocols are- DCOM and Web service.
This article discusses about difference between DCOM & Web service protocols.
DCOM is the original protocol of ADSA. Web Service was introduced later, this should be used when there is a firewall between the ADSA Directory Server and the clients. It has an IIS component: ADSAWebService (%SystemDrive%\inetpub\wwwroot\AspenTech\ADSAWebService).
DCOM uses a ranges of default ports –by-design behavior-; even if there is no firewall in between, and hence it’s suggested to use Web Service.
Keywords: Difference between ADSA protocols
ADSA
DCOM
Web service
References: None |
Problem Statement: "Error while checking out license BATCH21_AREAS" while using Batch Query tool on a client machine after migrating from Perpetual license to Token License Server. | Solution: If you have already follow solution article: Why do I receive the "Unable to acquire BATCH_21 Areas" message in Aspen Production Record Manager? and your issue is still not resolved then you may try this solution.
To resolve this issue configure the SLM Configuration Wizard on Aspen Production Record Manager Server to acquire license from Token license Server. User does not need to configure SLM Configuration Wizard on a client machine, as Batch Query tool will be acquiring licenses through Aspen Production Record Manager Server.
Keywords: SLM_BATCH21_AREAS
Aspen Production Record Manager
Batch.21
Token
Perputual
Migration
Batch Query
References: None |
Problem Statement: Getting "Unable to acquire SLM_RN_PMR_APRM64PRDSRV license" when launching Aspen Production Record Manager 64-bit | Solution: In versions V7.1 and higher of Aspen Production Record Manager, licenses based on the number of servers i.e., License will be acquire on Aspen Production Record Manager Servers and not on specific client machines.
First, the user needs to verify if the following License keys are available in the SLM Server.
RN_PMR_APRM64PRDSRV :- Aspen Production Record Manager 64-bit
RN_PME_APRM64CLSSSRV :- Aspen Production Record Manager 64 bit Cluster
Aspen Production Record Manager 64-bit will use the SLM Configuration Wizard 64-bit to acquire Network or Standalone licenses.
Note: Any aspenONE 64 bit application will use the C:\Program Files\Common Files\Aspentech Shared location and the SLM Configuration Wizard 64 bit for the Standalone license file.
Keywords: RN_PMR_APRM64PRDSRV
Aspen Production Record Manager
Batch.21
Token
SLM
64-bit
Migration
Batch Query
References: None |
Problem Statement: How to mass update Aspen Process Explorer graphics font size. | Solution: After upgrading Process Explorer Graphics to higher version there are possibilities that Graphics Text might be visible clearly.
User will need to reduce or increase the Font Size of their Graphics. There are various possible ways to update Graphics Text Font.
1. Start Aspen Process Graphics Editor.
2. Open your Graphics in Graphics Editor.
3. Single Text Box Updating:
a. User can select single Text Box and increase or Decrease the Font Size from Menu Tool bar.
4. Multiple Text Box Updating:
a. Highlight all the Text Box by Clicking and dragging the mouse cursor from one end to another.
b. Press CTRL key and unselect the Text Box which you do not want to modify.
c. Increase or Decrease the Font size from Tool bar menu.
5. Multiple Text Box Updating through XML:
a. Click File->Export XML
b. Save the XML file
c. Open the XML file in notepad
d. Use Find and Replace option to replace the Font Height “XXX�
e. Save the XML file and then open XML file in Graphics Editor
f. Save the Graphics to be used in Process Explorer.
Keywords: Font Size
Graphics
Truncated
Height
Process Explorer
Text
References: None |
Problem Statement: When you open a case file, a number of log files will get written to disk by default. This solution shows how to stop logging to external logs (eg. applog.txt, prclog.txt, sqllog.txt, eslog.txt). | Solution: 1. Open the case file
2. Go to the Developer tab | Command Line
3. Type: APPDATA
4. Find out the rows of "(LOGPRINT) Write to External File? [Y|N]"
5. Set N
6. Press F8 to save the table
7. Save the case file
Keywords: LOGPRINT
Log files
SCM
References: None |
Problem Statement: After starting the aspenONE V8.7 Supply Chain Management suite upgrade process, why does the installer exit without any notification? | Solution: The issue occurs when starting the upgrade process in the Supply Chain Management (SCM) V8.7 installer. The installer will disappear without any notifications due to the different features within the SCM V8.7 bundle that are not in V8.6.
As a workaround, you will need to uninstall SCM V8.6 prior to installing SCM V8.7.
Keywords: SCM, aspenONE V8.7
References: None |
Problem Statement: How do I review who made changes to an order in Aspen Fleet Optimizer? | Solution: The Audit Log tracks all changes that are made to a shipment from the time the shipment is created to the time the shipment is considered delivered. The Audit Log captures the user information, the date and time, the origin, and the modifications that are made to the shipment. The user will also have a choice of viewing the Audit Log or printing the Audit Log. The Audit Log can be accessed from the main Aspen Fleet Optimizer screen, the Replenishment Planner, or by right mouse clicking on a shipment in Replenishment Planner. There is also an Audit Log Report that can be printed for a particular shipment.
Keywords: None
References: None |
Problem Statement: How can I review who made changes to an order in Aspen Fleet Optimizer? | Solution: The Audit Log tracks all changes that are made to a shipment from the time the shipment is created to the time the shipment is considered delivered. The Audit Log captures the user information, the date and time, the origin, and the modifications that are made to the shipment. The user will also have a choice of viewing the Audit Log or printing the Audit Log. The Audit Log can be accessed from the main Aspen Fleet Optimizer screen, the Replenishment Planner, or by right mouse clicking on a shipment in Replenishment Planner. There is also an Audit Log Report that can be printed for a particular shipment.
Keywords: None
References: None |
Problem Statement: What is the load lock flag inside Aspen Fleet Optimizer used for? | Solution: The Load Lock flag (check box) at the top right of the screen allows the user to manually identify expected deliveries as already delivered shipments. With this box checked, the user can click on an expected delivery using the right side mouse button and mark it delivered. Aspen Fleet Optimizer will automatically add the delivery to the inventory. If this flag is not selected, Aspen Fleet Optimizer will automatically calculate what shipments should have been marked delivered. When forecasting by inventory only, Aspen Fleet Optimizer may require the user to use Load Lock to identify delivered shipments if Aspen Fleet Optimizer is unable to judge what was delivered.
Keywords: None
References: None |
Problem Statement: What are some variables that could cause an exception in Data Quality Manager? | Solution: There are many variables that could create exceptions and not allow inventory and sales data to reconcile. Sales figures may be out of range or erroneous, inventory figures may be incorrectly measured or transposed, a shipment may be late, or sales may skyrocket. Despite the number of possible cause combinations for an exception, there are only three areas where exceptions are created: sales figures, inventory figures, and shipments. When processing an exception, the user must look to each of these areas to find the figures that hinder a proper reconciliation.
Keywords: None
References: None |
Problem Statement: What parameters control exceptions in the Data Quality Manager? | Solution: In Data Quality Manager Processing, a customer's sales and inventory data is checked through a series of reconciliation tests. If Aspen Fleet Optimizer cannot reconcile a customer's newly gathered sales, inventory, and delivery information with historical information, that customer's information is flagged as an exception and highlighted in red. More specifically, exceptions happen if the pre-established parameters for sales and inventory fluctuations are exceeded. For example, if the user sets the inventory test range at 10 % inside of Product Setup and the reported inventory deviates from the expected inventory by more than 10 %, plus or minus, an exception is generated.
Keywords: None
References: None |
Problem Statement: High Performance Trend (HPT) is a new plotting tool available in the PCWS for version V8.4 and later. The tag search feature of the HPT may not work after a typical installation of the APC software. Here are some of additional settings that may be needed to get the tag search working. | Solution: If the HPT tag search function is not working on a new installation of PCWS, check for the following:
- Make sure that .NET Framework 3.5 HTTP Activation component is installed on the PCWS
- Make sure that the AspenDisPatchService in Application Pools under IIS Manager has same identify (username/password) as the account that the software is installed
- Make sure that the ISAPI filter of the IIS is set to c:\Windows\Microsoft.NET\Framework\v4.x.xxxxx\aspnet_filter.dll. Sometimes there is an extra "\" before the file name.
Remember any time a tag is added into the IP.21 database, the HPT database needs to be rescanned by going to PCWS>Configuration>HPT Search Configuration and then hit the Update button
Keywords: HPT
Tag search
References: None |
Problem Statement: Model plots are not displayed in the Model View page for a DMCplus controller; the following error message is displayed instead. | Solution: The most common cause of this problem is the use of " (double quotation) symbol in the Engineering Units or Description section of one or more of the independent or dependent variables of the controller. To fix this problem, the user would need to remove the double quotation symbol from the Engineering units (or Description) for the concerned tag names from the model (MDL) file. This can be done by fixing the Engineering Units for the concerned tag in the DPP file used to build the original model and re-export the updated model. If the original DPP file does not exist or is inaccessible, the user could import the existing model into DMCplus Model, re-assemble a new model with the curves from the original model and edit the tag properties to make the desired corrections.
Keywords: DMCplus Model
PCWS
IndexOutOfRange
References: None |
Problem Statement: Running Install Database Configuration (IDC) on one or more aspen watch servers could potentially freeze up the PCWS and cause problems for the users logged into PCWS. This occurs if ADSA settings pointing to Webserver is not disabled before running the IDC utility. | Solution: IDC is a program which requires restarting the IP.21 database and adds Aspen watch records to the IP,21 database.
The WebServer uses the ADSA configuration to connect to the IP21 database and retrieve the Aspen Watch history data. If the IP21 database is down, the Web Server would continuously keep trying to connect to the configured database and could become unresponsive.It is therefore recommended to remove the AW/IP21 data source in ADSA settings before starting the IDC run. This will avoid the potential freezing of PCWS.
Please remember to re-add the AW/IP21 data source back into the ADSA settings once the IDC run is complete and the IP21 database is back online.
Keywords: ADSA
Web Server
AspenWatch
Install Database (DB) Config
References: None |
Problem Statement: What can be done to overcome a user validation failure when launching APC web interface? | Solution: Follow the below suggestions to avoid running into this issue:
· Match the account that starts the AFW Security Client Service to the Aspen APC Web Provider Data Service. That account has to have full rights to get the Active Directory.
· Review the permissions of the path and file found in ProgramFiles(x86)\AspenTech\LocalSecurity\Access97\AFWDB.mdb.
· Make sure the PCWS page is added to the Local intranet sites. (Open IE and go to the Internet Options / Security / Local Intranet).
Keywords: PCWS, APC web interface, user not validated
References: None |
Problem Statement: How to set an automatic fileset back up based on the status change in Aspen InfoPlus.21 Administrator. | Solution: This article describes the procedure of creating an automatic fileset back up based on a status change. The fileset should be backed up once the status changes to SHIFTED.
To set the automatic back up for filesets, select YES for the Save shifted option for the repository that needs to be backed up.
In Aspen InfoPlus.21 Administrator, the path where the shifted fileset will be saved after backing up is found in the shifted location column.
Setting the options in this manner will start backing up the filesets once the file set status changes to Shifted.
Keywords: Automatic back up, Fileset back up, IP21 administrator, IP21
References: None |
Problem Statement: Unexpected service termination for NobleNet Portmapper for TCP (portserv.exe) service. How do i recover from it without restarting Aspen Infoplus.21?
NobleNet Portmapper for TCP (portserv.exe) service is required for the following services to function properly: Aspen Infoplus.21 Task Service and related infoplus21_api_server.exe processes. Portserv.exe is required to correctly map requests from IP.21 clients to the various IP.21 infoplus21_api_server processes. When it stopped, IP.21 clients (such as Aspen Process Explorer) will not be able to connect properly.
Symptoms:
· IP.21 Administrator: "Do retry" error message when attempting to browser the IP.21 server
· Aspen Process Explorer: When attempting to trend a tag, similar message may appear "IP21 is not currently running on XXX or is not accessible". | Solution: 1. Restart NobleNet Portmapper for TCP (portserv.exe) service.
2. Restart Infoplus.21 Task service.
3. Open IP.21 Manager and restart the following infoplus21_api_server.exe processes i.e. TSK_APEX_SERVER, TSK_ADMIN_SERVER, TSK_EXCEL_SERVER, TSK_DEFAULT_SERVER TSK_BACTCH21_SERVER and TSK_ORIG_SERVER.
Keywords:
References: None |
Problem Statement: The following error(s) are received when attempting to connect to Aspen OPC DA Server.
COM/OPC error 0x80080005 on CoCreateInstance();
Could not connect to server 'Aspen.Infoplus21_DA'; | Solution: The Aspen InfoPlus21 DA Server must be appear in DCOM for connection to the Aspen OPC DA server. The following procedure can be used to add the Aspen InfoPlus21 DA Server to DCOM
1. Open a command prompt
2. Browse to the directory \Program Files\AspenTech\InfoPlus.21\db21\code
3. Enter the command ip21da_server.exe /register
4. Verify that Aspen InfoPlus21 DA Server appears in DCOM.
Keywords: InfoPlus.21OPC-DA Server;
Could not connect to server 'Aspen.Infoplus21_DA';
COM/OPC error 0x80080005 on CoCreateInstance();
References: None |
Problem Statement: Getting error "Unable to acquire SLM_RN_PME_IP64_PRDSRV license" on InfoPlus.21 64-bit Server after starting a Database. | Solution: When starting InfoPlus.21 64-bit Database, users may notice the license error message listed above. The first step is to verify if following License keys are available in SLM Server:
1. Verify if below License Keys are available in License Server. Follow Solution article What is the SLM License Profiler and how do you use it?
RN_PME_IP64_PRDSRV :- Aspen InfoPlus.21 64-bit
RN_PME_IP64_CLSSSRV :- Aspen InfoPlus.21 64 bit Cluster product
If above license keys are not available then request for new license file through our support website, please follow solution article: How can I obtain a new license file?
2. If the License keys are available, then you should use SLM Configuration Wizard 64-bit to acquire licenses. InfoPlus.21 64 bit will use SLM Configuration Wizard 64-bit to acquire Network or Standalone licenses.
Note: Any aspenONE 64 bit application will use C:\Program Files\Common Files\Aspentech Shared location and SLM Configuration Wizard 64-bit for Standalone\Network license file.
Keywords: RN_PME_IP64_PRDSRV
RN_PME_IP64_CLSSSRV
64-bit
64 bit
SLM
License
Acquire
References: None |
Problem Statement: What is the purpose of the jsn_tcpip_server process in InfoPlus.21 server? | Solution: On the InfoPlus.21 server, TSK_SQL_SERVER listens on a socket (usually 10014) for any SQLPlus client trying to connect. Once a client connects, the TSK_SQL_SERVER spawns an NT task called jsn_tcpip_server to service the SQLPlus client and one jsn_tcpip_server task will be started for each client.
Keywords: jsn_tcpip_server
TSK_SQL_SERVER
SQLPlus
References: None |
Problem Statement: How can I configure Aspen Watch when changing Aspen Process Controller host? | Solution: Follow this procedure:
· Save an InfoPlus21.snp as a backup.
· Go to Aspen Watch Maker / Actions menu / Online Host Connection add the new one (as Type: RTE, the Port needs to be open); and stop the controller collection.
· Stop the Aspen APC Performance Monitor Service.
· Via IP.21 Administrator change AW_CTLDef / <ControllerName>_APC / AW_HOSTNAME to the new one and AW_AVAILAPPSDef / AW_AVAILABLE_APPs / AW_NUM_CHILDREN / AW_HOSTNAME to the new one.
· Restart the Aspen APC Performance Monitor Service.
· Go to Aspen Watch Maker and restart the controller collection.
· If required, restart IP.21 Manager External Task TSK_ACP1.
Keywords: Aspen Watch, Aspen Process Controller, host, RTE
References: None |
Problem Statement: When using the perpetual license scheme, a V7.3 IP.21 system may get a 'license denied' message error and the database is locked. | Solution: Starting with V7.3, IP.21 system in AspenWatch Server uses the "embedded" license type. To verify that the IP.21 system is on the embedded key, shut down IP.21 and open up IP2.1 Administrator. Ignore the warning message about server not running. Right click on the database and select "Set License Key Type"
The license key type should be set as embedded for AspenWatch IP.21 Database. Restart the database and check the License Status once again to confirm that the correct licenses have been acquired.
Keywords: license denied
AspenWatch
InfoPlus.21
References: None |
Problem Statement: Where are the built-in report kept and can they be modified? | Solution: The following built-in reports can be accessed from Production Control Web Server (PCWS).
· Constraint
· Management
· Performance
· Step Testing
These reports are generated from the following stored procedures in IP.21.Â
AW_WEBRPT_KPISTR
AW_WEB_CONSTRAINT_RPT
AW_WEB_MGMT_REPORT
AW_WEB_PERFORMANCE_CTL
AW_WEB_PERFORMANCE_DEP
AW_WEB_PERFORMANCE_FFW
AW_WEB_PERFORMANCE_MAN
AW_WEB_SMST_REPORT
AW_WEB_TESTAGENT_RPT
The source code for these procedures are not provided to the users and AspenTech does not recommend modifying them. If these are modified, there is no guarantee that other things that use these procedures would function as expected. Moreover,the changes would get overwritten every time Install Database Configuration utility is ran or the system is upgraded or patched.
Keywords: Built-in report
AspenWatch
References: None |
Problem Statement: On standard Process Explorer trend plots, how could one add static lines for upper and lower limits (i.e. IP_HIGH_LIMIT and IP_LOW_LIMIT) for a tag? In order to display a trend line of any type, there must be a tag with history to plot. There is no "history" for the upper and lower limits, they are simply constants. This article provides some suggestions. | Solution: Versions of Process Explorer prior to 5.0:
Create two tags and store constant values that update very slowly, therefore not generating much history. One can also choose the "Extrapolate" checkbox, which flat lines a value forward to current time, if the value has scrolled off the timeline. Plot the "data" tag and the 2 newly created tags for the limits.
Version 5.0 and later:
Create a "dummy" tag in the database that updates with a value of 0 every minute or so into history. Using Ad-Hoc calculations, (see solution 110471 for complete description), plot the dummy tag plus the high or low limit. For example if TagA has an IP_HIGH_LIMIT of 10, the Ad-Hoc calculation to display the high limit of 10 would be: =dummy+10.
Alternate Solution Suggested By A User:
One need not even create a "dummy" tag, merely multiply any existing tag by zero and then add any constant utilizing the Ad-Hoc calculations per the aforementioned description; saves creation of a tag that writes to history. -Aeric Arreguin of Solvay Chemicals, Inc.
KeyWords
limits
Keywords: None
References: None |
Problem Statement: On standard Process Explorer trend plots, how could one add static lines for upper and lower limits (i.e. IP_HIGH_LIMIT and IP_LOW_LIMIT) for a tag? In order to display a trend line of any type, there must be a tag with history to plot. There is no "history" for the upper and lower limits, they are simply constants. This article provides some suggestions. | Solution: Versions of Process Explorer prior to 5.0:
Create two tags and store constant values that update very slowly, therefore not generating much history. One can also choose the "Extrapolate" checkbox, which flat lines a value forward to current time, if the value has scrolled off the timeline. Plot the "data" tag and the 2 newly created tags for the limits.
Version 5.0 and later:
Create a "dummy" tag in the database that updates with a value of 0 every minute or so into history. Using Ad-Hoc calculations, (see solution 110471 for complete description), plot the dummy tag plus the high or low limit. For example if TagA has an IP_HIGH_LIMIT of 10, the Ad-Hoc calculation to display the high limit of 10 would be: =dummy+10.
Alternate Solution Suggested By A User:
One need not even create a "dummy" tag, merely multiply any existing tag by zero and then add any constant utilizing the Ad-Hoc calculations per the aforementioned description; saves creation of a tag that writes to history. -Aeric Arreguin of Solvay Chemicals, Inc.
KeyWords
limits
Keywords: None
References: None |
Problem Statement: How can I tell which Aspen PIMS features I currently have checked out? | Solution: In Aspen PIMS click on HELP, then "About Aspen PIMS", then click on "Licensing Information". A new dialog box will open which provides a listing of all the features which are currently checked out. An example is shown below.
Keywords: license
feature
References: None |
Problem Statement: What does the indicator "A" represent in Primal/Dual | Solution: Report
Solution
In the Primal/Dual Solution Report, for some rows there will be an indicator “A” before the row index. It represents equality constraints with marginal value equal to zero.
Keywords: Indicator "A"
Primal/Dual
References: None |
Problem Statement: When running the SLM Configuration Wizard, the last screen shows error an "Access Denied" error. | Solution: Running the SLM Configuration Wizard requires Administrator rights to write the configuration settings to the Windows registry. You can either log in as an Administrator or right-click on the SLM Configuration Wizard and selecting “Run as administrator.”
If the issue persist, please contact AspenTech Support.
Keywords: SLM error, SLM not finishing
References: None |
Problem Statement: Should Software License Manager (SLM) Server be upgraded when installing any aspenONE V8.7 products? | Solution: As general guideline, AspenTech recommends to always upgrade to the latest version of SLM Server from the latest version of aspenONE you are installing. When installing any products from aspenONE V8.7 DVD, you should also upgrade SLM Server.
Keywords: 8.5.3
V8.7
SLM Server
Upgrade
Sentinel Version
References: None |
Problem Statement: During the Aspen License Deployment Assistant, you get an error message: "The specified license server version is below the minimum required for the version of the Aspen License Deployment Assistant." | Solution: This message may occur when you are running an older version of the Software License Manager (SLM) server. Aspen License Deployment Assistance requires SLM Server from the aspenONE V8.5 or higher.
To resolve this problem, please upgrade SLM server to V8.5 or higher, then install the Aspen License Deployment Assistance tool.
Keywords: SLM Server
Aspen License Deployment Assistance
References: None |
Problem Statement: | Solution:
Keywords:
References: None |
Problem Statement: Can commuting be disabled on a client machine? | Solution: Commuting cannot be disabled on the client machine.
However, a work around is to delete the SLM Commute tool from the computer. To do so, follow these steps:
1) Find and delete SLMCommute.exe from:
C:\Program Files (x86)\Common Files\AspenTech Shared\SLM Client Tools (aspenONE v8.0 and higher)
C:\Program Files (x86)\Common Files\Hyprotech\SLM Client Tools (aspenONE v7.32 and lower)
2) Go to Start > All Programs > ApenTech > Common Utilities folder and delete the SLM Commute shortcut.
NOTE: When the SLM Tools are upgraded or repaired, the SLM Commute tool will be added back to its folder. The above steps will need to be repeated after upgrading/repairing the SLM Tools.
For a permanent solution, Aspen can disable commuting on your network license. However, all computers will not be able to commute a license with this solution. To have commuting permanently disabled on your network license, please submit a license request from Aspen's Support Site.
Keywords: Disable Commuting, SLMCommute.exe
References: None |
Problem Statement: What all steps need to be considered before migrating the License Server to a Virtual machine? | Solution: The following steps needs to be considered while migrating SLM License server to a Virtual machine.
1. Do you have a Dongle based license or a Dongle-Free License?
a. How to check if your license file is a Dongle-Free or Dongle based license.
i. Open License file in a notepad
ii. The first line in license file will display filename = “lservrc_080_xxxxxx” or “lservrc_XXX_XXXXXX”
iii. If the license file name has 080 then your license file is Dongle based, otherwise it’s a Dongle-Free license
2. Does your Virtual Machine supports USB ports?
a. If your Virtual Machine does not support USB ports then Dongle based license will not work for your Virtual machine, please follow solution to get Dongle- Free License: How can I obtain a new license file?
3. What operating System is supported for SLM License server on Virtual machine?
a. Download Software License Manager V8.7 Installation Guide to find the supported operating system and Hardware requirements.
Keywords: Virtual Server
SLM Server
Migration
References: None |
Problem Statement: What information do I need to provide when submitting license usage logs to AspenTech for processing? | Solution: NOTE: To avoid having to manually submit license usage logs, AspenTech recommends using the Auto Upload Tool (AUT), which automates this process. See KB130332 for details.
When manually submitting license usage logs, you will be required to provide the System Name for the license file and Server Name for the server in which the license is installed. This information is needed for AspenTech to maintain accurate records for your company’s usage logs.
System Name Verification:
AspenTech verifies your System Name with the license file that is currently installed on your license server. Please submit your license file along with the usage logs for verification. We recommend compressing both license and usage logs in a single file (zip format recommended).
To obtain your currently installed license file:
1. Go to Program Files(x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT (or Program Files\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT for 32-bit versions of Windows) and locate the file named “lservrc” (no extension), as seen in the screenshot below:
2. Copy the lservrc file and submit along with the usage logs.
3. AspenTech will verify your System Name by looking at the last field on the first line of the license file. For example:
NOTE: If you provide a different license file than the one specified above, AspenTech may not be able to verify your System Name.
Server Name Verification:
The Server Name can be obtained and verified by AspenTech directly from the same license usage logs you are submitting. The license Server Name can usually be seen in the first line of the usage log. In the example below, the Server Name is “LICENSESERVER1”
# Startup Sentinel RMS License Manager v8.4.0.900 Fri Feb 22 10:04:59 2014 1392995039 LICENSESERVER1 1 2328
Submitting Usage Logs for Multiple License Servers:
When submitting usage logs for multiple servers, please create separate compressed files (zip format recommended) for each server. Each compressed file must contain the license and usage logs corresponding to each license from each server.
Keywords: System Name Server Name Verification
Usage Logs
AUT
References: None |
Problem Statement: Error "Unable to commute because SLM Commuter must be initialized..." when attempting to use SLM Commute. | Solution: In aspenONE V8.0 and higher, you must initialize the licenses on your machine before you are able to commute. This task can be accomplished with the SLM Configuration Wizard:
1. Go to C:\Program Files (x86)\Common Files\AspenTech Shared
2. Locate the SLMConfigWizard.exe and right click on it
3. Select, "Run as administrator"
4. Configure the Wizard to point to the license server. See KB 134453 for details.
5. Open SLM Commute Tool to commute the product key
6. Run the Aspen product and then click file | about | License Information button
7. Verify the commuted license is working by seeing the a not "NO-NET" label under "License Server."
File | About | Licensing Information button
Keywords: SLM Commute Tool, SLM Configuration Wizard,
References: None |
Problem Statement: Using a laptop docking station that has it's own Ethernet Address may cause a dongle free license not to work. This may cause error
"Unable to acquire license" and "Error 18" | Solution: Dongle-free licenses could be locked to one of several unique identifiers on a physical computer. One of the unique identifiers may be the Ethernet Address of the computer.
Some docking stations have built in Ethernet Adapters. These adapters could have their own Ethernet address which could be different than the Ethernet address assigned to the laptop. If your dongle free license Ethernet lock information was obtained when your laptop was not connected to a docking station then there is a chance that the license file may not work if you plug your laptop into a docking station that has it's own Ethernet address.
The Windows ipconfig/all command can be used to determine if a docking station has its own Ethernet address. To execute, you will need to open a command prompt window from Start | Run. Then type "ipconfig/all" and hit enter:
When the ipconfig/all command is executed, it will list the TCP/IP configuration for all Network Adapters. If the docking station has an Ethernet Address, it will be listed under the docking station name.
Knowledge base article 135993 can be used to determine if your license is locked to the correct criteria.
Keywords: Ethernet, address, MAC, docking station, laptop, license, dongle-free
References: None |
Problem Statement: Commonly used terms regarding AspenTech licenses. | Solution: In this KB you will see a list of the terms we use during the installation and licensing procedure.
Locking Information: You might hear this when you request a new license. We use a specific component on your computer to lock the license to. Examples being Disk ID, Ethernet address, hostname. Before we can generate a license we need this information in order to lock a license to a specific component. An example of what locking information looks like is attached in this KB.
System Name: This is effectively an identifier for your license file. We use this to link each license file to a company or an account. The system name is stored in your license file and can be viewed by loading the license file into notepad or any other text editor.
Software License Manager (SLM): This is our license manager that allows you to manage your license using a graphical user interface. On your machine you will see this called SLM Tools.
SLM Server: This refers to our license server software. It allows you to install the license on a server. The users can then connect to the server and obtain the available licenses.
Standalone License: This refers to a license that is locked to a specific machine only. So if you have a laptop with one license then it will be classed as a standalone license.
Network License: This refers to a license that is installed on a central server and all the clients PC's connect to the server to obtain licenses.
Dongle Locked: This refers to a license locked to a USB Dongle Key. This does not replace a license file and does not contain a license file, it is only used for license file validation. It allows you to install the license file on a system of your choice, as long as the dongle is also plugged in. You still need a license file if you have a dongle.
Dongle Free: This refers to a license that is locked to a unique component on your computer. This type can be used for both network and standalone licenses.
Keywords: System name
Locking Information
dongle locked
network license
dongle free
SLM
Standalone license
SLM Server
References: None |
Problem Statement: The following solution lists some of the keyboard shortcuts that can be used in the Planning Board as of Aspen SCM V8.7.4. | Solution: Following are some of the shortcuts that can be used in the Planning Board:
1. Ctrl + Shift + L - Timing Link
2. Ctrl + Z - Zoom in
3. Ctrl + Shift + Z - Zoom out
4. Shift + Delete - Delete an Activity
5. F8 - Reset of PB Layout and Zoom
6. Ctrl + M - Move an activity
7. Ctrl + F - Find an activity(ies) based on Product, Facility, Time Period and/or Time Slice
(as shown in the screenshot below)
Keywords: PB
Keyboard Shortcut
References: None |
Problem Statement: Does AspenTech Officially Support USB Dongle-lock Licenses on Virtual Machines? | Solution: Virtual Machines usually require 3rd party hardware and/or software in order to recognize a USB device. Since AspenTech cannot verify that this 3rd party technology will work, we cannot officially support this environment.
We highly recommend exchanging your dongle-lock license for a dongle-free virtual machine license. In order to receive a dongle-free license, a license request from our Support Site is required.
However, we have seen customers follow this Virtual Machine/USB dongle deployment model, and we have seen it working without issues. The two cases to watch out for are:
1. While starting up Windows, the 3rd party technology that will emulate the USB drive may take a while to fully startup. Meantime, the SLM Server service might have already started, and is trying to load the license. If the 3rd party technology has not finished loading the dongle, the dongle will not be available, and it will fail to load the license. In order to load the license, you will to need restart the Sentinel RMS Service, after the dongle has been detected.
2. The emulated USB drive can go offline if there are temporary outages, which could make the server not issue licenses, as it cannot verify the validity of a license before issuing it to a client machine.
Keywords: Virtual Machine, License, Dongle
References: None |
Problem Statement: What happens when I unplug the USB Dongle from the SLM Server and plug it back in? | Solution: If the dongle is unplugged from the license server and then plugged back in, the connection between the dongle and the license breaks. You will need to reload the license.
To reload your network license, follow these steps:
1) Go to C:\Program Files (x86)\Common Files\Safenet Sentinel\Sentinel RMS License Manager\Winnt folder.
2) Run loadls.exe and click Remove.
3) Run loadls.exe again and click Add.
NOTE: A restart of the SLM License Manager service or a restart of the license server, does not fix the broken connection.
Keywords: Software License Manager
References: None |
Problem Statement: This knowledge base article describes how to determine if your license file is compatible with the 7.2 and 7.3 versions of aspenOne Manufacturing and Supply Chain Token-Term Install DVD. | Solution: The easiest way to determine whether a license file is V7.2 or V7.3 token compliant is to open the license file in question using the Notepad. If the SLM_IN_FNC_MSCTKUTL key is present, then this license file will support the V7.2 and the V7.3 Token-Term install. If the key is not present, please submit a request through the AspenTech Support Site.
KeyWords:
MSC V7.2
MSC V7.3
SLM_IN_FNC_MSCTKUTL
Keywords: None
References: None |
Problem Statement: Questions on setting up SLM reservation file
1. What is the limit for the number of users within a "group" in the SLM reservation file?
2. Is there a limit to the number of characters one can enter on a line describing a user? | Solution: Here are some of the Reservation file rules to follow:
1. Maximum of 256 groups and 1000 users in each group. Safenet has increased Group members from 256 in earlier SLM versions to 1000 in SLM release 8.0.6. This change is also reflected in release 8.0.6 of Wlsgrmgr program which is used to generate the reservation file.
2. Maximum of 64 characters per user name is allowed.
3. Add a "\" to signify the line continuation after about 100 characters to make the file more readable. There is no limitation on the number of characters you enter per line.
Keywords: Reservation
Group
References: None |
Problem Statement: The V8.7 Installation guide defines the recommended software for APS installation, but what are some of the minimum requirements that are supported? | Solution: 1) What is the minimum SQL Server Database version?
ANSWER: We support SQL Server 2008 R2 SP2 and above.
2) Which virtualization is supported?
ANSWER: Only Hyper-V based virtualization is supported.
3) What about the Operating System for the server? The installation guide says (see below) but what else is supported?
For Server Installation:
Windows Server 2008 R2 SP1 (64-bit)
Also supported:
SQL Server 2012 – Standard and DataCenter Editions
ANSWER: For Server: Windows 2012 Server is also supported.
For Client: Windows 7 and Windows 8.1 are supported. Our recommended OS is Win7 or Win8.1
64-bit with at least 16 GB of RAM.
Keywords:
References: None |
Problem Statement: How can I toggle between VOL and WGT for the units of measure, while publishing into the _CRDRUNS or the _RUNS tables? | Solution: From v8.7, the nature of publishing the _CRDRUNS and the _RUNS tables have changed.
Previously, the _CRDRUNS and the _RUNS tables would be published in volume, no matter whether the model is volume based or weight based.
The units of publishing the _CRDRUNS and the _RUNS tables are now concerned by two settings:
Model Crude Basis: This setting can be found in the Settings -> Model Settings tab
Crude Run Event Default: This setting can be found in the Settings-> Events Defaults tab
The fix implemented now takes both of these settings into account. So only if the Model Setting "Crude Basis" is set to WEIGHT and Events Default Crude Run Setting is set to WEIGHT, the results are published in weight, else the results are published in VOLUME.
The following table summarizes the above behavior in all possible combinations of the above two settings, and lists the difference in behavior against previous versions, and in v8.8. Additionally, the table shows the report writer query to be used in v8.8 to get the VOLUME and WEIGHT data. There will be a change in query needed only for the first case, where both the above settings are in WEIGHT
Crude Basis Crude Run Event Default _CRDRUNS/ _RUNS before v8.7 _CRDRUNS/_RUNS in v8.7 and above Report Writer Query to be Used in latest V88 (get both VOL and WGT data) Requires change to a RW Template? (Assume using ATDSOCrudeRuns in V7.3)
WGT WGT WGT WGT ATDSOCrudeRunsWeight (Read WGT data from _RUNS, automatically calculate VOL from WGT data) Yes
VOL VOL VOL VOL ATDSOCrudeRuns (Read VOL data from _RUNS, automatically calculate WGT from VOL data) no
WGT VOL WGT VOL ATDSOCrudeRuns (Read VOL data from _RUNS, automatically calculate WGT from VOL data) no
VOL WGT VOL VOL ATDSOCrudeRuns (Read VOL data from _RUNS, automatically calculate WGT from VOL data) no
Keywords: None
References: None |
Problem Statement: The Aspen Production Execution Manager (APEM) product has several third-party components that are integrated into it, like the JDK environment, which provides a Virtual Machine environment for Web Execution, and the Apache Tomcat Web server, which provides services to APEM such as broadcast management of Order and Phase status across all Workstations.
Sometime it might be necessary to change the port that Apache is using for communication. How do I change the port in Apache, and also all references to the port in APEM? | Solution: During installation you are asked to provide the port Apache is running on. The installation routine verifies the connection to Apache, and then configures APEM to talk to Apache on this port.
This solution will guide you through the steps necessary to make Apache listen on a different port, and reconfigure APEM to communicate on the new port. This example uses the default port (8080) as the starting point, and demonstrates changing it to a typical alternative port, 8888.
1. First, shut down APEM and Apache. Stop the Apache Tomcat Service.
2. From a Command Prompt use NETSTAT -a to check all of your LISTENING ports. When you see a port with a listening status, this means a process on your computer has reserved that port. Make sure to pick a port not already in use.
Ports Already In Use
3. Open the file: Server.Xml.
C:\Program Files(x86)\Common Files\AspenTEch Shared\Tomcat7.0.37\conf\
Note that this location may change depending on Tomcat Version installed and OS installed.
Search this file for your existing Apache port number and change to the new one. This screen capture shows the default port 8080. We will change it to 8888:
local:8080
Original Port Number
4. This is the only change necessary to reconfigure Apache Tomcat for a different port. Restart the Apache Tomcat Service. The Service should stay up and running. Enter the URL for your new port in your browser like this:
http://localhost:8888
You should now see the Apache Homepage:
Apache Tomcat Homepage
5. The next step is to change all the configuration files used by eBRS to contact Apache.
There are three points of contact where APEM interacts with Apache: (1) Synchronized Time Clock; (2) Notifier; and (3) API access (for web-enabled Basic Phases, Batch.21 and BPC.) The references to change these points of contact are contained in two APEM configuration files, and for Version 2004 and later, when using Basic Phases via a web interface, the Aspen ADSA component.
Change all references to the old port (8080) to the new port (8888) in these two files:
C:\Program Files\Aspentech\AeBRS\cfg_source\path.m2r_cfg
C:\Program Files\Aspentech\AeBRS\cfg_source\flags.m2r_cfg
In path.m2r_cfg:
HELP_DIRECTORY_NAME = http://DOBEASE4:8080/AeBRSserver/HELP
SOAP_SERVER_HTTP = http://DOBEASE4:8080/AeBRSserver/servlet/aebrsrouter
SOAP_SERVER_HTTP_NOTIFIER = http://DOBEASE4:8080/AeBRSserver/servlet/aebrsnotifier
SOAP_SERVER_HTTP_AEBRSBATCH21 = http://DOBEASE4:8080/AeBRSserver/servlet/aebrsnotifier
Note: The following line will be commented out unless you are using Aspen's BPC component as part of your AeBRS solution:
# SOAP_SERVER_HTTP_AEBRSBPC = http://DOBEASE4:8080/AeBRSserver/servlet/aebrsnotifier
SERVER_HTTP_SERVLETIMAGE = http://DOBEASE4:8080/AeBRSserver/servlet/imageUtil?IconID=$_$_END_HTML
In flags.m2r_cfg:
TIMESTAMP_PORT = 8080
6. Don't forget to now run codify_all.cmd, found in the same "cfg_source" directory. This creates compiled objects of all text configuration files in this directory, updating your run-time configuration.
7. If you are using Web-Enabled Basic Phases on your system, you will also have an eBRS service entry in your ADSA -- edit your ADSA configuration to update it to your new Apache port:
New Port Number for eBRS Service in ADSA
8. Next, restart the Windows Aspen Data Source Directory Service:
Windows Services
(right-click My Computer | Manage | Services and Applications | Services)
If all steps above are executed correctly, Apache and eBRS will now communicate correctly via the new port you have configured.
KeyWords
Tomcat
Apache
Port
change
conflict
Keywords: None
References: None |
Problem Statement: When loading the Aspen Production Execution Manager Weigh and Dispense application you may receive the error
R4109: Internal error. Terminate your work saving all data and start again. If the error persists contact the Aspentech support desk | Solution: These messages will occur when the application does not have a Booth created. You will need to open the Weigh and Dispense Administrator and ensure that under the Equipment tab you have a Booth configured for the workstation you are working with.
Please refer to the Documentation for the version you are using for more detailed information on creating and configuring Weigh and Dispense.
This document is available on the Support website under Documentation | Aspen Production Execution Manager | Version 8.7 or Version 8.8.
Keywords: Weigh and Dispense
Weigh
Dispense
Apem
Aspen Production Execution Manager
R4109
Booth
References: None |
Problem Statement: In the APEM Administrator's Manual it describes the security permissions group "Other \ Administrator" and says roles defined to this group can carry out all tasks within Production Execution Manager except for those explicitly denied. What are the tasks that are explicitly denied? | Solution: Role users who have security object "Other \ Administration" are called administrator. Administrator has all permissions except the objects in "User Defined Objects" to which the permission needs to be configured to allow access from the security manager.
Keywords: Administrator
Explicitly Denied
UDO
References: None |
Problem Statement: When loading the Aspen Production Execution Manager Weigh and Dispense application you will need to make some configuration changes first to allow the administrator access. | Solution: To Allow access you will need to follow the steps below in order for the Administrator account to have access into the Weigh and Dispense management tool.
1. Go to AFW, assign user accounts to roles, grant the configured roles the Access permission for Aspen Production Execution Manager.
2. On the server machine, go to Windows Services, make sure Tomcat is logged on under a domain account with user permissions to import/export W&D data, and access to the 3rd party label print software if configured.
If the Tomcat service must run under the Local System account, a domain user account with the required permissions must be configured for the W&D servlet. The solution is :
1) Go to C:\Program Files (x86)\AspenTech\AeBRS\cfg_source\
2) Manually edit path.m2r_cfg to uncomment the servlet user name and password lines, then specify a domain user account and password, then save the file.
3) From an elevated security (run as Admin) command prompt, run the command file CODIFY_ALL.cmd.
3. Restart Tomcat.
4. Go to the Management web site: http://localhost/WeighDispense.
Go to Administration tab to configure user permissions.
Keywords: Weigh and Dispense
Weigh
Dispense
Apem
Aspen Production Execution Manager
Tomcat
Configure
References: None |
Problem Statement: Why do I get a prerequisite message showing that the Java development Kit is not Installed? | Solution: AspenOne Manufacturing installation no longer includes the Java SDK during installation and is no longer stored on the DVD's. This means that users will need to download and install the 32 bit JDK 1.7.0_45 or higher as noted in the 'Required actions' in the screenshot above.
NOTE: Do not download any higher version of Java another then 1.7.0_45 for Version 8.5 and
1.7.0_51 for Version 8.7
Please refer to the Oracle website for the java download
These are External links and may change.
http://www.oracle.com/
Download the file for you version.
Version 8.5 download Java SE Development Kit 7u45
Version 8.7 download Java SE Development Kit 7u51
Note: This may require you to sign up for a free Oracle account to download.
Keywords: AspenOne
Aspen Production Execution Manager
AeBRS
Web21
Process Browser
Java
JDK
V8.5
V8.7
References: None |
Problem Statement: My Cim-IO server frequently goes into store mode, often for only a short period of time before forwarding the store file and returning to normal operation. Often the Cim-IO S&F Monitor tool does not even show any buffering. I find repeated errors in the Cim-IO server log file stating that Write timeout expired. | Solution: In the Aspen Cim-IO User’s Guide you will find potential causes discussed in a section titled "Socket Write Time-Out" in the Troubleshooting chapter. One suggested response to this problem is to increase the message send timeout.
The default timeout for the Store & Forward processes are:
cimio_sf_store - 3 seconds
cimio_sf_scanner - 3 seconds
cimio_sf_forward - 5 seconds
To begin with we suggest that you at least double the default timeout of store, scan and forward process to see if that helps. You should then experiment further with these to find optimum levels for your particular environment with the goal of reducing these short store mode occurrences.
If you are using the batch file mechanisms to manage the start-up and shutdown of the Cim-IO you should refer to knowledge base article: What are the Aspen Cim-IO Store & Forward startup command line arguments ?
If you have configured the Cim-IO device using the built-in I/O Configuration Wizard tool in the InfoPlus.21 Administrator you should refer to knowledge base article: How to add command line arguments to Aspen Cim-IO Store and Forward processes when the interface device was configured using the I/O wizard
If you are using V9.0+ of the Aspen Cim-IO Interface Manager you should refer to knowledge base article: How do I use Cim-IO Interface Manager to set additional parameters for the S&F processes?
Keywords: CIMIO_MSG_SEND_WRITE, Error writing to socket
CIMIO_SOCK_WR_TIMEOUT, Write timeout expired
frequent store mode
short S&F episode
References: None |
Problem Statement: This solution explains how to create a 64-bit and 32-bit Aspen SQLplus ODBC connections on a 64-bit machine using entries in the registry. A 64-bit ODBC connection will be necessary to retrieve data to applications running under 64-bit architecture that can hold this type of connections. | Solution: Use the .reg files contained in the .zip file attached to this solution to create new entries in the register.
For the 64-bit ODBC connection use next files:
- 64-bit SQLPlus connection.reg file will add the entry "HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\SQLplus 64-bit ODBC Connection"
- 64-bit Key entry.reg file will add a new entry on "HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources" with the same same as the previous connection
For the 32-bit ODBC connection use next files:
- 32-bit SQLPlus connection.reg file will add the entry "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\SQLPlus 32-bit ODBC Connection"
- 32-bit Key entry.reg file will add a new entry on "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\ODBC Data Sources"
The two entries for each ODBC connection are needed. You should have previously installed Aspen SQLplus ODBC drivers using the Aspen Installation DVD.
The new ODBC connection created on this way need to be edited from proper ODBC Data Source application:
in both cases, the new connection can be found under System DSN and the TCP/IP Host should be changed for the name or ip address of the IP.21 server:
Keywords: SQLplus
ODBC
64-bit
32-bit
References: None |
Problem Statement: In V8.8, Aspen InfoPlus.21 introduced a new definition record, called IP_AnalogDblDef, for storing double-precision real values. This solution provides the .rld files necessary for loading this definition record into historians that are older than V8.8. | Solution: Download the two rld files attached to this solution and move them to the Aspen InfoPlus.21 server. Use the article in solution 17415 to load IP_AnalogDblDefSupportRecords.rld first. Once this is done, use the same solution to load IP_AnalogDblDef.rld. Once this is done, IP_AnalogDblDef will now be configured for use on your Aspen InfoPlus.21 system.
Keywords: IP_AnalogDblDef
References: None |
Problem Statement: How to suppress user defined entry messages in an APC controller? | Solution: If you don't want to see messages about changes in a user entry defined for all Dependent/Independent/Testgroup variables, follow the below procedure:
1. Open APC Builder and open project.
2. Right click the Application in the workspace and bring up the Edit calculations dialog.
3. Remove the DefaultIOProperty of LogChange from the list of properties. Use the backspace key.
4. Redeploy the controller. Now you no longer get messages about this value changing.
Please note this procedure works only at the group basis. User defined entries can only be defined and edited at the Dependent, Independent, General, Subcontroller, and TestGroup level.
For instance, let's say we would like to suppress messages from a user defined entry called CNT. CNT is defined for all Dependent variables in the col5x3local controller.
Before making the change:
After making the change. Notice that LogChange is missing from the property, and also when expanding the DefaultIOFlags, the LogChange is now set to False.
Keywords: User defined entries, suppressing messages, APC, APC controller
References: None |
Problem Statement: This article describes how to gather debug information for Aspen IQ online applications. | Solution: For debug messages about these modules:
? SV - Sensor Validation
? IC - Input Calculation
? PR - Prediction
? OC - Output Calculation
? SSD - Steady-State Detection
? DC - Data Collection
Set these parameters (in CONFIG section):
? P1DBGLVL: 0 to 10 (10 is highest detail), default is 5
? P1DBGSW: number of execution cycles for debug messages
For debug messages about these modules:
? AZU - Analyzer Update
? LDC - Lab Data Collection
? LBU - Lab Bias Update
Set these parameters (in CONFIG section):
? P2DBGLVL: 0 to 10 (10 is highest detail), default is 5
? P2DBGSW: number of execution cycles for debug messages
Debug messages will be in DBG files in aconline/app/{application} folder (usually"C:\Program Files\AspenTech\AC Online\apps\{application}").
If sending to AspenTech, please include the IQF and any supporting files, e.g., MDL files, etc.
Solution Explanation
Aspen IQ actually runs two executables at (potentially) different frequencies to do its work. The P1 executable runs these modules:
? sensor validation (SV)
? input calculation (IC)
? prediction (PR)
? output calculation (OC)
? steady-state detection (SSD)
? data collection (DC)
in approximately that order. If you wish to gather debug information on these modules, then set the CONFIG variable P1DBGSW to a number equal to the number of execution cycles you would like to have output. P1DBDSW will count down as the application runs.
The true order for an application with multiple inferentials is as follows:
1. SV
2. IC1/PR1/OC1
3. IC2/PR2/OC2
4. ...
5. ICn/PRn/OCn
6. SSD
7. DC
where n is the number of inferentials.
The P2 executable runs these modules:
? analyzer update (AZU)
? lab data collection (LDC)
? lab bias update (LBU)
in that order. If you wish to gather debug information on these modules, then set the CONFIG variable P2DBGSW to a number equal to the number of execution cycles you would like to have output. P2DBDSW will count down as the application runs.
P1DBGLVL and P2DBGLVL control the amount of information output to the file. 10 is the highest value, but most of the information we need is output at a level of 5 which is the default value.
The Validation "module" is a virtual module and the validation is actually handled by the individual modules as needed. For example, validation on inputs to the prediction module are carried out by the prediction module.
If you wish to capture an event (like the entry of a lab sample) then set the PxDBGSW to a value that gives you enough cycles to capture the event. The files are verbose and full of information, but can often give us the vital clues as to what is being calculated.
For both the P1 and P2 processes, the debug messages will be output to files in the aconline/app/{IQ application name} folder. This can usually be found at "C:\ProgramData\AspenTech\AC Online\apps\{IQ application name}". Each process has it's own file, so you will find files named "iqp1_{IQ application name}.dbg" and ""iqp2_{IQ application name}.dbg" depending on which executable you set to output debug messages.
If sending these debug (*.dbg) files to AspenTech, please also include the application's IQF that created the debug messages, along with any other supporting files to make the IQF run, such as MDL files for FIR type predictions, etc.
Keywords: None
References: None |
Problem Statement: How to prevent users to Publish Trends/Graphics to aspenONE Process Explorer? | Solution: This solution describes a method by changing permissions over the Public folder itself.
1. Open Microsoft IIS, Go to Sites --> Default Website --> ProcessExplorer --> Files --> Public and select Actions and then Edit Permissions.
The physical path is C:\inetpub\wwwroot\AspenTech\ProcessExplorer\Files\Public
2. There are some Windows users pre-defined by IIS configuration like CREATOR OWNER, SYSTEM, Administrators, Users, IIS_IUSRS, and Trusted Installer. This example uses the USERS group. Edit permission over this group and set just Deny the Write Permission.
Having this in place prevents all the users within the USER group to publish it to PUBLIC folder and when they tried to publish they will be getting a message as shown below:
"Cannot create directory <C:\inetpub\wwwroot\AspenTech\ProcessExplorer\Files\Public\<Name>. Error is: Access is denied".
It is recommended to create specific group of users, instead of using the ones pre-configured to deny Write permission.
Keywords: aspenONE Process Explorer
Publish
Public
IIS
Write
Deny
References: None |
Problem Statement: What would cause off-schedule run messages for a controller on an Online server? | Solution: The off-schedule run message on an online server means that the system and/or communication load is too high and the controller could not execute all the applications on the specified schedule. Each DMCPlus controller has an CTOFF parameter that specifies when the controller should run. A value of 10 for CTOFF for a controller running once every minute means that the controller runs every minute, 10 sec after the top of each minute. If the controller engine does not initialize at 10 sec after the top of the minute, you would get that off-schedule run messages. There are two causes for a controller not to run on schedule:
1. The server is loaded with too many controllers running. There is not enough CPU to run all the controllers within the appointed cycle (CPU and Elapsed time are both high).
2. The communication between the Online server and the DCS is taking too long to finish thus all the controllers cannot be run within the appointed cycle (CPU time is low but Elapsed time is high)
The elapsed time and CPU time of a controller can be historized in Aspen Watch by following KB solution 135710.
Some of the recommendation to reduce the overall execute time of the system includes:
· Examine the CTOFF of all the controllers and stagger them appropriately to prevent overloading the system and/or communication channels.
· Slow down some the controllers if this results in none or negligible reduction in control performance.
· Increase the communication efficiency by setting up cached read when connecting to an OPC server and change the LISTSZ parameters to an appropriate number (it depends on the system so it is best to use trial and error to set it).
· Decrease the amount of read and write data to the DCS. Transfer only the important parameters. The rest can be accessed through Production Control Web Server (PCWS).
Keywords: DMCPlus
Off-schedule run
References: None |
Problem Statement: Do you need a Recycle operation in a closed loop simulation in Aspen HYSYS? | Solution: You do not need a recycle operation in a closed loop simulation in Aspen HYSYS. A Recycle operation is required when the downstream material streams mix with upstream materials. In a closed loop system the material does not change. For example, a typical Propane Refrigeration simulation does not require a Recycle operation.
In the above simulation the composition has been specified in the material stream 1. The material will remain unchanged in all the streams.
What will be the problem if someone decides to add a Recycle unit in the closed loop simulation as shown below?
In this case, there are two streams (stream 3 and 3-Rec) connected to a Recycle operation. Stream 3 contains specified composition and some other conditions. If you change any of the inputs in stream 1, those will be inconsistent with materials in the Recycle block outlet stream (3-Rec). Since the Recycle operation solves the simulation by iteration, in the iterative steps the updated results in the output stream will be inconsistent with the materials in stream 1. This will result in an Inconsistency error in the simulation.
Avoid using a Recycle operation in a closed loop simulation.
Keywords: Recycle Operation, Closed Loop Simulation
References: None |
Problem Statement: How is the Reid Vapour Pressure Index (RVI) calculated? What is it used for? | Solution: The Reid Vapour Pressure Index (RVI), available from the Stream correlations ("Petroleum" section), is related to the Reid Vapour Pressure (RVP) by:
where RVP has units of psia.
The RVI can be used an intermediate term in calculating the RVP of a product mixture stream if the RVPs of the individual feed streams are known. The calculation method involves determining the RVI for each feed stream (from the respective RVP), followed by calculating the weighted average (by volume) of the RVIs. Once the product mixture RVI is known, the RVP can be determined by the 1.25th root of the RVI. This is summarised by the equations below:
where
is the RVI of the product mixture stream
is the number of feed streams that are mixed together to create the mixture
is the fraction of the feed relative to the sum of the feeds (on a volume basis)
is the RVP for the individual feed
Then
where is the RVP of the product mixture
Keywords: Reid Vapour Pressure Index, RVI
References: None |
Problem Statement: How do I get access to Aspen COMThermo Workbench? | Solution: Aspen COMThermo Workbench is available after installing the Process Modelling (HYSYS). Currently, the shortcut is not exposed to user, but it is accessible by using the steps below:
1. In the Windows Folder Explorer, navigate to the Aspen Energy Analyzer installation directory: C:\Program Files (x86)\AspenTech\Aspen Energy Analyzer V9 (or V8.x)
2. Find "concepts.exe" In the folder.
3. Right-click concepts.exe and select "Create shortcut" to desktop.
4. Right-click on the shortcut (on the desktop) and select "Properties"
5. In the properties window, look at the "Target" entry => it will have something like:
"C:\Program Files (x86)\AspenTech\Aspen Energy Analyzer V8.6\concepts.exe"
6. Add "-hyprop3" to the target
=> it will become:
"C:\Program Files (x86)\AspenTech\Aspen Energy Analyzer V8.6\concepts.exe" -hyprop3 (Please note there is one space before adding -hyprop3)
7. Double click the shortcut to launch the COMThermo Workbench.
Keywords: Aspen COMThermo Workbench
References: None |
Problem Statement: What is the standard state for volume? | Solution: The standard state for vapor and liquid volume are different. In addition, vapor volume can depend on the units.
Standard State for Vapor Volume
Standard vapor volume flows are entered on streams as MOLE flows by choosing the appropriate units.
Standard conditions are ideal gas at 1 atm and 0. C for SI and MET units. 0. C , 1 atm ---- 22.414 m3/kg-mol (or 359.03 cuft/lbmol)
Standard conditions are ideal gas at 14.696 psi and 60F for ENG units. 60.F , 14.696 psi ---- 379.49 cuft/lbmol (or 23.69 m3/kg-mol)
For example:
MMSCF - Million standard cubic feet. Standard conditions are ideal gas at 14.696 psi and 60. deg F.
MMSCFD - Million standard cubic feet/day. Standard conditions are ideal gas at 14.696 psi and 60. deg F.
MMSCFH - Million standard cubic feet/hour. Standard conditions are ideal gas at 14.696 psi and 60. deg F.
MMSCM - Million standard cubic meters. Standard conditions are ideal gas at 1 atm and 0. C.
MMSCMH - Million standard cubic meters/hour. Standard conditions are ideal gas at 1 atm and 0 C.
MSCFD - Thousand standard cubic feet/day. Standard conditions are ideal gas at 14.696 psi and 60 deg F.
MSCF - Thousand standard cubic feet. Standard conditions are ideal gas at 14.696 psi and 60 degF
NCMH - Normal cubic meters (identical to standard cubic meters)/hour. Standard conditions are ideal gas at 1 atm and 0. C.
NCMD - Normal cubic meters (identical to standard cubic meters)/day. Standard conditions are ideal gas at 1 atm and 0. C.
SCFM - Standard cubic feet/minute. Standard conditions are ideal gas at 14.696 psi and 60. deg F.
SCM - Standard cubic meters. Standard conditions are ideal gas at 1 atm and 0. C.
SCMH - Standard cubic meters/hour. Standard conditions are ideal gas at 1 atm and 0. C.
There are property sets that can be used to report the standard vapor volume for a stream. These property sets are all at 0 C and 1 atm unless the temperature and/or pressure is otherwise specified on the Prop-Sets\Qualifiers sheet.
VVSTD - Pure Component Standard Vapor Volume
VVSTDMX - Mixture Standard Vapor Volume
VVSTDFR - Standard Vapor Volume Fraction
In addition, it is possible to use a mole flow property set with one of the standard vapor volume flow unit sets such as SCFM or SCMH. The conditions are the standard conditions of the units as listed above.
MOLEFLOW - Pure Component Mole Flow
MOLEFLMX - Mixture Mole Flow
MOLEFRAC - Mole Fraction
Standard State for Liquid Volume
Standard liquid volume flows are entered on streams as STDVOL flows.
Standard volume conditions are 60 deg F, 1 atm ( 14.696 psia )
There are property sets that can be used to report the standard liquid volume for a stream. These property sets are all at 60 deg F and 1 atm.
VLSTD - Pure Component Standard Liquid Volume
VLSTDMX - Mixture Standard Liquid Volume
VLSTDFR - Standard Liquid Volume Fraction
Note
In Aspen Plus 11.1 and earlier, when using the some of the stream formats (e.g. GAS_E or AIR_M), the stream summary indicates that the standard vapor volume is at 60 deg F. This is incorrect. It is at 0 C.
KeyWords
Standard State
Volume
Unit of Measure
Keywords: None
References: None |
Problem Statement: This demo will showcase how to leverage HYSYS Dynamics, the Safety Environment, and Flare System Analyzer to complete the pressure relief analysis for a system. The workflow involves running an emergency scenario in HYSYS Dynamics and using the results to size PSVs in the Safety Environment. The PSV design will then be imported into Flare System Analyzer and used to assess the adequacy of an existing flare network model. | Solution: This example will leverage Aspen HYSYS Dynamics, the Safety Environment, and Flare System Analyzer to complete a safety study.
Keywords: Dynamic simulation, dynamics, transient, HYSYS, HYSYS Dynamics, Flare, Flare System Analyzer, PSV, Safety Environment, safety, process safety, pressure relief, strip charts, process control, PID, blocked outlet, relief valve
References: None |
Problem Statement: How to request a product upgrade from our Support site? | Solution: Access the Aspentech Support site (esupport.aspentech.com), If you forgot your password you can reset it using your Email account.
Click on the Support option on the top of the screen and select the inside the Software Services the option for Order Upgrade.
Fill the form by entering all the requested information (User address, Shipping Address, etc.).
In the System information section, use the link if you don’t know how to retrieve your System Name.
Check on the AspenONE package you need. Select if you want to receive a physical installer along with the download links. Enter a timeframe for your upgrade.
Confirm your information by activating the checkbox at the bottom of the form and submit your request. Your order will be evaluated and you will receive the installation links once it has been processed.
Keywords: None
References: None |
Problem Statement: When trying to log into the Aspen Production Execution Manager ("APEM") MOC, where the user account logging in belongs to a different, but still trusted domain, an error results:
And in the MOC debug file, typically found at this location:
C:\Documents and Settings\All Users\Application Data\AspenTech\AeBRS\MOC\debug
the following error is seen:
14:15:39: E-1(chkUserFullNameRequired)
This error happens even though it is confirmed that the full name exists as part of the user's Active Directory account information. How can this problem be solved? | Solution: In a customer environment where this error occurred, the problem was that from the network domain where the MOC client existed, the domain controller in the other domain was only reachable via a fully qualified reference, like
ping mydomainserver.mynetwork.com
The short form like
ping mydomainserver
returned the error "Ping request could not find host."
In this case, by adding the IP address to the hosts file on the local MOC clients, thus allowing a successful ping via the short name, the full name info was then successfully retrieved from the other domain.
Keywords: Full name required for valid AeBRS users
References: None |
Problem Statement: By default, eBRS MOC application requires a username/password validation whenever it is opened. This is the default setting because the product is oriented toward compliant environments where electronic signatures and audit trails must be relied upon with confidence. Before Version 2004, this was not a configurable option.
Default Behavior
However for environments where compliance is not an issue, it would be convenient to have a method of logging into MOC directly | Solution: In Version 2004 and later the flag MUST_AUTHENTICATE_WINNT_USER controls this behavior. The flag does not exist in any configuration files, but can be added. If not defined by the user, it retains its default value of "1", forcing authentication.
To open MOC without authentication, add the flag to flags.m2r_cfg. To keep your configuration files organized, an appropriate place to add the flag would be near the "Defines default domain for WinNT users -" section:
# Defines default domain for WinNT users -
# if not defined, <domain>\<loginName> must be entered (e.g., to sign, change user,...)
# DEFAULT_DOMAIN =
#See Aspen Knowledgebase Article #121425 for details about this flag.
MUST_AUTHENTICATE_WINNT_USER=0
(As a quick side-note, if you want to still require username/password validation, but save your users the effort of always typing the domain name, you can supply a value to the DEFAULT_DOMAIN key.) Of course that configuration key is only usable if all your users exist in the same domain!
After adding the flag, run codify_all.cmd from the same directory. Next time you open MOC, no authentication is required:
New Behavior
Keywords: login
log in
authentication
user identification
security
password
References: None |
Problem Statement: By default, at the moment an automatic Basic Phase ("BP") becomes ready to execute, it will try to start on the same workstation whose previous action triggered its status change. The default wait time is .5 seconds. After .5 seconds if that workstation has not initiated execution, the BP becomes available for any ready workstation to pick up. .5 seconds seems like a long time for a computer, but sometimes the clean-up tasks relating to the previous phase execution may exceed half a second. So where the automatic BP executes is predictable "most" of the time, but not 100% guaranteed.
How can the system be configured to guarantee that the automatic BP's execute on the calling workstation? | Solution: To increase the default timeout period, use the flag:
MSG_PROCESSOR_READY_AUTO_PAUSE = 5
Units are in seconds, so in this case we have increased the availability window by 10x virtually guaranteeing the automatic BP will execute on the same workstation whose previous action made it available.
Keep in mind that if you have multiple automatic phases in parallel, it could potentially become more complicated, since some parallel phases might still go to other workstations.
KeyWords
automatic
phases
Keywords: None
References: None |
Problem Statement: A typical upgrade scenario is to install Aspen Production Execution Manager on a new server, then connect that newly installed server to the Database that needs upgrading, run the Wizard, then run AeBRSInstaller. However in that scenario, the installer will do many required tasks, but may not automatically run a compilation against the existing database objects. Why would this happen? | Solution: As documented in the Installation manual, installing APEM is really a three-part process:
1. DVD Install
2. Run Database Wizard.
3. Run AeBRSInstaller
However if steps 2 and 3 are done as part of setting up the new machine, when the intention is to migrate an old server to the new box, then that new box will already have configuration in place to run as its own "new" server install, and when attaching to an old database will not compile (i.e. "upgrade") the existing RPLs, BPLs and orders. Once in that position, the correct actions are:
1. Re-copy all the cfg_source contents from the old server to the new server, overwriting everything on the new server (nothing is "lost" by this operation, as far as newer config information, since the AeBRSInstaller will add all new configuration information for later product versions.)
2. Open each file ending with .m2r_cfg on the new server and do text search-and-replace to replace old server name with new server name. If the RDB is also going to be a new machine, make sure to edit the DATABASE CONNECTION OPTIONS section of path.m2r_cfg with the updated connection information.
3. Under cfg_source for a new install, a folder has been created for the current version, when the "new install" scenario was followed. For V7.3, for example:
Rename that cfg_source\V7.3 folder to any other name, like cfg_source\V7.3xx.
4. If not previously executed, run the DB Wizard to upgrade the RDB. This will update EBR_CONFIGURATION table, adding the new DB Version number and also keeping track of the previous database version you have just upgraded from (the Previous Verson line of the table.)
5. Re-run the installer, and it will now follow an upgrade scenario, (1) adding all necessary keys and values to the configuration files in the cfg_source files based on reading the Previous Version information from EBR_Configuration, and (2) it will also run a compilation on all objects.
To follow best practice for the above upgrade scenario, that involves upgrading APEM while moving it to a new machine, follow these steps:
1. Run the DVD install for the new version.
2. Copy over all cfg_source folder information from the old server, overwriting those files on the new server. Edit those files as explained in the other Step 2, above.
3. Run the DB Wizard on the original database, to upgrade it (Previous Version information is then available on the EBR_CONFIGURATION table.
4. Run the installer, and it will follow an upgrade scenario, (1) adding all necessary keys and values to the configuration files in the cfg_source files based on reading the Previous Version information from EBR_Configuration, and (2) it will also run a compilation on all objects.
Keywords: Compilation not running
Compilation does not run
orders not compiled
References: None |
Problem Statement: Is it possible to have different temperatures for different phases in a holdup volume? | Solution: Yes. If non-unity flash efficiencies are specified for the holdup then it is possible to see different temperatures for the phases within the holdup. Flash efficiencies are specified on the Efficiencies tab of the Holdup window (when using the Fidelity option - set this on the Options tab of the Integrator window). To see this window press the Advanced button on the Holdup page on the Dynamics tab of the operation.
Note that flash efficiencies can also be applied to the vessel within the Depressuring - Dynamics utility. This is enabled by activating the Detailed Heat Loss Model on the Heat Flux page. It is not necessary to have a Fidelity license to use non-unity recycle efficiencies in the depressuring utility.
For more information on flash efficiencies and the HYSYS non-equilibrium flash see solution #111644 and Section 1.3.3 (Non-Equilibrium Flash) of the HYSYS 2004 Dynamic Modelling guide.
When the Detailed Heat Loss model is used for a vessel in Dynamics or in the Depressuring - Dynamics utility, it is possible to specify different convection coefficients for heat transfer between the wall and the vapour phase and between the wall and the liquid phase. A coefficient for heat transfer between the vapour and liquid phases inside the vessel can also be specified. For more information see Section 1.3.4 (Heat Loss Model) of the HYSYS 2004 Dynamic Modelling guide.
For more information on flash efficiencies and the HYSYS non-equilibrium flash see:
How can I generate the temperature profile along the separator as a function of time?, and Section 1.3.3 (Non-Equilibrium Flash) of the HYSYS 2004 Dynamic Modelling guide.
KeyWords
Non-Equilibrium Flash, Efficiency, Recycle, Depressuring - Dynamics, Temperature, Detailed Heat Loss model
Keywords: None
References: None |
Problem Statement: How do I link an Aspen HYSYS user variable in Aspen Simulation Workbook?
I have a HYSYS simulation case with enabled user variables attached to the streams. I would like to report the values from the user variables on Excel using ASW. How can I do this? | Solution: User variables can be directly linked to ASW using ASW V10 and higher with Excel version 2016 using Copy/Paste or using the Variable Browser in the Organizer. We recommend upgrading Aspen products to V10 if using earlier releases.
In earlier releases, if you use the Variable Browser, you can see the user variable object, but it shows ?Missing?. If you use the Copy+Paste procedure, it says that the variable is not currently supported. The workaround to access the user variables in ASW is to use a Spreadsheet block as a bridge operation in HYSYS. Export the user variable result into one of the cells of a spreadsheet block and then the value in that cell will be accessible within ASW as part of the Spreadsheet block values.
Keywords: Simulation Workbook user variable
References: None |
Problem Statement: What are AspenTech's recommendations for running the Aspen Manufacturing Suite in a virtual environment? | Solution: While AspenTech supports the use of the AspenTech Manufacturing Suite applications in virtual environments, this support depends on the virtual environments themselves being implemented using the best practices recommended by Microsoft and VMware. Likewise, the combination of hardware and virtualization configuration must be in a manner supported by the virtualization supplier.
Virtual environments, by their very nature, require additional resources such as memory and CPU overhead, over and above those required by normal operating systems and physical hardware. Likewise, networking, storage requirements, and other I/O considerations can vary depending on hardware type and usage. Therefore, AspenTech recommends that users should be very thorough in their planning for the use of an aspenONE application in a virtual environment.
Even if the virtualization system is perfectly configured, Aspen InfoPlus.21 would run slower within a virtual machine than a similarly equipped physical machine, especially if the virtualization software has to handle contention for resources by multiple virtual machines.
If Aspen software runs fine on a physical machine but very poorly on a virtual machine, then possible causes might include:
· Improper configuration of the system, or
· Virtualization server overloading, or
· Too many virtual CPUs.
The latter problem may seem counter-intuitive as many people assume that the adding CPUs will improve performance when doing so can actually degrade performance. For example, Aspen Infoplus.21 performance could suffer when the hosting virtual machine has more than one virtual CPU.
The rest of this article explains why this is so and provides recommendation regarding virtual CPU count.
Microsoft or VMWare virtualization servers can host multiple virtual machines where each virtual machine has one or more virtual CPUs. The virtualization software maps virtual CPUs to physical CPUs.
Suppose you have physical server with four physical cores. Also suppose that it is hosting ten single-cpu virtual machines. In this case, only four of the ten virtual machines can be running at any given time. The other six virtual machines have to wait for a physical CPU to go idle. When a virtual machine relinquishes its CPU time (i.e., perhaps waiting on disk I/O), the physical CPU can be reallocated for use by another virtual machine that is ready for CPU.
But what happens if some of the virtual machines have been configured with multiple virtual CPU? For example suppose your four-core physical server is hosting ten single-vCPU virtual machines and one four-vCPU virtual machine. With some virtualization scheduling algorithms, the four-vCPU virtual machine may have to wait until all four physical CPUs are idle before it can become active. In other words, it would be waiting for all ten single-vCPU virtual machines to become idle. Obviously, it could be waiting for a very long time, with an obvious degradation of perform imposed on the virtual machine with more virtual CPUs.
Another potential problem relates to CPU cache if a virtual machine is given access to a core on a different physical CPU. If a virtual CPU is remapped to a different physical CPU, then the processor cache for the new core may need to be re-loaded with information previously cached on the old processor.
It is important to stress that the CPU contention problems described above may occur with some, but not all, virtualization platforms.
Another concern that is of special relevance for Aspen InfoPlus.21 is that context switches may be much more expensive on virtual machines than on physical machines.
If an Aspen InfoPlus.21 system of many processes (i.e., perhaps more SQlplus IQ tasks than necessary) constantly contending for Aspen InfoPlus.21 database access, then there will likely be frequent process context switches. Context switches are much more expensive on virtual machines, especially those with multiple virtual CPUs. Furthermore, processes contending for Aspen InfoPlus.21 database access perform better if they are running on the same virtual CPU.
Better performance might be obtained by setting process affinity so that processes that frequently interact with the IP21 database are assigned to the same CPU while other applications run on other CPUs.
Keywords: Virtualization
Aspen InfoPlus.21
References: None |
Problem Statement: Conversion of OPC error codes to Honeywell error code | Solution: If you are using the OPC Cim-IO Server with the Honeywell APP Node, and you see an error error message in valid.err like this ...
smst_rr_lpg Error writing tag: DBVL CMTC516.SP :
CIMIO_?_?, Facility: 77, Error: -499048395
Wed Nov 28 18:03:01 2001
smst_rr_lpg Error writing list 6: IDB: IDB_Write failure: PDB: Write failed for 1 or more values
... then you can discover the actual TDC error code by converting that number to hex and looking it up in the TPN Server User's Guide (tp11120.pdf or tp11110.pdf).
In the example above, the hex equivalent is FFE2412035. You can ignore everything except the last 4 characters; search the manual for those characters (case insensitive) and you should find your error.
For the example, a search of the manual yeilds this:
LCN_D_do_invalid_mode_attribute 0x2035 E_FAIL
OPC_E_* = 0xe2412035
OPC_BAD_CONFIG_ERROR
(In that case, we were lead to discover that the intermediate points were not linked to the appropriate CL package.)
KeyWords:
DMCplus, valid.err, cimio, OPC, appnode, TPN
Keywords: None
References: None |
Problem Statement: I want to publish information about source, destination and quantity of my streams. I have seen that this information can be published in _ZSTREAM_MOVEMENTS table, but I don't see any entries. | Solution: To publish information in _ZSTREAM_MOVEMENTS table, the following tables must be configured:
1.- CONFIG
The entry PUBLISH_MOVEMENTS must be added with a value of Y:
2.- ATORIONMovementSet
This table will define the Sets to be published. Set_ID is the identifier of the set. A value of 1 in the column ALL_DATA will define that all data is going to be published and a value of 0 indicates that just the entries in ATORIONMovementData will be published. The entry in column DURATION is the number of days that are going to be published.
3.-ATIORIONMovementData
In this table you will define the streams to be traced. For example given the next diagram:
If we would like to trace the quantity of StreamA going to UnitB, we should define the next sources and destinations:
And write the entries in table ATORIONMovementData as follows:
Column SET_SEQ will tell the corresponding set defined in ATORIONMovementSet. Column UNITID is optional and will help to search the periods related to this unit within the duration of the set; if empty APS will look if SOURCE or DEST are defined units.
Once these tables are filled, the corresponding data will be published in table _ZSTREAM_MOVEMENTS
Keywords: movements,ATORIONMovementSet,ATORIONMovementData,_ZSTREAM_MOVEMENTS,PUBLISH_MOVEMENTS
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.