question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: Is it possible to connect Batch.21 version 3.1 to Oracle version 8.1.5 on Unix? | Solution: As described in the Configuration Manual, Batch.21 v3.1 has been tested with the following Oracle databases:
Oracle v8.0.4 on NT
Oracle v8.0.4 on unix
Oracle v8.1.5 on NT
Since then we have also tried the following:
Oracle v8.1.5 on unix
The instructions in the Configuration Manual for Oracle v8.0.4 on unix also apply to Oracle v8.1.5 on unix. Note that, for performance reasons, we recommend that the user installs/upgrades to Oracle client version 8.1.6 + ODBC Driver patch version 8.1.6.2.0 as described in knowledgebaseSolution #104370.
Keywords: relational database
hpux
aix
References: None |
Problem Statement: Tag browser displays Specified driver could not be loaded due to system error 161: The specified path is invalid (Aspentech SQLplus, C:\WINDOWS\system32\ip21odbc.dll). Users may also see Invalid Tag displayed in trend plots. The behavior appears on 64-bit Windows 7 systems. | Solution: The PATH needs to be adjusted so that this part:
C:\Program Files (x86)\Common Files\AspenTech Shared
is not too far toward the end. Here is an example with the directory above near the last part of the PATH Statement
Here's an example with the AspenTech Shared section near the front:
To see what is in the path one can click on Start => Run => type 'cmd'. In the Command Prompt window issue the command 'path'.
If the 'Run' menu choice is not visible, click on Start and in the 'Search programs and files' box (right above the Start button) type 'cmd' The program 'CMD.exe' should appear at the top of the list.
The path can be adjusted through the 'System Properties' screen => 'Advanced' tab => 'Environment Variables' button.
Keywords: None
References: None |
Problem Statement: New rows added in Advanced option of IP.21 Configuration Wizard in the Aspen Excel Add-In are not visible | Solution: You can resize the IP21 Configuration Wizard section of the screen by clicking on the down arrow icon on the top right corner and select ‘size’ from the menu, and then move the divider line on the left to enlarge the area, like:
Once you resize the IP21 Configuration Wizard screen section you’ll see a scroll bar on the far right side in the Advanced section,
the scroll bar will allow you to move up and down the list or rows and see the additional lines you’ve added or add new rows and view them.
Keywords: Excel, Add-In, Configuration, Advanced
References: None |
Problem Statement: There are many products, components and technologies that comprise the Version 3.x Information Management Suite. A good understanding of how these various parts relate is beneficial before undertaking deployment. | Solution: The attached document is intended to help you plan for, install and configure version 3.1 of the Aspen Manufacturing Suite (AMS) Information Management products and the new AspenTech Framework components. Specifically this document was created to: (1) provide an overview of new AspenTech applications and concepts, (2) describe how those new applications work with the Information Management group of products, (3) provide an overview of the Information Management installation process, (4) provide an overview of the security features, and (5) provideSolutions to common problems observed at various customer sites
NOTE: This is a BETA version of the Deployment document. We invite your feedback, suggestions and comments via the Feedback link below.
Keywords: primer
getting started
introduction
installation
overview
dcom
network
firewall
security
server
pdc
domain
Trusted Domain
ADSA
account
framework
References: None |
Problem Statement: When stopping Aspen InfoPlus.21, the Aspen InfoPlus.21 Manager displays the message:
Error 231 returned by task service. All pipe instances are busy. | Solution: This problem may be caused by a lack of space on the disk drive where Aspen InfoPlus.21 is installed or on a disk containing Aspen InfoPlus.21 history file sets.
To solve this problem, try restarting the Aspen InfoPlus.21 Task Service. If the Microsoft Windows Services Applet can not stop the Aspen InfoPlus.21 Task Service, then use the Windows Task Manager to stop the process tsk_server, and then use the Microsoft Windows Services Applet to start the Aspen InfoPlus.21 Task Service. At this point you should be able to stop Aspen InfoPlus.21 using the Aspen InfoPlus.21 Manager.
Before starting Aspen InfoPlus.21 again, free up space on the Aspen InfoPlus.21 disk drive and on the disks containing Aspen InfoPlus.21 history file sets if the drives are almost full.
Keywords: Error 231
Pipe instances
References: None |
Problem Statement: What causes the message Not Enough Map Space in the field IP_HISTORY_STATUS in all the tags defined in an Aspen InfoPlus.21 database. You are most likely to see this message when Aspen InfoPlus.21 is first installed.
The Aspen InfoPlus.21 database starts correctly, and while the history repositories are working correctly, there is no history available for any of the tags in the database, and trend plots in Aspen Process Explorer will show the message the message Cannot read disk history (status -3) for a tag's value in the plot legend. | Solution: This message means the file map.dat does not exist in the folder:
C:\ProgramData\AspenTech\InfoPlus.21\c21\h21\dat
If this is a new installation of Aspen InfoPlus.21 using the demo database, then you can solve this problem by restarting Aspen InfoPlus.21.
If you see this message after upgrading Aspen InfoPlus.21, then you probably forgot to copy the file map.dat from your source system, or you inadvertently deleted the file map.dat. In this case, find a backup version of map.dat, stop Aspen InfoPlus.21, place the backup version of map.dat into C:\ProgramData\AspenTech\InfoPlus.21\c21\h21\dat, and restart Aspen InfoPlus.21.
Note:
Recreating the map.dat file with this procedure will build headers in the map.dat for the tags in the InfoPlus.21 database for historization and retrieval of tag values from the history subsystem from that point on. Any prior history information for tags would be lost since the new headers in the map.dat file do not have the necessary information to retrieve prior historical values.
Keywords: map
map space
map.dat missing
disk history
References: None |
Problem Statement: When using | Solution: ID 143040 to collect a crash dump of a crashing process, the command window used to launch ProcDump is launched with an interactive user and designed to capture immediate crashes. If a remote session is used to launch the command window, then ProcDump will crash once the remote session is exited. ThisSolution explains how to collect a crash dump for a process that crashes infrequently. ThisSolution is written for TSK_DBCLOCK, but can be applied to capture a crash of any executable on the Aspen InfoPlus.21 server.Solution
First, download ProcDump from Microsoft's website and place the executable on the server where the executable is crashing.
After this, create a new folder for the dump file to be created. For this example, we will use C:\temp\crash.
Next, create a new task named TSK_PROCDUMP in the Aspen InfoPlus.21 Manager that launches ProcDump.exe as follows:
Make sure that the executable path points to procdump.exe.
For 64-bit installations, the command line parameters should read: -accepteula -64 -ma -e dbclock.exe C:\temp\crash
For 32-bit installations, the command line parameters should read: -accepteula -ma -e dbclock.exe C:\temp\crash
Running the task will start ProcDump and set it to unload a crash dump in C:\temp\crash if dbclock.exe crashes.
Substitute the name of the executable image that is crashing for dbclock.exe.
Keywords: Crash Dump
TSK_DBCLOCK
References: None |
Problem Statement: After upgrading Aspen InfoPlus.21 from a 32-bit server to a 64-bit server the path for some file locations will change. When the history backup program (TSK_HBAK) executes, it pauses the repository but due to an incorrect path in the Backup Command lines the backup may fail to resume the repository. | Solution: When migrating an Aspen InfoPlus.21 system from 32bit to 64bit some folder locations may change. Before executing the history backup verify the paths are correctly pointing to the cleanup batch files in POST_BACKUP_COMMAND and LAST_ACTIVE_COMMAND
Example 64-bit path:
[POST_BACKUP_COMMAND]
C:\Program Files\AspenTech\InfoPlus.21\c21\h21\etc\system_cleanup.bat BACKUP PATH\system 5
[LAST_ACTIVE_COMMAND]
C:\Program Files\AspenTech\InfoPlus.21\c21\h21\etc\active_cleanup.bat BACKUP PATH\active TSK_DHIS 5
Example 32-bit path:
[POST_BACKUP_COMMAND]
C:\Program Files (x86)\AspenTech\InfoPlus.21\c21\h21\etc\system_cleanup.bat BACKUP PATH\system 5
[LAST_ACTIVE_COMMAND]
C:\Program Files (x86)\AspenTech\InfoPlus.21\c21\h21\etc\active_cleanup.bat BACKUP PATH\active TSK_DHIS 5
Keywords:
References: None |
Problem Statement: In aspenONE Version 2006.5 a limited runtime license checking functionality has been implemented along with the Aspen client application support for the MS Windows Vista operating system. In order to accommodate these changes Aspen Software License Manager (SLM) software had to be modified as well.
Thus, for the client installations of Aspen software running on MS Windows Vista to be able to successfully check out licenses, the site administrator will need to install version 8.1 of the Aspen Software License Manager and the Aspen SLM Tools and the site will need to upgrade their License Server to the same version - 8.1.
If the site SLM manager is not upgraded to version 8.1, the following client applications running on Windows Vista will be getting error messages: Aspen Process Explorer, Aspen InfoPlus.21 (IP.21) Server and the Administrator, Aspen Web.21.
1. Aspen Process Explorer messages occur when dropping a tag from IP.21 into a plot. Error dialog box reads:
ProcessExplorer.exe - License Error. Unable to acquire Process_Explorer license.
If you hit the Details button, one of the error messages will be:
Code: 25
Description: An error has occurred in decrypting (or decoding) a network message. Probably an incompatible or unknown server, or a version mismatch
2. Aspen InfoPlus.21 Server and the Administrator. This error messages shown below occur on the server, using Remote DeskTop connection, as well as on a 2006.5 client, attempting to plot data from that same 2006.5 server. When attempting to connect from a client, timeout process takes several minutes before the plot actually comes up; on the server, behavior is immediate plot after acknowledging the error messages.
Text of box is Unable to acquire InfoPlus.21 license. Invalid message encountered: Cannot acquire the IP21 Point Package Licenses.
Aspen InfoPlus.21 Administrator displays the error dialog when attempting to connect with the 2006.5 server. Message is This IP.21 server is running in Unlicensed Mode. Cannot acquire the IP21 Point Package Licenses.
Infoplus.21. The IP.21 Server cannot acquire the IP.21 Server license. Please verify that your License Manager is running and the appropriate license is available.
3. Aspen Web.21. Error message: Your Web.21 session is unlicensed! Error_while_checking_out_license_(SLM_Web21) 1000 no-net [...]
NOTE: The above error messages will also be received on any client or Aspen InfoPlus.21 server that has SLM Tools v8.1 installed while the License Server version is 7.3. | Solution: Aspen SLM Manager that comes with aspenONE v2006.5 distributes two different versions of the SLM client STRGXI2.dll file - version 2006.5.1.257 (which comes with SLM v8.1) and 2006.5.0.257 (which comes with SLM v7.3). The former is for MS Windows Vista operating system, and the latter is for Windows 2000, XP, and 2003. The problem is that the STRGXI2.dll v2006.5.0.257 is not compatible with the new client version of the dll for Vista - v2006.5.1.257. Hence, in a situation where the older version of the dll is present on the License Server and the newer version of the dll is present on a client machine, the above-mentioned errors will occur. Please see the attached PowerPoint slide for further explanation.
The bestSolution in this situation is to upgrade the License Server to v8.1 which will allow client machines running MS Windows Vista as well as those running Windows 2000, XP, and 2003 to properly check out runtime licenses.
If this is not immediately possible or there's only one or two client machines that inadvertently ended up with the newer version of the STRGXI2.dll then one could swap the dlls on those clients to resolve the issue. The STRGXI2.dll file is located in the following directory:
C:\Program Files\Common Files\Hyprotech\Shared\STRGXI2.dll
NOTE 1: In order to swap the dlls, one must stop the Aspen Batch.21 Services service and the Aspen Infoplus.21 Task Service.
NOTE 2: This will only work on clients running MS Windows 2000, XP, and 2003. MS Windows Vista requires the newer version of the STRGXI2.dll file.
Keywords:
References: None |
Problem Statement: Application support often involves troubleshooting crash or freeze situations. The attached document describes the procedure that should be followed when collecting information on an application crash or hang where the machine does not have a development environment on it or is a production machine (e.g. client).
The end result is to generate a memory dump of the suspect application so it can be sent to third-level support. | Solution: Please follow the steps in the attached document to download, install, and run the latest Microsoft Debugging Tools for Windows.
Keywords: WinDebug
windebug
win debug
References: None |
Problem Statement: If you change the Batch Unit name in the Batch Detail Display or the Aspen Production Record Manager administrator you may encounter an error which causes the APRM service to stop unexpectedly. | Solution: You can rename the Batch units although for this to take effect you will need to restart the APRM services.
Note: Before restarting these Services ensure that no Batches or queries are running from the BCU to avoid issues with data.
Keywords: UNIT
APRM
Batch.21
ASPEN PRODUCTION RECORD MANAGER
References: None |
Problem Statement: When you try to add a Microsoft control (i.e. Microsoft FlexGrid) to a VBForm in Aspen Process Explorer, you get the error The control could not be created because it is not properly licensed. | Solution: This is a Microsoft error. You must have a design-time license to use Visual Basic 6.0 ActiveX controls. These errors occur because the system registry does not contain the design-time license information. The following Microsoft knowledge base article lists two possibleSolutions to the problem:
http://support.microsoft.com/default.aspx?scid=kb;en-us;318597
Keywords: VBA
References: None |
Problem Statement: This knowledge base article provides an example Aspen SQLplus query which uses the CharacteristicConditions object to retrieve a list of batches which have characteristic values that meet specified criteria. | Solution: This example query returns all batches which have a batch number (BATCH NO) greater than 1000. In order to use this query:
Change the data source from HKLAP to a data source in your environment
Change the batch area from SQLDemo to a batch area in your environment
Add a reference to the Aspen Batch.21 Application Interface as shown below
local data_sources, batch, myarea, myquery, batchlist, i int;
local StartTime timestamp, EndTime timestamp;
data_sources = createobject('AspenTech.Batch21.BatchDataSources');
write data_sources('HKLAP').Areas.Count;
myarea = data_sources('HKLAP').areas('SQLDemo');
MyQuery = MyArea.BatchQuery;
-- Clear the query.
MyQuery.Clear;
Myquery.CharacteristicConditions.Add('BATCH NO', 1, atGreaterThan, '1000');
batchlist = MyQuery.get;
for I=1 to batchlist.count do
begin
write batchlist(i).characteristics.item('BATCH NO');
write batchlist(i).characteristics.item('Start Time');
write batchlist(i).subbatches('REACT').subbatches('HEAT1').characteristics.item('Start Time');
write batchlist(i).characteristics.item('CHAR');
exception
write 'No BATCH NO';
end
end
batchlist = null;
batch = null;
Keywords: API
Application Programming Interface
Automation Interface
Sample
References: None |
Problem Statement: What causes the error Compile error in hidden module: ThisWorkBook: when opening a Microsoft Excel 2007 spreadsheet containing the legacy Aspen InfoPlus.21 Process Data Add-In?
              | Solution: You may see this error after applying the Microsoft security update MS12-060 for Visual Basic 6.0 issued on August 14, 2012.
To resolve this problem, open an elevated command prompt with administrator rights. Â Go to c:windows\system32 and run the following commands:
regsvr32 /u mscomctl.ocx
and then command
regsvr32 mscomctl.ocx
You should see success messages for both commands if you have sufficient rights.
Keywords: Compile, Error, hidden, module, Thisworkbook
References: None |
Problem Statement: This Knowledge Base article shows how to calculate duration of a subbatch in Aspen Production Record Manager (APRM). | Solution: This example shows how to calculate duration of a subbatch called MIX.
· In APRM Administrator, expand the tree view in the navigation pane and create a duration characteristic called MIX_DUR1 under Phase Definition | Phase | Characteristic Definitions node, as shown below. Make sure Display Format is set to DP+H.0.
· Set up a simple calculation called MixDur, as shown below, binding the output of the calculation to characteristic MIX_DUR1. Make sure the calculation is using the Trigger instance.
The calculation will write the result directly to the characteristic at the end of the MIX phase.
Keywords: None
References: None |
Problem Statement: The following error appears when attempting to starting unit scheduling from the BCU Server Manager.
Failed to start unit scheduling : 'B21BSC-50002: Relational Database Error -2147217843:
[Oracle][ODBC][Ora]ORA-01005: null password given; logon denied' | Solution: This error is related to the ODBC Data Source used to connect to the Oracle Relational Database.
When configuring the ODBC Data Source with the Oracle ODBC Driver, there is a required User ID field. However, a separate field may not exist for the associated password. In this case, the user name and password must be specified in the Usier ID field using the following syntax.
user_name/password
For example:
Keywords: scheduling
unit
-2147217843
null
password
logon
denied
References: None |
Problem Statement: After Aspen's Excel Add-In is loaded into Excel and utilized normally, upon closing a spreadsheet the user receives a Microsoft Excel prompt:
Do you want to save the changes made to 'AtData.xla'? | Solution: Locate the AtData.xla file on the machine and right click to select Properties. Click the Attributes box for the Read-only option. This will allow spreadsheets to be closed without receiving the prompt for saving changes to the AtData.xla file.
Keywords:
References: None |
Problem Statement: This knowledge base article explains why the Aspen Tag Browser does not display a list of folders and why the Description field is grayed out when connecting to a particular data source. | Solution: This occurs because the user has configured the Aspen Tag Browser to connect through Aspen Web.21 in
View | Options | Web.21
When the Aspen Tag Browser is in this mode, it uses Aspen Process Data (Web) which does not support getting the description or the folder structure. This is because Aspen Process Data (Web) does not use an Aspen SQL Plus service, which is what provides this information for the Aspen Tag Browser in standard mode.
To ensure that you are not connecting through Aspen Web.21 ensure that the Use Web.21 Server option is not selected.
Keywords: Grey
unavailable
References: None |
Problem Statement: Why doesn't the Aspen Tag Browser display folders and why is the description field grayed out when using simple searches? | Solution: The Aspen Tag Browser uses Aspen SQLplus to perform searches. Start the ADSA Client Config utility and verify data source includes the Aspen SQLplus service component.
Keywords: ADSA
tag browser
expand
expansion
greyed
description
References: None |
Problem Statement: Aspen Process Explorer allows you to plot formulas using ad-hoc calculations. To create an ad-hoc calculation, enter the formula following an = sign as shown in the example below:
In this example, the ad-hoc calculation sums two flows, and Aspen Process Explorer displays the result; however, the description of the calculation, Ad-hoc Calculation, does not describe the purpose of the calculation. Is there a way to create a description for an ad-hoc calculation? | Solution: Create a shared ad-hoc calculation using Aspen InfoPlus.21 against the definition record IP_CalcDef
Give the record a meaningful description and set the field #CALC_LINES to 1.
Expand the repeat area #CALC_LINES, and enter the ad-hoc calculation as you would on an Aspen Process Explorer plot.
Now, plot this record instead of the ad-hoc calculation, and you will see a meaningful name and description.
You can also use the Aspen Calc GUI to create a shared on-demand calculation instead of using the Aspen InfoPlus.21 Administrator.
Open Aspen Calc and click on the Shared icon:
Select the Aspen InfoPlus.21 server that will store the calculation and click on the New button:
On the next screen, enter the Name of the ad-hoc calculation, a meaningful description, and the calculation itself. Then press the OK button.
This creates a record defined against IP_CalcDef in the Aspen InfoPlus.21 database as before.
Keywords: Shared on-demand calculation
References: None |
Problem Statement: This knowledge base article describes why the following error can be generated from a custom application which calls the Aspen Batch.21 Application Programming Interface (API).
Error reading property get: B21BSC-50001: Framework GetUserRoles method call failed: -2147024891 | Solution: This error is related to an Aspen Framework (AFW) / Aspen Local Security (ALS) function call. The error code -2147024891 translates to Access Denied. This indicates that the account which runs the custom application does not have the correct privileges within AFW / ALS or this account may not have the necessary network level permissions to query the active directory for group information.
You should verify that the account under which the Aspen Batch21 Services runs is a domain account which has privileges to query group information from the active directory. If your custom application also runs as a service or runs under the IIS anonymous user account then make sure this account can also query the active directory for group information.
The security diagnostic tool, SSTest, can be run to troubleshoot security related problems. SSTest can be downloaded from knowledge base article 106497.
Keywords: Deny
Permission
References: None |
Problem Statement: Warning message when opening Excel regarding missing Aspen Add-In, for example after a Aspen Process Explorer upgrade:
'C:\Program Files\Microsoft Office\Office\LIBRARY\ATData.xla' could not be found. Check the spelling of the file name, and verify that the file location is correct.
If you are trying to open the file from your list of most recently used files on the File menu, make sure that the file has not been renamed, moved, or deleted.
Note that the path of the file indicated in the error message may be different. Also, the problem persists even after removing and re-adding the Aspen Add-In. | Solution: If any Excel Add-In is missing - for example after a Process Explorer upgrade - and there is a problem re-adding it, try these specific steps:
1. Remove the existing Aspen Add-Ins (e.g. in Excel, go to Tools | Add-Ins and uncheck the box for Aspen Process Data Add-In)
2. Close Excel
3. Reopen Excel
4. Browse (in Excel, go to Tools | Add-Ins | Browse) to the location of the latest version of the Aspen Excel Add-In (file named AtData.xla) and add it back in. Note that while usually in C:\Program Files\Microsoft Office\OfficeXX\LIBRARY, the ATData.xla file could also be in C:\Program Files\AspenTech\APEx\PE\ADDIN or C:\Program Files\Common Files\AspenTech Shared directory, depending on the version of Process Explorer and on the version of Microsoft Office.
Be sure to follow all steps. In particular take care of closing and reopening Excel as indicated in steps 2 and 3.
Keywords: addin
installation
excel
cannot access
load
file name does not exist
error occurred
References: None |
Problem Statement: When trying to open a new plot after an install or upgrade of Aspen Process Explorer 'File | New' is grayed out | Solution: When File | New is grayed out after a new install or upgrade of Aspen Process Explorer there are three different scenarios that can cause this behavior
1. Make sure the URL path under the client registry entries and server registry entries tab in the AFW Tools (Start --> Programs --> Aspentech --> AFW Tools) is pointing to the correct AFW security server. The URL path should be like following
http://nodename/AspenTech/AFW/Security/pfwauthz.asp
For instance if 'CMAIFP2' is the nodename of the security server then the URL looks like following
http://CMAIFP2/AspenTech/AFW/Security/pfwauthz.asp
When this URL is copied onto an internet explorer webpage it should leave blank without any errors which means that the URL path defined is correct.
2. Go to AFW Security Manager, expand the Applications and then Process Explorer. After that click on Secure Commands and see if you have FileSave, VBA, and FileNew in that area and if Execute is checked for all the securable objects. If so this behavior might be because the Application XML files were not properly imported into AFW security manager on the security server. Re-import the two XML files PE.xml and Graphic.xml and check on Execute option for all the securable objects.
3. When the credentials of user logging into the Aspen Process Explorer have no enough privileges defined in the AFW security manager this problem will occur as well. Check and see if a user account having problem is configured in the Roles within AFW Security Manager.The user account having this problem has to be added to the Role in AFW Security Manager and a proper privilege has to be granted. The user has to be identified by its user name (not as a group member) in the proper Role in the Security Manager.
For instance, if an individual user is a member of the Admin group on the server and the Admin group was added to the Role of the engineer. You would have to add the user directly in the Engineer Role and give him/her the proper privilege.
Keywords: Plot
File
File|New
greyed out
References: None |
Problem Statement: When running the Aspen Tag Browser on a non-English Windows operating system for the first time, you get the error Type Mismatch. | Solution: The reason for this error is that during installation, registry keys have been translated from English into the language of the operating system.
You can overcome this error by executing following steps:
1. Run Regedit
2. Navigate to HKEY_CURRENTUSER\Software\AspenTech\
3. Delete the 'Aspen Tag Browser' entry
After these steps, the Tag Browser should start without errors. The (correct) registry key will be created when you close the Tag Browser.
Keywords: Tagsearch
References: None |
Problem Statement: This knowledge base article describes the possible ways to move an Aspen Batch.21 BCU configuration from one server to another server. | Solution: If you only need to move the batch structure (without the data) from one server to another then transferring the BCU configuration will just involve loading the *.bcu file(s) from server A into server B. This assumes that the batch structure, etc. will be the same on both servers and that you've already exported the batch structure from the old server to the new server through the xml export/import function.
Since version 6 the BCU structure is stored in the Aspen Batch.21 database,. Therefore, if you need to move the batch structure as well as the existing batch data to a new server then you can make all necessary changes within the Aspen Batch.21 database tables. If the Aspen Batch.21 tables are copied to a new server, first verify that the BCU_* tables are present and populated. To change the BCU server to the new server you then only need to ensure that the server name entry is correct in the BCU_SERVERS table.
Keywords: migrate
References: None |
Problem Statement: The Batch Administrator is extremely slow to expand the Data Sources object, displaying the available Batch data sources. The delay to expand the data sources can be up to 6 minutes. Once the data source is expanded, subsequent activity in the Batch Administrator is not unnecessarily slow or delayed.
This problem can exist for v2004.2 Batch systems that are unable to acquire a license for Golden Batch Profiling. | Solution: The Golden Batch Profiling component was added to Batch.21 in version 2004.2. Profiling requires that a Golden Batch Profiling license be acquired from the SLM server license server the first time Profiling is used. You can check if a license has been acquired by right mouse clicking the Profiling object in the Batch Administrator. Select Properties from the context menu. The License Check button will indicate if a license has been acquired or not.
If a license has not yet been acquired, the Batch Data Sources object will check the SLM license server to see if a Golden Batch Profiling license is available. This license check can take a long time if the license server is not running or if an invalid SLM host name has been specified in the SLM Configuration Wizard.
To verify that the SLM host name is correct, open the SLM Configuration Wizard from Start | Programs | AspenTech | Common Utilities. The second screen in the wizard will display the Servers that have been configured as SLM servers. If one of the host names is incorrect, it should be removed or corrected.
Keywords:
References: None |
Problem Statement: The Aspen Tag Browser has an option to save frequently used searches under a Favorites option,
Where does the Aspen Tag Browser save this list? | Solution: The Aspen Tag Browser saves the favorites list in a file in the Application Path\User Name\favorite.fav folder.
The path for this would be:
C:\Program Files (x86)\Common Files\AspenTech Shared\Apex\<User name>
Where <User Name> is the name of the login user in the system.
Keywords: TagBrowser, favorites
References: None |
Problem Statement: Advanced Search and Description are not available in the Tag Browser and it is not possible to do a simple search using the description field because it is grayed out. Advanced Search option is also grayed out. How do I get these options enabled? | Solution: Simple Search by Description as well as the Advanced Search uses SQLplus. Make sure that the SQLplus Service component is configured as a service for the data source.
Keywords:
References: None |
Problem Statement: When installing the Aspen Manufacturing Suite, the installation can sometimes fail on the Noblenet Portmapper core component. The following message will be returned:
set up of core component noblenet failed. Installation can not continue
This article provides suggestions to work around this error. | Solution: Ensure that no other noblenet portmappers services are already installed/running on this PC. There are a few 3rd party products from other software vendors which install another portmapper. The existence of any other portmapper besides the one distributed on the AspenTech installation CD can cause the Noblenet Portmapper core component to fail during the installation.
Another option is to install the noblenet core component manually from this folder on the installation CD:
Core\Noble Net
double click on setup.exe when in this folder.
If the installation still fails after trying these suggestions, then please examine the psetup.log from this PC to determine exactly which files the installation routine cannot install. This log file will contain debug messages regarding the installation process.
Keywords:
References: None |
Problem Statement: This knowledge base article describes how to troubleshoot the scenario in which creating batches through the Aspen Batch.21 Application Programming Interface (API) within an Aspen SQLplus query takes an excessively long time. | Solution: - First, check the actual execution time on your query to see how long it takes for the complete query to execute. The following query will calculate the execution time of an Aspen SQLplus query:
LOCAL T TIMESTAMP;
T = GETDBTIME;
--Insert your query being tested here
WRITE GETDBTIME - T;
After you know the total execution time for the query you can use this technique to determine which specific lines of your query take an excessively long time to execute.
- Make sure that your CompQueryDef record or QueryDef record is the only record processed by a given TSK_IQ# (an instance of iqtask.exe). This will ensure that your batch creation query does not have to wait for any other queries to finish processing before it can execute. Instructions to create a new instance of TSK_IQ# to process a new query can be found inSolution # 101389.
- Monitor the CPU & memory usage of all processes on your server to see if any processes are using excessive amounts of resources. In particular, monitor the batch21services and iqtask.exe. If the Oracle processes are the only processes using excessive resources you may want to ask the site's Oracle DBA to tune the database for better performance.
- Run a disk fragmentation check to see if the drive is fragmented. If the drive is moderately fragmented then defragment the drive.
- Ensure that your query destroys the objects that it creates. Otherwise, this may eventually lead to excessive resource usage by the batch21services. To destroy the objects set them to null at the end of your script, like this:
characteristic = null;
batch = null;
DataSource = null;
Keywords: custom
creation
performance
slow
lag
References: None |
Problem Statement: You receive an error in the application log in Aspen Process explorer that reads atConnections.GetServerList: Can't create ADODB.Recordset!
Or
You open the 'Tag Browser' and no servers are shown in Aspen Process Explorer or Infoplus.21 Administrator.
or
You get the error message Retrieving the COM class factory for component with CLSID {00000514-0000-0010-8000-00AA006D2EA4} failed due to the following error: 80040154 in Aspen Process Explorer. | Solution: This occurs when the Msado15.dll becomes unregistered to fix this issue you will need to register the Msado15.dll. This is typically located in C:\Program Files\Common Files\System\ado\ folder.
To register the DLL open a Command Prompt with administrator privileges.
Enter the commands
cd c:\windows\system32
regsvr32.exe Msado15.dll
Press Enter and re test application.
Keywords: Msado15.dll
Tag Browser
Aspen Process Explorer
Aspen Process Browser
IP.21
References: None |
Problem Statement: The Display multiple maps for tags option of the Tag Browser in View | Options, is supposed to return multiple instances of a tag based on it's map record associations. That is, if a tag has two or more map record associations, it appears two or more times in the Tag List - once for each map record association. If Display multiple maps for tags is not checked, then only the default map record association should be returned. This article describes a situation where Display multiple maps for tags is not checked BUT multiple maps are returned. | Solution: If there are multiple map records associated to a Definition record, then each map record corresponds to a particular repeat area. There is a field, Map_IsDefault, that determines which map record is used as the standard default map record. For example, in the definition record PMCAnalogDef, there are two repeat areas: one for raw data and one for compressed data. Hence there are two map records - one for each repeat area: PMCAnalogRawMap for raw data and PMCAnalogMap for compressed data. One of these map records is considered the default map record. Typically this is the compressed map record. So, in the Map_IsDefault field for PMCAnalogMap, this field is set to TRUE and for the PMCAnalogRawMap, this field is set to FALSE. If you want BOTH maps returned in Tag Browser searches, the Display multiple maps for tags option needs to be checked. If you do not want multiple maps returned, just the default map, then this setting should not be checked.
If the Map_IsDefault field for BOTH map records is set to TRUE and the Display multiple maps for tags is NOT checked, the Tag Browser will return an instance for both map record associations - as they are both considered default in this configuration. This is not a desirable setup and can lead to confusion.
Keywords:
References: None |
Problem Statement: The legacy (older) process data add-in for Microsoft Excel will not work and when selected will produce a message like this:
Microsoft Visual Basic for Applications (title of dialog box)
Compile error in hidden module: frmCurrValue.
This error commonly occurs when code is incompatible with the
version, platform, or architecture of this application. Click Help
for information on how to correct this error.
How can this condition be corrected so that the add-in will work correctly? | Solution: The settings in Microsoft Excel have been tightened and this causes the add-in to not work correctly. Here's where to go to relax the settings:
Excel 2010 and Excel 2013
'File' => 'Options' => 'Trust Center' => 'Trust Center Settings...' button => 'ActiveX Settings'
On this screen, if the top option is selected (the one which says 'Disable all controls without notification') then the add-in will have trouble running and will produce the error message. A less-restrictive option should be selected like the second one:
Prompt me before enabling Unsafe for Initialization (UFI) controls with additional restrictions and Safe for Initialization (SFI) controls with minimal restrictions
or the third one:
Prompt me before enabling all controls with minimal restrictions
Note: The 'Safe mode' selection which also appears on this screen can remain checked.
Keywords:
References: None |
Problem Statement: The start time for aggregates in Aspen Process Explorer and Excel Add-in is not at the desired time. | Solution: Under the HistoryParamDef definition record is a record named HistoryParameters. At the bottom of the record, the AGGREG_DAY_START field dictates the timestamp used in Aspen Process Explorer for Start of Day aggregates.
Keywords: average
aggregate
time
spreadsheet
start
day
start of day
daily
References: None |
Problem Statement: Both Process Explorer and the Excel Add-Ins provide the ability to make on-the fly calculations such as Averages. This | Solution: is aimed at showing the different options for handling Timestamps when calculating Averages.Solution
Looking first at the Aspen Excel Add-ins (via the Aspen Process Data Add-In):
Click on Aspen -> ProcessData -> GetData -> Trend/AggregateData and Type = Average
Let's use an example of defining a Timespan that extends from 8:07am to 11:07am, and we are asking for Averages with a Period (length) of 20 minutes. Clicking on the Settings button and the Aggregation tab, there are 2 Radial buttons, one for Start of Day and the other for Start of Time. What is the difference between these choices?
Start of Day gives averages at 8:20, 8:40, 9:00 ..... 10:40 (so timestamp is start of 20 minute intervals based on midnight.)
Start of Time gives averages at 8:07, 8:27, 8:47 ...... 10:47 (so timestamp is start of the 20 minute intervals based on start time for span.)
In other words, Averages will always be timestamped at the 'Start' of the Period. However the Periods themselves will vary depending on whether they are to be calculated from Midnight (StartofDay), or the 'Start Time' of the timespan (StartofTime.)
Next, let's look at Process Explorer Trend Plots:
Right Click on a tag in the Legend and choose Properties -> Sampling and Type=Average, then click on the Settings button. You are presented with the same two choices as above, StartofDay and StartofTime. Selection of either one of these gives the same results as you get with Excel Add-Ins. However, Process Explorer itself has more user options.
First, as seen by clicking 'Settings', you will see a Timestamp Anchor with 3 choices.
-- Begin. This choice will again give the same results as the Excel Add-Ins - in other words the associated timestamp will be the 'Start' of the Period.
-- End. This choice will give the same average values as before, but the associated timestamp will be the 'End' of the Period.
-- Middle. As expected a choice of Middle will give the same average values but the associated timestamp will be the 'Middle' of the Period.
Also, Process Explorer provides a 'Shift' option. This will affect how the Trend Plot 'line' looks in relation to the timeline at the bottom of the display, but it will NOT affect the timestamps as seen in the Show Data Table option
Keywords:
References: None |
Problem Statement: When viewing an IP_TextDef record in an Aspen Process Explorer trend plot, the current value (value displayed to the right of the trend plot area) flashes from the actual textual value to asterisks. | Solution: In most cases, this can be resolved by clicking in the legend and selecting the Extrapolated option for that pen.
For text tags that don't store a value in history very often, it may also be necessary to use a Sampling Type of Actual, check the Extrapolated option, and modify the record's IP_MAX_TIME_INT parameter based on the typical time span being viewed in the plots.
Keywords: asterisk
text
References: None |
Problem Statement: The 'Find' (binoculars) button in the Aspen Production Record Manager Batch Detail Display (BDD) allows a user to type in a Batch Number (or whatever value has been set as the Batch Designator) so that the batch details can be viewed in the BDD. However, it is also possible to look up batches in the BDD by the Batch Handle. The Batch Handle is an internal unique identifier for a single batch that contains both the data source name and the individual BatchID. In other words, BatchHandle = DataSourceName.BatchID | Solution: To search on batches by the Batch handle, hold down the Ctrl key while clicking the Find button in the BDD. A dialog box as shown below will appear and prompt for the batch handle.
Keywords: find
Batch Detail Display
References: None |
Problem Statement: Sometimes, after backup/archive & purge in the Batch.21 Administrator, a user will be unable to delete the area. The usual message 'Are you sure you want to delete area 'xxx' and all its contents' appears. After clicking 'Yes' the following message pops up: 'B21BSC-50233 Unable to get resource string for string ID 50233'. Clicking OK leaves the area intact.
What does the error 'B21BSC-50233 Unable to get resource string for string ID 50233' really mean? | Solution: The error message indicates that the user has some BCU configuration tied to this area. The meaning of the error message is as follows:
IDS_ERR_AREA_DELETE_NOT_ALLOWED_BY_BCU_UNITS
Deleting this item is not allowed because there are BCU units installed in the area. You must delete the associated BCU units first.
=========================================
This means that you will need to delete the associated BCU units first before you can delete the area in the Batch.21 Administrator. (IMPORTANT: please make sure the units are also deleted from the scheduler table.)
Keywords:
References: None |
Problem Statement: One of the following errors is received:
1. When starting the Tag Browser:
2. When creating a new file or opening an existing plot in Process Explorer:
3. When opening the Web.21 home page: | Solution: Verify the file AtProcessData.dll exists in the correct path.
The default location is: C:\Program Files\AspenTech\ProcessData\
If the file is missing and the problem occurred in Process Explorer or the Tag Browser, reinstall Process Explorer. If the problem occurred in Web.21 you will need to reinstall Web.21 on the web server.
If the file does exist you will need to manually register it.
1. Stop the affected application(s) if running.
2. Unregister the dll.
a. Open the Run command and type: regsvr32 /u and then drag AtProcessData.dll onto the command line as shown below.
b. Click OK. If the unregistration is successful you will see the message:
3. Register the dll:
a. Open the Run command and type: regsvr32 and then drag AtProcessData.dll onto the command line:
b. Click OK. If the registration is successful you will see the message:
4. Retest the application to verify that the problem has been corrected.
Keywords: ActiveX component can't create object
Could not Create DataSources object
Check that AtProcessData.dll is registered
The object has an invalid ProgID of 'AtProcessData.S95'
References: None |
Problem Statement: How do you enable debug logging for Aspen Tag Browser? | Solution: To enable debug logging for the Aspen Tag Browser please do the following:
1. Open a Windows OS Command Prompt by right-clicking and selecting 'Run as Administrator'.
2. Navigate to the directory where the tag browser executable (TagBrowser.exe) is located (usually one of the following):
C:\Program Files\Common Files\AspenTech Shared\Apex
or
C:\Program Files (x86)\Common Files\AspenTech Shared\Apex
3. Issue this command: tagbrowser.exe -debug
4. This will create a text file called TagBrowser.log in a username subdirectory beneath the directory where the executable resides. For example, if the username is starkt and it is a 64-bit Windows OS it would be located here:
C:\Program Files (x86)\Common Files\AspenTech Shared\Apex\starkt\TagBrowser.log
This should be done on any system which is experiencing an issue with the tag browser.
Keywords:
References: None |
Problem Statement: | Solution: # 103699 provides information on how to disable writes to the Aspen InfoPlus.21 database version 2.5.1 from Aspen Process Explorer/Excel Add-ins. However, this suggestion does not work for Aspen InfoPlus.21 version 3.x and higher.
The question becomes: How to implement Excel Addin security in Aspen InfoPlus.21 version 3.x and higher?
Solution
Starting with AMS version 3.x, Aspen implemented database security through the use of Aspen Local Security. Through that tool, roles are added and Windows users and groups are assigned to roles. Using the Aspen InfoPlus.21 Administrator tool, the roles are assigned database permissions such as READ, WRITE, CREATE, and DELETE.
If you want to disable writes to Aspen InfoPlus.21 from Excel, you will need to implement Aspen InfoPlus.21 database security limiting some or all roles from writing. The login used to launch the Excel application will be checked for permissions within the Aspen Local Security server.
Keywords: None
References: None |
Problem Statement: You get the message Function Not Supported By Server displayed in Aspen Process Explorer when you set the sampling type to Interpolated for a tag from a v7.2 InfoPlus.21 data source. You do not get this error if you set sampling type to Actual or Best Fit, in fact in these cases the tag trends correctly.
When using v7.2 of Aspen Process Explorer you do not get this error message, even when trending the same tag as before, it only happens if you mix the client/server versions, eg. use v7.3, v8.0, etc client software with v7.2 InfoPlus.21 server.
You also note that when using Excel Process Data add-in it produces empty cells of output data plus a status with the Function Not Supported By Server error message when you attempt to read Interpolated data from the v7.2 data source.
Should you then review the Process Data diagnostic logs you see the following entries:
(5692) 02/25/2014 15:16:31.719 AMRHIS21INTERPOLATE: Function Not Supported By Server.
(5692) 02/25/2014 15:16:31.891 SMRHIS21INTERPOLATE: Function Not Supported By Server. | Solution: AMRHIS21INTERPOLATE and SMRHIS21INTERPOLATE API functions were added to v7.2 (initially in cumulative patch 6) to improve reporting of daylight saving transitions. Your client programs are expecting to find these functions but you are running a version of the API that does not have them.
Apply the update which includes the patch for defect ID: CQ00422363 to your v7.2 InfoPlus.21 server. This can be found in the latest Aspen InfoPlus.21 v7.2 Cumulative Patch.
Keywords: AMRHIS21INTERPOLATE
SMRHIS21INTERPOLATE
Function Not Supported By Server
Mixed versions
Interpolated different than Actual
References: None |
Problem Statement: Attempting to start the BCU Unit Scheduling returns a failed to start unit scheduling '(null)' error message. | Solution: Before BCU Unit Scheduling can be started using the BCU Server Manager a Batch Area has to exist first. If there are no Batch Areas defined in the Aspen Production Record Manager Administrator, then the BCU Server Manager will return the error message: failed to start unit scheduling '(null)' . This is normal. Add a Batch Area and then you will be able to start the BCU Unit Scheduling.
Keywords: failed to start unit scheduling '(null)'
BCU Server Manager
scheduling
References: None |
Problem Statement: Unlike Tag Browser searches of an IP.21 database, when using the Tag Browser to search a tags in a relational database, the Description field is grayed-out. The user is unable to search for RDBMS tags by description. | Solution: This behavior is by design. The description field of the Tag Browser search is only enabled when SQLplus is supported for the data source. SQLplus is not supported for RDBMS tags.
Keywords: relational
database
SQL
Oracle
description
References: None |
Problem Statement: What is the Value - Incomplete or Integral - Incomplete option used for?
These options appear in the Process Data Add-In's functional area:
Process Data | Get Data | Trend/Aggregate Data => Settings => Aggregation tab => Aggregation Method. | Solution: Version 6.x and higher of Excel Add-In was enhanced to add the Value - Incomplete and Integral - Incomplete aggregation methods. These features are described in the Aspen Process Explorer v6.0 Release Notes:
Process Data Add-Ins now allow aggregate trends for incomplete samples. The Add-Ins now have the options for sampling data where the LAST aggregate bucket is incomplete but you still want a trend or value returned. This will continue to be exposed in the plots, as well.
So there are now two options when performing aggregate requests. If it's not desired to compute a value for an incomplete aggregate period, use the Value or Integral method. If it is desired to compute the aggregate for such a period, then use the Value Incomplete or Integral Incomplete method.
A documentation defect has been submitted for this information to be added in the Excel Add-In's Help file.
Keywords: Integral
Integral - Incomplete
Value - Incomplete
Excel Add-in
Aggregation Method
References: None |
Problem Statement: Base on KB125643 , while right click on the toolbox and select Additional Controls, Additional Controls Dialog Box is not showing. | Solution: This problem usually happen when we change or config our Microsoft Office to new version.
you can run Process Explorer in compatibility mode.
Keywords: additional controls
compatibility
process explorer
VBA
References: None |
Problem Statement: How do you use Ad-hoc calculations in Aspen Process Explorer to highlight relationships between Aspen InfoPlus.21 tags? This technique can be used to transform the Aspen InfoPlus.21 database from a collection of time-stamped values to more of a relational database. This approach could be used as a primary tool for driving process improvements. | Solution: Introduction
Aspen InfoPlus.21 is not a relational database. Each Aspen InfoPlus.21 tag is an independent collection of time-stamped values. Aspen InfoPlus.21 does not define any sort of relationship between tags. However, process variables in reality are often highly correlated. Ad-hoc calculations in Aspen Process Explorer allow users of any skill level to quickly and easily translate their intimate knowledge of the way their processes work into simple, easy to create Ad-hoc calculations that express these multivariable process relationships or interactions.
Example
A simple example will help to illustrate this technique. We'll look at three tags from the Aspen Chemical demo database: ATCTIC301 (reactor temperature); ATCPRODN (product made,values of 1, 2 or 3) and ATCQUAL (product quality, varies from 70-79%.) Using an Aspen Process Explorer trend plot, the goal is to highlight: Values of Reactor Temperature (ATCTIC301)only where Product Made (ATCPRODN) = 3 and Product Quality (ATCQUAL) < 75%. To do this, define the following Ad-hoc pen:
=If ATCPRODN=3 and ATCQUAL < 75 Then ATCTIC301
The trend for ATCTIC301 will appear on the plot only where the conditions expressed in the Ad-hoc calculation are True. The rest of the plot will be blank. Values of ATCTIC301 will be displayed based not just on Start Time and End Time but on selection criteria applied to two (or more) other tags. This is completely different than just displaying a group of tags based only on their Start Times and End Times. This type of Ad-hoc query is more or less equivalent to performing a SQLplus Join but is much easier to create.
You could add more tags to the condition. You could add many tags to the condition:
=If ATCPRODN=3 and ATCQUAL <75 and ATCLOST < -400 Then ATCTIC301.
A between condition selecting values of ATCQUAL between 75 and 79 would be expressed in the following way:
=If ATCQUAL >75 and ATCQUAL < 79 Then ATCTIC301.
In the plot below, wherever the purple tag (ATCTIC301) is visible the conditions are true. Wherever the plot is blank the conditions are false.
This calculation could be simplified by substituting the value 1 for the tag ATCTIC301 in the calculation. Where the purple line is visible the condition is true. Where it's not visible the condition is false.
Two Basic Ways to apply this Technique
The user can use this technique in two basic ways:
They can look back through historical data and mine out time periods where particular operating conditions or process interactions described by the Ad-hoc calculation were true. How many times in the last year has this multivariable combination of conditions occurred? These conditions may represent ideal conditions or they might represent bad conditions. This technique can be used to explore the data in hindsight looking for potential process improvements or to troubleshoot problems.
This approach can also be used for a sort of real-time monitoring. Assume that the Ad-hoc calculation in this example describes a problem situation. When the Ad-hoc pen appears on the plot, that would be an indicator that there is a developing problem. Operational personnel could then respond in a timely and appropriate way.
Because the Ad-hoc pen is a multivariable calculation combining several or many process variables, it is potentially a powerful diagnostic tool. Ad-hoc calculations like the ones described here do not necessarily represent rigorous statistical measures of what's happening with the process unless the equations are the result of a formal multivariate analysis done in with some other tool. This is an informal technique that allows users of all skill levels to easily create calculations that incorporate their own understanding of the process and see what that understanding looks like for a particular time period. It's very easy to adjust the threshold values in a sort of sensitivity analysis or add additional variables to the calculation and view the new results immediately. This is a very visual and intuitive technique that is accessible to a wide range of users.
Ad-hoc vs On-Demand
Users can create Ad-hoc calculations by themselves and save them for reuse by saving the plot. Alternatively, it is possible to create Shared On-Demand calculations in Aspen Calc. Shared On Demand calculations can easily be reused by all database users. Shared On Demand calculations are defined in exactly the same as the Ad-hoc calculation and can express the same multivariable logic as Ad-hoc calculations. Shared On Demand calculations are available to a wide audience through the Aspen Tag Browser. Ad-hoc calculations can contain individual tags as well as Shared On-Demand calculations. An Ad-hoc calculation can consist of multiple Shared On-Demand calculations combined together with individual process tags.
=IF ON_DEMAND1 < 45 AND ON_DEMAND2 = 120 and ON_DEMAND3 > 14 and ON_DEMAND3 < 25 THEN 1
Keywords: on demand, shared on demand, ad-hoc, ad hoc, relational, process improvement, ad hoc calculations, multivariate, multivariable, univariate
References: None |
Problem Statement: Example of using an Aspen SQLplus iq.exe command line program to run a simple Command from the Aspen BCU Administrator. When a trigger fires a Command is executed which runs a parameterized SQLplus script and dumps out a message containing the internal Batch ID (not the Batch Designator) of the batch being processed and the time the trigger fired. | Solution: Example SQLplus script saved as a text file in C:\MyBatchReport.sql
Set Append 'C:\MyReport.txt';
Write 'Batch is Really Finished'||' '||&1' '||'&2';
Add a new Command to a BCU trigger in a BCU script, right click on trigger and select Add Command.
In the Command line for this trigger enter:
C:\Progra~1\Aspentech\InfoPlus.21\db21\code\iq.exe C:\MyBatchReport.sql
Specify an additional argument of Batch ID. Set the Argument source to Batch ID using the drop-down. The Batch ID will be passed to the query as &1.
Specify a second argument of Time of trigger. To do this, click into the empty cell right next to Batch ID. Specify the Argument source as Batch ID using the drop-down. This will be passed to the query as &2. The single quotes around &2 in the SQLplus query are required because it will be returned as a string.
Save the BCU script and schedule it.
When the trigger fires containing Command the SQLplus query will be executed and the output text file will be updated.
Example C:\MyReport.txt output from trigger firing several times:
BATCH IS REALLY FINISHED 1040 7/13/2006 2:51:50.800000 PM
BATCH IS REALLY FINISHED 1041 7/13/2006 3:03:12.400000 PM
BATCH IS REALLY FINISHED 1042 7/13/2006 3:25:16.000000 PM
BATCH IS REALLY FINISHED 1043 7/13/2006 3:46:18.100000 PM
This is a trivial example, but with this technique the user could perform a calculation, run a report, send an email, send a page, update values in a remote data base.
Here's another possible example. Suppose the trigger is the End of Batch trigger. The firing of this trigger could cause a SQLplus script to run that uses the Batch COM API to read characteristic values from the Batch database, creates a formatted end of batch report using those values and emails it out to a list of recipients etc.
Keywords: BCU Administrator, BCU Script, command, SQLplus, iq.exe, BCU command, argument source, arguments, Aspen Batch.21, Batch.21, BCU
References: None |
Problem Statement: Users starting Microsoft Excel might see a message like the following:
Aspen Process Data Excel Add-In (Title of Message Box)
To ensure that AspenTech Process Data Excel Add-In works properly, it
requires that Excel be closed and restarted manually. Do you want to
exit Excel now?
or
Aspen Production Record Manager Data Retrieval Add-In (Title of Message Box)
To ensure that AspenTech Production Record Manager Excel Add-In
works properly, it requires that Excel be closed and restarted manually.
Do you want to exit Excel now?
What do these messages mean, and why do they appear? | Solution: The new COM add-ins for Excel are marked by the AspenTech installation program to be loaded into Excel but doing so requires Excel to be restarted. These messages should appear the first time Excel starts after the installation is completed but should not appear again after restarting Excel.
Keywords:
References: None |
Problem Statement: The following error message can be returned when configuring batch query criteria in an Aspen Batch.21 web report page.
Invalid batch query criteria
This knowledge base article explains why this error message can be returned. | Solution: This error message is returned when unrealistic batch query criteria are specified in the creation of the web report. In particular, ensure that the batch end time is greater than the start time. If the end time is equal to or earlier than the start time then this error will be returned. The image below shows that this error can be generated when the start time and end time offsets are equal, thus making the start time and end time equal.
Keywords: Advanced
webreport
References: None |
Problem Statement: Strange values appear in some Q plot fields. | Solution: When a data set in Process Explorer has some points equal to NaN (null values in IP.21) one can expect to see unusual values displayed in the following plots:
X-Bar - No errors observed.
Range - No errors observed.
CUSUM - Target displays 1.#R (a nonsense number) in the area above the legend but the correct number appears in the plot Standard Deviation - No errors observed.
EWMA - Target and limit fields display 1/#R (a nonsense numbers) Histogram - Mean, Cp, Cpk, Pp, Ppk, LPC, Std Dev, and UPC fields all display 1.#QNB (a nonsense number)
Keywords:
References: None |
Problem Statement: How do you enter an ad hoc calculation for log in PE? What is the syntax? | Solution: =log(number,base) This answer was found in the Aspen Calc on-line help. The syntax is the same.
It should be noted that some basic ad hoc calculations can be done in PE without having Aspen Calc installed, such as =atcai + 1. However, for more advanced functions, such as log, Aspen Calc must be installed for this function to work.
Keywords: log
References: None |
Problem Statement: This behavior was observed when Process Explorer was being used on a thin client machine in conjunction with Citrix. A newly opened or created trend plot works as expected initially. The timeline may be increased/decreased and scrolled back in time to display the appropriate data. However, after the plot has been left open for a period of time (perhaps 15 minutes or longer), it appears to freeze. Data no longer updates when the timeline is moved or increased/decreased.
After stopping and restarting Process Explorer, the trend plot begins working normally again. | Solution: The customer found that this behavior was resolved after installing a newer version of the Citrix software. In this case, and upgrade to Citrix release 9.0 resolved the problem.
Keywords: citrix
References: None |
Problem Statement: After installing Process Explorer and the Excel Add-In, attempting to use the Excel Add-In produces an error from Aspen Process Data -- Init Automation:
#ERROR: -2147220999
Automation Error
error in the dll
Once you OK this error, the Add-In's dialog box is displayed, but it doesn't work correctly, and anything you select launches this same error. | Solution: This can typically be resolved by registering the file AtProcessDataAuto.dll
Keywords: -2147220999
automation error
References: None |
Problem Statement: Can I use Microsoft SQL Server to backup and purge batch data? | Solution: You should always use the Aspen Production Record Manager administrator to back up and purge batch data because batch data is stored across several tables, and the administrator backs up the data in a logical format before purging the data. This allows you to restore the batch data later if necessary.
Keywords:
References: None |
Problem Statement: When viewing a tag in Process Explorer from a Setcim database, no data is displayed, and the following error is shown in the value field of the legend:
Unexpected error -10, Stop code 5 returned from database | Solution: One cause of this behavior was due to the map record, defined by ATMapDef, associated with the record being viewed had become corrupt. Two possibleSolutions:
1. If there is a test/development server available, load a backup snapshot from the production machine onto the test machine, and save the map record. Then load the record into the production server. You can save and load records using the Setcim utilities: RECSAVE and RECLOAD located in the SETCIMCODE directory.
2. Delete the map record and create it again.
Keywords: Unexpected error -10 code 5 returned from database
Map record
References: None |
Problem Statement: Sometimes users have a file with tags in Aspen Process Explorer linked to a certain Data Source. If this user needs to use the same file but now linked to another Data Source, he must add and change the Data Source within Aspen Process Explorer. | Solution: 1) In this example we are going to change the current Data Source WIN12V87 to WIN-JB7K00KCE6C.
Click on the Process Explorer Option button.
OR
2) Open the tab named ADSA, select the Data Source that you wish, and click Apply. In this case, it will be WIN-JB7K00KCE6C.
3) Go to the Source tab an now chose the Data Source needed.
4) Now select all the tags and right click, go to properties
5) Go to the Source tab, under server, scroll down until you reach your data source. Click Apply followed by OK. In this case WIN-JB7K00KCE6C.
Now all the tags are going to be linked to the new Data Source. This is how you change the Data source of your tags.
Keywords: Aspen Process Explorer
Tags
Change Data Source
References: None |
Problem Statement: When starting unit scheduling, the following error occurs: Failed to start unit scheduling: Invalid batch area. This error appears after deleting an area in the Batch Administrator. | Solution: A defect in the Batch system allows an area to be deleted while it still has units running on the BCU Scheduling table. This results in the error listed above the next time unit scheduling is started because there is a reference on the BCU_UNITS table that references an invalid area in the Areas table. The defect has been addressed for 2006.
To start unit scheduling in this situation, a user will need to access the tables in the Batch database to remove the occurrences related to deleted area.
1. In the AspenBatch database, check the Areas table to get a list of all area_id values.
2. Check the BCU_UNITS table to see if any unit_id values have an area_id that is not listed in the areas table. Get the list of these unit_id values.
3. Check the values in the BCU_TRIGGER_STATUS table to see if there are any entries in the table that have the unit_id values found in step 2. If so, delete these entries in the BCU_UNITS_TABLE.
4. Delete the entries in the BCU_UNITS table found in step 2.
Entries in the BCU_TRIGGER_STATUS table must be deleted before deleting them in the BCU_UNITS table because of a foreign key constraint.
Keywords:
References: None |
Problem Statement: In Aspen Process Explorer, an error message: Query completed with errors may be found in the value field for all tags. This error occurs when Aspen IP.21 Process Browser (previously named Web.21) client components are downloaded onto a machine running Aspen Process Explorer, and the Aspen IP.21 Process Browser components are from more recent version than Aspen Process Explorer. | Solution: Upgrade Aspen Process Explorer to the current version of Aspen IP.21 Process Browser or re-install Aspen Process Explorer. Aspen Process Explorer and Aspen IP.21 Process Browser clients are only able to work on the same machine if they're both at the same version.
NOTE: With reference to current V7.1 IP21 Process Browser (Web.21) installation document (Chapter 2), the following is stated:
Do not download the current version of the Aspen IP.21 Process Browser client onto a computer that has an older version of Aspen Process Explorer installed; doing so may cause Process Explorer trends not to display.
Keywords:
References: None |
Problem Statement: Some customers have dual or multiple monitor configurations. Does Aspen Process Explorer work correctly in conjunction with this type of configuration? | Solution: Yes, Aspen Process Explorer does function correctly when used on a system configured for multiple monitors. There is one caveat though. The Primary monitor must be configured as the top left monitor.
Keywords: monitor
References: None |
Problem Statement: This knowledge base article describes why the following error may occur during the installation of products from the aspenONE DVD set.
Error 1931. The Windows Installer service cannot update the system file C:\winnt\system32\msxml3r.dll because the file is protected by Windows. You may need to update your operating system for this program to work correctly.
This message has been observed with the installation of products in the Aspen Manufacturing Suite and the Aspen Engineering Suite. | Solution: This error is generated by the Windows installer. It means the file
C:\winnt\system32\msxml3r.dll
already exists on this computer and cannot be updated with the version of the same file from the AspenTech installation DVD. Please check with your IT department to determine whether or not this computer has a customized security policy which prevents this file (and possibly other files) from being updated by external programs. Adopting such security policies has become more common lately as IT departments develop more stringent 'locked down' systems which minimize the control a user has over a workstation.
If the installation and post reboot setup process completes without any other errors then the application should function normally, despite the fact that msxml3r.dll was not updated. If any problems persist with the application after the installation has finished please contact the AspenTech support team with the following information:
- Version of msxml3r.dll currently on your computer
- Version of AspenTech software being installed
- AspenTech products being installed
- Windows operating system version & service pack
Keywords: Fail
Install
Error code
Microsoft
References: None |
Problem Statement: This knowledge base article describes how to reference history repeat area occurrences in the Process Explorer ad-hoc calculations. | Solution: Repeat area occurrences can be referenced in ad-hoc calculations as shown in the example below.
={Atcai 1 IP_Trend_Value}
In this example:
Atcai is the tag name
1 is the repeat area occurrence number
IP_Trend_Value is the repeat area field
The curly brackets {} must be used around the entire tag name, occurrence, field name combination in order for Process Explorer to group the occurrence and field name with the tag name.
Note: This only works with history repeat areas. It is not possible to reference a normal repeat area occurrence (such as the output_line field in a QueryDef record) in an ad-hoc calculation.
Keywords:
References: None |
Problem Statement: The following message can be returned from the aspenONE installation when installing on Windows 2003 SP1.
1603: Error installing Windows Installer engine. A file which needs to be replaced may be held in use. Close all applications and try again.
This knowledge base article explains why this message is generated. | Solution: Windows 2003 SP1 includes a newer version of the Windows installer than the aspenONE media distributes. This error is encountered because the installation of the Windows installer from the aspenONE media fails. The reason the Windows installer fails is because there is already a newer version of the installer on the server which came with Windows 2003 SP1. If this error is encountered with Windows 2003 SP1 the error can safely be ignored (click OK then continue with the installation). The Windows installer distributed with Windows 2003 SP1 will work fine with the aspenONE product installation.
Keywords: Win2003
SP1
SP2
References: None |
Problem Statement: Under certain circumstances it is possible for TSK_DBCLOCK to use up to 50% of the CPU time, which could lead your InfoPlus.21 database to become unresponsive or appear to hang. This could occur if, for example, TSK_DBCLOCK was continually kept busy by the timestamp rescheduling configured by the database administrator.
Here is an example of such a situation:
Let's say that the XYZ database has twenty thousand records defined by xyz_analogdef, a custom definition record. Each of these records has three scheduling timestamp fields and three corresponding reschedule interval fields (IP_HIST1_RESCHED_INT, IP_HIST2_RESCHED_INT, IP_HIST3_RESCHED_INT.)
The IP_HIST1_RESCHED_INT field indicates that its corresponding scheduling timestamp (IP_HIST1_SCHED_TIME) should be rescheduled every hour. What if you mistakenly configured IP_HIST1_RESCHED_INT to have one-minute reschedule intervals instead of one-hour intervals?
Here is what would happen:
Let's say that the XYZ database has ten thousand scheduling timestamps configured at one minute reschedule intervals. This means that TSK_DBCLOCK has to activate and reschedule all ten thousand records every minute. The problem is that TSK_DBCLOCK requires more than a minute to process, trigger, and reschedule ten thousand scheduling timestamps. By the time it finishes one pass, it discovers that they all need to be retriggered and rescheduled all over again, ad infinitum. | Solution: InfoPlus.21 really is not intended to handle such a HUGE number of scheduling timestamp fields, regardless of the reschedule interval. This is perhaps 100x the number at a more typical site. The CPU time required to trigger and reschedule a single scheduling timestamp field is roughly proportional to the total number of schedule timestamp fields. The rescheduling of a single timestamp can be CPU intensive when there are large numbers (i.e. more than a few hundred) scheduling timestamps.
TSK_DBCLOCK would keep up without any problem if you reconfigured IP_HIST1_RESCHED_INT to have one-hour reschedule intervals instead of one-minute intervals.
If one minute rescheduling is really required, then perhaps a different mechanism could be used for scheduling the activations of all these records. For example, one record defined by ScheduledActDef could be configured to activate all these records. This might be a nice way to approach the problem if TSK_DBCLOCK is not handling it.
Keywords: 50%
unresponsive
hanging
References: None |
Problem Statement: This knowledge base article explains why a single value entered into an Aspen InfoPlus.21 database record may seem to be able to trigger more than a single alarm state for the database record. | Solution: The way the deadbanding works with the alarm states is that the data value must actually exceed the alarm limit for the alarm state to change. For example, if the alarm limits were configured in the database record as follows:
IP_HIGH_HIGH_LIMIT = 30
IP_HIGH_LIMIT = 20
IP_LOW_LIMIT = 10
IP_LOW_LOW_LIMIT = 0
and if the following data values are then entered into the database record in the following order, the value of 20 may seem to cause two different alarm states.
IP_INPUT_VALUE = 15 --> IP_ALARM_STATE = OK
IP_INPUT_VALUE = 20 --> IP_ALARM_STATE = OK
IP_INPUT_VALUE = 25 --> IP_ALARM_STATE = HIGH
IP_INPUT_VALUE = 20 --> IP_ALARM_STATE = HIGH
If the value is initially 15 (OK) and the value 20 is then typed in, the alarm state won't actually change to High because the IP_HIGH_LIMIT of 20 has not been exceeded. In order for the High alarm to be activated a value in excess of 20 (ie. 20.01) must be entered.
The same applies when changing from a high alarm state back to an OK state. The value in IP_HIGH_LIMIT (20) must be crossed again for the alarm state to change. This means that a value below 20 (ie. 19.99) must be entered for the alarm state to change back to OK.
Keywords: cross
pass
boundary
References: None |
Problem Statement: Aspen MES cluster is a redundancy | Solution: offered by AspenTech. While adding a cluster, you may receive the error:
Failed to open cluster <CLUSTER NAME>.Could not contact the specified cluster.
Followed by the error message:
Retrieving the COM class factory for component with CLSID {F2E~...}failed due to the error:80040154.Solution
AspenTech’s MES redundancySolution is based on Microsoft’s Failover Cluster feature,therefore a cluster must exist before enrolling an Aspen MES server application.
The computers hosting the clusters must meet the minimum requirements which involves enabling the Microsoft's Failover Cluster feature.
The Failover Cluster Feature is available with Windows Server 2008 R2 and above.
Follow the steps mentioned below to enable clustering.The steps mentioned are for Windows Server 2012
1. Log onto the first VM that will become a cluster node, then launch the Server Manager.
2. Select Dashboard from the left panel, then click Add other servers to manage.
3. Specify the name of the second VM and click Find Now. After the computer appears in the lower panel, click the right arrow to add it to the list of managed servers, and then click OK to finish.
4. From the dashboard, click Add roles and features, click Next, then select Role-based or feature-based installation, and then click Next.
5. Select Select a server from the server pool, then select the first VM in the list, and then click Next.
6. Click Next to skip roles, then enable Failover Clustering.
7. Click Add Features when prompted to add additional features.
8. Under the Remote Server Administration Tools feature, enable both the Failover Cluster Automation Server, and the Failover Cluster Command Interface options.
9. Enable the check box to restart the destination server automatically, then answer yes to confirm.
10. Perform the same steps to add the cluster feature to the other VM. Since we added that VM into the server pool, the feature can be added without leaving the current VM.
11. Click Add Roles and Features, follow the wizard, but instead select the second VM from the sever pool list, skip roles, select Failover Cluster feature, then add the additional remote administration options, then click Install, and then click Close.
12. Create snapshots of the two VM's at this point (if you want).
With this, the VM's are ready to be enrolled as clusters
Keywords: Failed to open cluster
Clustering
80040154
References: None |
Problem Statement: You may want to load on a production Aspen InfoPlus.21 system some custom records developed on a test Aspen InfoPlus.21 system. Rather than exporting a snapshot, which will overwrite the production database when being loaded there, you would prefer to export a list of specific records.
Is there a simple way to pick a group of records and extract them all to a single RLD file? | Solution: Yes, this is possible. In the Aspen InfoPlus.21 Administrator right-click on the database object and select Save Records from the context menu. In the GUI, select Find and the Aspen InfoPlus.21 record finder will appear. Query the records you like and drag and drop them to the Save Records window. Then save it in one file.
Keep in mind that customized definition records and their customized fields need to be saved as well. On the destination machine, save your snapshot before attempting to load your RLD file, in case there are errors or problems. Then do a test load to see if the RLD file loads successfully.
Refer toSolution # 106305 for information on the range of hexadecimal numbers that should be used when creating a custom definition record.
Keywords: recload
recsave
.rld
save records
find records
export
References: None |
Problem Statement: While trying to install AMS software, the user has a logon failure and cannot complete the installation. | Solution: When performing an AMS install, the account being used to install the software must be a member of the local administrator''s group. The reason for this is that the administrators group has particular user rights and policies that allow the appropriate permission for the activities required during an installation. If for some reason the user rights and policies of the local administrator''s group have been changed, a user may encounter a logon failure during the install.
To ensure the proper user rights assignment on a Windows 2000 machine:
Go
to Start | Settings | Control Panel | Administrative Tools | Local Security
Policy
Expand ''Local Policies''
Click on ''User Rights Assignment''
Check that the following Local Settings and Effective Settings specify the Administrator account (or an account that belongs to the Administrator''s group):
-- Access this computer from the network''
-- Log on as a service
-- Log on locally
To ensure the proper user rights assignment on a Windows NT machine:
Go to Start | Programs | Administrative Tools | User Manager
Select the Policies menu item, and the User Rights sub item
Check that the following User Rights specify the Administrator account (or an account that belongs to the Administrator''s group):
-- Access this computer from the network''
-- Log on as a service
-- Log on locally
Keywords: network logon failure
invalid account
References: None |
Problem Statement: InfoPlus.21 cumulative patch V7.3.0.3 provided a basic application that allowed the user to relocate the InfoPlus.21 folder locations (Defect ID: CQ00461057). IP21ProfileConfiguration could redefine the InfoPlus.21 Data Root folder and some additional child folders by creating the IP21Profiles.xml file.
This handy application is not installed in any other version of InfoPlus.21. You will not find it anywhere in V8.0, V8.4, V8.5 etc. | Solution: Since V8.0, the new InfoPlus.21 Server System Profiles Manager has completely replaced IP21ProfileConfiguration. It offers much improved functionality as listed below:
An InfoPlus.21 system profile specifies the location of certain InfoPlus.21 folders that hold configuration files: history system files, SQLplus query files, Cim-IO definition files, InfoPlus.21 group files (i.e., group200 folder). A profile also persists other configuration settings such as the defined task list and access control.
For example, you might want one InfoPlus.21 system profile for the InfoPlus.21 demo system and another profile for the production system. On startup, the InfoPlus.21 server will work with whichever profile is active.
Or you might need to move the InfoPlus.21 system folder, like group200, to another disk. Simply moving the folder using Windows Explorer will not work because InfoPlus.21 will not know about their new locations.
The InfoPlus.21 Server System Profiles Manager provides this capability and can be invoked from the Actions menu of the Aspen InfoPlus.21 Manager. Detailed instructions are included in the Aspen InfoPlus.21 Administration Tools Help.
Keywords: InfoPlus.21 Profile Configuration application
IP21ProfileConfiguration.exe
IP21ProfileConfiguration missing
IP21ProfileConfiguration not found
Where is IP21ProfileConfiguration?
References: None |
Problem Statement: The following error(s) may be received when attempting to install and application that requires the use of IEWebControls on a Windows Vista client.
Error 1: There was a problem with installing IEWebControls. The error return Code was 1603. Installation cannot proceed
Error 2: The specified path http://Nodename/Webctrl_client folder is unavailable. The Internet Information Server might not be running or the path exists and is redirected to another machine. | Solution: The Vista Metabase Compatibility component of IIS 7 must be installed on the server where Aspen Online will be installed. ** This component is not installed by default.**
To install the compatibility component
1. Open the Programs & Features page from the Windows Control Panel
2. Select Turn Windows Features On or Off
3. Then Select Internet Information Services > Web Management Tools > IIS 6 Management Compatibility > IIS Metabase and IIS 6 Configuration Compatibility.
Keywords: Error Code 1603;
Aspen Online;
IEWebControls;
IEWebControls.msi;
IEWebControls.exe;
References: None |
Problem Statement: How to load a Visual Basic (VB) combo box with the content of a selector record''s repeat area? | Solution: This can be accomplished two different ways:
The first example is as follows:
If you create a VIEWDEF that contains the Select_description fields. Example: create view prod_name as select select_description from product names;
The code that will get the contents of the view query into an ADO recordset and then populate a listbox name List1 with the results is as follows:
Note: The Microsoft ADO library will have to be added to the project for this to work.
Dim adoCon As New ADODB.Connection
Dim adoRecords As ADODB.Recordset
adoCon.Open (SQLplus on localhost)
Set adoRecords = adoCon.Execute(Select * from PROD_NAME) Do While Not adoRecords.EOF
List1.AddItem adoRecords!SELECT_DESCRIPTION
adoRecords.MoveNext
Loop
In the second example, the view is not necessary. The contents of the selector record''s repeat area is available using the recordname.1 syntax as follows: Select * from productnames.1; So the VB could be the following:
Dim adoCon As New ADODB.Connection
Dim adoRecords As ADODB.Recordset
adoCon.Open (SQLplus on localhost)
Set adoRecords = adoCon.Execute(Select * from productnames.1) Do While Not adoRecords.EOF
List1.AddItem adoRecords!SELECT_DESCRIPTION
adoRecords.MoveNext
Loop
Keywords: combo box
repeat area
References: None |
Problem Statement: When Aspen OnLine recovers from a previous failure, it only starts up steady state detection, but not the engine , why? | Solution: The watchdog program monitors the steady-state program and the optimization program. If it detects a problem with either program, it sets the Aspen OnLine Status signal (APOSTAT) to a value as a notification that a problem has occurred. If the Restart on Failure signal (RESTART) is set to 1, the watchdog program will automatically restart the optimization program when a failure occurs. It always restarts the steady-state program when it fails.
Keywords: Restart, failure, recover, watch dog, watch, engine
References: None |
Problem Statement: A spreadsheet using the Excel add-in feature is created and put on a shared directory for all to use. Each user has their own PC with permissions to read and write into the shared directory. However, when a user attempts to access the spreadsheet, the spreadsheet is unable to retrieve and display the data. The add-in is not retrieving Batch or Process data.
A Microsoft Excel dialog box opens stating:
The workbook you opened contains automatic links to information in another workbook. Do you want to update this workbook with changes made to the other workbook?
Selecting Yes to the question leads to the error messages as follows:
Microsoft Excel cannot find 'Retrieve Duration' on 'AtBatch.xla' Microsoft Excel cannot find 'GetBatchHandles' on 'AtBatch.xla'
Selecting No allows you to open the spreadsheet, but the data is absent.
Note: Error includes AtBatch.xla or AtData.xla depending on whether Batch or Process data.
This problem occurs when the machine attempting to access the spreadsheet does not retrieve the *.xla file from the same location as the machine which created the spreadsheet. | Solution: Verify that the location of the .xla files are identical on all machines. Then, based upon which location the spreadsheet is using, re-select the .xla file to be used by Excel Add-In. If you select a cell that should contain data, the path to this *.xla file is displayed in the formula box.
I. The paths must be identical on all the machines. The path is: <drive letter>:\Program Files\Microsoft Office\Office\Library
II. (1) Open a new spreadsheet
i. Select Tools > Add-Ins
ii. De-select Aspen Batch
iii. Click OK
iv. Close Excel.
2. Open a new spreadsheet
i. Select Tools > Add-Ins
ii. Select Browse, find the *.xla file that the spreadsheet was searching for. For example, C:\Program Files\AspenTech\Desktop\AtBatch.xla
iii. Dialog box appears with Do you want to replace...., choose YES.
3. The Add-in dialog box should now have Aspen Batch selected.
i. Click OK
ii. Exit Excel
4. Now open the spreadsheet.
Keywords: Excel add-in
shared
batch.21
process data
Process Data Add-in
Microsoft Excel
References: None |
Problem Statement: User cannot get a steady state report when user clicks on the Report button. They get a message ssd status.txt does not exist. | Solution: There is a Signal Tag (Signal named SigSSPrint, default tag named SSDPRT) which controls whether the SSD report file is generated. The normal value of this tag is 1, meaning yes, write the SSD report file each time the SSD program executes (normally once per minute). Pushing the button on the ControlPanel just opens the file and displays the results in some GUI forms, and if the file doesn't exist then you will get the message The value of the Signal Tag which should be set to 1 will make it work as expected.
Keywords: steady state report, ssd status.txt
References: None |
Problem Statement: The log file BcuAdministrator.ApplicationInterface.svc_mes.log has been seen on a few occasions to contain messages to the effect of:
(26424) 01/30/2006 15:44:37.419 CBatchRegistry::OpenKey: E_FAIL
for no specific reason. This knowledge base article describes the severity of these messages. | Solution: This message indicates that one of the Aspen Batch.21 Application Programming Interface (API) calls tried to access a key in the registry which could not be located. Although this message is logged as an error (E_FAIL indicates an error) this message is not critical and can be ignored if no other problems are noticed on the system. This message will be reduced from an error message to a warning message in a future release.
Keywords: Error
Failure
System
Access
References: None |
Problem Statement: In SQL Server 7.0, problems surrounding object ownership can arise from a login being added to the sysadmin fixed server role. | Solution: This information is pertinent to Event.21 & Batch.21 troubleshooting when receiving an error like:
Msg 208, Level 16, State 1
Server ''MOVER'', Line 1
Invalid object name ''event_db..b21_batch_area_rel''.
In SQL Server 7.0, objects are referred to by the following syntax:
servername.databasename.owner.objectname
Servername can be omitted and the current server is assumed. Databasename can also be omitted and the current database is assumed. It is normal programming convention to refer to an object as
databasename..objectname
When omitting the owner name, the normal course of events is that SQL Server tries to locate an object matching the current user as the owner, and if unsuccessful, it tries dbo as the owner. For example, a reference to event_db..event21 by the user aspen first resolves to event_db.aspen.event21. If it fails to find a match, SQL Server will next look for event_db.dbo.event21.
This sequence of mapping occurs even in cases where the user aspen is a member of the db_owner role. Objects owned/created by aspen are not addressed by databasename.dbo.objectname, but instead by databasename.aspen.objectname.
This changes, however, if the login (a login is different than a user in SQL Server speak) for the aspen user is associated with the sysadmin fixed server role. In this case, as far as the database is concerned, the user is always known as dbo and never aspen. Thus, in the example above, event_db..event21 is resolved straight to event_db.dbo.event21 and never as event_db.aspen.event21.
The significance is that the Batch.21 installation scripts that create the tables in SQL Server default to the user aspen owning the tables. If, subsequent to Batch.21 installation, the login for the user aspen is added to the sysadmin role, the tables in the database will appear to be missing when using the syntax of databasename..objectname.
There are two ways to resolve this.
Remove the login from the sysadmin role.
Change the object owner to dbo from aspen by using the stored procedure sp_changeobjectowner. An example of this command is:
sp_changeobjectowner ''aspen.event21'', ''dbo''
If you do not know what your user name is for a given database, simply log in, then issue the following command to SQL Server (from Query Analyzer, etc.) while working within that database:
select user_name()
It is also worthwhile noting that the On-Line Books for SQL Server describe different circumstances, but this has been logged as a bug in the documentation.
You can refer to MSKB Article Q226488 and MS Bug # 55136 (SQLBUG_70)
Keywords: SQL
SQL Server
MS SQL Server
Batch
Batch.21
Batch Errors
References: None |
Problem Statement: Encounter errors when using Aspen Batch.21 API function ImportBatchDataXML in Aspen SQLplus due to XML containing escape characters such as '<', '>', '&', etc. | Solution: Escaped characters MUST be escaped using either numeric character references or the strings such as < and >. Below is a list of the strings for characters that need to be escaped.
Escape character
Replacement String
<
<
less than
>
>
greater than
&
&
ampersand
'
'
apostrophe
"
quotation mark
Keywords: ImportBatchDataXML
SQL
XML
escape character
greater than
less than
ampersand
apostrophe
quotation mark
single quote
double quote
References: None |
Problem Statement: Is there a Batch.21 interface that can read BatchML format? If not, is there any other possible way to import batch data from DCS ABB Batch for 800XA like it was possible for ABB DigiBatch with the OpenBatch Interface? | Solution: Aspentech does not have an interface with this capability and it is not currently on the Development roadmap.
However we do support BPD documents transmitted on the TIBCO Infobus. This is S95 compliant.
Also, depending on the format it might be possible to write a custom XSL file to transform the content to Batch.21 XML.
Keywords: BatchML
IMPORT
EXPORT
FORMATS
References: None |
Problem Statement: When opening an Excel spreadsheet with Process Data Add-In data on the sheet, Excel asks to Update the link path. | Solution: Hiding or protecting data on the spreadsheet can cause this problem. Unhiding and unprotecting these values should solved the problem.
Keywords:
References: None |
Problem Statement: When you open or create an Event.21 plot in Aspen Process Explorer, you get following error: Unable to initialize event system: warning(0) sql code(0) | Solution: This error can be caused when you have added the wrong ADSA Service Component to the ADSA data source. For Event.21, you should add Aspen Event.21 Data (.Net Events)
Keywords:
References: None |
Problem Statement: How do I prevent the error message Failed to create object. OLE error: Class not registered when opening a real-time SPC plot in Aspen Process Explorer? | Solution: Make sure that you have installed the Real-time SPC component. If you do not see this directory on your machine:
32bit systems: Drive:\Program Files\AspenTech\APEx\Q
64bit systems: Drive:\Program Files (x86)\AspenTech\APEx\Q
it means that you don't have the Real-time SPC component installed. In this case, you should run the installation again, selecting Modify. Then, under Aspen Process Explorer select Real-time SPC.
If you do see this folder in your machine and you still have the issue, re-register AtSPCControls.ocx located in the above directory:
1. Click on Start | Run and type cmd. Hit Enter
2. Navigate to Drive:\Program Files\AspenTech\APEx\Q\ by typing the command:
32bit systems: cd Drive:\Program Files\AspenTech\APEx\Q
64bit systems: cd Drive:\Program Files (x86)\AspenTech\APEx\Q
where Drive is the installation drive (usually C)
3. Unregister the ocx file: regsvr32 /u AtSPCControls.ocx
4. Re-register the ocx file: regsvr32 AtSPCControls.ocx
This should resolve the problem.
Keywords:
References: None |
Problem Statement: Selecting an APEx short cut icon on the desktop produces the following error:
Cannot find the file 'C:\Documents and Settings\..\Desktop\XXXXX.apx' (or one of its components). Make sure the path and filename are correct and that all required libraries are available. | Solution: Recent code changes fixed this behavior, but it appears that it can occur unexpectedly. This error occurs when the information in one or more of the Use DDE settings in the windows file type associations has become corrupt.
APEX attempts to fix such errors automatically at startup by registering all its file types. But in some cases, it may become necessary to fix this problem manually.
To do so (Windows 2000):
1. Double-click My Computer.
2. On the Tools menu, click Folder Options.
3. Click the File Types tab.
4. Click on the File Types column header to sort by file type.
5. Locate all the Aspen Process Explorer extensions. The current file extensions are: APX, ATGCS, ATGRAPHIC, ATPLOT, MVA, ATVBA, APWS, ATWORKSPACE.
6. Select one of the extensions, and examine it as follows:
o Click the Advanced button. There should be one action, the open action. Select it.
o Click the Edit... button.
o Verify the Application used to perform action: text box contains the correct path to ProcessExplorer. This should be in the short filename format. For example, C:\PROGRA~1\ASPENT~1\APEx\Pe\PROCES~2.EXE %1
o If the Use DDE checkbox is unchecked, check it by clicking it.
o Verify the DDE Message: text box contains the following: [open(%1)]
o The Application: and Topic: text fields will be filled automatically upon closing this dialog.
o Select OK, OK, and Close to close out the dialogs and save changes.
7. Repeat step 6 for all extensions as necessary.
Keywords: Cannot find the file
InfoPlus21
Process Explorer
components
References: None |
Problem Statement: How can you display a current value on a VBForm in Process Explorer (APEx)? | Solution: The attached Aspen Process Explorer VBForm includes the example code to display the time and value of one tag using process data. When you first open the form it will complain about the data source name. Change the tag name and data source name and save the APEx document for use with your system.
Keywords:
References: None |
Problem Statement: A message like the following appears when trying to apply a patch for Batch.21:
<long string> is not installed ProductState returned is -1
An example of this message would be the following:
{E85B786E-7A76-48D3-9A66-27DF1F46055A} is not installed. ProductState returned -1
Even though Batch.21 is supposed to be installed it does not appear in 'Add or Remove Programs'. Users may encounter problems with subsequent attempts to remove Batch.21 or to install it over-the-top. Some of those attempts may produce errors like the following:
Internal Error 2753. Batch21Services.exe | Solution: One may wish to use the 'Windows Installer Cleanup Utility' which was created by Microsoft. Information about it can be found here:
http://support.microsoft.com/kb/290301/
The website includes this caveat:
Warning: The Windows Installer CleanUp Utility is provided as is to help resolve installation problems for programs that use Microsoft Windows Installer. If you use this utility, you may have to reinstall other programs. Caution is advised.
After running the utility one may need to remove the corresponding service-related entries from the Windows registry and possibly reboot before attempting subsequent reinstallations.
Keywords: None
References: None |
Problem Statement: This knowledge base article explains why the following installation error can occur:
path...\prop in:[Main] validation: Validation code failure
Note that path... can be any path on the CD or DVD drive. | Solution: This problem is usually the result of a dirty, scratched or defective installation CD or DVD. If this error occurs try the following:
Wipe off the bottom of the CD or DVD.
Check the bottom of the CD or DVD for scratches.
Reboot the machine then attempt the installation again.
If cleaning the CD or DVD and rebooting do not resolve the problem, please request new installation media by accessing the Upgrades / License request page from the AspenTech Support Web site. Note in the request that this is s replacement key. Here is a link:
http://support.aspentech.com/webteamasp/My/FrameDef.asp?/webteamasp/LicenseKeys.asp
Keywords: DVD
reinstall
References: None |
Problem Statement: The Fill Background field in a Process Explorer Process Graphics Data Field is checked and grayed out and cannot be changed. | Solution: The ability to un-check this field for data field objects in a Process Graphic was deprecated in version 5.0.1. There were problems associated with frequent updates of this field. The fix was to permanently disable it. The check box was not removed from the properties dialog because it is still functional for Text fill backgrounds.
Keywords: fill background, Process Graphics, check box, background, data field
References: None |
Problem Statement: This knowledge base article describes why the following error may occur during the installation of products from the aspenONE DVD set.
Error 1931. The Windows Installer service cannot update the system file C:\winnt\system32\msxml3r.dll because the file is protected by Windows. You may need to update your operating system for this program to work correctly.
This message has been observed with the installation of products in the Aspen Manufacturing Suite and the Aspen Engineering Suite. | Solution: This error is generated by the Windows installer. It means the file
C:\winnt\system32\msxml3r.dll
already exists on this computer and cannot be updated with the version of the same file from the AspenTech installation DVD. Please check with your IT department to determine whether or not this computer has a customized security policy which prevents this file (and possibly other files) from being updated by external programs. Adopting such security policies has become more common lately as IT departments develop more stringent 'locked down' systems which minimize the control a user has over a workstation.
If the installation and post reboot setup process completes without any other errors then the application should function normally, despite the fact that msxml3r.dll was not updated. If any problems persist with the application after the installation has finished please contact the AspenTech support team with the following information:
- Version of msxml3r.dll currently on your computer
- Version of AspenTech software being installed
- AspenTech products being installed
- Windows operating system version & service pack
Keywords: Fail
Install
Error code
Microsoft
References: None |
Problem Statement: This knowledge base article describes how to reference history repeat area occurrences in the Process Explorer ad-hoc calculations. | Solution: Repeat area occurrences can be referenced in ad-hoc calculations as shown in the example below.
={Atcai 1 IP_Trend_Value}
In this example:
Atcai is the tag name
1 is the repeat area occurrence number
IP_Trend_Value is the repeat area field
The curly brackets {} must be used around the entire tag name, occurrence, field name combination in order for Process Explorer to group the occurrence and field name with the tag name.
Note: This only works with history repeat areas. It is not possible to reference a normal repeat area occurrence (such as the output_line field in a QueryDef record) in an ad-hoc calculation.
Keywords:
References: None |
Problem Statement: Some customers have a programming need to utilize a user's default time span setting. Where is this information stored? | Solution: A user's default time span setting is stored in the following registry key.
HKEY_CURRENT_USER\Software\AspenTech\AtTime\Settings
The string name for the setting is DefaultSpan.
Keywords: time
span
default
References: None |
Problem Statement: Neither * nor ? have wildcard functionality when searching RDBMS tags in v5. | Solution: As a workaround, use:
_ as a one-character replacement wildcard.
% as a wildcard for a string of characters.
Functionality of * and ? as wildcards has been restored in v6.0.1.
Keywords: wild
card
References: None |
Problem Statement: The AtProcessDataAuto library, though not documented, is visible to programmers as a library:
with a number of available object as shown below:
A question on documentation, or lack of, will often arise. | Solution: Unfortunately the AtProcessDataAuto objects are not fully supported for custom implementation. The only supported automation interface objects are those documented in the 'Automation Interfaces' section of the Process Explorer Help files.
Objects documented there are fully supported and have commitments from Development that they will function correctly from version to version. The undocumented objects (e.g. AggregatedData) have no such assurances and may change from version to version (or stop working altogether) and are therefore not supported for customer use.
Keywords: ProcessData
ProcessDataFunctions
automation interface
References: None |
Problem Statement: When Launching Aspen Process Explorer the following error pop up:
Security Initialization Error:
Could not locate Authorization. IPFWAuthorization in registry | Solution: This problem is either caused by a bad installation or network issues. To troubleshoot, check:
1. When installing APEX, make sure you login using an Administrative account. If not, re-install
2. Check that you have the following path in your registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Authorization.IPFWAuthorization
If not, you might have problems writing to the registry. Make sure the account used to install has privileges to write to the registry and re-install.
34. Open AFW Tools at Start | Programs | Aspentech, and make sure you are pointing to the correct Security Server (URL). It should be set as follow: http://<security_server_name>/AspenTech/AFW/Security/pfwauthz.asp, where <security_server_name> is the nodename or IP address of your security server.
4. Re-register authorization.dll located in <drive>:\Program Files\Aspentech\BPE\ directory
5. If none of the 4 options help, check the psetup.log file from the c:\windows directory and send this file to Support.
Keywords: IPFWAuthorization
Security initialization error
References: None |
Problem Statement: When attempting to connect an AspenTech client application to an Aspen InfoPlus.21 server (such as plotting a tag in Aspen Process Explorer), the user may encounter the error message
Connection Failure is Fatal | Solution: The errror message Connection Failure is Fatal could mean that (1) the client machine is unable to locate the Aspen InfoPlus.21 server on the network; or (2) Aspen InfoPlus.21 security access denial.
Troubleshooting steps for (1) the client application (such as Aspen Process Explorer) is unable to locate the Aspen InfoPlus.21 server on the network.
1. Stopping and restarting task TSK_APEX_SERVER from the Aspen InfoPlus.21 Manager solved the problem in some cases.
Note: Make sure that the task TSK_APEX_SERVER has the argument '-v3' in the Command Line Parameters line in the Aspen InfoPlus.21 Manager program.
2. Stopping and restarting Aspen InfoPlus.21 solved the problem in other cases.
3. Try to ping the Aspen InfoPlus.21 server from the client PC. If you can't ping the server, you will not be able to retrieve data from the Aspen InfoPlus.21 database. If this is the case, check with your network administrator to resolve this problem.
4. Check if the client PC can resolve the nodename of the Aspen InfoPlus.21 server into the correct IP address, by doing a reverse lookup. Please refer to Knowledge Base article 107955 for a detailed discussion on reverse lookup.
5. If you get the same error on the Aspen InfoPlus.21 server, then the problem is likely the ADSA data source configuration. Open the ADSA Client Config Tool and check the ADSA configuration for the data source in question. Make sure that both the Aspen DA for IP21 and Aspen Process Data (IP21) components are added and the Host Name for Aspen DA for IP21 component is pointing to the correct nodename. Restart the Aspen Data Source Directory service after making any changes. Also, restart the IIS service, which will also restart the Aspen Registry Security Server.
6. If you are using a public data source, check the ADSA configuration on the ADSA server. Make sure that the components Aspen DA for IP21 and Aspen Process Data (IP.21) are added, and point to the correct node name.
7. If only some client PCs are affected, please check the following on the affected client PCs:
a. If you are using a user defined data source, check the ADSA data source configuration. Make sure that both the Aspen DA for IP21 and Aspen Process Data (IP21) components are added, and the Host Name for Aspen DA for IP21 component is pointing to the correct nodename.
b. If you are using a user defined data source, try entering the server's IP Address into Aspen DA for (IP.21) instead of the server name. Restart the Aspen Data Source Directory service after making any changes.
c. Add the Aspen InfoPlus.21 server's nodename and IP Address to the client Hosts file, and add the client PC's nodename and IP address to the server Hosts file. Reboot both computers for the change to be recognized. If the connection subsequently works this points to a name reSolution problem on the network.
d. If database security is implemented, explicitly add the user names of all affected client users to the correct role in the AFW Security Manager. Restart the Aspen Registry Security Server service after making any changes.
e. Remove and re-create the ADSA data source to the Aspen InfoPlus.21 server.
f. Remove and re-create the client system ADSA cache, see AspenTech'sSolution 115104 for instructions to do this.
g. If running Aspen Process Explorer on Windows XP with SP2 Windows XP firewall is turned off. Any third party firewalls should be disabled as well.
h. Remove the user from the Windows Active Directory group, add the user back in, and then stop and restart the Aspen Registry Security Server service.
8. Again, if only specific client PCs encounter this problem, try the following:
a. Compare the network adapter settings between the working client PCs and the non-working client PCs. Ensure that all network adapter settings are the same.
b. Open a DOS command window then issue the command ipconfig/all on each client PC. Ensure that all of the network settings shown by the ipconfig command are the same between the working and non-working client PCs.
c. Swap the network cables between the working and non-working client PCs. This error has been observed to occur due to faulty network cables.
Troubleshooting steps for (2) InfoPlus.21 security denial.
1. On the remote machine, run a simple query (e.g. SELECT * FROM ATCL101) for the same tag that Process Explorer returned the 'Connection failure is fatal' error.
2. The SQLplus will return the error 'Error reading definition record (ID=XXX) fixed fields: Access Denied...'.
3. Check the Infoplus.21 database/record permission. Ensure that the user's role has the necessary permission.
Keywords: Connection failure is fatal
Connection failure
reverse lookup
fatal
nslookup
References: None |
Problem Statement: Why do I see SLM_InfoPlus21_Points in Value column of Aspen Process Explorer? | Solution: ThisSolution is relevant when there are more than one InfoPlus.21 server pointing to one license server.
Use the WlmAdmin tool to check the total number of InfoPlus.21 pointing to the license server. The total points consumed should not exceed the entitled consumable points. If it exceed the entitled points, use the Aspen InfoPlus.21 Administrator to reduce the maximum point count.
Keywords: WlmAdmin
License Server
Points
InfoPlus.21
References: None |
Problem Statement: What URL does the Aspen Production Record manager Web Reports use in a Cluster environment?
In a cluster environment you will have two servers for example Node 1 and Node 2. | Solution: If you are in a cluster environment you will have a cluster name for the two servers.
For example if you cluster name is APRMServer then use the URL
http://APRMServer/batch21/pages/reporting/reporting.aspx
Keywords: Cluster
APRM
Batch21
Batch.21
Aspen Production Record Manager
Reports
Web Reports
References: None |
Problem Statement: Many of the icons on the top bar in Aspen Process Explorer appear faded and are not clickable. | Solution: If the Trend Plot option appears grayed out and not clickable, along with many other icons in Aspen Process Explorer, like in the figure below, it means that the application is not granting any permissions to access data.
The first thing to check if the security settings in the AFW security manager are defined as mentioned inSolution 113184.
If the error still persists, open the AFW Tools application as an administrator on the local computer having the issue. Scroll to the bottom under the tab Client Registry Entires and double-click UseServerADSI. Change the value in the Data field from 0 to 1. Press OK to close out of the UseServerADSI box and press OK again to close out of the AFW Tools application. Close and reopen Aspen Process Explorer. The trend plot and other buttons should now be available.
Keywords: Process Explorer
buttons grayed out
References: None |
Problem Statement: This knowledge base article provides suggestions to resolve the following error message, which can be generated by Aspen Process Explorer.
Error 1324. The path Program Files contains an invalid character | Solution: ? Make sure that when you type
C:\Progra~1
into Windows Explorer you are taken to
C:\Program Files
? Ensure that the path to Program Files that you are attempting to access is on your local machine. If the path points to Program Files on a remote machine ensure that the path is properly shared and mapped to your local machine. If the path points to a cluster, ensure that the cluster machine you are trying to access is running and active.
? Make sure that the user account name does not contain any special characters (such as /, -, *) in the name. If it does, then try to login (and possibly re-install) under a different user account that does not have special characters in the user name. Microsoft eludes to this in the following article, although it was written for Windows NT4.0:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q247366&ID=KB;EN-US;Q247366
? Try to use English-US as the language in Regional Settings.
Keywords: ProgramFiles
d:\progra~1
References: None |
Problem Statement: Inserting old data into Aspen InfoPlus.21 (IP.21) using the Aspen Process Data Add-In for Excel, returns Result -50008 | Solution: This error result translates to the following message:
Unable to write to the tag specified. Verify the time range.
The most common cause of this error is the PAST parameter of the tag's repository not allowing such old data.
Check Knowledge BaseSolution ID 112998 (What is the maximum value of the PAST parameter for history repositories?) for instructions on changing this parameter as well as details about the maximum setting.
Even if the repository PAST parameter is sufficient to allow the old data, it is possible that the data is older than the creation date of the tag record within the Aspen InfoPlus.21 database. In this case, the XOLDESTOK function must be used to allow the data insertion for the particular tag. See Knowledge BaseSolution ID 103040 (How to insert data older than creation time of a record; how to use XOLDESTOK.) for information regarding this function.
Keywords: 50008
PAST parameter
XOLDESTOK
References: None |
Problem Statement: This knowledge base article explains why the scheduling table in the Aspen BCU Administrator can show negative timer intervals. | Solution: A Negative number in the Aspen BCU Administrator's Scheduling Table means that the unit processing has taken longer than the Processing Cycle time. This usually just means that the Processing Cycle time is too short for the amount of data which needs to be processed. However, it could imply that another application is using excessive amounts of computer resources, thereby not giving the Aspen Batch.21 processes enough CPU time. If your timer intervals go negative frequently you may want to consider increasing the processing interval.
If you do not wish to change your Processing Cycle interval, or if changing the Processing Cycle interval does not correct the negative timer values then try the following suggestions.
1. If you have a lot of logging options configured in the Aspen BCU Administrator then remove all logging flags which are not needed. Writing large amounts of text data to disk can waste CPU resources.
2. Restart Aspen InfoPlus.21. This has caused the timer intervals to return to positive values in many cases.
3. If restarting Aspen InfoPlus.21 does not resolve the problem then restart the Aspen Batch.21 Service, the Aspen Batch.21 BCU Service and then restart Unit Scheduling.
4. If neither suggestion above causes the timer intervals to change to a positive value then try the steps below.
a) Make sure that Aspen InfoPlus.21 is currently receiving timely data. Check to be sure that any Store and Forward processing has finished.
b) In the Aspen Batch.21 BCU Administrator stop the unit processing and delete the scripts from the Scheduling Table. Next purge the batches that have been processed since the upset occurred. Also, delete any batches in the Recent Batches Cache.
c) Restart the Aspen Batch.21 service and the Aspen Batch.21 BCU Service.
4) Re-load the scripts with a start time around the time of the upset.
Keywords: Re-start
pos
neg
References: None |
Problem Statement: Can Aspen Process Explorer plots and/or graphics run or be displayed on a Blackberry or PDA? | Solution: Using the standard Aspen Process Explorer plots and graphics, these cannot be displayed on a Blackberry or PDA.
Trend plots and graphics can be displayed on a Blackberry or PDA using the Web.21 PIE (Personal Internet Explorer) module. This module is part of the Aspen Operations Manager-Role Based Visualization product.
Keywords:
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.