question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: This knowledge base article discusses the use of the Aspen Advisor objects Production docks and Consumption docks. | Solution: Production docks are used to model cases in which material is brought into the plant at no cost. Typical uses of production docks are to model compressed air being pulled from the environment and water being taken from a nearby ocean.
Consumption docks are used to model cases in which materials are used within the plant and, therefore, are consumed without being sold. The most typical example of the use of a consumption dock is to model gas sent to a flare.
Keywords: Build
Construct
Technique
Create
Destroy
References: None |
Problem Statement: How do I change the default 'Advisor3' account password using AdvPassword.exe utility? This | Solution: also illustrates the procedure that can be used to force the password change to appear on all client machines by distribution of IISYS.INI file to all clients.Solution
'Advisor3' account comes with a default password and all the administrator privileges to modify the database (i.e. at the relational database level). The AdvPassword.exe utility shown in the screen shot below can be used to change the default ID and password to connect for the Advisor model .
Note: This utility needs to be installed separately and will not get installed with the Aspen Advisor installation.
Run the Advisor Password Database Utility and change the DB User ID and Password so it can be encrypted. This will generate a new 'IISYS.INI file' (C:\WINDOWS) with the updated ID and password.
By distributing the newly updated 'IISYS.INI' file to all the users, it will update the user id and password on their machines.
But, after changing the 'Advisor3' account, please remember that you still need to change the username and/or password in the ODBC setup on each client machine. Also, please make sure that your new user account has the same database privileges as the existing 'Advisor3' account.
Note: For Aspen Advisor version 2006.5 the user name and password that are changed using the AdvPassword.exe utility are stored in the Windows Registry.
Starting from V7.2.changing the password using AdvPassword.exe utility is writing the encrypted user name and password to the AspenTech.MSC.Settings.XML file however it's going to modify this XML file for the user who is logged in only. In order to populate the same settings for the rest of the windows users on the same machine or on different machines you either have to copy those two lines with encrypted DB Username and Password into the settings XML file or copy the xml file directly in case if the settings are same for all the users.
Keywords: Advisor3
password
AdvPassword.exe
References: None |
Problem Statement: How can I tell if my AeBRS implementation is using a local Resource folder or a shared one?
If you follow the advice in | Solution: 113646 to add your own custom language resource, you may find it only works on the user workstation. But there is no obvious key in the AeBRS config files to specify that the resource directory contents be read from a shared path! What is theSolution to share the contents of one ...\AEBRS\resource\ directory with many users?Solution
In AeBRS version 6 and greater the resource folder location is hardcoded as follows:
<MyConfigPathLocation>\resource\
So theSolution is to make sure you edit the config.m2r_cfg file and specify a shared CONFIG_PATH location (typically on the AeBRS server.)
EXAMPLE BEFORE:
CONFIG_PATH = C:\\Program Files\\AspenTech\\AEBRS\\
EXAMPLE AFTER:
CONFIG_PATH = \\MyAeBRSServer\\Program Files\\AspenTech\\AEBRS\\
After doing this, and running codify_all.cmd, all files in the INCLUDE_FILES key will be read from this shared location (unless you specify a full path!) And now your resource folder will be the resource subdirectory under your shared CONFIG_PATH location. Now all workstations will have access to any custom User Resource file you have created, and your language files will only need to be updated in one place.
Keywords: lng
References: None |
Problem Statement: It is not immediately apparent from reviewing the Database Programmer's API manual how to retrieve values from EBRS via the AeBRS Web Service and use them. | Solution: The first step is to open a session and get a Session ID returned via OpenUserConnection. Next call the SQLSelect method to retrieve your data.
What is not as obvious is that it is necessary to use ValueOf or ValueOfArray to then use the data that has been returned (see pages 3-9 and 3-10 of the Version 6.0 Database Programmer's API manual.)
Here is example code that retrieves information from multiple fields:
string retValue;
string query;
string values;
string paramValues;
object[] testObj = new Object[10];
query = SELECT ID_USER, CODE, TAG FROM EBR_USER;
values = arrayId, arrayCode, arrayTag;
paramValues = ;
retValue = AeBRSService.SQLSelect(query,values,paramValues);
testObj = AeBRSService.ValueOfArray(arrayId);
TextBox1.Text = testObj[0].ToString();
TextBox2.Text = testObj[1].ToString();
testObjCode = AeBRSService.ValueOfArray(arrayCode);
...
testObjTag = AeBRSService.ValueOfArray(arrayTag);
Keywords:
References: None |
Problem Statement: Margins assigned in the path.m2r_config file are not being recognized in pdf files. How can the margins for Acrobat documents be adjusted? | Solution: The margins that currently exist in the path.m2r_config file only effect Word documents. In order to manipulate the margins of your Acrobat, PDF documents, please add an additional line to the path.m2r_config file to specify the EBR_PDF_PERMISSIONS.
Example syntax would be:
EBR_PDF_PERMISSIONS = no-modify no-annotate --top 6cm --bottom 6cm --left 5cm --right 5cm
Keywords: margins
adobe reader
reports
layout
formatting
References: None |
Problem Statement: When using SQLInsert to insert data into a user table in EBRS, a 1 is returned for success, a 0 for failure. A customer may find success using multiple SQLInsert statements, but failure when those same statements include Date values. | Solution: It is not possible to insert Date values directly. It is first necessary to use the SetValueOf function. For example:
SetValueOf(myDate, 2004-05-25 00:00:00, date) // This is fixed format... and assumed to be UTC
The myDate value can then be inserted into the correct table column with SQLInsert
(The ellipses are to indicate that other values will likely be part of the statement also, and are not correct syntax.)
Note that for a SQLUpdate statement, SetValueOf still applies, but additionally, the date variable needs to be enclosed in dollar signs, like this:
SQLUpdate(UPDATE MYUSERTABLE SET . . , MYDATEFIELD=$myDate$, . . . )
Keywords: java.sql.SQLException:
ORA-00904:
invalid column name
References: None |
Problem Statement: The Database Wizard fails and you get an Aspen eBRS server unavailable or not updated message. | Solution: There are several possible causes for this problem.
The most likely cause may be an incorrect installation order. It is important for Version 6 to follow this installation order: (1) install 6.0, (2) run the Database Wizard, (3) install Service Pack 1, and then (4) run the Database Wizard again. At this point, any additional cumulative ER for 6.0.1 can be applied.
If you applied the Service Pack, and any additional ER's first, and are then getting this error when trying to run the Database Wizard for the first time, run the following line in either your SQL Server or Oracle query tool:
UPDATE EBR_CONFIGURATION SET VALUE='6.0.1' WHERE ITEM='DB_VERSION'
The Wizard should then execute successfully. If it does not, please check the rest of the advice in this article first, and then contact Customer Support.
If you are trying to connect to Oracle, then verify that port 8888 is available.
Verify that DriverJDBC.jar exists:
<installdrive>:\Program Files\Apache Tomcat4.0\lib
If this file does not exist, then the 6.0 Installation manual instructions have not been followed correctly (downloading ODBC14.JAR from the Oracle website, and installing it.) Once installed, there will be a DriverJDBC.jar file in the \lib directory. If SQL Server is picked during the initial installation routine, then the correct DriverJDBC.jar file is loaded during install. This issue exists because Aspentech did not have the right during the 6.0 release timeframe to distribute the necessary Oracle JAR.
Keywords:
References: None |
Problem Statement: When first opening the Administrator tool, there is no default connection configured. Also, the Help files do not include a direct explanation of adding a server. | Solution: To add a specific AeBRS server to the Administrator module, follow these steps:
After opening the Administrator module, right-click on AeBRS Administrator, and choose Insert Node.
The WebServiceName by default should be AeBRSAPIService, unless you specified something different; the port number is 8080 by default (again, unless you specified a different port), the Web Service Node Name is the name of the box where your AeBRS server resides on the network.
After you click OK, a node is inserted under AeBRS Administrator. Right-click that node and choose Connect
Keywords:
References: None |
Problem Statement: After initial install, attempting to start MOC client causes an error box to be displayed:
Java Virtual Machine Launcher
Could not find the main class. Program will exit! | Solution: This problem occurs because the client fails to find and load the aebrs.jar file. Much like the ADSA gives InfoPlus.21 connection information back to a client, in the case of a MOC client, the AEBRS_SETTINGS.INI file on the server gives connection (i.e. addressing) information back to the client, also, specifying where required resources are located:
Therefore when first installing a client, make sure that the account under which the installation is being done can read the contents of the share
\\MyAPEMServer\ebrsbase
That share is made by the server install automatically for the AeBRS folder, found at the default install location:
C:\Program Files\AspenTech\AeBRS
At a specific point the client install will ask for the location of that file. Browse to the UNC path for the ebrsbase share and select AEBRS_SETTINGS.INI. This will then give the client install all the above addressing to connect to the JDK, to Tomcat (where the critical aebrs.jar file resides) and the main aebrs directory for compiled config files.)
A typical reason the No Class Found error could happen would be that a new MOC user logs in, but their Active Directory account does not have the right to access the Share on the server to pick up the AEBRS_SETTINGS.INI file on startup. If the error happens to everyone, perhaps the Share itself has been modified or removed.
Keywords: None
References: None |
Problem Statement: On a system where Aspen eBRS/Batch.21 functionality has been enabled, the API Server debug file typically has a statement like this written to it at 10 second intervals:
12:01:44: batch21.DMQueueB21.EBR_BATCH21_QUEUE.reloadAll:SELECT OBJECT_ID,EVENT_ID, ORDER_ID,RECORD_ID,BLOCK_ID,ERROR_PROC,SIGNATURE FROM EBR_BATCH21_QUEUE | Solution: This is normal operation, and the method employed by Aspen eBRS to make sure events written to the EB_BATCH21_QUEUE are written to Batch.21 on a timely basis (i.e. every 10 seconds queue contents will be read by eBRS, and then written to Batch.)
The debug key that controls whether this message gets written or not is the data model debug key (DATAMODEL_DEBUG), not specifically the Batch.21 debug key (BATCH21_MSG).
We recommend leaving DATAMODEL_DEBUG active, since this key drives much of the content of the debug file in terms of listing SELECT statements from many eBRS components. If a problem were to occur on a system, having the DATAMODEL_DEBUG key active is good practice, so that the API Server debug file has useful information.
Keywords:
References: None |
Problem Statement: While executing the Database Wizard, it fails with the message:
dbWizard_err_directoryNotFound
either appearing on the screen or written to the Database Wizard logfile, which is located at:
C:\Program Files\Common Files\AspenTech Shared\RepositorySetup\RepositorySetup.log | Solution: This error can occur if modifications have been to AeBRS configuration files, but the codify_all.cmd file has not been executed. codify_all.cmd reads all current configuration text files and update the Apache Web Server. It is necessary to run it after every configuration change to the AeBRS application.
You may also find, in the Apache stderr.log file an entry reporting that:
...\webapps\AEBRSserver\conf\config.cfg
cannot be found.
Run codify_all.cmd and try running the Wizard again.
Keywords: directory not found
fail
freeze
dbwizard
References: None |
Problem Statement: Calling the SetProxyUser method can cause an Internal Java Error | Solution: The Internal Java Error is a product defect resolved in Versions 7.0 and later. However for Version 6.0.1 and earlier the error only occurs when the programmer does not include the required SetProxyOrderPhase function in their code. In 6.0.1 and earlier this call to the SetProxyOrderPhase function must come before a SetProxyUser function is invoked. In 7.0 and later it is just necessary that SetProxyOrderPhase be called somewhere in the relevant code portion (not necessarily before.) In 7.0 and later, if SetProxyOrderPhase is omitted, an error message should result, instead of an Internal Java Error.
Additional Information About Using Proxy Functions
There are three Proxy functions. When writing information to the Batch Record (i.e. writing a Block of data), these functions are used (one is required, two are optional):
SetProxyOrderPhase. (Required.) This function gives order and phase context where the Batch record block should be recorded to. SetProxyUser. (Optional.) Use this if the Batch record block should be assigned to a user different than the user account under which the program runs. SetProxyTimestamp. (Optional.) Use this to specify a time other than when the Batch record block is actually added to the AeBRS Batch record.
The logical flow could typically follow this example:
SetProxyOrderPhase // Specify the order and phase for the phase
SetProxyUser // optional - specify a different user for the Block operation
SetProxyTimestamp // optional - specify a time other than current system time
InitBlock() // Start batch record block
BatchWrite // Write specific information to the Batch Record, using the context provided in the above functions (Order/Phase, User and Timestamp.)
// BatchWrite may be executed as many times as necessary in the given context.
DoneBlock // Commit the BatchWrite block addition to the Batch Record
IMPORTANT NOTE: Even though the Proxy User and Proxy Timestamp can be specified, this is only for batch recording purposes. The Audit trail that is generated will still keep a record of the actual User making the call, and the actual time when the program executed.
Keywords: setproxyuser
Set proxy userr
References: None |
Problem Statement: When the Refresh_screen() function is set to Yes, an overflow compile error results, giving a MOC debug output like the following:
09:37:44: Exception
java.util.EmptyStackException
at java.util.Stack.peek(Stack.java:79)
at java.util.Stack.pop(Stack.java:61)
at runtime.vm.chkVMRuntime.popValue(chkVMRuntime.java:346) at runtime.vm.chkVMRuntime.executeStmts(chkVMRuntime.java:621) at runtime.vm.chkVMRuntime.executeStmts(chkVMRuntime.java:531) at runtime.vm.chkVMRuntime.executeStmts(chkVMRuntime.java:517) at library.component.chkComponentUtil.execEvent(chkComponentUtil.java:593) at library.component.chkDisplayLabel.refreshValues(chkDisplayLabel.java:255) at library.component.chkRefreshableDisplayLabel.access$001 (chkRefreshableDisplayLabel.java:24) at library.component.chkRefreshableDisplayLabel$1.run (chkRefreshableDisplayLabel.java:111)
09:37:44: Thread-35(TREATMENTS):ERROR:Overflow error. Terminate your work saving all data and start again. If the error persists contact the AspenTech support desk. | Solution: This error can be worked around by setting RefreshableDisplayLabel Refresh with window property to NO. The error occurs because there is an execution (stack) conflict between refresh_screen() refresh and the component's own refresh method.
This known issue is documented in CQ #145384. It will be fixed in Version 7.0.
Keywords:
References: None |
Problem Statement: How can I choose my own color scheme for the Procedure, Operation and Phase levels in the Order Tracking module? | Solution: AeBRS allows you detailed control over the display colors used in the Order Tracking module.
Typically, the default colors should meet most needs. However changing colors might be useful to conform to a corporate standard, or perhaps to accommodate a user who is not able to differentiate between certain colors.
UNDERSTANDING HOW DEFAULT COLORS WORK
The set of default colors are specified in the language resources files. On a system using English, the default language resources file, resources_en.properties is located along this path:
C:\Program Files\AspenTech\AEBRS\resource\resources_en.properties
In that file, search for 255 to quickly move to the relevant section. Scroll another page or so to the specific section:
# Order Tracking Background Colors
This section has two lists - one used to specify the default colors at the top two levels in order tracking (Unit Procedure and Operation.) The second to control the default colors for the Phase level. A Phase has more potential states than a Unit Procedure or Operation unit, so there are more colors that can be controlled. Let's look at typical default colors from the top level of an order down to a Phase.
First, notice that an In Progress Order has a default color of Dark Blue for the state Initiated | Ready for both the Unit Procedure and Operation:
UNIT PROCEDURE AND OPERATION DEFAULT COLOR
FOR INITIATED | READY STATE
Look at the highlighted line from the Unit Procedure and Operation list:
# Unit Procedure & Operation StepColor = 128, 128, 128
StepColor_ENABLED = 128, 128, 128
StepColor_ENABLED_NOT_READY = 128, 128, 128
StepColor_ENABLED_BLOCKED = 128, 128, 128
StepColor_ENABLED_READY = 004, 174, 004
StepColor_ENABLED_SKIPPED = 128, 128, 128
StepColor_EXECUTING = 255, 000, 000
StepColor_EXECUTING_READY = 255, 000, 000
StepColor_INITIATED = 000, 000, 132
StepColor_INITIATED_READY = 000, 000, 132
StepColor_FINISHED = 095, 095, 095
StepColor_FINISHED_COMPLETED = 095, 095, 095
StepColor_FINISHED_SKIPPED = 095, 095, 095
StepColor_CANCELLED = 140, 140, 140
StepColor_CANCELLED_READY = 140, 140, 140
Looking at the text file it is not easy to understand what number combinations make a particular color. Microsoft's Paint utility can provide an easySolution. Open up Paint, and choose Edit Colors under the Paint Colors menu. Now click on the Define Custom Colors button. The dialog that opens up lets you click and drag across a color palette, or type in the Red, Green and Blue (RGB) values. When we enter 0, 0, 132, for example, we see the StepColor_INITIATED_READY color in the Color|Solid preview pane.
Finally, let's drill down to our Phase:
Notice that our three states:
Finished | Completed
Enabled | Ready
Enabled | Not Ready
correspond to three of the many state colors specified in the Phase section:
# Order Tracking Background Colors
# Phase
PhaseColor_ENABLED_NOT_READY = 128, 128, 128
PhaseColor_ENABLED_READY = 004, 174, 004
PhaseColor_FINISHED_COMPLETED = 095, 095, 095
CHANGING THE DEFAULT COLORS
For our example, let's change the colors so that the Unit Procedure and Operation are both green for an active order, and a Phase that has Enabled | Ready status is orange.
OLD VALUES:
# Unit Procedure & Operation
StepColor_INITIATED_READY = 000, 000, 132
# Order Tracking Background Colors
# Phase
PhaseColor_ENABLED_READY = 004, 174, 004
NEW VALUES:
# Unit Procedure & Operation
StepColor_INITIATED_READY = 004, 174, 004
# Order Tracking Background Colors
# Phase
PhaseColor_ENABLED_READY = 255, 128, 000
Once the file is edited and saved, make sure MOC is closed, then run the codify_all.cmd to compile the changes:
C:\Program Files\AspenTech\AEBRS\cfg_source\codify_all.cmd
When MOC is restarted, the new color scheme will be in effect:
New default color of Green for the Initiated | Ready status for both Unit Procedure and Operation:
UNIT PROCEDURE AND OPERATION SET TO GREEN
FOR INITIATED | READY STATE
New color orange used for Phase in Enabled | Ready state:
Keywords:
References: None |
Problem Statement: In an AeBRS environment, often all the client config files are set to use a shared location. So how can a setting for the local workstation be effective if the config information is all shared? | Solution: The mechanism for sharing configuration information in an AeBRS information is as follows:
On each client, in the file config.m2r_cfg, the CONFIG_PATH key is set to something like:
CONFIG_PATH = \\<myAeBRSServer>\\Program Files\\AspenTech\\AEBRS\\
where <myAeBRSServer> is a shared folder on the server.
A few lines down, the INCLUDE_FILES line defines which configuration file information will be read from that shared location, using the pipe symbol as a delimiter. However, if in the INCLUDE_FILES key a full path is provided, then the share location will be ignored. So if the INCLUDE_FILES KEY looked like this:
INCLUDE_FILES = path.cfg|C:\\Program Files\\AspenTech\\AEBRS\\local.cfg
then they are read like this:
\\MyEBRSServer\\Program Files\\Aspentech\\AEBRS\\path.cfg
C:\\Program Files\\AspenTech\\AEBRS\\local.cfg
EXAMPLE:
The flags.m2r_cfg file contains a Default font family name at the end of the file:
DEFAULT_FONT_NAME = Dialog
Since the CONFIG_PATH is shared, that value will be read from the server. However, if the same key exists in multiple places, it will be read from the share path first, and then the absolute path (i.e. server, then client.) So the final time the key is read will be the value it keeps. So by editing local.m2r_cfg, to add the key, but with a different value:
DEFAULT_FONT_NAME = Arial
A local DEFAULT_FONT_NAME is successfully set.
Keywords:
References: None |
Problem Statement: It might take up to one minute for the EBRS MOC client to open. | Solution: If MOC takes a long time to open, the issue may be a slow connection to the JDK components that are resident on the server. If improving network performance is not an option, then a work-around to the problem is to install the JDK components on each client, and then modify the eBRS configuration files so that the local JDK is the one used by the clients.
Steps to install JDK on an EBRS client and change the configuration files so that the local JDK is used:
Insert the AMS installation CD-ROM for your version of eBRS.
Navigate to the JDK setup directory:
<MyDrive>:\Media\Core\JDK1_4
Run Setup.exe in the JDK1_4 directory and accept all default prompts.
Edit the AeBRS.cmd file, located at:
<install drive>:\Program Files\AspenTech\AEBRS\AeBRS.cmd
on each client for which a local JDK installation is performed. You will change the JAVAW.EXE line to reflect the local JDK install. If you installed JDK to the C drive, then the edited line would be as follows:
SET J=C:\j2sdk1.4.0_01\BIN\JAVAW.EXE
As a last step, if all clients are redirected to a local JDK install, then you can eliminate the reference to the shared JDK on the server (though this is not required.) To do so:
Edit the codify.bat file, located on the server at:
C:\Program Files\AspenTech\AEBRS\cfg_source\codify.bat
as follows:
C:\j2sdk1.4.0_01\bin\java -cp <rest of the line remains unchanged>
Keywords: slow
freeze
unresponsive
initial
initiate
start
References: None |
Problem Statement: When trying to create a Master Recipe (MR) via the API, customer gets an error. What is the minimum XML definition needed to use that function? | Solution: At a minimum, both the ID and the Version of the Master Recipe need to be specified in the XML:
MR name specified in the function call; and
MR version controlled by AeBRS.
The Master Recipe name is required because the BatchML schema dictates it (it is a standard from WBF.)
The version should not be required. This is a known issue (CQ167250) that may be addressed in a future version.
Keywords: 14:06:11: soap called OpenUserConnection with arguments:
14:06:11: Result = 261ADAC6D899CB873650E2032A917633
14:06:11: Diagnose = OK
14:06:11: m2rDatabaseConnection - HttpProcessor[8080][6] TRANSACTION Start:0 14:06:11: m2r.DataModel.m2rSQLDataModel.SQL_GETTIME47.Query:select sysdate from dual 14:06:11: m2rDateField.now()=2004-04-29 14:06:11.0
14:06:11: m2rDatabaseConnection - HttpProcessor[8080][6] TRANSACTION Start:1 14:06:11: DataModel.chkDMAPIActionAudit.EBR_API_ACTION_AUDIT.insertExternalRow:INSERT INTO EBR_API_ACTION_AUDIT (ID_ACTION,API_CALL,RETURN_VALUE,DIAGNOSTIC,PAR_COUNT,AUDIT_USER_ID, AUDIT_DATE,SIGNATURE) VALUES (2239,'OpenUserConnection','261ADAC6D899CB873650E2032A917633', 'OK',0,-1583013783,TO_DATE(SUBSTR('2004-04-29 14:06:11.0',1,19),'YYYY-MM-DD HH24:MI:SS'), 4099577260)
14:06:11: m2rDatabaseConnection - HttpProcessor[8080][6] TRANSACTION Commit:1 - rollBackFlag = 0
14:06:11: m2rDatabaseConnection - HttpProcessor[8080][6] TRANSACTION Commit:0 - rollBackFlag = 0
14:06:11: soap called createMasterRecipe with arguments:
14:06:11: Arg[0] =<MasterRecipe><Formula><Parameter><ID>fCuve</ID><Value> ;<ValueString>SP05</ValueString></Value></Parameter><Parameter ><ID>fLique</ID><Value><ValueString>LB5</ValueString>< ;/Value></Parameter><Parameter><ID>fQuantite</ID><Value>&l t;ValueString>600</ValueString></Value></Parameter></Formula>< ;/MasterRecipe> 14:06:11: Arg[1]=TEST_MR
14:06:11: Arg[2]=GLUCOSE
14:06:11: Arg[3]=10
14:06:11: Result = 0
14:06:11: Diagnose = OK
14:06:11: soap called GetLastError with arguments:
14:06:11: Result =
14:06:11: Diagnose = OK
14:06:11: null called CloseUserConnection with arguments:
14:06:11: Result = 1
14:06:11: Diagnose = OK
References: None |
Problem Statement: What does Parent Product and Product's Subsystem in Aspen Operations Reconciliation and Accounting (AORA, formerly called Aspen Advisor) mean? | Solution: What is Parent Product?
In AORA, Parent Product defines a hierarchical relationship between different products. For example, three products can be defined as Gasoline, Unleaded Regular, and Unleaded Super. The Parent Product for Unleaded Regular and Unleaded Super can be set to Gasoline. This association is stored in the database and can be used for reporting aggregations of data.
Another example is Crude. There are different types of crude used in the refinery: Arabian, Mayan, and Alaska crude. In this case it's desirable to create a Parent Product called CRUDE that combines all types of crudes. This allows for aggregate data in the reports (for example, a refinery production report) to see the total crude being received.
In the same way, you have grand_parent and great grand_parent, all used by the reports. Aspen Reporter have an option called Number of Parent Levels (File => Preferences =>Display tab) that determines the number of levels shown in a report (Please note that by default this parameter is set to 2).
What is Product's Subsystem?
Product's Subsystem defines whether the inventory of a product is contained in a subsystem object.
Subsystem is grouping of tanks according to product. Subsystems are objects that contain inventories for several tanks. They are mainly used to group tanks where the internal movements between them are unknown, so it's desirable to consider them as one.
A good example is, Company A has several Spherical tanks or bullets that gravitate and have movements between them that are unaccounted or not important. In this case, the several tanks are considered to be one, having the total inventory of the subsystem.
Keywords: Parent Product
Products subsystem
AORA
References: None |
Problem Statement: What algorithm does Advisor use to determine Daylight Savings Time (DST) changes? | Solution: DST switches come from the operating system, and more specifically, the C-runtime libraries associated with the compiler or operating system.
Keywords:
References: None |
Problem Statement: Gauge instruments in Aspen Advisor have a checkbox which says Outage Gauge. See below for an example.
This knowledge base article defines the term outage gauge. | Solution: A typical gauge used for most tanks measures the height of liquid in the tank by measuring the distance from the bottom of the tank to the top of the liquid in the tank. This type of gauge is referred to as an innage gauge. An outage gauge works in somewhat the opposite way from an innage gauge. Namely, for an outage gauge, the height of liquid in the tank is determined by measuring the distance from the top of the liquid in the tank to either the top of the tank or to a reference point near the top of the tank.
Keywords: plant terms
definition
process
References: None |
Problem Statement: This knowledge base article describes the Oracle server and client version combinations that are supported for Aspen Operations Reconciliation and Accounting (AORA, formerly called Aspen Advisor). | Solution: The following versions of AORA support the referenced versions of Oracle database server and client combinations.
V7.3
Oracle 9i Database Release 2
Oracle 10g Database Release 2
Oracle Client 10.2.0.4
Oracle Client 10.2.0.5
V7.2
Oracle 9i Database Release 2
Oracle 10g Database Release 2
Oracle Client 9.2.0.10
Oracle Client 10.2.0.4
V7.1 and 2006.5
Oracle 9i Database Release 2, Oracle ODBC driver 9.02.0.6.5,
Oracle Database 10g Release 2, Standard Edition
Oracle Client 9.2.0.10
Note: Oracle Client must be 10.2.0.4 for Windows Server 2008 to function properly.
Aspen Operations Accounting is a 32-bit application that uses only 32-bit database drivers. When using a 32-bit driver on a 64-bit edition of Windows, use odbcad32.exe to create a 32-bit system DSN.
Please refer to the AORA documentation in the Aspentech Support website
http://support.aspentech.com/
for the Oracle databases we support for versions prior to 2006.5.
Keywords: DB
Relational
Oracle
AORA
References: None |
Problem Statement: The following error occurs when attempting to load a CHK file into a BP: | Solution: This error occurs when trying to open an older ___.CHK file (version 4 or older) in a later version of EBRS. The error can be resolved by opening the ___.CHK file in Notepad, and replace the command chkOperContainer with chkRoutineContainer in the first line. chkOperContainer is the old internal object, and chkRoutineContainer is the new one.
Keywords: E20216: Design not compatible
References: None |
Problem Statement: Attempting to use AeBRS API calls, like OpenUserConnection method, for example, fails, with a message like the following:
{0} Exception caught.>System.Net.WebException: The request failed with HTTP status 404: | Solution: Verify that if a port other than the the default 8080 is being used, that the WSDL file is updated, then run the CODIFY_ALL.CMD file. The file specific to AeBRS is the aebrs_api.wsdl file. Read pages 2-2 to 2-3 of the v6.0 AEBRS Programmer's
Keywords: {0} Exception caught.>System.Net.WebException: The request failed with HTTP status 404: Not found. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse (SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at WebApplication3.AeBRSAPIService.AeBRSAPIService.OpenUserConnection() in D:\Projects\Pilsner\Software\JK\WebApplication3\Web
References: Guide for configuration details. This file is required for setting up Web Services for an application. |
Problem Statement: When starting the Aspen Production Execution Manager (formerly Aspen eBRS) MOC (or any individual Production Execution Manager module) this error occurs:
after which MOC fails to open. Subsequent attempts do not show the error at all, because the javaw.exe process is running on the PC (if it is killed, this error will reappear the next time MOC is initiated.) Also, the MOC debug file has an Exception entry like this:
08:46:49: Icon path=C:\Program Files\AspenTech\AeBRS\ICONS
08:46:49: Locale: en_US
08:46:49: TZ: America/Chicago
08:46:49: Exception
I0
at Aspentech.View.AeBRSSplash.showWindow(AeBRSSplash.java:84)
at m2r.Application.m2rFrameApp.<init>(m2rFrameApp.java:128)
at m2r.Application.m2rMDIApp.<init>(m2rMDIApp.java:32)
at m2r.Application.m2rMDIAppDB.<init>(m2rMDIAppDB.java:22)
at MOC.common.chkMDIApp.<init>(chkMDIApp.java:52)
at MOC.common.chkMDIApp.<init>(chkMDIApp.java:60)
at MOC.mocApp.<init>(mocApp.java:122)
at Moc.main(Moc.java:22)
08:46:49: m2rNormalizeNumber.MAX_SIGNIFICANCE_DOUBLE=15(16)
08:46:49: m2rNormalizeNumber.SIGNIFICANT_MARGIN_DOUBLE=4
08:46:49: m2rDecimalFormat(en_US).decimal='.' - thousand=',' - groupSize=3
08:46:49: m2rNormalizeNumber.maxSignif=15 - signifMargin=4
08:46:49: m2rNormalizeNumber.ACTIVE_ROUND_PROCESS=true
Restarting the machine also does not help. | Solution: The problem may be a failure of AeBRS to successfully connect to the AspenSplash.exe program. This is a common component used by all Aspen client applications at startup. For some reason it is not loading successfully. Take the following troubleshooting steps:
1. Using Windows Explorer make sure that aspensplash.exe exists in the Program Files\Common Files\Aspentech Shared directory.
2. Type the command: aspensplash /RegServer, and press enter. Please note the importance of the capital R and S
3. Now try starting MOC again.
If MOC still will not start, check the Windows Task Manager and make sure any pre-existing javaw.exe instance is killed.
Keywords: aspensplash
module
IO: Internal Error. Save your data and try again. If the error persists contact Aspentech Support
Orders: Exception
m2r.Util.m2rInternalException: 'I0'
at m2r.Application.m2rPresentation.showWindow(m2rPresentation.java:76) at m2r.Application.m2rApp.<init>(m2rApp.java:304) at m2r.Application.m2rSDIApp.<init>(m2rSDIApp.java:90) at m2r.Application.m2rMDIApp.<init>(m2rMDIApp.java:99) at m2r.Application.m2rMDIAppDB.<init>(m2rMDIAppDB.java:55) at Order.orderApp.<init>(orderApp.java:187)
at Orders.main(Orders.java:45)
References: None |
Problem Statement: MOC fails to start up, with this error:
Initialization of the dynamic link library C:\WINNT\System32\ddraw.dll failed. | Solution: This error can happen because of a conflict with the third-party product PC Anywhere. Uninstall PC Anywhere to resolve the error.
Keywords: Freeze
crash
startup
initialize
install
installation
References: None |
Problem Statement: While running the Aspen Database Wizard, installation fails with message:
R4003 internal error. Terminate your work saving all data and start again. If the error persist, contact the Aspen Technical Support. | Solution: There are several problems that might cause this error:
1. Correction needed to SQL Server Authentication mode.
The Aspen Database Wizard requires SQL Server to be set for Mixed Mode Authentication. To change your SQL Server environment to Mixed Mode, open SQL Server Manager, and follow these steps:
A. Right-click on your instance of SQL Server, and choose Properties.
B. Click the Security tab.
C. Change Authentication radio button to SQL Server and Windows
VERY IMPORTANT: Additionally, if the Wizard progressed to the point where it created the actual database and users, it is necessary to drop the database and users manually. The DB is called AEBRS by default, and the users created are aspen and aebrs. Additionally, make sure to restart Apache web server before retrying the Wizard.
2. MS JDBC files needed (Version 2004.)
If you are using SQL Server as your database, and you have not specifically downloaded and installed the Microsoft JDBC drivers, the R4003 error will result.
Please see pages 2-10, 3-19, 3-26 and 13-3 of Aspen eBRS Installation Guide v2004 for instructions on how to download, install and configure the correct drivers. The reference on page 13-3 does not explicitly give the syntax. It is as follows:
Original line:
SET D=C:\Program Files\Apache Tomcat 4.0\lib\DriverJDBC.jar
Edited line:
Set D=C:\Program Files\Apache Tomcat 4.0\lib\msbase.jar;C:\Program Files\Apache Tomcat 4.0\lib\mssqlserver.jar;C:\Program Files\Apache Tomcat 4.0\lib\msutil.jar
3. When using an Oracle Database, try defining the Database with the full DNS name.
Keywords: None
References: None |
Problem Statement: The existing documentation provides explanations of all the various eBRS functions. However it does not necessarily show how to use a set of functions to accomplish a particular task. | Solution: In this case, the following three functions used together allow an AeBRS programmer to create and execute an order programatically without needing to interact with MOC:
CreateOrderFromControlRecipe
This function generates an Order based on information contained in XML files. The XML file contains the Control Recipe logic, and is also the storage place for any parameter values associated with the Control Recipe.
(At this point the view from the MOC Orders module would show that a new Order exists.)
SetOrderState
This function can set the newly created Order to an Executable state.
(At this point the Workstation module would show BP(s) ready for Execution.)
ExecuteOper
This function execute the BP(s) related to the Order, and can specify the workstation on which the BP(s) appear.
(At this point a BP should display on the specified workstation, ready for operator input.)
Keywords:
References: None |
Problem Statement: API Debug file gives error like this:
19:05:46: Exception
m2r.Util.m2rNeedReloadException: E4125: Another user has changed the data, it is necessary to perform a refresh from the server. Reload at m2r.DataModel.m2rDataModel.getExternalRow (m2rDataModel.java:3634) | Solution: The E4125 error results because the signature in eBRS is generated based on the value as it is handed off to the API. For nearly all types of data, the value written to the database is of course the same as the data that can then be read back into memory. However there are several special cases:
1. Floating point numbers that are too large, or have too many values to the right of the decimal.
2. Nulls and empty strings.
3. Strings that have leading or trailing spaces.
As with all data, at a certain point the eBRS API hands off data to the Relational Database. But for the special cases listed above, the Relational Database may change the data before storing it. For the first case, the floating point number may be trimmed or modified depending on how much precision the RDB can handle. For the second case, each database (Oracle and SQL Server) have their own way of handling data (see the table below), and for the third case, the RDB may trim either leading or trailing spaces.
In each case, then, the problem arises because eBRS creates a signature based on the data it is writing to the RDB. This signature is the eBRS mechanism to ensure that data is not tampered or changed in any way. However, when the string (or number) is stored to the database, the database treatment as described above can change the data. Therefore, when the data is read back into memory, it no longer matches the recorded signature, and the E4125 error can result.
First, let's examine empty strings. The key to avoiding the error is allowing eBRS to handle your empty or NULL strings for you.
When you insert empty strings directly into the database, like this:
PRODUCT_MODEL= ,PRODUCT_MODEL_TYPE=, . . .
Oracle inserts the empty strings as NULL values, and SQL Server will insert them as 0 length strings (i.e. empty strings.) The obvious problem is you have written one simple statement, but your data is handled and stored differently, depending on which RDB you're using. Worse yet, it can lead to the above error when your code executes.
To avoid this error condition, instead of inserting values directly, allow AeBRS to handle the data conversion itself. By design, AeBRS converts all empty strings (any string only containing blanks of any length) to NULL and trims all non-empty strings, before inserting them into DB.
So even though the AeBRS API allows you to write constant values directly, the better practice is to define variables, and insert their values so that AeBRS can take care of conversion chores for you. If you follow this advice, you will not see the above error in your API Debug file!
As a last note, when you do choose to insert values directly, the following table highlights the differences between how SQL Server and Oracle treat VARCHAR values:
Database
Declaration
Trimming
Blank string
Empty string
Oracle
VARCHAR2
NO
Blank string
NULL
MSSQL
VARCHAR
Right
Empty string
Empty string
i.e.:
NO trimming means that string is saved as is.
right trimming means blanks are removed from the end of the string before saving it into DB. blank string means a non-empty string full of blanks: ' '
empty string means a string of zero length (different than NULL)
Leading or Trailing Spaces
Another cause of the E4125 error can be inserting strings with leading or trailing empty spaces. The Relational Database (Oracle or SQL Server), depending on its configuration, may automatically trim leading or trailing spaces when it stores data. Modify your application to make sure leading or trailing spaces are eliminated before attempting to store values in AeBRS.
ADDITIONAL NOTE: The E4125 error may still happen occasionally in Version 5.0.1 even after the advice in this article has been followed. Design improvements have been made in Version 6.0.1 and later to make null/empty string handling by the API more reliable. If you are running Version 5.0.1 we advise assigning Null directly in your code to give your application the highest level of reliability.
Keywords:
References: None |
Problem Statement: A paragraph on page 14-23 in the AeBRS Design User Guide states:
If it evaluates to TRUE (example illustrated above) the first Unit Procedure becomes Ready again and Phase 60 that in the above case was executed and finished, becomes Ready again. All three phases (60, 61, 62) have to be re-executed while the second Unit Procedure remains not Ready. | Solution: The word NO should be substituted for TRUE in the paragraph above. In addition to being an error, the mistake implies that TRUE and FALSE and YES and NO are evaluated differently, when in fact they are just labels for the standard boolean operator (TRUE/FALSE) and are not different.
Keywords: true/false
yes/no
true
false
yes
no
BOOLEAN
Boolean
References: None |
Problem Statement: If the SQL Server user database is restored to a different SQL Server or to the same SQL Server after either rebuilding or reloading an old version of the master database, user logons and permissions on the database may not be correct. | Solution: This is a known issue with MS SQL Server. Microsoft addresses this in several of their Knowledgebase Articles. Below are links to these articles. However Article Q240872 is the one with the key information, and below are specific steps a customer took to solve this problem with their own restored AeBRS database:
User Logon and/or Permission Errors After Restoring Dump:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q168001
Resolve Permission Issues When You Move a Database Between Servers That Are Running SQL Server:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q240872
Moving SQL Server databases to a new location with Detach/Attach:
http://support.microsoft.com/?scid=kb;en-us;Q224071
SPECIFIC RESolution STEPS:
Go to Microsoft's Knowledgebase Article Q240872 and download Sp_sidmap.sql and the readme.txt files.
Execute Sp_sidmap.sql in Query Analyzer (after selecting the right AeBRS DB).
Click Query and then Results in Text.
Execute from Query Analyzer the following lines:
EXEC sp_Sidmap @old_domain = MYDOMAIN,
@new_domain = MYDOMAIN,
@old_server = MYOLDSERVERNAME,
@new_server = MYNEWSERVERNAME
(substitute your own information for MYDOMAIN, MYOLDSERVERNAME and MYNEWSERVERNAME.)
You should have success at this point. If the output from Sp_sidmap.sql indicates there are still problems, review the troubleshooting advice contained in the readme.txt file you downloaded in Step 1.
Keywords: Exception java.sql.SQLException:
Cannot open user default database. Using master database instead. at com.inet.tds.e.a
Unknown Source
References: None |
Problem Statement: What components of Aspen Operations Reconciliation and Accounting (AORA) need to be installed for Aspen Advisor Recon Publisher service? Also, this knowledge base article describes how to manually add this service in case it is missing after the AORA installation . | Solution: The Recon Publisher is installed as part of the AORA Expert system Installation. In order to install Recon Publisher, ensure that the `Expert Engine? sub-option is selected during the AORA installation. Other than the Expert system NO specific components need to be selected.
In cases where the Aspen Advisor Recon Publisher service is missing from the Services after the AORA installation, it can be manually created by following these steps:
1. Open a DOS prompt then change the directory to
<drive>\Program Files\AspenTech\Advisor (for 32-bit systems)
<drive>\Program Files (x86) \AspenTech\Advisor (for 64-bit systems)
2. Run the following command:
AdvReconPublisher /service <domain>\<userid> <password>
3. Open the Services snap-in. The Aspen Advisor Recon Publisher should now be in the list of services and by default will be set to manual.
Note: Do not start the service until it has been configured. Please refer to the Recon Publisher Installation Guide for more information on how to configure it.
Keywords: Recon Publisher
Advisor
Installation
References: None |
Problem Statement: During the expert system's initialization step the flow instrument's standardized volumetric flow is passed to the expert system to be used as the original flow. However, in some cases, the expert system's original flow can differ from the standardized volumetric reading that is displayed in the instrument. This knowledge base article explains under what circumstances the expert system's original flow can differ from the standardized volumetric flow reading. | Solution: The image below shows that the standardized volumetric flow reading is 1000 m3.
However, when this standardized volume is passed to the expert system, it appears as 800 m3.
This is due to the fact that there is no product specified for the flow instrument. The image below shows that _Not in this zone is specified for the product.
The _Not in this zone product is not actually a product in the model, and therefore should not be used as a default product. If a default product is required, the user should specify a product on the actual pipe, which will be used by the instrument in case a product is not specified on the instrument itself. If a default product cannot be specified on the pipe, the user should ensure that the product named _default is used as the default product.
Once an actual product is specified for the instrument and the expert system is re-initialized, the expert system's original flow will match the standardized volumetric flow in the instrument reading.
Keywords: match
calculation
IRS
IRSS
reconcile
reconciliation
References: None |
Problem Statement: On Windows 2000 with SP4, when attempting to run the Aspen Database Wizard, the following error occurs:
Unable to create SoapClient30 object. | Solution: Windows 2000 SP4 is incompatible with MS SOAP 3.0. Microsoft© has provided a patch. To apply this patch, you should install Aspen eBRS 6.0.1 Service Pack and then download the executable available through the following link:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q825075
You must run the executable file and then the DBWizard application.
This Known Issue is documented in Aspen's Service Pack 1 Release Notes for Aspen eBRS. Because the problem is common to all WIN2K SP4 environments the information is repeated here in our online database for customer convenience.
Keywords:
References: None |
Problem Statement: Aspen Advisor multiplies the measured volume by a Volume Correction Factor (VCF) to standardize all volumes to volume they would occupy at a given reference temperature. This knowledge base article describes how to view the VCF calculated by Aspen Advisor for a given product, temperature and pressure. | Solution: In Aspen Advisor go to Tools | System Calculator. The VCF tab will contain fields for the product, temperature and relative gravity.
The VCF will be calculated according to the equation of state that is specified for the product at the temperature and density that is specified when the Calculate button is pressed.
Note: The equation of state is specified in the product's Type field as shown below . There are several different equations of state available because a single equation of state is not appropriate for every type of product.
Keywords: EOS
API
Generalized
Refined
Lube
LPG
References: None |
Problem Statement: In general, there are three classifications of equipment objects in a model: vessels, pipes, and instruments. Each classification is further segregated by events such as Sales, Receipts, Transfers, and Charge and Yield. Furthermore, events in Aspen Advisor can be listed based on the event type. This knowledge base article explains how Aspen Advisor determines the event type classification for each event. | Solution: Event type information is not saved in the database tables. The event type categories are determined in an ad-hoc fashion when the event table is queried.
Events are classified and identified by their pipes - more specifically the pipe end points. The end point 'type' is found on an object's Detail | Advanced tab. You can create any type of event under any type listing. It is the pipe that the event gets put on that later determines how the event appears.
For instance:
If a pipe has a source vessel type of 10400-10499, the pipe and therefore any associated events are Receipts. A typical end point that defines a pipe/event as a Receipt is 'Receiving Dock' (type 10420).
If a pipe has a destination vessel type of 10400-10499, the pipe and therefore any associated events are Sales. A typical end point that defines a pipe/event as a Sale is 'Consumption Dock' (type 10430).
If a pipe has a source or destination vessel type in 10200-10299, the pipe and therefore any associated events are Charge and Yield. A typical end point that defines a pipe/event as a Charge and Yield is 'Column' (type 10250).
Else the pipe/event is a 'Transfer'.
Keywords: charge
yield
receipt
shipment
transfer
dock
References: None |
Problem Statement: When saving Expert system results logged in as superuser, Advisor returns the following message You are not authorized to save... | Solution: In version 5.5 of Aspen Advisor, the superuser User Name does not have access to save Expert system results. In later versions of Aspen Advisor, superuser has priviledge of saving the Expert System results.
Keywords: None
References: None |
Problem Statement: This | Solution: illustrates the work around If there is a huge gap in values between the volume and mass readings in Advisor. The reason for this is that if the properties are not defined in Advisor, it uses Default value for density of the liquid (which is 349.788). As a result, the volume measurement is multiplied by that default density value resulting in a Mass number that is significantly different compared to the volume.Solution
Following is the procedure to address the problem of difference in mass and volume readings in Advisor.
Go to the database (Access, SQL server or Oracle) and look at the OLOCONFG table which has all the properties defined. Change the density of the liquid in the database to the specific value (say 1 if it is liquid).
After changing the value check to make sure the Mass and volume readings in Advisor are almost the same.
Keywords: Mass
Volume
OLOCONFG
References: None |
Problem Statement: The creation of the tables for EBR_TEMPLATES module (MIGRATION-40-41.SQL, CREATE_TABLES_WITHOUT_STORAGE.SQL and CREATE_TABLES.SQL) have some incorrect variable declarations.
Oracle also reported problems using the system date format after running the scripts provided with the AeBRS 4.0 media. | Solution: The attached Oracle scripts have been corrected. To implement the proper scripts, please place the scripts in the AeBRS\Database folder, then execute them against the Oracle database using the Server Manager. For detailed instructions on installing the scripts, please refer to page 3-28 of the AeBRS 4.1 Installation Manual.
Keywords:
References: None |
Problem Statement: In Which Table Aspen Operation Reconciliation and Accounting ( formally known as Advisor ) Simulated Tank Compositions are stored ? | Solution: AORA can simulate Tank Compositions on daily basis , based on the Tank Initial composition and the amount material received for the day. The Table named DOSMUNIT, has all the simulated values stored.
Please note that the user need to perform IRS-S to simulate the value for the next operating day.
Keywords: simulate
composition
References: None |
Problem Statement: When launching Aspen Advisor, the following error message is encountered. | Solution: Starting with Windows XP Service Pack 2, there is a feature called Data Execution Prevention (DEP) (http://support.microsoft.com/kb/875352).
1. Right-click on My Computer.
2. Select the Properties option from the context menu.
3. Select the Advanced tab in the System Properties dialog.
4. Click on the Settings button under the Performance section.
5. Select the Data Execution Prevention tab in the Performance Options dialog.
If the selected option is Turn on DEP for all programs and services except those I select, add Aspen Advisor into the list of programs to make sure that DEP is turn off for Aspen Advisor.
Keywords: 0xC0000005
Data Execution Prevention
DEP
References: None |
Problem Statement: The Aspen Operations Reconciliation and Accounting Reporting Tool includes a Date Selection Wizard accessible from the Menu Bar icons and from the Reporter File Menu bar options to aid in date range (start and end time) selection for generating standard reports.
This | Solution: explains how the date selection works for Daily Reports and MTD (Month To Date) Reports.Solution
First, open the Aspen Operations Reconciliation and Accounting Reporter Tool and make sure the Daily or MTD Reports you wish to generate are displayed in the Selected Reports Window Frame on the Right Hand Side of the Reporter GUI.
Once you are ready to generate the selected reports, then open the Date Selection Wizard, i.e., Change Time dialog form that allows for the Begin Time and End Time entries for generating the reports.
This wizard / dialog form can be opened one of two ways as shown per the screen shots provided below, and when displayed it will have the form heading Time Frame.
The Time Frame window has two parameters to be set to generate reports, depending upon whether you are running Daily or Month To Date (MTD) Reports.
1. Begin Time
2. End Time
When you are generating Daily Reports, the report is generated based on the End Time ONLY, and thus Begin Time is immaterial in the case of daily report generation.
Daily Report Example: 1
Begin Time selected: 02-SEP-2009 12:00 AM
End Time selected : 02-SEP-2009 12:00 AM
Then Reporting Date and Data Displayed will be for 02-SEP-2009, as per the End Time.
Daily report Example: 2
Begin Time selected: 01-SEP-2009 12:00 AM
End Time selected : 03-SEP-2009 12:00 AM
Then Reporting Date and Data Displayed will be for 03-SEP-2009, as per the End Time.
Please note again that irrespective of the Begin Time , the Reporting Date is ALWAYS that of the selected End Time, in the case of generating Daily Reports.
If you generate MTD Reports, then Begin Time defines the Start Date of the MTD Report Data and the End Time defines the End Date of the MTD Report Data, such that data on the report is displayed for the Entire Date Range as specified by the selected Begin Time and End Time.
mtd report Example: 1
Begin Time selected: 01-SEP-2009 12:00 AM
End Time selected : 03-SEP-2009 12:00 AM
Then MTD Reporting Date displayed on the Month to Date Reports will be from 01-SEP-2009 to 03-SEP-2009 as per the selected Begin Time and End Time, and as such Data displayed on the Report will be data for the Midnight to Midnight date range of 01-SEP-2009 to 03-SEP-2009.
In Summary, when running Daily Reports you ONLY need to set the End Time as per the date for which you want to execute the report and display data, and for the Month To Date (MTD) Reports you need to select and set BOTH the Begin Time and End Time as per the date range for which you want to execute the report and display data.
Keywords: date
range
Reporter
Begin Time
End Time
Change Time
References: None |
Problem Statement: For ALL versions of Aspen Operations Reconciliation and Accounting (formerly known as Aspen Advisor), how do you change to or select and apply the appropriate Base System UOM Equation DLL that is required to account for the base measurement system that is to be used for a new model or that is currently being used by existing models?
(UOM = units of measure)
I see that a New Equation DLL Selection and Save Path feature was added to the Model Settings section of the User Tab located on the File | Preferences... dialog form in the Aspen Operations Reconciliation and Accounting (AORA) application GUI starting in V2006.5.
How is this New Equation DLL Selection and Save Path feature used, and how does it affect AORA usage procedures with respect to selecting and applying the appropriate Equation DLL for New Models created with V2006.5 and Higher and for Existing Models Upgraded from prior versions to V2006.5 and Higher? | Solution: INTRODUCTION SUMMARY: -- Available Base Measurement Systems and Equation DLLs --
The yield accounting model database that is created and used by the Aspen Advisor application, now currently identified as Aspen Operations Reconciliation and Accounting (AORA), it can be configured to use one of three available base (Model Basis) measurement systems as follows:
US System with base temperature of 60o F
Metric System with base temperature of 15o C
Metric System with base temperature of 20o C
The corresponding Model Basis measurement system Equation DLLs for each of the three base measurement systems that are available for use with AORA models are initially installed in the main AORA Measurement folder located in the root AORA install directory following a new AORA installation, and those Equation DLLs as of V2006.5 are named as follows:
iiequa32_us.dll (to be paired and used with US system, 60o F Models)
iiequa32_m15.dll (to be paired and used with Metric system, 15o C Models)
iiequa32_m20.dll (to be paired and used with Metric system, 20o C Models)
In summary, then it should be noted that the selected and/or applied Base system measurement units and the corresponding equations of state and algorithms used for the VCF and API calculations for a given AORA model database are determined based on the selection of the following items:
The applied selection of one of the three Model Basis measurement systems noted above.
And also the selection / application of the appropriately matched dynamic link library (DLL), i.e., the selection of the correct Equation DLL to properly coincide with the selected and applied Model Basis.
PROCEDURES FOR Setting AND/OR Changing the Base System UOM Equation DLL
** The three additional PrimarySolution Documentation Sections that now follow which are needed to discuss and review the procedures required to set and/or change the Equation DLL for various AORA model versions, those supplemental documentation sections will now be presented in the exact order listed below:
Setting and Changing the Equation DLL for ALL AORA Versions Prior to V2006.5
Setting and Changing the Equation DLL for V2006.5 ONLY
Setting and Changing the Equation DLL for V7.1 CP1 and Higher
1. Setting and Changing the Base System UOM Equation DLL for ALL AORA Versions Prior to V2006.5
For any AORA model created prior to V2006.5, then in order for the model to make use of the correct Equation DLL needed for its configured Model Basis the appropriate Equation DLL MUST reside in the ..\AspenTech Shared\ directory before attempting to open and use the model.
** When Installing Pre-V2006.5 AORA versions for the first time on New Client machines, the Default Base System UOM Equation DLL that ALWAYS gets installed first out-of-the-box is the one that is required for and used by the US System, 60o F Model Basis.
Thus, when creating a Metric Model for the first time on a fresh New Pre-V2006.5 Install of AORA, then one of the first tasks you will need to complete following the install is to load the appropriate Metric Equation DLL to match with the selected Metric System Model Basis that you will be using for the AORA Model.
NOTE: This means that for Pre-V2006.5 model versions you cannot (or at least you should not) load a model if its associated Model Basis does not comply with the Equation DLL that currently resides in the ..\AspenTech Shared\ directory, as doing so will or may result in startup errors and/or calculation and operational during model usage.
Thus if you have multiple AORA models configured for production usage, and if each or more than one of the models is configured to utilize a different base measurement system to accommodate data in different base units of measure (say for plants that reside in various countries or regions), then when switching between them you must also swap out the appropriate Equation DLL to coincide with the model's base measurement:
For all cases then involving older model versions where a user wants to load another Equation DLL to allow for the proper loading and use of other models configured against a different Base System UOM, then the procedures for selecting and applying the appropriate Equation DLL for that different Base System UOM for versions of AORA prior to V2006.5 are as follows:
? First, completely close and exit both the AORA application GUI and ALL open AORA models that are using the currently loaded Equation DLL.
Next, delete the existing Equation DLL (i.e., the iiequa32.dll) from the ..\AspenTech Shared\ directory.
Now, to continue and allow for the proper loading and usage of the other AORA database models that are configured to use a different base measurement system then load the correct Equation DLL as needed by selecting the appropriate Equation DLL from the set of those available in the ..\Advisor\Measurement\ directory and copying it to the ..\AspenTech Shared\ directory.
<< See the Screen Shot for this procedure provided below >>
Then, to complete the Equation DLL change transaction, Rename the selected Equation DLL that you copied to the ..\AspenTech Shared\ directory to iiequa32.dll in order to enable it for use.
Last, using the AORA application GUI you may now open and use the other model(s).
If you need to switch again to allow for the loading and usage of yet more models that have been configured to use a different base measurement system and corresponding Equation DLL, then again follow and repeat the procedures provided above to swap out the required Equation DLL as needed before loading the other models.
ADDED NOTES:
If the installed Equation DLL copies are being stored in a different directory (NOT Recommended) or if you have deleted the backup copies, then respectively you would need to select and copy over the appropriate Equation DLL from the directory in which they reside or obtain a copy from the DVD or a Network Share as needed.
When swapping out the AORA Equation DLLs, then to facilitate the swap you cold also place all of the individual file copies (one for each of the three Model Basis System) in the ..\AspenTech Shared\ directory and simply rename them as needed to enable and disable the one you need; however, this method is not recommended and should be practiced with care is used, as the recommended practice to avoid any confusion between files is to delete and replace the file altogether as noted in the above procedures.
2. Setting and Changing the Base System UOM Equation DLL for V2006.5 ONLY
** By Design Starting with aspenONE V2006.5, the following changes were made in relation to how the application of the selected Base System UOM Equation DLL is handled:
The former AORA version requirement that involved manual placement of the appropriate Base System UOM Equation DLL in the C:\Program Files\Common Files\AspenTech Shared directory was removed.
To account for the requirement removal noted above and to better facilitate proper selection of the Base System UOM Equation DLL for V2006.5 and Higher, a New Equation DLL Selection and Save Path Feature was added to the Model Settings section of the User Tab located on the File | Preferences... Dialog form in the Aspen Operations Reconciliation and Accounting (AORA) application GUI.
** Along with this New Equation DLL Selection and Save Path Feature comes various new user prompts, warnings, and reminder messages and dialogs (post installation) that will display when upgrading, opening, and/or creating and configuring new and/or existing models (more detail provided further below).
-- Recommended Quick Guide Procedures for selecting the Equation DLL for V2006.5 AORA Models --
Added notes and screens are provided below to help explain the new functionality and items that you need to know in order to understand and work successfully with this New Equation DLL Selection and Save Path Feature in regards to properly setting the required Equation DLL of choice for the desired and/or selected AORA Model Basis.
? Again, as noted earlier in the above paragraphs the New Equation DLL Selection and Save Path Feature is located on the Model Settings section of the File | Preferences... User Tab dialog form that is accessible from the AORA GUI File Menu (see screen shots provided further below).
With the New Equation DLL Selection and Save Path Feature you now have FULL selection control from the AORA GUI to interactively choose the appropriate Base System UOM Equation DLL for your Model Basis that gets used for the API and VCF Calcs.
The New Equation DLL Selection and Save Path Feature is comprised of a new ComboBox file selection control (with browse button) labeled Equation: and a corresponding Save full Equation DLL path? checkbox control which are both used to facilitate the selection of the appropriate Equation DLL and/or corresponding file path if so desired.
? To coincide with this New Equation DLL Selection and Save Path Feature, users will now also be prompted to select an appropriate Equation DLL when opening the Model for the First Time after upgrading from older AORA model versions up to V2006.5 or Higher.
The new user selection functionality allows you to select either the Equation DLL File Name ONLY when the Save full Equation DLL path? checkbox is unchecked, OR when the Save full Equation DLL path? checkbox is checked then you can also select BOTH the Full Path and File Name.
The Equation DLL selection setting (File Name ONLY or Full Path and File Name) is set once Globally for ALL Users and the selected setting is saved and stored in the OLOCONFG Table of the AORA Database.
The Equation DLL selection setting MUST be configured by the Superuser account login or a user role account with Superuser (Full Admin) privileges. Thus, any user that is logging in without Superuser privileges will not have access to the feature and will not be allowed to select an Equation DLL, and in that case that user would see the selection feature in the AORA GUI disabled (grayed out and non-functional).
Please keep in mind that the Equation DLL file that you select MUST be installed in the same folder on ALL computers on which Advisor is installed. This requirement, however, should not be a problem as long as the default installation path is the same for all computers, and if needed you can try copying the required Equation DLL to a Network Share and pointing to that copy when completing the selection (using the Full Path and File Name option) via the AORA GUI.
For Creating New Models the selection of a valid Equation DLL is also required during the initial creation step, and as such the New Equation DLL Selection and Save Path Feature has been implemented the SAME on the New Model dialog and user form (see screen shots provided further below).
The V2006.5 user prompts and screen displays that you will see in reference to this New Base System UOM Equation DLL Selection Feature starting with V2006.5 will be the same or similar to those shown in the attached screen shots included below and on the next slide.
NOTE: In the two error / user prompt screens shown below the first will display when opening an upgraded model for the first time and the second will display if you try to exit the File | Preferences... dialog form without selecting and saving an appropriate Equation DLL for the model settings. And you will continue to be prompted as such to define an Equation DLL for the model until a valid selection has been completed and saved.
Likewise, if any other closed model (New, Upgraded, or Existing) is being opened and it still does not have a valid Equation DLL defined, then the following warning error message is immediately displayed when the model is done loading.
Detailed Example Screens of the New Equation DLL Selection and Save Path Feature
showing how the Equation DLL selection is executed and saved.
The Next screen shot provided below is a follow up to the screen set shown above, and thus in the supplemental screen that follows a visual example of the proper and recommended selection of the appropriate Equation DLL from the AORA root install Measurement directory is shown, i.e., selection of the iiequa32_us.dll for a US System, 60F Model Basis.
New Model dialog/user form screen shot showing the implementation of the Equation DLL Selection and Save Path Feature that is now utilized as well when creating New Models.
During use of the New Model dialog/user form to create a New Model, then as shown in the next screen shot provided below if you do not make the proper Equation DLL selection then you will be presented with an error and will not be allowed to continue until a valid Equation DLL selection has been made.
In summary, the New Equation DLL Selection and Save Path Feature and associated user prompts, etc. that have been added to AORA for V2006.5 and Higher now overrides and eliminates any and all need to manually swap the required AORA Equation DLL files (i.e., the iiequa32.dll files) into the ..\AspenTech Shared\ directory. Users can instead use this new selection feature to now complete and apply the required selection via the AORA application GUI when needing to set or change to using the required Equation DLL of choice as needed for proper loading and use of a different Model Basis (15C, 20C, or 60F).
3. Setting and Changing the Base System UOM Equation DLL for V7.1 CP1 and Higher
Starting with the release and application of the Cumulative Patch 1 for aspenONE V7.1 AORA models, the New AORA GUI driven Base System UOM Equation DLL Selection Feature that was added in V2006.5 was modified as follows to provide a slightly different but more robust and less confusing look and feel for the selection design and display:
In aspenONE V7.1 CP1 (Build 11.0.0.74) and Higher Versions, the selection of the Required Equation DLL to set the Base System UOM of choice is now controlled via replacement of the Equation: selection ComboBox and Save full Equation DLL path? checkbox with 3 Radio Selection Buttons, one each for the US 60F and Metric 15C and 20C Model Basis Equation DLLs.
With this Equation DLL selection modification change, then starting with aspenONE V7.1 CP1 (Build 11.0.0.74) and Higher Versions the selection can now be completed by simply selecting the appropriate radio button selection for either the 60F, 15C, or 20C or Model Basis as needed.
Once you have selected the appropriate Equation DLL for your model, then now for aspenONE V7.1 CP1 (Build 11.0.0.74) and Higher Version AORA models when you click the OK button located at the bottom of the preferences form the corresponding name of the selected Equation DLL will automatically be saved to the OLOCONFG Table, and the reference to the Equation DLL file location will automatically be hard-coded and saved to the Windows Registry based on the location that was setup for the Measurement directory during the Installation.
In short, the reference to the file name and path for the selected Equation DLL(s) is now mapped and stored in the windows registry in accordance with the default or other directory path location where they are installed by default as per the selected install directory specified during aspenONE V7.1 CP1 (Build 11.0.0.74) and Higher Version AORA Installs.
This newly added Windows Registry and OLOCONFG Table Equation DLL file mapping functionality combo now allows the users to then Install AORA (on either a Client or Server machine) into any directory they want (C:, D:, E:).
When a valid Equation DLL has not been selected or one can not be determined and loaded based on the Windows Registry and OLOCONFG file name/path mapping combo mentioned above, then the Equation DLL messages (prompts, warnings, errors, etc.) still apply the SAME as noted earlier in thisSolution for V2006.5.
Unless changed during or after Installation, the default location of the Measurement directory where the three Equation DLLS (iiequa32_us.dll, iiequa32_m15.dll, iiequa32_m20.dll) are stored is as follows:
C:\Program Files\AspenTech\Advisor\Measurement.
-- Recommended Quick Guide Procedures for selecting the Equation DLL for version V7.1 and Higher --
The Screen Shot provided below shows the Base System UOM Equation DLL Selection Feature as it now appears and functions starting with aspenONE V7.1 CP1 (Build 11.0.0.74) and Higher Versions.
Again, for selecting the required Equation DLL when Creating New Models in aspenONE V7.1 CP1 and Higher Versions, then the Base System UOM Equation DLL Selection Feature is also implemented the same on the New Model dialog/user form as per the radio button functionality discussed above.
IMPORTANT CLOSING NOTES:
** AspenTech DOES NOT recommend moving the Measurement directory after installing, nor should you move, delete, or rename the default Equation DLLS that are installed and located in that directory, as doing so would then require modification of the registry settings.
On any Client or Server installs or upgrades of AORA using the aspenONE V7.1 CP1 (Build 11.0.0.74) and Higher Version software, then if for any reason the AORA Equation DLL(s) are renamed or removed from the original install location and added to another file directory without also modifying the registry to account for such changes (NEVER Recommended); then in such cases an appropriate warning message will be displayed both when opening the model and/or trying to set the Equation DLL for the first time to let you know that the selected Equation DLL is invalid or could not be located, in which case it is then up to the user to insure that the correct and original files are put back in the proper location as originally installed.
** As long as you don't rename or delete the Equation DLL(s) from their default / selected installation directory, then following completion of the installation and configuration procedures documented in the Install Guide AORA will then continue to use without error the Equation DLL path logged in the windows registry that was specified and or selected respectively during the installation or afterwards along with the Name of the selected Equation DLL stored in OLOCONFG to locate, verify, and load the correct Equation DLL each time the model is opened and loaded moving forward.
Keywords: base measurement system
base system UOM
Equation DLL
iiequa32.dll
iiequa32_m15.dll
iiequa32_m20.dll
iiequa32_us.dll
Save full Equation DLL path?
References: None |
Problem Statement: When Importing movements as events from Aspen AtOMS into Aspen Advisor, the TEMPERATURE (Properties of the Temporary Integrator-Volume) coming from Aspen AtOMS is showing 15oC in Aspen Advisor even though the default temperature is in Degree F. | Solution: When movements are imported to Aspen Advisor from Aspen AtOMS as events, AtOMS2Advisor interface reads the temperature specified in Atoms2Advisor.ini file located at 'C:\ProgramFiles\AspenTech\AtOMS\Interfaces\AtomsAdvConnect' directory and sends it to the temporary Integrator volume instruments. The Atoms2Advisor.ini file has the parameters called TempBaseValue and TempUOM under [Property Config] section. If these parameters are different than the default units with which Aspen Advisor model has been created, the interface will import the incorrect temperature values and UOM to Aspen Advisor.
[Property Config]
......
TempBaseValue=60
TempUOM=F
......
.....
For example if using 'iiequa32_us.dll', these parameters should be 60 and Degree F respectively. If these parameters are not the same as shown above for a model using US default units, change that to 60 and F respectively to see if you get the correct temperature and UOM values into Aspen Advisor when importing movements.
Keywords: Temperature
Integrator volume
Atoms2Advisor.ini
References: None |
Problem Statement: This knowledge base article explains why a corrected volume may be calculated that is slightly different from the raw volume when the temperature of the reading is at the base temperature and density. A base temperature is 60F for the US model and 15C/20C for metric models. | Solution: The newer versions of Aspen Advisor (2004.2.1.x and later) use the new API 2004 standard whereas the previous versions of Aspen Advisor used the API standard 2540. While API standard 2540 corrected volumetric readings to a standard temperature and density, the API 2004 standard corrects the volumetric readings to a standard base temperature, density and pressure.
The corrected volume at standard conditions is computed by multiplying the volumetric reading at the operating temperature by a volume correction factor (VCF).
Vbase = Voperating * VCF
It is the inclusion of the pressure in the API 2004 volume correction factor calculation that causes the corrected volume to appear to differ from the raw volume at standard conditions. However, the API 2004 standard states that the standard condition for pressure is 0 psig. Therefore, if the pressure used with the volumetric reading is not 0 psig (or an equivalent pressure in another pressure unit) then the computed VCF will be slightly higher than 1. Evidence of this can be observed by using Aspen Advisor's System Calculator.
To access the System Calculator go to Tools | System Calculator.
A common case is to have the default pressure set to 101.325 kpa. However, when this value is used in the VCF computation the VCF is calculated to be 1.00005 instead of 1. This is because 101.325 kpa is not equal to 0 psig.
If the pressure is changed to be equivalent to 0 psig (-94.43030 kpa in this case) then the VCF is computed to be 1.
In Aspen Advisor the default pressure can be set for every product. To do this:
1. Go to Configure | Global | Properties
2. Select the Pressure property then click on the Details tab
3. Change the default pressure value. This value is entered in base units of measure. You may need to change the maximum or minimum value to allow the new default to be used.
Keywords: match
differ
difference
References: None |
Problem Statement: Aspen Operations Reconciliation and Accounting (AORA) cannot start in Windows Server 2003 R2 SP2 when full Data Execution Prevention (DEP) is enabled. When AORA is started up, it closes itself after the splash screen (verifying license...).
Checking the event log, you may find the following: | Solution: Turn ON DEP for essential Windows programs and services only.
[Instructions from Microsoft Website]
If you are logged on as an administrator, you can manually configure DEP to switch between the OptIn and OptOut policies by using the Data Execution Prevention tab in System Properties. The following procedure describes how to manually configure DEP on the computer:
1. Click Start, click Run, type sysdm.cpl, and then click OK.
2. On the Advanced tab, under Performance, click Settings.
3. On the Data Execution Prevention tab, use one of the following procedures:
o Click Turn on DEP for essential Windows programs and services only to select the OptIn policy.
o Click Turn on DEP for all programs and services except those I select to select the OptOut policy, and then click Add to add the programs that you do not want to use the DEP feature.
4. Click OK two times.
Keywords: Advisor
Windows 2003 R2 SP2
Faulting application Advisor.exe
References: None |
Problem Statement: This | Solution: illustrates how to add user defined tools in the Aspen Advisor Tool bar using Configure Tools in Aspen Advisor.Solution
In order to add the user defined tools to one of the tabs in the Aspen Advisor Toolbar
Go to Tools-->Configure tools. Click add and browse for the executable of the tool that needs to be added and select Command line as status
After this the specific tool will be added to Aspen Advisor under Tools in the tool bar.
Keywords: Configure
Tools
References: None |
Problem Statement: Is there a way to add a Standard report to the Aspen Operations Reconciliation and Accounting (AORA, formerly called Aspen Advisor) database using Aspen Reporter? | Solution: Following is the procedure on how to save the report to the AORA database,
1. Go to the Aspen Reporter and open the model for which you want to add the reports.
2. Within the Aspen Reports go to Reports --> Report List, and select the report you want to add to the database and click on modify.
3. This opens a separate window where you can check the option 'Save Report to the Database'. Checking this option will save the report selected to the database within OLORPTLS table. This OLORPTLS table lists all of the Advisor reports that have been selected by the user. Please refer the Aspen Reporter help for more information on how to configure different parameters.
Note: With this option checked user can see/run the reports by simply logging into the Aspen Reporter on a machine located in the network avoiding the need to add it onto each and every client machine separately.
Keywords: Reports
Save
Database
OLORPTLS
References: None |
Problem Statement: When opening the Aspen Advisor Reporter application, the user default preferences for the preferred Advisor Reports and Report Groups are no longer being loaded respectively into the Selected Reports application window and the Report Group selection drop-down box. | Solution: IMPORTANT:
The user configuration and preference settings for Aspen Advisor that were previously saved and stored in the *.ini files (aion.ini, iirpt.ini, iisys.ini, atautoprocess.ini, advexcel.ini, etc.) in ALL versions prior to v2006.5 are now saved and stored in the Windows Registry in matching keys created using the same file names.
These new Advisor Registry Keys that now replace the old *.ini files are located in the following key folder or registry hive in the Windows Registry: HKEY_CURRENT_USER\Software\AspenTech\Advisor
The user configuration and preference settings for the Aspen Advisor Reporter that control the default user views and settings for the Advisor Reports are saved and stored in the registry keys located in the following key folder: HKEY_CURRENT_USER\Software\AspenTech\Advisor\iirpt.ini.
If this problem occurs when opening the Aspen Advisor Reporter such that the default user configuration and preference settings for the preferred Reports and Report Groups no longer load, then check the Advisor IIRPT.INI Registry Keys against those found on a Working PC to try and determine what the differences are and whether any of the key values have possibly been deleted or are missing.
To open the registry click Start | Run and type in regedit then press the Enter key or click the OK button.
Once you have determined the differences in key values between machines and/or have determined which key values you require that are missing, then the two options you can use to restore your user configuration and preference settings are as follows:
Option 2 is recommended if the default user preferences at least in regards to the report names and the selected reports and report groups are to be installed and configured the same on many or all of the client machines for your site; otherwise, you may have to use Option 1 or a combination of Options 1 and 2 as needed.
1. Restore the default user configuration and preference settings for the preferred Reports and Report Groups by Manually resetting and rebuilding/re-adding the Report Groups and Report user preferences using the Aspen Advisor Reporter GUI. Once the preferences have been restored manually using the Reporter GUI, then when you refresh the registry view you should now see the corresponding key values added to the appropriate IIRPT.INI Registry Keys.
2. Export/Import key values from the Working PC to the Problem PC as needed. To export the desired registry key from the Working PC to the Problem PC please proceed as follows:
Open the Windows Registry Editor on the Working PC using the procedure as previously noted in thisSolution.
First highlight the desired key in the registry editor explorer window, i.e., in this case the IIRPT.INI key or one of its Sub-Keys depending on whether you want to export/import all report and/or group settings or just a sub-set of these settings.
Then you can either right click on the desired key and select Export from the options menu or from the registry editor menu bar click File | Export... to bring up the Export Registry File dialog box.
Now using the Export Registry File dialog box select or enter a file name for the export file then select a location to save it to and click the Save button.
Transfer the saved registry key file to the Problem PC or to a shared directory as needed.
Now open the Windows Registry Editor on the Problem PC and import the selected registry key information that was saved and exported from the Working PC by first clicking File | Import... from the registry editor menu bar to open the Import Registry File dialog box.
Now complete the registry key import process using the Import Registry File dialog box select the registry key file that you exported and saved from the Working PC and click the Open button to complete the import.
NOTE: You may also import the registry key information by simply double clicking on the saved registry export file and then following the user prompts that will appear.
Customer Example:
In the Registry for Advisor 2006.5 there is a Report Group key (as noted below) that stores the Default Report Group user preferences that have been configured for the Aspen Advisor Reporter on the respective client machine, and somehow the settings in that registry key on a specific user's machine got deleted.
--- HKEY_CURRENT_USER\Software\AspenTech\Advisor\iirpt.ini\Report Group ---
This problem was discovered by comparing the contents of the Advisor Registry Keys on the user's machine to the contents found in the same registry keys on the server where the Aspen Advisor Reporter was working and displaying the expected defaults for Selected Reports and Report Groups. Once we discovered the problem, we simply exported and saved the contents of the registry key on the server (key file name/location as noted above) to a *.reg file, and then imported the contents from that file into the same registry key on the user's machine.
After exporting / importing the Report Group defaults from the server registry key to the registry key on the user's machine, then the defaults were restored and the user could once again see them loaded when opening the Aspen Advisor Reporter and was able to run the reports again as needed.
Keywords: Advisor Registry Keys
Aspen Advisor Reporter
IIRPT.INI
INI Settings
Reports
Report Groups
User Preferences
References: None |
Problem Statement: Is Windows Server 2008 a Supported Platform for Aspen Operations Reconciliation and Accounting V7.1. | Solution: NO, as per the V7.1 Release Notes for this Product, which are Correct:
Aspen Operations Reconciliation and Accounting V7.1 is NOT supported on the following Platforms:
Windows Server 2008
Non-English editions of Windows
NOTE: This applies to all associated applications licensed in the Aspen Operations Reconciliation and Accounting package (formerly known as Aspen Advisor) including Connect, Reporter, DBTools, SSI (Spreadsheet Interface), the Excel Add-In, the Reconciliation Publisher, and the Expert System, ALSR (Advisor Least Squares Reconciliation) Math Engine and other added modules (for Sales and Receipts, ERP, and Planning) as used by the Main application GUI.
Keywords: Aspen Advisor
Aspen Operations Reconciliation and Accounting
Supported Platforms
V7.1
Windows Server 2008
References: None |
Problem Statement: This Knowledge Base article answers the following question: What is the meaning of MLbs in Advisor? | Solution: MLbs means 1000 pounds and MMLbs means a million pounds.
Mlbs is short hand for 1,000 pounds of mass. The s is added to indicate plurality. The capital M is from the Roman numeral system where M represents 1000. This should not be confused with the M commonly seen in the metric system which is Mega for million.
Keywords: None
References: None |
Problem Statement: Aspen Advisor's simulation tool is used to propagate realistic values for property, component and/or product component data to the next accounting period to be used in the event that no actual readings are imported. It is also used to track user-defined properties (such as percentage of sulfur) throughout materials in an Aspen Advisor model. This knowledge base article provides a description of the update from readings and the linear blend (LB) algorithms. | Solution: The update from readings strategy simply propagates today's physical property, components, and/or product component values forward to the next accounting time interval. Today's property, component, and/or product component values may represent actual readings entered by the user for the current accounting interval or values which were previously simulated during the previous accounting time period. The system will take the simulated values for yesterday and then update them with the latest readings on the tanks and pipes for today. No GC calculated, product default, or global default values will be propagated to the next accounting period.
The LB algorithm blends the properties or product compositions in a linear fashion based on the amount of each product present in the mixture. The LB algorithm assumes perfect mixing in each vessel. The best way to illustrate the LB algorithm is with an example.
Assume a single tank has two pipes flowing in and one pipe exiting as in the following image.
Pipe A has 1000 lbs of product A and pipe B has 1000 lbs of product B. All of product A and product B flow into the tank. Since equal amounts of each product exist in the tank, the tank will then have a composition of 50% product A and 50% product B. The properties (temperature, density, any user defined properties, etc) will be blended in a similar fashion.
Linearly blending temperatures and pressures can yield unrealistic results. It is usually better to set the the linearity attribute of the properties that you do not want linearly blended to 'non-linear' so that these properties are updated from readings when simulation is run.
Keywords: LinearBlend
UPD
References: None |
Problem Statement: I am either Upgrading to or Installing for the first time my Aspen Operations and Reconciliation Accounting software and model database using an aspenONE version (V2006.5 or Higher) that now utilizes the API 2004 specifications for API-VCF Calculation, but my site still imposes regulations that require me to use and maintain values consistent with the the API 1980 specifications.
When Upgrading to or Installing aspenONE V2006.5 and Higher software release versions of Aspen Operations Reconciliation and Accounting (formerly Aspen Advisor), then for API-VCF Calculation in V2006.5 and Higher AORA Releases, how do I switch from API 2004 back to API 1980 if my site still requires API 1980 usage and value matching? | Solution: Download and/or Print and Review the PDFSolution File noted below that is attached to thisSolution
Changing between API 1980 and API 2004 for VCF Calculation.pdf
Keywords: API 1980
API 2004
AspenTech.MSC.Settings.xml
legacyvcf
VCF
Volume Compensation
Volume Correction
References: None |
Problem Statement: How can we force and/or insure that a New and separate Pipe is created for each New User-Defined Discrete Event (material movement transaction) that is manually entered or imported?
Reason for Asking:
When manually entering New Event Data using the AORA (Aspen Operations Reconciliation and Accounting) GUI we have found that if you select the SAME Source and Destination as per what is already used by an Existing Event, then in this case the System automatically selects and uses the same pipe associated with the Existing Event.
The result is that you end up with Multiple Events (different discrete stream flow transactions) associated with and combined onto the same pipe in the model. And in the case where the Integrator Instruments are used for the reading measurement quantities (Volume or Mass), then before you assign a Volume or Mass measurement reading for the New Event you must also manually create and attach a respective yet separate Integrator Instrument to the existing pipe; otherwise, the system forces you to use the one of the existing Integrator Instrument(s) which results in overwrite of existing readings if the same End Time is also used.
When importing New Events for the same Operating Date where more than one of the Events to be imported (or Existing Events for that date) use both the same Source and Destination objects, then in this case we can also see that the system also uses the same pipe. And one advantage point we also see when importing is that when using Integrator Instruments an individual instrument (one for each event assigned to the pipe) is created automatically by the system.
However, due to this default system behavior described above, trying to then reconcile and troubleshoot problems with the daily balance can become confusing and much harder for the users to then sort out which events are the source of errors. For this reason we want the system to instead create an individual (separate and unique) pipe for each and every User-Defined Discrete Event that is either manually entered or imported, regardless of whether a selected event uses the same source and destination objects as other events. | Solution: Manual Event Creation using the AORA GUI:
NOTE: When you attempt to manually create an Event (material movement transaction) in AORA using the GUI menus and associated dialog forms and you select a Source and Destination that is already associated with a Pipe created for an Existing Event, then by default the AORA System will Auto select that same pipe for the New Event Entry. Using the same pipe is OK, assuming that you do not enter the SAME start and end time that coincides with any of the existing event(s) that are already using that same pipe.
In the case that you do prefer or need to have a separate pipe created for the New Event, then the Trick to forcing/allowing for a New Pipe to be created for the New Event entry is as follows:
1. Once the Source and Destination objects are selected, then in the Pipe: field on the Event entry dialog you must then select __Not in this zone from the Drop-Down.
2. Now click the Modify button located at the bottom of the Event entry dialog form. You will receive a message box that includes the following text, Pipe Does not exist. Do You want to Auto Create it?
3. Click the Yes button on that message box, and the New Pipe will then be created and you can continue with the remaining configuration and setup procedures required to complete the Event Entry.
Event Creation via import of the ILEEVENT and other associated import table data for Events:
NOTE: Event data held in the AORA Import Tables can be imported to the database Data Tables using either the AORA Importer (located in the GUI) or using AORA Connect to execute user defined Standard Text File or Historian import processes.
With that said, when Importing Events there is NO method or import switch that exists to mimic the manual creation procedure noted in the previous section above to allow for creating a New Pipe for each New Event that is imported.
Thus, when importing New Events for the same Operating Date where more than one of the Events to be imported (or Existing Events for that date) use both the same Source and Destination objects, then in this case both the AORA Importer and AORA Connect as currently designed will automatically assign those events to the SAME Pipe regardless of whether there are 2 Events or 200 Events that share the same Source and Destination objects.
The following Enhancement Request referenced below has been submitted to the AspenTech Development Team to ask for an added import switch or configuration (user preference) setting to also allow for separate pipes to be created individually for each new event that is imported.
CQ00406038: Request to Add a New Import Switch to allow system to create multi-movements (same Pipe, Src, Dest.) each on its own Pipe.
Keywords: Auto Create
Events
Multiple Movements
Not in this Zone
Pipe
Same Source
Same Destination
References: None |
Problem Statement: Since upgrading to the Aspen Advisor V2006.0 software release, there are now 2 tanks out of the 20 tanks included in the model database that are showing the wrong temperature readings after we import the inventory and property data and run the Expert System then execute the Simulation for Properties. The imported temperatures for these two tanks are showing up both in the GUI and on the Standard Tank Reports as a value of -99.9999.
Confirmed Root Cause:
The reason for the -99999 and/or -99.999 values being displayed on the Tank Reports is because that is what was actually being returned by the API call made to the Aspen InfoPlus.21 historian and then imported to the AORA model database Data Tables. And in this reported case for the two problem tags in question, the History values for both were either Bad or completely missing for the selected import date, and thus as a result the Connect application then imports the -99999 or -99.999 value returned by the API.
? In fact for the tags involved in this case, it was later confirmed that the value for IP_TREND_VALUE was consistently being logged as ?????, and a check of the past History values revealed this was true going back at least 6-8 months. And the customer's IT Team confirmed that both tags had either been shut down or were not working properly out in the field. As a result, further investigation found a set of secondary tags in IP.21 that were collecting Good History values for the Lab Temperature Readings for the same two tanks in question, and those respective tags appeared to be collecting the data we needed. Once we changed the Tag Name linkages between IP.21 and Advisor to use these alternate tag names, this helped resolve the problem.
With that said, further research and regression tests have confirmed that for all Aspen Advisor software versions released prior to V2006.0, the Advisor Connect application recognizes the resulting Bad Tag value cases where the -99999 or -99.999 value is returned by the API call for invalid history collections; and thus it will reject the -99999 or -99.999 return value and force an import failure for such tags as expected to also include the appropriate import error failure message in the import log.
Before upgrading to V2006.0, then using the previous software releases what was happening in the case outlined above is that no new values were being imported for the two bad / shutdown tags, and instead simply the last good temperature reading that was imported was being carried forward the same each day both in the Advisor database and on the Reports as simulated value propagated by running the Simulation using Update from Readings.
IMPORTANT: Thus the default import behavior did change adversely starting with the aspenONE V2006.0 software release. See KB Article 131693 for more detail on the related defects that have been submitted for this and related problems where import the of Snapshot values results in a return value of -99999 or -99.999. | Solution: To fix the problem in Advisor and on the Advisor Reports for the 2 problem Tanks the following steps were completed:
1. In the Advisor GUI, opened the Details Dialog for each problem Tank's Lab Vessel Instrument and changed the Tag Name of the Tank's Lab Vessel Instrument to match the New Tag/Record Name that we found in the Aspen InfoPlus.21 Data Historian that was collecting valid and Good Quality Level History values.
2. Reran the Tank Inventory Advisor Connect Import Process and observed in the Import Log and in the Advisor GUI that the correct value for the Tank Temperature for both tanks was now being imported successfully.
3. Reran the Expert System IRSS steps (Initialize, Reconcile, Save, and Simulate) to refresh and save the corrected Tank Temperature import values to the Data (Reporting) Tables.
4. Last, we reran the associated Standard Aspen Advisor Tank Report currently being used by the customer to verify that the Tank Temperature for the 2 problem tanks now displaying on the Reports was correct.
IMPORTANT: In the case where a Tank Temperature, Inventory, or other Snapshot reading import still results in an imported value of -99999 or -99.999, then the best way to correct or prevent this value from being imported to your model is to check the History values in the Aspen InfoPlus.21 Data Historian for the problem tags before executing the import from Connect to first insure that the collected History values do exist for the selected import date and that they are valid (including a Good Quality Level). And if needed then manually correct any remaining readings using the Instrument dialog forms before rerunning the Expert System, Simulation, and Reports.
Keywords: -99999
-99.999
Imported Readings
IP_TREND_VALUE
Lab Vessel Readings
Tank Reports
Tank Temperature Readings are Invalid
References: None |
Problem Statement: The following message may be observed when adding an object to an Aspen Operations Reconciliation and Accounting (AORA) model:
This knowledge base article documents this message and describes why it occurs. | Solution: This message is returned because the user has attempted to add an object to the model that is outside of the flow sheet boundary. Since the boundary limits are hard coded in AORA there is not any way to change the boundaries. Therefore any objects that are added to the AORA model need to be added within the boundary.
By default the boundary line is not visible to the user. You can make the boundary line visible by checking on Draw Boundary Rectangle within Other tab in Diagram--> Preferences from the AORA GUI as shown below. With the boundary lines visible you will be able to ensure that new objects are added within the boundary and, therefore, prevent this message.
Keywords: Boundaries
Trying to add the vessel outside of the boundaries. Do you want to add it inside the boundaries?
Diagram
References: None |
Problem Statement: This knowledge base article describes one method that may be used to handle a Subsystem imbalance. A subsystem imbalance may occur if the subsystem tank product service is changed to another product service, which is not part of a subsystem. | Solution: There is a instrument type called Product Adjustment which may be used for adjusting imbalances around subsystem objects when there is a non subsystem tank service changed to subsystem or subsystem tank changed service to non subsystem tank. This also allows you to make adjustments in positive imbalance or negative imbalance, by using positive and negative values accordingly.
When the product adjustment instrument is used the adjustment is only for the subsystem inventory not the individual tank inventory.
Keywords: Product Adjustment.
Subsystem
References: None |
Problem Statement: I am using the Aspen Operations Reconciliation and Accounting Excel Add-In to set up an Event Entry for a movement or transfer and then Import that Event Entry into the AORA model database.
The required Text Import File processed by AORA's Connect Application is created successfully by the Add-In, but when I execute the event import through Connect using the Add-In interface execution commands then the attached log file error shown in the screen shot provided below is occurring.
What does the Priority error mean and how can I resolve this error to allow for a successful Event Entry import? | Solution: The errors that read like the following:
Error - 1 EIM1 Priority-> is not integer for reading.
Error - 2 EIV1 Priority-> is not integer for reading.
The associated EIM1 records and errors represent Mass Events, while the associated EIV1 records and errors represent Volume Events.
These errors are occurring (and will prevent a successful import) because the corresponding Event Entry located on the ImportEvent sheet in the Excel import template file being by the Add-In does not contain a valid Priority reading.
IMPORTANT: All Event Entries must be imported with a Priority reading (integer value) of 0 for Firm or
1 for Estimated. The Priority level reading is entered in the column labeled F=0/E=1.
Thus to resolve the error and allow for a successful import of the problematic Event Entry then please enter an integer value of 0 or 1 in the F=0/E=1 field (column) for the required Priority reading and try again.
Also, the Beginning Volume or Mass Reading entered in the Column labeled Begin should be set to a value of 0 for all Mass and Volume Event Entries where the Integrator Instrument option is used.
*** Added Notes about Add-In Data Entry ***
When using the Add-In it is much easier in most cases (especially for first time users) to enter and set all the necessary information if you use the recommended Data Entry form (shown in second screen shot below).
To open the Data Entry form simply put the cursor in the cell in Column A where the Event Tag Name is located and Right-Click and select Data Entry from the Right-Click menu options.
Keywords: Advisor.xla
Connect
Data Entry
EIM1 Priority-> is not integer for reading
EIV1 Priority-> is not integer for reading
Estimated
Excel Add-In
Event Import
Firm
References: None |
Problem Statement: This knowledge base article describes if it is possible to import the data into Aspen Operations Reconciliation and Accounting (AORA), formerly called Aspen Advisor, model for multiple days using AORA add-in through AORA Connect. | Solution: The AORA add-in does not automatically handle importing data for multiple dates. When there is data for multiple days in the spreadsheet, at the process of creating text file in the AORA add-in will build a text File for all of the data that includes multiple dates. But, when the Run AORA Connect routine is executed it will only import data for the date you have selected on the interface for import. The rest of the data will be processed but remain in the import tables until the data is manually imported for each date using the Import from the Tools menu in the AORA GUI or via an extra batch script run from AORA GUI or AORA Connect.
Keywords: AORA Import
Multiple days
Connect
add-in
References: None |
Problem Statement: This knowledge base article explains how the extrapolate options of the strap tables work in Aspen Advisor. | Solution: Aspen Advisor uses Strap Tables for Volume look up from the tank gauge readings.
If the entered Gauge Reading is within the Strap Table height, then Aspen Advisor picks up (calculates) the Volume reading from Strap Table by either the taking the value of the straight lookup if an exact match is found, or by using the interpolate options if the gauge height reading falls between specified point in the Strap Table.
If the entered Gauge Reading is above the Strap Table maximum height (i.e., out of range per the defined table range), then Aspen Advisor tries to extrapolate the Volume. This is the default behavior by design in Version 2006.5, and this same default behavior can be added to previous versions (2004.x.x and 2006.0 versions) as well by applying the latest patches for those versions.
If you want to override the extrapolate behavior of Aspen Advisor, i.e. if you do NOT want to use the default extrapolate feature, then adding the following setting to the OLOCONFG database table will help:
Insert a New Record in the OLOCONFG table with the TAG Column value set to EnforceStrapRange and the LDESC Column value set to 1. Valid values are 0 and 1:
0: = Use extrapolate feature in the Strap table.
1: = Do not extrapolate strap table
When this record is not present, then the Aspen Advisor default behavior is assumed according to a 0 setting.
Below is the sample screen shot for the above configuration. Please remember, TIME_BEG and TIME_END should also be set as appropriate for your model period:
Keywords: Strap table
interpolate
extrapolate
heights
above
out of range
References: None |
Problem Statement: This knowledge base article describes one approach that may help to allow a large model to converge when the error
Error returned DMO system status =5
is encountered in the ASRC_XXX.log files. | Solution: The aforementioned error may occur when the Aspen Least Squares Reconciliation (ALSR) engine is used to distribute random error on a very large model.
When this error is returned check the ASRC_XXX.log files to determine the size of the sum of the square of the error encounter by the solver. In many cases the sum of the square of the error will be quite large (on the order of 1e+13 or greater). If this is observed, go to the Mathematical Reconciliation preferences in the Expert menu then set the Objective Scale from its default value of 1 to a value that, when multiplied by the observed sum of the square of the error, will roughly equal 1e+9.
For example, if the sum of the square of the error is observed to be 1e+13 set the Objective Scale to 1e-4.
Quadratic solvers are typically designed to scale around unity. However, most quadratic solvers are robust enough to handle large problems sized around 1e+10. The Objective Scale is an objective function multiplier that is exposed to the user to allow tuning for convergence of complex models.
Keywords: QP
Quadratic Program
Convergence
References: None |
Problem Statement: How to resolve the error 'The procedure entry point?............could not be located in the dynamic link library IIPL.dll.' shown in the screen capture below
One might encounter this error while opening the model after the new install or upgrade of Aspen Advisor. | Solution: This error 'The procedure entry point?............could not be located in the dynamic link library IIPL.dll.' occurs if Aspen Advisor does not locate some of the files in the dll's during the installation/upgrade. In order to resolve this issue delete all the Aspen Advisor folders as well as entries in the registry (if using 2006.5) on the machine. After this do a re-install of Advisor.
Reinstallation of Aspen Advisor helps in resolving the 'The procedure entry point?............could not be located in the dynamic link library IIPL.dll.' error.
Keywords: Procedure
Entry
Upgrade
Install
References: None |
Problem Statement: Aspen Advisor has 'Integrator Mass / Volume' instrument to configure custody transfer meters for reconciliation purposes.
If you enter manual value for 'Integrator Mass/Volume' meter, through Advisor GUI, it will accept but the readings does not consider the flow during reconciliation. Why? | Solution: Aspen Advisor 'Integrated Mass / Volume meters' can be used in only in conjunction with Events. In Other words, Integrated mass/ volume meters readings should always come from Events. Events may be imported from Aspen AtOMS, Advisor Excel-addin or through Aspen Advisor event creation GUI. So Aspen Advisor considers integrator Mass / Volume readings only from events , for reconciliation purposes. It is the way , Integrator Instruments are designed in Aspen Advisor.
Keywords: Integrator
Event
reconciliation
References: None |
Problem Statement: As of version 2006.5, Aspen Advisor now stores the *.INI File model configuration settings and user preferences for all but a few of the Advisor Applications in the Windows Registry rather than using the actual *.ini files that were previously stored in the Windows and Advisor Install directories for all Advisor versions prior to 2006.5.
These new Advisor Registry Keys that now replace the old *.ini Files are located in the following key folder or registry hive in the Windows Registry: HKEY_CURRENT_USER\Software\AspenTech\Advisor
For Aspen Advisor version 2006.5 and higher, these INI registry settings are now configured, set, stored, and accessed on a per user basis. Previous Advisor Systems (versions) that used the INI Files demanded that ALL users on a machine had to share the same settings.
This Knowledge Base article answers the following question often posed nowadays by customers upgrading to v2006.5 and higher from earlier versions of Advisor...........
How to migrate the Advisor App configurations settings and preferences stored in the *.INI files to the Registry for v2006.5 and Higher? | Solution: Use the *.INI File Settings Migration Utility provided by development and attached to thisSolution. Aspen Advisor 2006.5 introduced the relocation of the INI settings to now use the Windows System Registry instead of the previously used text-based *.INI Files that were common in ALL previous versions of Advisor.
File Distribution for the Utility is as follows:
Attached Zip File:
INI Settings Migration Utility 2006.5 Jun-2008.zip
3 Files Included in Zip:
-- AdvExcel.INI.reg
(relates to and used for migration of the Advisor Excel Add In settings)
-- README.txt
(reiterates instructions and notes included below)
-- SettingsUtility.exe
(this is the utility executable used to run the migration utility program)
The utility included in the attached zip file is to be used ONLY for aspenONE 2006.5 installations of Advisor. It is not meant for nor will it work with any previous version of Advisor. This INI settings migration capability will be integrated directly into Advisor in future releases.
The SettingsUtility.exe program converts the following *.INI Files to the registry:
-- iisys.ini
(This is the MAIN ini file for the Advisor GUI model settings and user preferences)
-- AdvExcel.ini
(This is the ini file for the Advisor Excel Add-In settings and preferences)
-- ATAutoProcess.ini
(This is the ini file for the Advisor Connect settings and Import Process configuration)
-- iirpt.ini
(This is the ini file for configuring the Reports for the Aspen Advisor Reporter)
-- aion.ini
(This is the ini file for the Expert System and associated settings and preferences)
The settings in these files are migrated into the following registry hive:
HKCU\Software\AspenTech\Advisor\<ini_file_name>
e.g.
HKCU\Software\AspenTech\Advisor\iisys.ini for migration of the iisys.ini file and likewise for the others.
[PREREQUISITES -- ONLY if Migrating the AdvExcel.ini]:
The original versions of 2006.5 Advisor did not migrate the settings of the Advisor Excel Add-in to the registry.
Releases of 2006.5 posted after Mar-2008 have this capability.
If you are running an Advisor 2006.5 release prior to Mar-2008, then the AdvExcel.INI.reg file included in the attached zip file has to be imported into the registry first, and to do this simply double-click the AdvExcel.INI.reg file before running the SettingsUtility.exe utility.
If running a Post Mar-2008 Advisor 2006.5 release, then simply running Advisor with the following command line parameter will allow this to work: C:\Program Files\AspenTech\Advisor>advisor /register
[USAGE]:
To Start the utility, double-click the SettingsUtility.exe from Windows file Explorer.
The utility has two functions:
1.) Import from INI:
When this button is pressed, the utility will search out the 5 INI Files listed above. The utility looks for these files in the Advisor installation directory (assuming the SettingsUtility.exe is itself installed in the Advisor installation directory), then it will look in the Windows directory, in that order.
If the Overwrite check box is checked, any existing Advisor settings in the registry are cleared out before importing the available INI file data.
SPECIAL PROCEDURES for migrating AdvExcel.ini:
Although the utility does migrate the contents of the AdvExcel.ini file to the registry, the registry key it uses is not the required key that 2006.5 was designed to use for the Advisor Excel Add-In, and thus a Workaround MUST be applied in order to successfully migrate the AdvExcel.ini file to the registry such that the Advisor Excel Add-In will recognize those settings when loaded.
The Workaround procedure currently required for the AdvExcel.ini file migration is provided in the following Known Issue KB article:Solution ID 125064: CQ00350243: The Aspen Advisor INI File Settings Migration Utility Migrates the AdvExcel.ini file settings to the Wrong Registry Key.
http://support.aspentech.com/webteamasp/KB.asp?ID=125064
2.) Export to INI:
When this button is pressed, the utility will take the current settings in the registry and write out the original INI Files to the user's TEMP directory. The utility does NOT write the files to the installation directory nor the Windows directory.
[ADDITIONAL NOTES]:
The Spreadsheet Interface (SSI) application for Aspen Advisor 2006.5 still uses the direct IIMPT.INI File and DOES NOT look at the Windows registry to obtain SSI settings. Testing by AspenTech Support has confirmed that Advisor still uses the IIMPT.INI file for the SSI that is located in C:\Windows or C:\Winnt depending upon the OS being used.
The reason for NOT including the SSI file IIMPT.INI in the registry as part of the INI File Migration change for Aspen Advisor 2006.5 is that the SSI at some point in the future will no longer be supported. Going forward, the plan is to eventually phase out and completely replace the SSI with the Advisor Excel Add-In, which many customers are already using in addition to or as an alternative to the SSI.
The Date on which the Spreadsheet Interface application will No Longer be Supported has not yet been set, but as soon as this Date is known a corresponding Product Lifecycle Policy will be issued.
Keywords: Advisor
IISYS.INI
IIRPT.INI
AION.INI
ATAutoProcess.ini
INI Settings Migration
References: None |
Problem Statement: All applications which write data to Aspen Advisor place the data in the Aspen Advisor import tables. The data is then moved to the Aspen Advisor data tables using the Aspen Advisor Importer. Sometimes it becomes necessary to monitor the data in the import tables before it is moved to the data tables. This knowledge base article explains how to capture the data in the import tables before it is moved to the data tables. | Solution: The Aspen Reporter contains reports which return the contents of each import table. ThisSolution involves creating a batch script which launches the Aspen Reporter then exports each of the import table reports to html format. The batch script which invokes the Aspen Reporter should be scheduled to execute through the Windows Scheduler after the data has been written to the import tables, but before the data has been moved to the data tables (before the Aspen Advisor Importer has been executed).
Note: Aspen Advisor Connect will, by default, automatically execute the Aspen Advisor Importer. If you need to view the data in the import tables which was imported through Aspen Advisor Connect you must set Aspen Advisor Connect to not automatically execute the Aspen Advisor Importer.
Procedure:
Two batch files are required. The first batch file is named RunReporter.bat. This batch file launches the Aspen Reporter then calls the second batch file. This is the file which should be scheduled to run through the Windows Scheduler. The contents of this first batch file are shown below.
------- BEGIN RUNREPORTER.BAT -------
c:
cd \program files\aspentech\advisor
Report32.exe .\batch\ExportImportTables.bat
------- END RUNREPORTER.BAT -------
The second batch file is called ExportImportTables.bat. This file opens a specified Aspen Advisor model then executes the import table reports. The ModelName, UserName and Password need to be changed to open a model at your site.
Note: The batch script commands in ExportImportTables.bat reference specific report names. If the iirpt.ini file on your system has these reports named differently then reports will not run from this batch script. The attached iirpt.ini contains report names which work with this batch file.
------- BEGIN EXPORTIMPORTTABLES.BAT -------
openmodel ModelName, UserName, Password;
AddReportForExport View Import Gauge Table, html, c:\ilrgauge.htm;
AddReportForExport View Import Fractional Gauge Table, html, c:\ilrgfrc.htm;
AddReportForExport View Import Integrator Mass Table, html, c:\ilrintgm.htm;
AddReportForExport View Import Integrator Volume Table, html, c:ilrintgv.htm;
AddReportForExport View Import Lab Pipe Table, html, c:\ilrlabpi.htm;
AddReportForExport View Import Lab Vessel Table, html, c:\ilrlabvs.htm;
AddReportForExport View Import Inventory Mass Table, html, c:\ilrmass.htm;
AddReportForExport View Import Meter Table, html, c:\ilrmeter.htm;
AddReportForExport View Import Inventory Volume Table, html, c:\ilrvolum.htm;
AddReportForExport View Import Components Table, html, c:\ivrcomp.htm;
AddReportForExport View Import Properties Table, html, c:\ivrprop.htm;
Exportall;
closemodel;
exit;
------- END EXPORTIMPORTTABLES.BAT -------
Once these two batch files have been verified to produce reports when RunReporter.bat is double clicked in your environment, you can then schedule RunReporter.bat to run with the Windows Scheduler. To do this:
Open Scheduled Tasks by going to Start | Program | Accessories | System Tools, and then click Scheduled Tasks.
Follow the instructions to configure a new Scheduled Task. When prompted to select a file to run, browse to the folder which contains RunReporter.bat.
Next, select the time that you would like the file to be executed.
When prompted to enter a user account to run the task, make sure to specify an account which has permissions to execute programs.
Keywords: Collect
Schedule
Gather
Monitor
Dump
References: None |
Problem Statement: This knowledge base article explains why all events are treated as estimated when both estimated and firm events exist on the same pipe. | Solution: Aspen Advisor's reconciliation is done on a pipe basis, not on an event basis. It is not possible to have a pipe with some estimated events and some firm events. If you need to use estimated and firm events for the same source and destination vessels you will need to define two separate pipes between these vessels. One pipe will hold the firm events while the other holds the estimated events. You will need to use permanent pipes instead of temporary pipes if you want to have separate pipes for estimated and firm events.
Since the reconciliation is performed on a pipe basis, even if you choose to use a single (temporary) pipe for the firm and estimated events, the overall balance for this pipe should still work out to be ok even if the individual events within the pipe are not adjusted correctly.
Keywords: balance
multiple
References: None |
Problem Statement: Companies may change the names of products for marketing reasons, or because of mergers or acquisitions. Although the product may have a different name, it is essentially the same product.
Most attributes of objects in Advisor models are time-stamped and show the different attribute values assigned for different active time periods. The name attribute has been designed differently by the Advisor development team in that it consistently shows the current value, even when looking at historical data before the name change. Reconciliations and reports regenerated for historical data, show the new product name instead of showing the old name as might be expected.
The reason for this design decision was that many clients had requested to be able to change the name of an object and have it affect the data for all time, since the name is considered a key by many systems. Since Advisor uses an integer key as an index reference to the object, this was possible, without having to change all of the data that references the object. If Advisor allowed the name to change over time, it would be difficult to show a month to date report that broke production down by product, since two different product names would really refer to the same product.
In some cases, however, customers may wish to see reconciliations and reports showing the old name for historical data, while using the new name for current and future reconciliations and reports. | Solution: If you want to have a different product name for current and future data, and still want to maintain the old product name for historical data, then you need to create a new product global object with the new name, enter in the same default properties for it as the old product, and then re-assign your pipes, tanks, meters, gauges, events, etc. to start using the new product on a particular date. This will maintain the historical usage of the old product name while enabling the use of the new product name in current and future reconciliations and reports.
Keywords: product names
historical data
Advisor model objects
References: None |
Problem Statement: How do the properties, Gas Heating Value and Mass Heating Value, affect Aspen Operations Reconciliation and Accounting calculations? | Solution: Advisor uses the Gas Heating Value (GHV) and Mass Heating Value (MHV) properties to calculate the fuel oil equivalent (FOE) liquid volume of gaseous and solid products, and there are some specifics that need to be mentioned as well about how and when these property values get applied in the FOE Calculation.
NOTE 1:
The FOE calculation also uses a Net Liquid Fuel Equivalent (NLFE) factor, which is defined as the heat energy per fuel oil equivalent volume, and this added NLFE factor must be configured by each client in Configure | Global | Units of Measure (UOM).
This NLFE factor represents a constant that is typically in the range of 5.7-6.5 MM BTU's/FOE Barrels. In Aspen Advisor the Default UOM Name for this factor in Newly Created US 60F Basis Models is NLFEB to represent the NLFE per Barrel of Oil, and the corresponding default value is 5960000 BTU's/FOE Bbls.
NOTE 2:
To ensure consistency in calculations, all measurements and constants should be in the chosen base Units of Measure.
NOTE 3:
Gas volume flow will be corrected to standard temperature and pressure by Advisor before being used in calculations, and the conversion from Volume flow to Mass flow or vice versa as needed for each calculation noted below is obtained respectively by the Mass flow divided by the Density to get the Volume flow and/or the Volume flow multiplied by the Density to get the Mass Flow.
In such cases where the density is needed in the calculation for Volume/Mass conversions, then if NO explicit Density reading value is supplied to represent the density of the Gaseous flow, then the DensityAir value from OLOCONFG is used. Otherwise if an explicit Density Gas value is supplied in the Properties Table for the Reading, then that supplied value is used.
NOTE 4:
In the addedSolution and example text provided below, the term explicit that is used when discussing the property values (GHV, MHV, and Density Gas) used for FOE Calculation refers to those property values whose Source field in the Properties Table when listed indicate a source other than Default, i.e., meaning that the value being displayed and used for calculations was supplied in one of several ways as follows:
Either the property value was supplied as an explicit Reading (either manually entered or imported), in which case its Source value would show as Reading.
Or the supplied property value represents instead a value that has been carried over and/or calculated by an Update from Readings or Linear Blend Simulation, in which case its Source value would show as Simulated.
Or the supplied property value represents instead the value that has been defined for the assigned Product Code being used to represent the specific material code (name, state, type, class) of the corresponding inventory, event, or flow reading volume or mass, in which case its Source value would show as Product.
Or the supplied property value represents instead a value that has been supplied as a separate Lab value that was entered or imported with a Lab Vessel or Lab Pipe instrument or entered via another inventory or flow meter instrument attached to the same vessel or pipe object, in which case its Source value would show as Instrument.
** SeeSolution 118864 for added notes and detail on all the the possible sources of property data including those already mentioned above.
Logic applied when Advisor Calculates FOE for gaseous and solid products:
1. If the product is in a gaseous state (e.g. fuel gases), then the following if True:
If NO explicit property values are specified for either the Gas Heating Value or for the Mass Heating Value such that both properties are still using the global default values, then in this case the system uses the Gas Heating Value; and thus the calculation will use the current global system default that has been assigned for GHV in the Global | Properties Table listing.
The Gas Heating Value is also used if an explicit reading, simulated, product, or other instrument value is specified such that the source of the GHV value in the Properties Table shows something other than Default. And this is True regardless of whether or not an explicit Mass Heating is also specified.
In the Final case where an explicit value has been provided or supplied for the Mass Heating Value but not for the Gas Heating Value, then in this case the system will use the Mass Heating Value instead of the global system default value for GHV.
** Thus, in short, for Gases then the Gas Heating Value is always used for FOE calculation (default value or not) except in the one case as noted above, where for GHV and MHV then the GHV property reading and source equals the currently defined global system Default value, and an explicit value has been supplied ONLY for the Mass Heating Value.
2. If the product is solid (e.g. petroleum coke), then the Mass Heating Value is ALWAYS used.
FOE Equations and Calculation Examples for the US 60F Model Basis:
** The examples provided below ALL represent US 60F Model Basis Examples where NLFEB = 5960000 BTU's/FOE Bbls and DensityAir in OLOCONFG = 76.35565466343201 Lbs/Mscf, and in all cases where gas flow calculations require a Density Gas value and no explicit value is supplied then the DensityAir value is used.
The fuel oil equivalent liquid volume (FOE) calculation for gaseous products as discussed above is then:
When an explicit GHV property value is supplied, or when BOTH GHV and MHV values and source are default.
-- for Gas Flow Readings supplied in Volume UOMs --
FOE = Gas Volume Flow * Gas Heating Value / NLFEB
-- for Gas Flow Readings supplied in Mass UOMs --
FOE = (Gas Mass Flow / Density Gas) * (Gas Heating Value / NLFEB)
When an explicit heating value is supplied ONLY for MHV and the GHV value and source are default.
-- for Gas Flow Readings supplied in Volume UOMs --
FOE = (Gas Volume Flow * Density Gas) * (Mass Heating Value / NLFEB)
-- for Gas Flow Readings supplied in Mass UOMs --
FOE = Mass Flow * Mass Heating Value / NLFEB
For solids, the fuel oil equivalent liquid volume (FOE) calculation is ALWAYS as follows:
FOE = Mass Flow * Mass Heating Value / NLFEB
such that the flow measurement for a solid is and should always be supplied as a Mass Flow Reading.
** ADDED NOTES:
For the FOE Calculation examples provided below, the Flow Volume and Flow Mass Instruments were used to enter the Readings and Properties used in the FOE Calculations, and each example documented below is accompanied by a corresponding Properties Table screen shot and Expert System Balance/Schematic screen shot to show the GHV and MHV representation in the Properties Table and the corresponding FOE Barrels calculated in each case by the Expert System.
Since the FOE Calculation for Solids is ALWAYS, FOE = Mass Flow * Mass Heating Value / NLFEB, no examples are included below for solids as any examples documented for solids would be the same as the Mass flow and Mass Heating Value Examples for Gases only that the Mass Flow used in the examples would then represent a measurement amount for a solid product instead of a measured flow amount for a gaseous product.
EXAMPLE 1:
Mass Flow for Gaseous Product = 2500 Lbs, and GHV and MHV are both using the Global System Defaults, and NO explicit Density value for Density Gas is supplied, thus the Density Gas used will be the DensityAir value (76.35565466343201 Lbs/Mscf) from OLOCONFG.
Advisor uses the Gas Heating Value (GHV) for FOE Calculation.
FOE = (Gas Mass Flow / Density Gas) * (Gas Heating Value / NLFEB)
FOE = (2500 Lbs / 76.35565466343201 Lbs/Mscf) * (1527113.093 BTU/Mscf / 5960000 BTU's/FOE Bbls)
FOE = 8.389 Bbls.
NOTE:
In this case where neither an explicit GHV or MHV is supplied, then note that if FOE is calculated using the MHV Equation and default MHV value of 20000 MBTU/MLbs the FOE Calculation will yield the SAME result for the calculated FOE Barrels.
FOE = Gas Mass Flow * MHV / NLFEB = 2500 Lbs * 20000 BTU/Lbs / 5960000 BTU's/FOE Bbls = 8.389 Bbls
** This shows that assuming a material's GHV and MHV values are both representative of values calculated for the same material at the same reference conditions (temperature, pressure, density, etc.), then irregardless of whether both or only one of the MHV or GHV values are supplied for a Gaseous Product the selected heating value and corresponding equation used for the FOE Calculation in either case should yield the same end result.
EXAMPLE 2:
SAME conditions as used in EXAMPLE 1, except that now an Explicit Density Gas value of 85.275 Lbs/Mscf is specified for the Mass Flow reading for the gaseous product flow.
Again, Advisor uses the Gas Heating Value (GHV) for FOE Calculation.
FOE = (Gas Mass Flow / Density Gas) * (Gas Heating Value / NLFEB)
FOE = (2500 Lbs / 85.275 Lbs/Mscf) * (1527113.093 BTU/Mscf / 5960000 BTU's/FOE Bbls)
FOE = 7.512 Bbls.
NOTE: For any FOE Calculation including the remaining examples provided further below, then any time an explicit Density Gas value is supplied to override the global system default (DensityAir) value, then as expected that explicitly supplied value will be used by the system in the FOE Calculation as needed for Volume to Mass and Mass to Volume conversions as shown in this example and the associated screen shots that follow.
EXAMPLE 3 (Scenarios A, B, C):
Mass Flow for Gaseous Product = 2500 Lbs for ALL three scenarios, and NO explicit Density value for Density Gas is supplied, thus the Density Gas used in ALL three scenarios will be the DensityAir value from OLOCONFG as noted earlier in EXAMPLE 1.
Scenario A: An Explicit Gas Heating Value of 1600000 BTU/Mscf is specified, MHV = Global System Default.
Advisor uses the Gas Heating Value (GHV) for FOE Calculation.
FOE = (Gas Mass Flow / Density Gas) * (Gas Heating Value / NLFEB)
FOE = (2500 Lbs / 76.35565466343201 Lbs/Mscf) * (1600000 BTU/Mscf / 5960000 BTU's/FOE Bbls)
FOE = 8.790 Bbls.
Scenario B: An Explicit Mass Heating Value of 25000 MBTU/MLbs is specified, GHV = Global System Default.
Advisor uses the Mass Heating Value (MHV) for FOE Calculation.
FOE = Gas Mass Flow * Mass Heating Value / NLFEB
FOE = 2500 Lbs * 25000 BTU/Lbs / 5960000 BTU's/FOE Bbls
FOE = 10.487 Bbls.
Scenario C: An Explicit value is specified for BOTH theGas Heating Value and Mass Heating Value equal to the respective values noted above for Scenarios A and B.
** For Scenario C, the FOE Calculation applied and the result obtained is the SAME as Scenario A.
EXAMPLES 4 and 5:
Volume Flow for Gaseous Product = 2500 Mscf, and GHV and MHV are both using the Global System Defaults, and NO explicit Density value for Density Gas is supplied, thus the Density Gas used will be the DensityAir value (76.35565466343201 Lbs/Mscf) from OLOCONFG.
Advisor uses the Gas Heating Value (GHV) for FOE Calculation.
FOE = Gas Volume Flow * Gas Heating Value / NLFEB
FOE = 2500 Mscf * 1527113.093 BTU/Mscf / 5960000 BTU's/FOE Bbls
FOE = 640.568 Bbls.
** Now if the same Gas Volume Flow and default Property Conditions are used but an Explicit value of 25000MBTU/MLbs is instead specified for the Mass Heating Value to override the global system default value, then in this case the FOE Calculation will be as follows:
Advisor uses the Mass Heating Value (MHV) for FOE Calculation.
FOE = (Gas Volume Flow * Density Gas) * (Mass Heating Value / NLFEB)
FOE = (2500 Mscf * 76.35565466343201 Lbs/Mscf) * (25000 BTU/Lbs / 5960000 BTU's/FOE Bbls)
FOE = 800.709 Bbls.
** Although not provided in thisSolution, similar examples would apply as well for Metric Models for both the 15C and 20C Basis where property values for GHV, MHV, Density, and the value for the NFLE factor are supplied or needed in Metric Units of Measure. And for Metric Models the same FOE calculation equations documented in sections and examples already documented above will be selected and applied based on the same application logic that was noted earlier as well in theSolution documentation already provided above.
Keywords: NLFE
Net Liquid Fuel Equivalent
FOE
Fuel Oil Equivalent
GHV
Gas Heating Value
MHV
Mass Heating Value
References: None |
Problem Statement: What is a reclassification, and when can a material reclass occur in my AORA model?
What procedural and data entry requirements are needed to properly account for a material reclass?
What does AORA do with this Reclass information, i.e., how does it affect the system calculations and Expert System results, and where on the standard reports would I see how AORA had reclassed my transactions in such cases?
How would procedures differ if instead the Tank Service is to remain unchanged for a Product Inventory change, such that the model transaction should be treated and configured as a Blend transaction instead of a Reclass? | Solution: Content as intended for customer viewing while the HTML form content issues currently being experienced with this and otherSolution are being Fixed.
Please also review the other related and associated AspenTech Knowledge BaseSolutions referenced to thisSolution as well which are listed again below:
Related Product Composition Tracking and SimulationSolutions:Solution ID 115508: How can I configure Aspen Advisor to track products compositions in tanks?Solution ID 118875: What do the linear blend and update from readings algorithms do?Solution ID 115583: How can I linear blend certain properties while updating other properties from readings?
RelatedSolutions about Property Data sources for AORA:Solution ID 118864: What are the possible sources of property data?
Applicable Version(s):
All
Keywords: Blend
Event
Inventory
Tank Service
Transaction Type
Reclass
References: None |
Problem Statement: How do I resolve the error I/O Error received Address already in use: JVM_Bind | Solution: The error Address already in use: JVM_Bind is a common exception in Java when an application is trying to connect on a particular port and some other processes either Java or non Java is already connected on that port.
The error may be resolved by exiting out of the application then ending all Java related processes in the Windows Task Manager. In rare cases the problem may need to be resolved by performing a reboot of the workstation.
Keywords: I/O, JVM
References: None |
Problem Statement: Version 2004 uses Aspen's AFW Security model, and also has new web-based features. What are the key factors along the upgrade path to make sure that (1) the new Security Model is implemented correctly, and (2) eBRS web pages can be viewed? | Solution: Section One: Migration Advice
Follow the entire Post-Install Configuration on page 3-25 of the AeBRS Installation Guide. If using Microsoft SQL Server, note that the new required JDBC driver is not included in the install -- use the provided web address to download it from Microsoft.
AeBRS v2004 has its security integerated with ALS and Windows domain security. This means that you need to add the appropriate user to the AeBRS Administrator role before you will be able to open MOC. See the Creating Aspen Framework Application and Roles section in the AeBRS Installation Guide. This section will allow you to load your existing AeBRS security structure into the AFW Security Manager and allow your user (corp/<your username>) access to MOC.
NOTE: To use MOC off the network, you may need to add your local administrator account to the AeBRS Administrator role in the AFW Security Manager. Then logon to your machine with this local administrator account to use MOC. If, when opening MOC you get a message about AeBRS needing a Full name, access your administrator account via the Computer Management snap-in and enter a value into the full name field of your local administrator account. At this point you should be able to open the MOC successfully.
Section Two: Accessing AeBRS from the Web
First, you will need to follow the Configuring an AeBRS Workstation section on page 11-13 of the AeBRS Installation Guide. This will add your machine to the AeBRS Config module so that AeBRS recognizes it as a valid web workstation. Since AeBRS needs to know where a given action takes place to generate a valid audit trail, this node information is mandatory before web features can be used.
To then access either the Order Management or Execution web pages directly, use the following addresses:
http://<your server name>/AeBRS/AeBRSOrderManagement.aspx - this webpage allows you to view/administer orders from the web.
http://<your server name>/AeBRS/AeBRSWorkstation.aspx
Note that only orders generated from a certified RPL can be executed using the second link above.
These AeBRS ASPx pages are accessed via AspenTech Single-Sign-On. This mechanism logs you into the AspenTech environment and from then on (as long as the browser is left open) you can navigate to any AspenTech webpage without additional authentication checks. You will automatically be redirected to the AspenTech Single-Sign-On page when you enter one of the above addresses. You should logon using the same domain/account with which you logged onto your machine - (<yourdomain>/<your username>).
Section Three: Troubleshooting
Make sure your VPN firewall is off prior to accessing AeBRS from the web.
If you're working with a demo version of eBRS in a laptop environment, you may have installed the Microsoft Loopback Adapter to start InfoPlus.21 in a Windows XP environment. In this case, make sure to disable (or reduce the network priority of) the loopback adapter before accessing AeBRS via the web while connected to a network.
Keywords:
References: None |
Problem Statement: When Upgrading my Aspen Operations Reconciliation and Accounting application software and INI Settings to
aspenONE V7.2 and Higher from previous versions including older/former Aspen Advisor versions, then what
execution procedures are required and/or recommended by AspenTech Support in order to successfully migrate
my existing Application INI (File or Registry) Settings to the new AspenTech.MSC.Settings.xml file for
V7.2 and Higher software versions? | Solution: IMPORTANT NOTES:
There are two OPTIONS available for migrating the INI (File or Registry) Settings to the XML file.
You can either use the AUTO Migration Procedures or the MANUAL Migration Procedures as outlined in the attached How To... PDF Instruction Manual noted below.
To avoid possible migration errors, all INI (File or Registry) Settings MUST be migrated at the same time.
NOTE: The reason for this firm recommendation is that moving only one set of application settings at a time and then ?testing? may cause another section of the settings XML file to be created inadvertently. And the system will not add to or overwrite settings in the XML if the associated INI Settings Section already exists in the file for the application whose file or registry key settings you are trying to import/migrate. Thus, once an INI settings section has been created in the XML for a particular AORA application, then its existence will subsequently prevent that section of the XML file from being updated if further migration of the INI settings for the application is still required.
INCLUDED FILE ATTACHMENTS:Solution Overview and Instruction Manual for INI Settings Migration Procedures:
Download and/or print and review thoroughly the two PDF file attachments that are listed below.
Review theSolution Overview content first, then follow explicitly the detailed Migration Procedures
provided in second How to PDF document.Solution Overview for INI Settings Migration Procedures.pdf
How to Migrate AORA Application INI Settings to V7.2 and Higher.pdf
Scripts to Migrate INI File Settings from Pre-V2006.5 software versions to V7.2 and Higher:
The two *.bat files listed below are included in the following ZIP attachment:
INI Registry Key Migration Scripts (V2006.5-V7.1).zip
Delete_Legacy_RegKeys.bat
MigrateINISettings_Pre-V2006.5.bat
Scripts to Migrate INI Registry Settings from V2006.5 and V7.1 software versions to V7.2 and Higher:
The two *.bat files and *.vbs file listed below are included in the following ZIP attachment:
INI File Migration Scripts (Pre-V2006.5).zip
SettingsCreate_RegKeyPrep.bat
SearchAndReplace.vbs
MigrateINISettings_V2006.5_Or_V7.1.bat
If you encounter any problems downloading any of the file attachments or need help executing the required AORA Application INI Settings migration procedures for your upgrade, then please call AspenTech Support to log a Help Request.
Keywords: AdvExcel.ini
aion.ini
AspenTech.MSC.Settings.xml
ATAutoProcess.ini
iimpt.ini
iirpt.ini
iisys.ini
INI Settings Migration
SettingsCreate.exe
Upgrade
References: None |
Problem Statement: When opening or launching any Aspen Operations Reconciliation and Accounting (AORA) applications following a clean install of Aspen software either on Windows 7 or Server 2008, one might get the following Critical Failure Errors that result in the applications immediately crashing and shutting down.
The first Error Message is an ObjectWindows Exception error that complains about an Invalid Menu Handle as shown in the first screen shot attached below.
clicking the OK button on the above error message, results in a second Abnormal Termination, uncaught XBASE error message that essentially includes the same text but states the there was a Critical failure and that the System is shutting down.
How do I resolve this error chain? | Solution: There are 2 options for resolving the errors (If company policy allows it, then Option 2 is RECOMMENDED):
1. If the DEP (Data Execution Prevention) is turned ON for ALL Programs, e.g., if the selected DEP option is set to the Turn on DEP for all programs and services except those I select radio button value selection, then Add the following AORA executables to the DEP Exceptions List:
Advisor.exe Executable for the MAIN Model GUI (Graphical User Interface)
IIAutoHist.exe Executable for the AORA Connect Data Import Application Interface
Report32.exe Executable for the Standard Reporter
SSInterface.exe Executable for the Older Spreadsheet Interface Import Tool
DbTools.exe Executable for the Database Administration Tool
** The execution procedures required for this option are as follows:
a.) Right-click on My Computer.
b.) Select the Properties option from the context menu.
c.) Select the Advanced Tab in the System Properties dialog or the Advanced System Settings Link.
d.) Click on the Settings button under the Performance section.
e.) Select the Data Execution Prevention Tab in the Performance Options dialog.
f.) Update the exceptions list with the AORA Executables previously listed above.
NOTE: All of the executables above are located in the default \Program Files\AspenTech\Advisor\ folder (or the Program Files (x86) equivalent on 64-Bit systems), and if for any reason the same error occurs when trying to login to the AORA model from Advisor Excel Add-In then the Advisor.xla file needs to be added to the DEP exceptions list.
2. Or simply Turn OFF DEP by changing the setting to the alternate setting labeled
Turn on DEP for essential Windows programs and services only, then Reboot and retest.
NOTE: The specific error messages displayed are not always the same depending on the Operating System, but below are a few added Knowledge Base articles that further discuss the DEP recommendations.Solution ID 125984: Can Data Execution Prevention (DEP) prevent Aspen Advisor from starting?Solution ID 125819: Advisor launching error - *** Unhandled Exception! ExpCode: 0xC0000005 ExpFlags: 0 ExpAddress: 0x003D7D30 Please report!
Keywords: Application Fails to Launch
Abnormal Termination, uncaught XBASE
Critical Failure
Data Execution Prevention
Invalid Menu Handle
ObjectWindows Exception
TADecoratedMDIFrame
References: None |
Problem Statement: Starting with aspenONE V7.2, all of the INI Configuration Settings for the Aspen Operations Reconciliation and Accounting application user and preference settings and process configurations, they are now stored in a single xml file named ?AspenTech.MSC.Settings.xml?.
Did AspenTech also include starting with V7.2 any program tools or utilities for customer's to use that provide an automated execution method or procedures for programmatically or systematically migrating a machine's or user's
Aspen Operations Reconciliation and Accounting application INI configuration settings? | Solution: Starting with aspenONE V7.2, a new INI Settings Migration Utility named ?SettingsCreate.exe? was provided to help customer?s migrate their INI (File or Registry) Settings to the new ?AspenTech.MSC.Settings.xml? file as needed.
CAUTION: Use of the ?SettingsCreate.exe? utility is NOT intended for general users, and before using this tool customer?s should first review and proceed with the scripted and ?Recommended? INI Settings Upgrade and Migration Procedures that are outlined in Chapter 6 of the Aspen Operations Reconciliation and Accounting Installation Guide.
Only your IT group or someone with System Admin experience should use this new migration utility.
And if any help is required to migrate your prior Aspen Advisor or Aspen Operations Reconciliation and Accounting application INI Settings outside the scope of the ?Recommended? procedures that are provided in the Installation Guide, then you should contact AspenTech Support to submit a Help Request.
The ?SettingsCreate.exe? migration utility is located in the following directory location after installing V7.2 and higher:
?C:\Program Files\Common Files\AspenTech Shared?
This new ?SettingsCreate.exe? utility can be executed manually (scripted), or it can also be run ?interactively? from DOS such that the tool actually steps you through the procedures required to migrate INI Settings a from a file or registry key into the new ?AspenTech.MSC.Settings.xml?.
NOTE: This V7.2 migration utility is not GUI based like the one used for V2006.5 and V7.1, and is instead strictly provided for use as a DOS based utility only.
SettingsCreate.exe Usage Summary:
Commands:
SettingsCreate [interactive]
[[Scope] [RegistryKey] [Recurse]]
[remStr [Scope] [RegistryKey]]
[addStr [Scope] [RegistryKey] [Value]]
[ini [Scope] [Base path] [Ini path]]
Parameters:
[Scope] - either LocalUser, Machine (as tested customer?s should use LocalUser)
[RegistryKey] - for ex. Software\AspenTech\Advisor
[Recurse] - true or false
[Base path] = base path for location of setting file to migrate
[Ini path] = path for the ini file, i.e., the actual NAME of the INI File or INI Registry Key.
[Value] = a string value to add to file
NOTE: Using a Command Prompt (cmd.exe) window, then if you CD (change directory) to the AspenTech\Shared directory and then type in SettingsCreate.exe /? you will see the same usage structure and help information on how the commands must be written/executed as per what is listed above.
*** ================================== ***
EXECUTION EXAMPLES FOR PHYSICAL INI FILE MIGRATION:
(Applicable for Migrating INI file settings to V7.2 from versions Prior to V2006.5)
SPECIAL PRE-REQUISITE NOTE:
The V7.2 Install will install some Legacy Registry Keys by default.
The first command listed below will Delete the HKCU Advisor INI Files Settings Keys.
The second set of commands listed below will Delete the HKLM IniFileMapping Keys.
Deleting these Legacy registry keys used only for V2006.5 and V7.1 software versions will then allow you to run the new V7.2 SettingsCreate.exe utility commands to properly complete the INI Settings migration to the new global xml file named, AspenTech.MSC.Settings.xml.
reg delete HKCU\SOFTWARE\AspenTech\Advisor /f
reg delete HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\IniFileMapping\AdvExcel.ini /f
reg delete HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\IniFileMapping\aion.ini /f
reg delete HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\IniFileMapping\ATAutoProcess.ini /f
reg delete HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\IniFileMapping\iimpt.ini /f
reg delete HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\IniFileMapping\iirpt.ini /f
reg delete HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\IniFileMapping\iisys.ini /f
IMPORTANT: When migrating the AORA Application INI Settings from the Physical INI Files to the new central xml file for V7.2 and higher versions, then if the above reg delete commands are NOT executed from a *.bat file or from a Command Prompt window BEFORE running SettingsCreate.exe, then the migration will FAIL.
Running SettingsCreate.exe Interactively
If you want to actually put the utility in Interactive mode to allow you to run it step by step with some displayed execution choices to select from, then simply type SettingsCreate.exe Interactive at the command prompt.
In the example screen shot provided below, the commands executed will migrate the Physical IISYS.INI File Settings to the AspenTech.MSC.Settings.xml file. And this example assumes of course that a copy of the IISYS.INI File was placed in the C:\Program Files\AspenTech\Advisor\ini directory before executing the file migration commands shown below.
Running SettingsCreate.exe Manually via Single Batch Line Command
The same File migration command set execution noted above for the IISYS.INI File can also be executed from a *.bat (batch) file or Command Prompt window using the equivalent Single line batch command:
C:\Program Files\Common Files\AspenTech Shared\SettingsCreate.exe ini LocalUser iisys.ini
C:\Program Files\AspenTech\Advisor\ini\iisys.ini
EXECUTION EXAMPLES FOR WINDOWS REGISTRY KEY INI SETTINGS MIGRATION:
(Applicable for Migrating INI settings to V7.2 from the Windows Registry for versions V2006.5 and V7.1)
Running SettingsCreate.exe Interactively
In the example screen shot provided below, the commands executed will migrate the IISYS.INI Registry Key Settings to the AspenTech.MSC.Settings.xml file.
Running SettingsCreate.exe Manually via Single Batch Line Command
The same Registry Key migration command set execution noted above for the IISYS.INI registry key and sub-key settings can also be executed from a *.bat (batch) file or Command Prompt window using the equivalent Single line batch command:
C:\Program Files\Common Files\AspenTech Shared\SettingsCreate.exe LocalUser
Software\AspenTech\Advisor\iisys.ini True
NOTE: To migrate all of the AORA Application INI Registry Key Settings at the same time using only one execution run of the SettingsCreate.exe instead having to complete one execution run for each application, then you would simply accept the utility's default values which translates to the following batch command:
C:\Program Files\Common Files\AspenTech Shared\SettingsCreate.exe LocalUser
Software\AspenTech\Advisor\ True
Keywords: AspenTech.MSC.Settings.xml
ATAutoProcess.ini
iisys.ini
iirpt.ini
INI Settings
Migration
SettingsCreate.exe
Upgrade
References: None |
Problem Statement: For custom Aspen Operations Reconciliation and Accounting Reports, how do we find the link between Sales and Receipts back to the event's OBJ_TYPE?
REASONS FOR ASKING:
We are writing a Custom report outside of the Aspen Operations and Accounting Reporter Application and we want to find the link between Sales and Receipts back to the OBJ_TYPE ? eg. we can see that in the OLOCODES table for Events that the DBINDEX for a Sale = 21100, but we are having trouble finding which table or field links this to the event. We know that the reporter creates temporary tables to store the Source, Destination and SORR value, and SORR we thought is supposed to represents Sale or Receipt. However, we have looked at the ERD diagrams for the database tables and this does not help us with the relationship.
For Example, the Temporary Table names from our Custom Report that store this information are as follows:
RPMSR493, RPMSR984. | Solution: Documented in PDF Attachment: Reporter TempTable (RDPSR and RDMSR) Source Data Linkages.pdf
** To review the DetailedSolution Summary, download and/or print the attached PDF File **
Keywords: Custom Reports
Temporary Tables
DLOEVENT
DSRPD.RPT
IND2SOURCE
IND2DESTIN
MSRPD.RPT
OBJ_TYPE
OLOCODES
PLOUNITS
RPDSR
RPMSR
SORR
References: None |
Problem Statement: This knowledge base article provides an example and a demo model which illustrate how to configure Excel sheets to import data into Aspen Advisor using the Aspen Advisor Excel Add-in.
Note: The superuser password in the attached demo model is superuser. | Solution: 1. Create a new text file import process within Aspen Advisor Connect. The Aspen Advisor Excel Add-in first writes data to this text file then calls Aspen Advisor Connect to import the data from the text file into Aspen Advisor.
Open Aspen Advisor Connect
Go to File | Set Imports
Click Add. For the interface type select Text File.
Give the text file import process a name. The name used in this example is Meters From Excel. For the process type select Standard Process.
Note: If you do not wish to manually create an import process in Aspen Advisor Connect you can use the *.ini files attached to this article. These *.ini files will create the necessary import process for you. To use these *.ini files:
a) Copy AtAutoProcess.ini to C:\Windows (be sure to backup your existing file first)
b) Copy AdvExcel.ini to C:\Program Files\AspenTech\Advisor
c) Restart Aspen Advisor Connect and Excel
2. After the import process has been successfully configured open a new Microsoft Excel worksheet.
3. In Excel select Advisor | General Interface.
4. Select the ODBC data source which corresponds to the attached demo model. Change the date in the General Interface dialog box to January 2, 2006. Click the Apply button to save your settings.
If prompted to Update From Database now, select Yes.
5. Click the Read Model Information button. This will launch a dialog box which will let you select the model information you wish to retrieve. In the Model Configuration Read section check Meters then click OK. Examine the data in the newly added worksheet.
6. Go to Advisor | General Interface. Check the Import Flow Data checkbox. Ensure the date is January 2, 2006 then click Initialize Text Import. If prompted to Initialize with Flow Tag Names select Yes.
7. This process will create a new sheet named ImportFlow, where readings for flow instruments can be entered. Enter the following data into the ImportFlow sheet. (All other columns in the sheet can be left blank.)
Tag
Time
Value
Flow UOM
Import
FI01
2006-01-02 00:00:00
173
scm
Yes
FI02
2006-01-02 00:00:00
0
m^3
Yes
FI03
2006-01-02 00:00:00
17000
m^3
Yes
FI04
2006-01-02 00:00:00
670000
m^3
Yes
FI14
2006-01-02 00:00:00
0
m^3
Yes
FI15
2006-01-02 00:00:00
731000
m^3
Yes
8. In Excel, go to Advisor | General Interface then click the Create Text Import File button. This creates the text file that Aspen Advisor Connect will use to import the data into the Aspen Advisor database tables. Click on the ImportFlowMsg sheet. You should see that 6 new flows were written to the import text file. Open the newly created import file to view its contents. If you used the *.ini files attached to this article the text file will be located here:
C:\Program Files\AspenTech\Advisor\Excel\MetersFromExcel.txt
9. Once you have viewed the contents of the text file data which will be imported to Aspen Advisor, go back to Excel then go to Advisor | General Interface. Ensure that the selected date is January 2, 2006. Click the Apply button to save the date. Select Run Advisor Connect. When the Run Advisor Connect dialog box appears, enter the Superuser name and password and ensure that the Meters From Excel process is selected in the Flow ListBox. Once this has been done click the Run Process button.
10. Open the Aspen Advisor model. Ensure that the meters now have flow readings for January 2, 2006 by examining the data in Data | Instrument Readings | Meters...
Keywords: addin
Add
in
XL
xla
References: None |
Problem Statement: Microsoft Visual Basic
Run-time error '-2147417851 (80010105)':
Method '%%%' of object 'ICOM_AutoHist' failed | Solution: The Excel Add-In accesses Advisor Connect as a DCOM object. In order to create this DCOM object you must:
1. Logon to this machine as an Administrator and Run Advisor Connect once (you do not need to open the model just open the application and close it).
2. This action will create the necessary entries in the registry to create the object.
3. Log off and test as a normal user again by running Advisor Connect from Excel.
Keywords:
References: None |
Problem Statement: This knowledge base article describes how to force a Aspen Advisor to re-upgrade the database table structure to the latest version when the upgrade from a previous version was not successful. This may allow new units of measure and new properties (which should have been added to the database when upgrading from Aspen Advisor version 7.0.1) to be added to the database tables. | Solution: In case the database table structure upgrade was not successful (for example, if the new property Compressibility or the new unit of measure Bars does not get added to the property list when upgrading from Aspen Advisor version 7.0.1 to a newer version) the upgrade can be executed again. Sometimes a second execution of the database table structure upgrade adds the new properties and units of measure in cases where the initial upgrade did not. The procedure to follow is:
1. Make a backup of your model. You will first attempt this procedure on this backup.
Note: This technique has not been thoroughly tested for all versions, so you will need to verify that it works without problems on a backup model before trying it on a production model. This method could potentially corrupt your database.
2. Open the OLOCONFG table. Change the TABLE VERSION field from the post upgraded value
to the value that it had before the upgrade was run. For example, if upgrading from Aspen Advisor 7.0.1, set the TABLE VERSION to 7.0100 (the trailing zeroes after the 1 are required)
3. Open the model with the new version of Aspen Advisor. The next time the model is opened with a newer version of Aspen Advisor the table upgrade will be attempted again since the older TABLE VERSION is detected.
An error will be flagged if the table structure upgrade attempts to add values to the database tables which already exist.
Keywords: UOM
create
missing
deleted
UOMs
unit
References: None |
Problem Statement: This | Solution: documents how to add a new user to an existing Aspen Operations Reconciliation and Accounting (AORA) model.Solution
1) Open Aspen Operations Accounting DB Tools
2) Go to File | Open Model and log in to the specified model as a 'superuser' or any account that has permissions to add the roles
3) Go to Tools | Manage Users...
4) This opens up a pane where a user can be added and modified to have a certain username, password, and access level to the database.
5) Once the preferences are set, press 'OK' and close Aspen Operations Accounting DB Tools.
6) Upon opening AORA again, the newly added user will be able to log in and edit the model with the permissions configured.
Keywords: AORA
Configure new user
References: None |
Problem Statement: This knowledge base article explains the extent to which Aspen Advisor is affected by the new Daylight Savings Time (DST) rules in March 2007. | Solution: Aspen Advisor is not directly affected by the new DST changes in March 2007. Aspen Advisor relies on the operating system time for the DST change. However, you must have the latest Microsoft patch for the new DST rules installed on your systems for Aspen Advisor and other Aspen applications to correctly recognize the new DST standard. Also, relevant Aspen Process Data patches must be installed on your system(s).
Keywords:
References: None |
Problem Statement: Can Aspen Operations Reconciliation and Accounting (AORA) Connect be configured to import Lab Data directly from a LIMS System? | Solution: No. In order to retrieve and import data into AORA model directly from a Real-Time Database Historian or any other data system, there must exist an interface (iis3*.dll) specifically coded to reference and access the required Database Fields or History Repeat Areas where the necessary data values you desire to import reside.
With that said, then for AORA Connect AspenTech does not currently offer an interface for LIMS.
Alternative Import Methods:
The methods that are available for retrieving and importing LIMS (Lab) Data to AORA are as follows:
1. Utilize a Data Historian -- First historize the Lab Readings from the LIMS System by transferring the data to corresponding Tags (Records) created in one of following three Data Historians -- Aspen InfoPlus.21, PI, or PHD. Once the necessary data has been transferred to one of those three Data Historians, then use AORA Connect to create a standard historian import process that can be configured to import the historized Lab Readings directly from the historian.
The created Historian Import Process can also be automated via a scheduled Batch Script execution.
AORA Connect provides Native (Legacy) Import Interfaces for both the Aspen InfoPlus.21 and PI Data Historians, and it also provides a standard ADSA (Process Data driven) Import Interface that can connect to and import data from all three of the aforementioned Data Historians including PHD.
And to facilitate a successful import of the reading values from the historian, then either the Tag Name or the specified Tag Alias of the Instrument attached to a Vessel or Pipe that is configured for each Lab Reading -- one of those names must match 1:1 with the Name of respective Lab Tag (Data Record) in the historian.
2. Dump the LIMS data into an Excel spreadsheet, then use the Standard AORA Excel Add-In (Advisor.xla) to facilitate the import to the AORA model database via Connect's Text File Import functionality as follows:
** Refer to the Excel Add-In User Guide (AdvExcel.pdf) for added instructions **
Create a Text File Import Process in AORA Connect that will later be used by the Add-In to facilitate the actual execution of the data import. The Process Name you assign to the configured import process must also be referenced in the User's Preference settings for the Add-In located on the ?RunConnect? userform.
Then using the Add-In setup the required data import template that is provided for importing Lab Data.
Next use the generated import template to organize and prepare the Lab Data for import.
Once the Lab Data is ready, then click the Create Text Import File command button located on the Add-In's General Interface form to create and populate the Text Import File with the data. During this step the data (Tag Names, Out of Range Values, etc.) will be validated to check for errors. If all validation tests pass, then the Text Import File will be created successfully. Else in cases where errors are confirmed they will be individually recorded on a separate worksheet and you will be required to review and correct those errors before continuing, in which case this step will then need to be repeated until the Text Import File can be created successfully.
Then click the Run Connect command button also located on the Add-In's General Interface form to launch the secondary command form that you will then use to login to the model database with AORA Connect and confirm and execute the selected import process that is required to complete the data import. In summary, when AORA Connect is launched using the Excel Add-In, it automatically opens and processes the created Text Import File based on the selected command form reference pointer that links the import execution to the corresponding Text File Import Process that you previously configured in AORA Connect using its application user interface.
3. Or customers can instead create their own custom interface or query to facilitate the import of the Lab Data to AORA by using one of the following interface execution methods:
Either dump the LIMS data into a Text Import File such that the flat file content and structure follows the documented Standard Text Import File Formatting Requirements ? In the aspenONE V8.0 and Higher Releases refer to the AORA Connect Help Files to review these documented requirements, or for prior aspenONE releases refer toSolution ID 106864 to download the requirements PDF document. Then create a standard AORA Connect Text File Import Process to process and import the data from text file.
NOTE: Although the Excel Add-In is already doing the same thing after the data is manually entered in Excel, this option would still provide the added automation required to speed up the process and eliminate the required daily user interaction.
Or create their own custom interface to query and select the data from LIMS and insert it directly into the corresponding AORA model database Import Tables where the Importer Utility in the Advisor.exe GUI (accessible from the Tools Menu) can then be used to complete the import to validate the data records and move the Lab Data from the Import Tables into the Data Tables.
NOTE: And for this case a Batch Script could be created that would allow the User to run the final Importer execution via a Single Menu Click completed from the AORA Tools Menu.
Keywords: Advisor.xla
Excel Add-In
Lab Data
LIMS
Historian Import Process
Text File Import Process
References: None |
Problem Statement: Where can I find more information on the database tables and structure that is included in the Aspen Operations Reconciliation and Accounting (AORA) Model Database formerly known as Aspen Advisor? | Solution: NOTES:
In Older AspenOne Advisor Versions prior to V2006.5, the Database Help File will be named IIDB.HLP.
As of V2006.5 the Database Help File Name was changed to aspeniidb.chm
Currently this Database Help File CANNOT be accessed from the Help File Menu option that provided in the Aspen Advisor Application GUI, and MUST instead be accessed manually or via the Aspen Advisor Application Menu Links / Shortcuts located in the Start | All Programs Menus as shown in the second screen shot below.
If the default install location is used then the AORA Database Help File that documents the listing, purpose, structures, linkages, etc. of the database tables will be located in the following directory:
C:\Program Files\AspenTech\Advisor\
Keywords: Advisor
Database
CHM Files
Help Files
References: None |
Problem Statement: How does the diagram preference option Show Tank Inventory in Diagram --> Preferences... --> Objects works with Aspen Operations Reconciliation and Accounting? | Solution: Aspen Operations Reconciliation and Accounting has an option to Display the Tank Inventory in the form of a rectangular BAR that is drawn over top of the Tank's graphic image in the GUI.
This feature can be enabled by first accessing the Diagram --> Preferences... --> Objects dialog form using the application's menu bar selections, and then selecting the Show Tank Inventory check box that is located in the Other Settings section of the Objects configuration tab.
IMPORTANT: Please note that in order for this feature to work correctly for each tank such that the rectangular BAR is drawn and displayed for the tank's inventory, then it is also necessary to configure the Maximum Inventory property for each of the Tanks via the configuration entries that are located in the Volume Ranges section of the Details tab of each Tank's Configuration.
When this option is enabled, Aspen Operations Reconciliation and Accounting Displays the tank inventory in the GUI diagram's flow sheet as follows:
Screens for Required Configuration Steps:
Keywords: Inventory
Bar
Display
Preference
References: None |
Problem Statement: When utilizing Pressure Readings, does Aspen Operations Reconciliation and Accounting (formerly Aspen Advisor) expect / assume Gauge or Absolute Pressure for calculations requiring a Pressure, such as in the case of LPG Calculations to include the Mass of the Vapor (Phase) Space included in the Total Mass for Pressurized LPG Tanks? | Solution: Unless entered or imported in true Absolute Units like PSIA or otherwise specified, then the Aspen Operations Reconciliation and Accounting (AORA) calculations especially the LPG Calculations to include the Mass of the Vapor (Phase) Space as noted above expects / assumes that all pressure readings entered in Units of Measure (UOMs) other than PSIA are then Gauge Pressure readings.
Thus, anytime a Pressure Reading is entered or imported using a Unit of Measure other than PSIA, then as currently designed a Gauge Pressure is assumed by the system and internally the AORA application will then convert the Gauge Pressure Reading(s) to Absolute Pressure as needed for further calculations.
In the specific case of the internal LPG Calculation used to get the Mass of the Vapor (Phase) Space in the Tank, it is actually a requirement that the Pressure Reading be entered as a Gauge Pressure in an appropriate Unit of Measure other than PSIA such as PSIG, bars, kg/cm^2, or kpa (kilopascals).
NOTE1: The LPG Product Type and corresponding Calculation Algorithms for VCF and Vapor Phase Mass were not added to Aspen Advisor until AspenOne 2004.0.
NOTE2: Starting in V2006.5 and some patched versions of 2004.2.1 and 2006.0, Pressure was also added to the VCF Calculation as per the API 2004 Standards.
Keywords: Absolute
Gauge
LPG
Mass of Vapor
Pressure
References: None |
Problem Statement: Aspen Advisor Floating Roof Tanks have the option to specify Critical Area section on a tank basis. This knowledge base article explains how the critical area works with Aspen Advisor floating roof tanks. | Solution: The critical area for a floating roof tank is a zone where the tank roof is neither fully floating or fully under rest. It is also referred to as a semi floating zone, critical zone, inaccurate zone or inaccurate region for the tank. In principle the tank should never operated at critical area because the inventory calculations are inaccurate if we operate in the critical area. Aspen Advisor has an option to specify 'critical area start' and 'critical area end' for a floating roof tank because the tank inventory calculations vary depending on whether or not the gauge reading is in the critical area for the tank.
Typically a floating roof tank has three sections of operation.
1. Operation above critical area section
2. Operation inside the critical area section, which is never advisable
3. Operation below the critical area section
Aspen Advisor performs three different calculations depending upon the area in which it is operating.
Please note if you define 'critical area' for a floating roof tank, then
Gross volume ( uncorrected volume) = Strap table look up + floating roof adjustments.
1. If the tank is operating above the critical area section, then it is true that the roof is fully floating and the full mass of the roof is acting on the liquid surface. So Aspen Advisor consider the full roof weight for floating roof adjustment calculation, and accordingly gross volume ( uncorrected volume) is calculated.
2. If the tank is operating in the critical area section, which is never advisable but happen occasionally, then only a portion of the roof is acting on the liquid surface because a portion of the roof is supported by roof legs which are resting on the tank bottom plate. So, Aspen Advisor considers only the proportionate amount of roof weight for floating roof adjustment calculation ( Not the full amount of the roof weight) and accordingly the gross volume( uncorrected volume) is calculated.
3. If the tank is operating below the critical area section the roof is fully under rest and it is not floating. So Aspen Advisor does not consider the roof weight for the floating roof adjustment. Consequently, gross volume is calculated ignoring roof weight just like a fixed roof tank because the roof weight is not at all acting on the liquid surface.
From the descriptions above, the importance of defining the correct values for the critical area start and end while configuring floating roof tanks in Aspen Advisor should be understood.
Keywords: Tank
float
roof
fra
critical
References: None |
Problem Statement: A Database Trigger Example is needed for Advisor to Prevent the Import of Negative Flows into Advisor from PI. | Solution: NOTE: The best reSolution answer and/or fix long term for preventing the import of undesired negative flow data into Advisor would be to fix the data problem within PI, so that you don't send negative values (Bad Data) to Advisor and thus eliminate altogether the problem at its root.
Advisor Connect does include a Validate option in the Import Process Settings section of the Process Files dialog (File | Set Imports...) that when checked is supposed to validate and prevent the import of data that is out of range as defined in Advisor for such items as Property Data, but Support is not aware of that setting ever being applicable to Flow or Inventory Reading data in any Aspen Advisor software version and the Validate option even for Property Data has not worked for several versions dating back to v2004.x defect (CQ00319347), thus as already mentioned the best thing to do to prevent negative flow or inventory readings is to make sure that the Historian Data Source that is providing the data does NOT Allow or does NOT Send Negative Readings or to Add a Trigger to the Database as documented below.
ORACLE DATABASE TRIGGER EXAMPLE:
Oracle syntax is fairly easy when creating a trigger to execute BEFORE UPDATE OR INSERT:
CREATE OR REPLACE TRIGGER ADVISOR3.NO_NEGATIVE_ILRFLOWV
BEFORE
INSERT
OR
UPDATE ON ADVISOR3.ILRFLOWV FOR EACH ROW BEGIN
IF :new.FLOW_RATE <= 0 Then
:new.FLOW_RATE := 0;
END IF;
END;
RELATED SQL SERVER DATABASE TRIGGER EXAMPLES:
In SQLServer the syntax is a bit more complex because there is no concept of BEFORE or AFTER. You are instead dealing with a Pseudo Table called Inserted.
Provided below are some related examples of various triggers written for AtOMS that may give you an idea of how to write your Advisor Database Trigger in SQLServer if needed:
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
ALTER TRIGGER [dbo].[CLEAR_90PCT_ALARM] ON [dbo].[ATOMS_MOVEMENT] FOR UPDATE
AS declare @STATE_ID int declare @DBINDEX int
BEGIN
/* ***********************************************************************************************
* This procedure will clear the 90% AtOMS Alarm when a movement is completed
* ***********************************************************************************************/
select @DBINDEX = (Select Dbindex from inserted WITH (NOLOCK))
select @STATE_ID = (Select State_id from inserted WITH(NOLOCK))
IF @STATE_ID = 10003
Update AtOMS_Alarm
Set CLEARED = 1,
TIME_CLEARED = getdate()
Where IND2OBJECT = @DBINDEX And
ALARM_TYPE_ID IN (10001,10004) And
CLEARED <> 1
END;
Keywords: Advisor Database Trigger
Advisor Import
Negative Flows
PI
SQLServer
Oracle
References: None |
Problem Statement: This knowledge base article explains why the batch script command, Import, may fail with the message
Additional Parameters Needed
when importing lab pipe data or lab vessel data. | Solution: At first you may notice that the batch script which imports lab pipe or lab vessel data does not run to completion. If this occurs, place the
OpenConsole;
command as the first line in the batch script. This will generate a debug message in the console window for each line in the batch script. If the message Additional Parameters Needed is subsequently returned then the cause is a missing argument when the Import batch script object is invoked.
The full syntax of the Import batch script object is as follows:
Import ModelName, ImportOption[, parameter2][,TraceMask];
When importing data for lab pipes or lab vessels the [parameter2] argument is not optional. If the [parameter2] argument is not specified the Additional Parameters Needed message will be generated. Here is an example of how the batch script import object should be used to import data for lab instruments.
Using LV to import lab vessel data and PP to import with properties, the correct syntax will be:
Import ModelName, LV, PP; (the [TraceMask] argument is optional)
Where the value for [parameter2] can be one of the following:
PP Import with properties.
CC Import with components.
PC Import with properties and components.
MM Import with product components.
PM Import with properties and product components.
CM Import with components and product components.
PCM Import with properties and components and product components.
Keywords: scripting
fail
tables
prop
References: None |
Problem Statement: This Knowledge Base article describes how to determine whether or not a daily balance has been run for a given accounting day. | Solution: There are multiple ways to determine whether or not the expert system balance has been executed.
From Advisor:
Load the Expert System then the look in the Expert | Preferences dialog box. The reconciliation status will show 'Not Saved' if no expert results have been saved. The value displayed in this dialog box is the value stored in the REC_STATUS column of the DLORECON table. After saving the expert system results for the first time on a given accounting day this status will be set to 'Preliminary'.
From the Reporter:
Run the Ovalues.rpt.
Look at the II_ReconTimeDaily or II_ReconTimeDailyStr parameters. These parameters show the time that the reconciliation was last saved or will show No Reconciliation in the event that the expert results haven't been saved.
Keywords: Balance
Period
References: None |
Problem Statement: How to make a backup of an Advisor model | Solution: There are three steps you need to perform in order to backup the Advisor model successfully.
I. via Data Sources (ODBC) - Create an ODBC to an Access database (destination database for backup)
1. Open Data Sources ODBC from Control Panel
2. Click on either USER DSN (only one user can see this data source ) or System DNS (all users can see this data source) and click on Add.
3. Double-click on Microsoft Access Driver (*.mdb)
4. from the ODBC Microsoft Access Setup dialog box, enter the following information: Data Source Name field ==> enter any name you want (ie. Testing)
Description field ==> enter any thing you want to describe this model (ie. Testing for Chevron in Louisiana)
Database: click Create
in the New Database dialog box => 1) in the Database Name area, type in Testing.mdb and 2) in the Directories area, drill down to where you want this model to reside. Then click OK to the New Database dialog box. The ODBC Microsoft Access Setup message box will come up with the following message: Database C:\Aspentech\Support\Advisor\Testing.mdb was successfully created. Click OK to this message box.
Click OK to the ODBC Microsoft Access Setup dialog box
Click OK to the ODBC Data Source Administrator dialog box
II. via DBTOOLS
1. Open DBTools
2. Open the model you want to be backed up
3. From the menu bar within DBTools, go to Tools => Backup/Export Model
4. In the Backup/Export Model dialog box:
a. in the Model field, select the empty model you just created earlier in the Data Sources (ODBC) steps above (ie. Testing)
b. select either Complete backup or Time-period backup. If you want to backup the entire model, then select Complete backup. If you want to backup only a few days of data, then select Time-period backup
c. If you select Time-period backup option, then put in the date and time you want to back up.
d. once all done, click OK
III. Test the backup model
1. Go to Aspen Advisor ==> File ==> Open Model ==> select Testing from the model drop down list ==> put in ID, PW and click OK.
2. Check to see if the backed up model (i.e. Testing) is loaded successfully with the date you specified when doing export.
Keywords: back up
DBTools
ODBC
References: None |
Problem Statement: Sometimes when attempting to execute a configured Aspen Operations Reconciliation and Accounting (AORA)
Connect Import Process using Batch Commands, more specifically the OpenModel command, the following
Batch Logon fail and Failed to Connect error problem occurs as shown in the screen attached below.
However, as observed this apparent account or connection issue only occurs when using a particular AORA login account (User Name and Password) in the Batch Command used to open the AORA model database and execute the defined import process.
With that said, then what causes the AORA Connect Batch Command errors Error - Batch Logon fail and
Error - Failed to Connect to 'Model Name' when executing Historian or Text File import processes from
Connect or via automation from external Add-Ins and interfaces? | Solution: The typical root causes for this reported Batch Command induced execution error are as follows:
Either one or both of the User Name and/or Password was typed incorrectly or mis-spelled in the batch command.
The AORA login account (User Name and Password) specified in the batch command has been deleted and no longer exists in the model database.
The User Name and/or Password text includes illegal characters such as double quotes that cannot be processed successfully when executing batch commands to automate import process executions.
NOTE: The recommendation NOT to use double quotes when defining User Names and Passwords for the AORA login accounts is also noted in the Known Issue documented in KB Article 133296 that has been tested and confirmed regarding the Excel Add-In Run Connect execution.
Thus, to resolve this problem then proceed as follows:
1. First verify that the login account exists in the database as per the specified User Name currently being used in the written batch command. You can verify the login account User Name by looking for it in the User Names listing located on the Manage Users form in DBTools. You will need the Superuser Password to login to DBTools or the Password for an account with equivalent Administrator AORA Security Model User Role permissions. Alternatively, using one of the following two queries provided below you can also verify the User Name by searching for it in the OLOUSERS Table of your model database.
Example Query 1: Select * from OLOUSERS;
Example Query 2: Select * from OLOUSERS where TAG = '<User Name>'
2. Once you have verified that the User Name for the problem login account still exists in your model database, then check and verify in your Batch Job/File script or code that the spelling of both the User Name and Password in the batch commands as needed. Complete any necessary typo and spelling corrections and retest.
3. If Steps 1 and 2 do not help, then check the User Name and Password text to insure that no illegal characters are included. In addition to NOT using double quotes, other characters discouraged for use in the User Names and Passwords configured for AORA login accounts although they may still work include the following:
Single Quote: '
Comma: ,
Arithmetic: +, -, /, *, < >, =
Other: !, @, #, $, %, ^, &, (), ?
Keywords: Batch Logon fail
Failed to Connect to
OLOUSERS
OpenModel
Password
User Name
References: None |
Problem Statement: I am thinking about Upgrading my Aspen Operations Reconciliation and Accounting (AORA) system or have already Upgraded and need more information about where the application configuration and user preference settings are stored in the newer software versions.
As such I am looking for a History of the Application INI (File and/or Registry) Settings location changes that have been implemented for all aspenONE product versions of Aspen Operations Reconciliation and Accounting, formerly known as Aspen Advisor. | Solution: AORA Application User Configuration INI Settings Location
Keywords: AspenTech.MSC.Settings.xml
INI Settings
SettingsUtility.exe
SettingsCreate.exe
AdvExcel.ini
aion.ini
ATAutoProcess.ini
iimpt.ini
iirpt.ini
iisys.ini
User and Preference Settings
References: Table
AORA Component
Prior to V2006.5
V2006.5 - V7.1
V7.2 and higher
Main Application
(Database GUI)
iisys.ini
HKCU\Software\Aspentech\Advisor\iisys.ini
AspenTech.MSC.Settings.xml
Expert System
aion.ini
HKCU\Software\Aspentech\Advisor\aion.ini
AspenTech.MSC.Settings.xml
Connect
(Auto Historian)
ATAutoProcess.ini
HKCU\Software\Aspentech\Advisor\ATAutoProcess.ini
AspenTech.MSC.Settings.xml
AspenIPFields.ini
Physical AspenIPFields.ini file (for IP.21 and IP-X Interface Import) is still used in the Windows directory, No Registry Key or XML is currently used / created for any version.
Reporter
iirpt.ini
HKCU\Software\Aspentech\Advisor\iirpt.ini
AspenTech.MSC.Settings.xml
SpreadSheet Interface (SSI)
iimpt.ini
iimpt.ini still used by default, but iimpt.ini registry key can be added with help from support if desired.
AspenTech.MSC.Settings.xml
Excel Add-in
AdvExcel.ini
HKCU\Software\Aspentech\Advisor\AdvExel.ini
AspenTech.MSC.Settings.xml
Recon Publisher
AdvReconPublisher.ini
Physical AdvReconPublisher.ini still used.
AspenTech.MSC.Settings.xml
Versions Prior to V2006.5:
=====================
For all older aspenONE software versions of Aspen Advisor released prior to V2006.5, the application INI Settings were still stored in the physical ini files as noted in the Reference Table provided above.
The ?Working? copy of AdvExcel.ini should always be located in the following directory, assuming you installed Aspen Advisor using the default location.
?C:\Program Files\AspenTech\Advisor?
For all aspenONE versions prior to V2006.0, ALL OTHER ?Working? INI Files should be located in the
Windows directory (Either in C:\Windows or C:\Winnt depending upon your OS).
For aspenONE V2006.0 the ?Working? iisys.ini file may be located in the root install directory instead of the Windows directory as follows:
?C:\Program Files\AspenTech\Advisor?
Versions V2006.5 and V7.1:
======================
Starting with aspenONE V2006.5, all of the AORA application INI File Settings (excluding the three exceptions noted in the Reference Table -- iimpt.ini, AspenIPFields.ini, and AdvReconPublisher.ini), they were moved and relocated to the Windows Registry in order to allow for and provide support for Windows VISTA Systems.
The top level read/write store location created in the registry for the settings is as follows:
HKEY_CURRENT_USER\Software\Aspentech\Advisor
Sub-Keys using the same name as the previous physical INI Files are also created to continue to separately store the INI Settings for each individual AORA application. The corresponding INI File registry paths (sub-keys) are noted in the Reference Table provided above.
For V2006.5 and V7.1 a utility named SettingsUtility.exe was provided to automate the execution procedures required to successfully migrate a Machine's / User's INI File Settings to the proper Registry Keys.
IMPORTANT: For more detail on the Usage of the SettingsUtility.exe utility please see the |
Problem Statement: It is not immediately apparent from reviewing the Database Programmer's API manual how to retrieve values from EBRS via the AeBRS Web Service and use them. | Solution: The first step is to open a session and get a Session ID returned via OpenUserConnection. Next call the SQLSelect method to retrieve your data.
What is not as obvious is that it is necessary to use ValueOf or ValueOfArray to then use the data that has been returned (see pages 3-9 and 3-10 of the Version 6.0 Database Programmer's API manual.)
Here is example code that retrieves information from multiple fields:
string retValue;
string query;
string values;
string paramValues;
object[] testObj = new Object[10];
query = SELECT ID_USER, CODE, TAG FROM EBR_USER;
values = arrayId, arrayCode, arrayTag;
paramValues = ;
retValue = AeBRSService.SQLSelect(query,values,paramValues);
testObj = AeBRSService.ValueOfArray(arrayId);
TextBox1.Text = testObj[0].ToString();
TextBox2.Text = testObj[1].ToString();
testObjCode = AeBRSService.ValueOfArray(arrayCode);
...
testObjTag = AeBRSService.ValueOfArray(arrayTag);
Keywords:
References: None |
Problem Statement: Margins assigned in the path.m2r_config file are not being recognized in pdf files. How can the margins for Acrobat documents be adjusted? | Solution: The margins that currently exist in the path.m2r_config file only effect Word documents. In order to manipulate the margins of your Acrobat, PDF documents, please add an additional line to the path.m2r_config file to specify the EBR_PDF_PERMISSIONS.
Example syntax would be:
EBR_PDF_PERMISSIONS = no-modify no-annotate --top 6cm --bottom 6cm --left 5cm --right 5cm
Keywords: margins
adobe reader
reports
layout
formatting
References: None |
Problem Statement: When using SQLInsert to insert data into a user table in EBRS, a 1 is returned for success, a 0 for failure. A customer may find success using multiple SQLInsert statements, but failure when those same statements include Date values. | Solution: It is not possible to insert Date values directly. It is first necessary to use the SetValueOf function. For example:
SetValueOf(myDate, 2004-05-25 00:00:00, date) // This is fixed format... and assumed to be UTC
The myDate value can then be inserted into the correct table column with SQLInsert
(The ellipses are to indicate that other values will likely be part of the statement also, and are not correct syntax.)
Note that for a SQLUpdate statement, SetValueOf still applies, but additionally, the date variable needs to be enclosed in dollar signs, like this:
SQLUpdate(UPDATE MYUSERTABLE SET . . , MYDATEFIELD=$myDate$, . . . )
Keywords: java.sql.SQLException:
ORA-00904:
invalid column name
References: None |
Problem Statement: The Database Wizard fails and you get an Aspen eBRS server unavailable or not updated message. | Solution: There are several possible causes for this problem.
The most likely cause may be an incorrect installation order. It is important for Version 6 to follow this installation order: (1) install 6.0, (2) run the Database Wizard, (3) install Service Pack 1, and then (4) run the Database Wizard again. At this point, any additional cumulative ER for 6.0.1 can be applied.
If you applied the Service Pack, and any additional ER's first, and are then getting this error when trying to run the Database Wizard for the first time, run the following line in either your SQL Server or Oracle query tool:
UPDATE EBR_CONFIGURATION SET VALUE='6.0.1' WHERE ITEM='DB_VERSION'
The Wizard should then execute successfully. If it does not, please check the rest of the advice in this article first, and then contact Customer Support.
If you are trying to connect to Oracle, then verify that port 8888 is available.
Verify that DriverJDBC.jar exists:
<installdrive>:\Program Files\Apache Tomcat4.0\lib
If this file does not exist, then the 6.0 Installation manual instructions have not been followed correctly (downloading ODBC14.JAR from the Oracle website, and installing it.) Once installed, there will be a DriverJDBC.jar file in the \lib directory. If SQL Server is picked during the initial installation routine, then the correct DriverJDBC.jar file is loaded during install. This issue exists because Aspentech did not have the right during the 6.0 release timeframe to distribute the necessary Oracle JAR.
Keywords:
References: None |
Problem Statement: When first opening the Administrator tool, there is no default connection configured. Also, the Help files do not include a direct explanation of adding a server. | Solution: To add a specific AeBRS server to the Administrator module, follow these steps:
After opening the Administrator module, right-click on AeBRS Administrator, and choose Insert Node.
The WebServiceName by default should be AeBRSAPIService, unless you specified something different; the port number is 8080 by default (again, unless you specified a different port), the Web Service Node Name is the name of the box where your AeBRS server resides on the network.
After you click OK, a node is inserted under AeBRS Administrator. Right-click that node and choose Connect
Keywords:
References: None |
Problem Statement: After initial install, attempting to start MOC client causes an error box to be displayed:
Java Virtual Machine Launcher
Could not find the main class. Program will exit! | Solution: This problem occurs because the client fails to find and load the aebrs.jar file. Much like the ADSA gives InfoPlus.21 connection information back to a client, in the case of a MOC client, the AEBRS_SETTINGS.INI file on the server gives connection (i.e. addressing) information back to the client, also, specifying where required resources are located:
Therefore when first installing a client, make sure that the account under which the installation is being done can read the contents of the share
\\MyAPEMServer\ebrsbase
That share is made by the server install automatically for the AeBRS folder, found at the default install location:
C:\Program Files\AspenTech\AeBRS
At a specific point the client install will ask for the location of that file. Browse to the UNC path for the ebrsbase share and select AEBRS_SETTINGS.INI. This will then give the client install all the above addressing to connect to the JDK, to Tomcat (where the critical aebrs.jar file resides) and the main aebrs directory for compiled config files.)
A typical reason the No Class Found error could happen would be that a new MOC user logs in, but their Active Directory account does not have the right to access the Share on the server to pick up the AEBRS_SETTINGS.INI file on startup. If the error happens to everyone, perhaps the Share itself has been modified or removed.
Keywords: None
References: None |
Problem Statement: On a system where Aspen eBRS/Batch.21 functionality has been enabled, the API Server debug file typically has a statement like this written to it at 10 second intervals:
12:01:44: batch21.DMQueueB21.EBR_BATCH21_QUEUE.reloadAll:SELECT OBJECT_ID,EVENT_ID, ORDER_ID,RECORD_ID,BLOCK_ID,ERROR_PROC,SIGNATURE FROM EBR_BATCH21_QUEUE | Solution: This is normal operation, and the method employed by Aspen eBRS to make sure events written to the EB_BATCH21_QUEUE are written to Batch.21 on a timely basis (i.e. every 10 seconds queue contents will be read by eBRS, and then written to Batch.)
The debug key that controls whether this message gets written or not is the data model debug key (DATAMODEL_DEBUG), not specifically the Batch.21 debug key (BATCH21_MSG).
We recommend leaving DATAMODEL_DEBUG active, since this key drives much of the content of the debug file in terms of listing SELECT statements from many eBRS components. If a problem were to occur on a system, having the DATAMODEL_DEBUG key active is good practice, so that the API Server debug file has useful information.
Keywords:
References: None |
Problem Statement: While executing the Database Wizard, it fails with the message:
dbWizard_err_directoryNotFound
either appearing on the screen or written to the Database Wizard logfile, which is located at:
C:\Program Files\Common Files\AspenTech Shared\RepositorySetup\RepositorySetup.log | Solution: This error can occur if modifications have been to AeBRS configuration files, but the codify_all.cmd file has not been executed. codify_all.cmd reads all current configuration text files and update the Apache Web Server. It is necessary to run it after every configuration change to the AeBRS application.
You may also find, in the Apache stderr.log file an entry reporting that:
...\webapps\AEBRSserver\conf\config.cfg
cannot be found.
Run codify_all.cmd and try running the Wizard again.
Keywords: directory not found
fail
freeze
dbwizard
References: None |
Problem Statement: Calling the SetProxyUser method can cause an Internal Java Error | Solution: The Internal Java Error is a product defect resolved in Versions 7.0 and later. However for Version 6.0.1 and earlier the error only occurs when the programmer does not include the required SetProxyOrderPhase function in their code. In 6.0.1 and earlier this call to the SetProxyOrderPhase function must come before a SetProxyUser function is invoked. In 7.0 and later it is just necessary that SetProxyOrderPhase be called somewhere in the relevant code portion (not necessarily before.) In 7.0 and later, if SetProxyOrderPhase is omitted, an error message should result, instead of an Internal Java Error.
Additional Information About Using Proxy Functions
There are three Proxy functions. When writing information to the Batch Record (i.e. writing a Block of data), these functions are used (one is required, two are optional):
SetProxyOrderPhase. (Required.) This function gives order and phase context where the Batch record block should be recorded to. SetProxyUser. (Optional.) Use this if the Batch record block should be assigned to a user different than the user account under which the program runs. SetProxyTimestamp. (Optional.) Use this to specify a time other than when the Batch record block is actually added to the AeBRS Batch record.
The logical flow could typically follow this example:
SetProxyOrderPhase // Specify the order and phase for the phase
SetProxyUser // optional - specify a different user for the Block operation
SetProxyTimestamp // optional - specify a time other than current system time
InitBlock() // Start batch record block
BatchWrite // Write specific information to the Batch Record, using the context provided in the above functions (Order/Phase, User and Timestamp.)
// BatchWrite may be executed as many times as necessary in the given context.
DoneBlock // Commit the BatchWrite block addition to the Batch Record
IMPORTANT NOTE: Even though the Proxy User and Proxy Timestamp can be specified, this is only for batch recording purposes. The Audit trail that is generated will still keep a record of the actual User making the call, and the actual time when the program executed.
Keywords: setproxyuser
Set proxy userr
References: None |
Problem Statement: When the Refresh_screen() function is set to Yes, an overflow compile error results, giving a MOC debug output like the following:
09:37:44: Exception
java.util.EmptyStackException
at java.util.Stack.peek(Stack.java:79)
at java.util.Stack.pop(Stack.java:61)
at runtime.vm.chkVMRuntime.popValue(chkVMRuntime.java:346) at runtime.vm.chkVMRuntime.executeStmts(chkVMRuntime.java:621) at runtime.vm.chkVMRuntime.executeStmts(chkVMRuntime.java:531) at runtime.vm.chkVMRuntime.executeStmts(chkVMRuntime.java:517) at library.component.chkComponentUtil.execEvent(chkComponentUtil.java:593) at library.component.chkDisplayLabel.refreshValues(chkDisplayLabel.java:255) at library.component.chkRefreshableDisplayLabel.access$001 (chkRefreshableDisplayLabel.java:24) at library.component.chkRefreshableDisplayLabel$1.run (chkRefreshableDisplayLabel.java:111)
09:37:44: Thread-35(TREATMENTS):ERROR:Overflow error. Terminate your work saving all data and start again. If the error persists contact the AspenTech support desk. | Solution: This error can be worked around by setting RefreshableDisplayLabel Refresh with window property to NO. The error occurs because there is an execution (stack) conflict between refresh_screen() refresh and the component's own refresh method.
This known issue is documented in CQ #145384. It will be fixed in Version 7.0.
Keywords:
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.