question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: When dragging an I/O device name to the Cim-IO object in the IP.21 Administrator tool, this error is returned:
RDBVALS invalid field type. | Solution: This error occurs because there is another record in the database with the same name as the device been dragged. Either change the device name or rename the existing record.
Keywords: I/O
dragged
References: None |
Problem Statement: How to resolve differences between different conversions.atc files, or merge files to have a combined conversions.atc file. | Solution: The .dtx files are from Aspen Calc Version 2.5.1 or earlier. The .atc files are from Aspen Calc Version 2.5.2 or later.
In Aspen Calc Version 4.0 or later, you can export engineering units to an XML file (using the 'Export Unit XML' right click menu option on the server in the calculation tree). You can then import this file into another system (using the 'Import XML' right click menu option). This import will merge the units in the file with the currently defined units.
If the customer is not running Aspen Calc Version 4.0 or later, they could copy the .atc files to an Aspen Calc Version 4.0 computer, merge them using the XML export/import and then copy the merged file back to a Version 2.5.2 or later system.
Keywords: Merge
Combine
Calc
References: None |
Problem Statement: When configuring multiple Aspen Cim-IO redundancy devices, not all primary and secondary devices are recognized. | Solution: There is an operating system limitation that limits the number of devices that can be configured in any one process due to the number of TCP/IP sockets that a process can open. If configuring Aspen Cim-IO redundancy with multiple devices it may be necessary to create more than one TSK_Detect task IE: TSK_Detect2, TSK_Detect3 and split the devices over the additional tasks. Additional TSK_Detect records can be created simply by copying the existing record in the Aspen InfoPlus.21 Administrator. Additional TSK_Detect tasks can be created simply by copying the existing task in the Aspen InfoPlus.21 Manager.
Note: tests indicate that defining over 7 devices in any one TSK_Detect task will cause this problem. However, because this limitation is controlled by the operating system your results may vary.
Keywords: redundancy
cimio_c_changeover
References: None |
Problem Statement: This | Solution: illustrates the procedure on how to compute the size of the store file when 'NOTAGINFO' argument is used in the Cimio_sf_start file.Solution
When the 'NOTAGINFO' command argument is used in the cimio_sf_start file, Get and Unsolicited transfers replies using a - instead of the original tag name. So for estimation of store file size when using this argument, simply assume a tag name of 1 character for every tag for each point.
A LongTagGetDef is constructed with 100 integers, 100 reals, and 100 TextDef strings. The GetDef rate is once per 5 seconds.
The amount of space required for the store file is
Overhead of 500 bytes
300*42= 12,600 bytes for the points
As only one character is returned for tag names there is no need to accommodate space for Long Tag Records
An additional 100 * 100 = 10,000 bytes string space
Thus, the total is 500+12600+10000= 23,100 bytes.
The update rate of 5 seconds results in a file size growth rate of 23,100 * 12 = 277,200 bytes per minute.
An outage of 1 hour (60 minutes) would generate a file of size 16,632,000 bytes. If the plant allocates 1 GB for the store file, the maximum outage time covered would be
1024 * 1024 * 1024 / 16,632,000 = 64.55 hours instead of the 35 hours if the tag names were returned without using the argument.
Note: In order to Compute the Store file size without using NOTAGINFO please refer the Chapter 'Cim-IO Store and Forward' in Aspen Cim-IO User's guide
Keywords: notaginfo
cimio_sf_start
size
store file
References: None |
Problem Statement: Getting processing inconsistent with value in field IO_MAIN_TASK error message when adding new PUT or GET records. | Solution: This error indicates that the IO_MAIN_TASK field has not been defined. You will need to define a valid task in the field IO_MAIN_TASK for the new PUT or GET record before it can be made usable.
Steps to create a new PUT or GET record are:
1) Open IP.21 Administrator
2) Go to the IoPutDef or IGetDef record in the Definition Records area
3) Right-click the definition record and select the New record defined by IoXXXDef... option
4) Type in the name of the record you are creating, click on RootFolder (or another folder in the list of available folders), and click OK. As soon as you click the OK button, the Processing inconsistent with value in field IO_MAIN_TASK error message appears. When you click on OK, the message box disappears.
5) Press F5 to refresh the screen and you will see the newly created record under the definition record. There will be a large red X next to it.
6) Click on the new record and go to the IO_MAIN_TASK field in the right hand pane. Click in the Value area of this field and select the correct main task (ie., TSK_M... ) from the drop list. Remember to hit the ENTER button on your keyboard to accept the selected entry.
7) Finally, fill in the rest of the information for this record. Once done, right-click on the record and select the Make Usable option to make the record usable.
Keywords: IO_MAIN_TASK
inconsistent
IOPUTDef
IOGETDef
References: None |
Problem Statement: Deployment of Aspen CIM-IO software across a WAN (Wide Area Network) link can be problematic due to the latency inherent to these types of connections. | Solution: In this scenario we are discussing a WAN connection between the CIM-IO Server and the CIM-IO Interface, ie. if there is a WAN between CIM-IO Core and the Server running the CIM-IO Interface software and/or DCS.
Users may see error messages in the CIM-IO message log on the CIM-IO Server and CIM-IO Client of the type:
CIMIO_USR_GET_RECEIVE, Error receiving a GET reply from device
CIMIO_MSG_RECV_TIMEOUT, Time-out trying to receive a message
Since it is not possible to rely on CIM-IO Store and Forward to resolve timeouts and connection drops in the above scenario, it is important to design and maintain the WAN link to be as efficient and latency free as possible. Store and Forward is a mechanism which allows for buffering of data if the link between the CIM-IO Server and CIM-IO Client (typically Aspen InfoPlus.21) is lost. In this instance a data file will be created whilst the connection is reinstated and then data is able to unbuffer.
In deploying a CIM-IO Server communicating across a WAN to a DCS, there are baseline factors which must be adhered to:
Latency must be kept to a minimum. Typically a measure of 300ms or more is considered too high for most TCP/IP based communication, and any measure over this may result in loss of connection and ability to receive data from the DCS
Number of network hops should be minimized as much as possible. This strongly ties in to the above as any device, be that a router, ISA server or firewall will add to the latency of the network.
Firewalls must be configured to allow traffic across them for communication from the DCS to the CIM-IO Server and back
There are certain mechanisms within AspenTech software which can assist if deploying CIM-IO connectivity over highly latent networks:
It is strongly advised for GET transfer records within the Aspen InfoPlus.21 database to be set to communicate via Asynchronous communication. This is due to synchronous transfers requiring a response to be received before communication can continue and before any subsequent request can be made. In a highly latent network this will cause communication issues in itself. This feature is turned on in the GET record by changing the IO_ASYNC? field to YES. This is covered in the CIM-IO User's Guide documentation
Settings of the IO_TIMEOUT_VALUE field should be checked. This field allows to specify the timeout value that the main CIMIO client task is to use during synchronous read operations, and by default this is set to 5seconds. As mentioned above if the network suffers from high latency it is recommended to use asynchronous transfers and for asynchronous transfers the time-out value is the expected maximum time the client will need to send the request to the server and receive an acknowledgement.
Every WAN is of course different to the other and the above comments are guidelines for the user to consider. AspenTech relies on the network to be responsive and to not suffer from undue latency, as such we advise our customers to, where possible, deploy across local area networks or networks with low latency.
Keywords: WAN
DCS
CIMIO
References: None |
Problem Statement: Normal data collection from the Aspen Cim-IO server works properly. However when the system goes into Store mode, the Store file is not created. The cimio_msg.log may have the following messages:
CIMIO_SF_STORE_SEND_REPLY_CREATE, Error creating store file
CIMIO_SF_FILE_OPEN_OPEN, Error opening file
System Error, errno=13 Permission denied | Solution: The account running the Aspen Cim-IO Manager service on the Cim-IO server must have Read&Execute, Read, and Write permissions to the folder where the store file resides.
Keywords: None
References: None |
Problem Statement: Enhanced Aspen Cim-IO diagnostics records a large amount of information to the diagnostics log file (C:\Program Files\AspenTech\CIM-IO\log\cimio_diag.log). In many cases, it is desirable to control the type of information that is logged to the file. Category parameters in the configuration file (C:\Program Files\AspenTech\CIM-IO\etc\cimio_diag.cfg) can be used to achieve this goal.
Information in this article is intended to supplement the Aspen Cim-IO diagnostics information in the Aspen Cim-IO User's Guide. | Solution: Syntax for Category parameters in the configuration file (C:\Program Files\AspenTech\CIM-IO\etc\cimio_diag.cfg) is as follows.
Category, Message-DETAIL-MESSAGETYPE-TRANSFERTYPE
Available options for DETAIL include HEADER,CONTENT_HEADER and CONTENT.
Available options for MESSAGETYPE include REQ, REPLY, NOTIF.
Available options for TRANSACTIONTYPE include GET, GETHIST, PUT, DECL, CANC, UNS, STOPPUT, STOPGET, CONNECT, DISCONNECT.
Category parameters accept wildcards (*) as in the example below.
Category, Message-*-*-*
Category parameters also accept any combination of specified parameters, as in the following example.
Category, Message-*-REQ,REPLY-GET,PUT
DETAIL
The DETAIL parameter tells the Cim-IO diagnostic engine the level of detail for messages sent to the cimio_diag.log file. Options for the DETAIL parameter are listed below.
HEADER - Header information logs general information regarding the message being passed by the Cim-IO processes. An example of a message header is below.
+------------------- Message Header ----------------------+
Message Type = REQ Transaction type = PUT Priority = 1 Trans no = 1132207725
Message Size = 610 Header Size = 292 Template Size = 192 Data Size = 126
Message Source Service = TSK_M_MATRIKON_200 Node = HKLAP
Message Destination Service = CIOMATRIKONOPCS Node = HKLAP
Request Source Service = TSK_M_MATRIKON_200 Node = HKLAP
Reply Destination Service = TSK_M_MATRIKON_200 Node = HKLAP
CONTENT_HEADER - In addition to logging the normal HEADER information, the CONTENT_HEADER parameter will log such information as the listid of the transfer record (which will correspond to the recid of the transfer record in the Aspen InfoPlus.21 database), the logical device name, data transfer type and number of tags to be transferred. An example of the extra information that the CONTENT_HEADER parameter will log is pasted below.
+------------------- Content Header ----------------------+
Listid = 2050, Num Tags = 1, Device= CIOMATRIKONOPCS, Unit= 0, Acc Type = SYNC, Intid Flag = 0
CONTENT - In addition to logging all of the HEADER and CONTENT_HEADER information, the message CONTENT flag will allow the specific data contents which are passed between the Cim-IO client processes to be logged. The example below shows that 1 ascii tag, with a size of 6 characters and a value of HELLO! was logged to the cimio_diag.log file. The tag name on the OPC server is write only.String.
NOTE: If each transfer record contains several tags, enabling the CONTENT option will cause the cimio_diag.log to grow large very quickly.
+------------------- Message Content ---------------------+
Tag IntID1 IntID2 Out Flag Type DType Size Value
----
Keywords: None
References: None |
Problem Statement: After stopping and restarting the Cim-IO server, typically at least one history occurrence for tags in the Aspen InfoPlus.21 Administrator will exhibit the following characteristics.
The Timestamp is 1/10th of a second after the last successful entry before the Cim-IO server shutdown
The IP_TREND_QSTATUS = Unavailable
The IP_IP_TREND_QLEVEL = Bad
As a result, when these tags are plotted in Process Explorer, the bad status causes an 'x' and a gap to be placed on the trend plot--representing the Cim-IO server down time.
In other cases, the unavailable occurrences is not written to tag history. | Solution: Cim-IO client tasks run on the Cim-IO client machine (InfoPlus.21 server). If running, the tasks send ping messages to the Cim-IO server to confirm that a connection exists. The ping messages are not a typical network ping. Instead, they are a Cim-IO message--in the same way that a Cim-IO GET or PUT is a Cim-IO message. These Cim-IO messages pass through firewalls whereas network pings may not.
The client tasks that send the Cim-IO ping messages are the main task (TSK_M_xx), the asynchronous task (TSK_A_xx), and the unsolicited task (TSK_U_xx). In version 2004 and above, ping messages are also sent by the TSK_Detect.
The frequency of ping messages can be set as a registry entry on the Cim-IO client (InfoPlus.21 server). The registry entry (HKEY_LOCAL_MACHINE\SOFTWARE\AspenTech\CIM-IO\CimioPingFrequency) has a default value of 60 seconds.
A second registry key--HKEY_LOCAL_MACHINE\SOFTWARE\AspenTech\CIM-IO\CimioMaxPingFailures--is also of interest.
The presence of an unavailable occurrence in a tag's history is dependent upon the product of the two values (CimioPingFrequency and CimioMaxPingFailures). Using the defaults of 60 and 3, the resulting product is 180 seconds. In such a case, if the Cim-IO server has been shutdown or stopped for 180 or more seconds (3 or more minutes), an unavailable occurrence will be written. If the shutdown is less than 3 minutes, the occurrence will not be written.
These registry key values settings can be modified. However, the values should not be set too small. If the product of the two is too small, misleading unavailable IP_TREND_QSTATUS entries (due to brief network glitches) may be recorded.
Keywords: Cim-IO
data
unavailable
IP_TREND_QSTATUS
References: None |
Problem Statement: What can be possible options to handle PIMS Simulator Interface (PIMS-SI) server files when the user wants to switch from the use of PIMS SI to PIMS AO? | Solution: Following are some of the options with PIMS AO depending on the usage of PIMS SI:
1. If the use of PIMS-SI is not critical, then just remove the servers from the model tree and don’t update the model.
2. If PIMS-SI is used to call an Excel workbook for use with SPYRO (a 3rd party steam cracking simulation), then the user can consider using Aspen Olefins Regression Calculator (AORC) with SPYRO to generate regressed furnace models that can be attached as external models with PIMS-AO.
3. If PIMS-SI is used with Excel servers or to call EXE programs, then the user will have to consider using Aspen Custom Modeler (ACM) to create DLL’s that can then be used as external models with PIMS-AO.
4. If the equations that are updated with PIMS-SI are fairly simple, putting equations on the Non-linear Equations branch of the PIMS-AO model tree is also a potential option.
Keywords: PIMS SI
PIMS AO
ACM
External model
References: None |
Problem Statement: The following errors may occur when running the Aspen Cim-IO Test application ( CimIO_T_API.exe)
CIMIO_USR_GET_RECEIVE, Error receiving a GET reply from device CIMIO_MSG_RECV_CHK, Error checking connections
CIMIO_SOCK_CHK_RECV_FAIL, Error peeking at socket
System Error, errno=0 No error
CIMIO_SOCK_RD_BROKEN_PIPE, Connection was terminated by peer System Error, errno=54 Unknown error
WNT Error=10060 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | Solution: The errors above generally indicate that the Aspen Cim-IO client processes cannot access the Aspen Cim-IO server processes. If the configuration is OK and the Aspen Cim-IO server processes are running the problem may be related to the Windows Firewall. If the Windows Firewall is active then one suggestion is to disable it. If for some reason the Windows Firewall must be active then add an exception for all Aspen Cim-IO executables including the CimIO_T_API.
Programs and Services exceptions are added through the Windows Firewall window.
Keywords: CIMIO_T_API
Socket
References: None |
Problem Statement: Sometimes, during Cim-IO configuration or while trouble-shooting Cim-IO issues, it?s useful to turn all IO_DEVICE_PROCESSING and all IO_RECORD_PROCESSING off or on.
How can I stop all Cim-IO devices and all record processing? | Solution: The quickest way of doing this is by using SQLplus.
An update statement is required to turn OFF the IO_DEVICE_PROCESSING and IO_RECORD_PROCESSING.
See example below:
UPDATE IOSIMUL
SET IO_DEVICE_PROCESSING = 'ON'; --
UPDATE AspenChem_Get
SET IO_RECORD_PROCESSING = 'ON';
You can also have a statement to check the current state of the logical device processing and the record processing.
SELECT NAME,IO_RECORD_PROCESSING FROM AspenChem_Get;
select NAME,IO_DEVICE_PROCESSING from iosimul;
IMPORTANT: Please note that it?s not advisable to use SQLplus to start all devices at once, as it might cause issues with Cim-IO Server. We strongly advise to start each device one by one, or followSolution ID: 103176 ?How do I perform a clean restart of a Aspen Cim-IO Interface with Store and Forward??
Keywords: Cim-IO
SQLplus
IO_RECORD_PROCESSING
NAME,IO_DEVICE_PROCESSING
References: None |
Problem Statement: How can one force critical Cim-IO processes (e.g. AsyncDLGP.exe and the Store and Forward processes) to restart if they stop unexpectedly? | Solution: This functionality is available with all of the Cim-IO interfaces but the example in thisSolution uses Cim-IO for OPC due to its widespread usage.
With Aspen Cim-IO for OPC there is a process called AsyncDlgp.exe which is critical in the acquisition of process data. If it or any of the Store and Forward processes (cimio_sf_scanner.exe, cimio_sf_store.exe, and cimio_sf_forward.exe) go down unexpectedly then data loss could result. The following procedure enables some functionality that will detect if any of those processes crash and automatically restart them:
1. The functionality is only available when the Cim-IO interface is set up via the I/O Wizard in the Aspen InfoPlus.21 Administrator. If the device already exists and was set up using the manual method involving OPCProperties.exe, cimio_autostart.bat, and cimio_autostop.bat it will not work. Devices set up via the manual method may show up beneath the I/O container in the InfoPlus.21 Administrator but they will have a question mark symbol next to them and there will not be a corresponding devicename.CSD file in \Program Files\AspenTech\CIM-IO\management on the Cim-IO server machine. Note that for 64-bit versions of Windows that the directory will be \Program Files (x86)\AspenTech\CIM-IO\management . To get them to be able to use this functionality they would need to be removed and then added via the wizard.
2. If the Cim-IO device does not exist use the I/O Wizard to create it by right-clicking on the I/O container and choosing Add new device.... Step through the wizard. The key step that enables the restart functionality is in the third screen. Make sure to check the box which says Health Check - Check server processes:
3. If the Cim-IO device already exists and shows up with a dot next to its name (a red dot means the device is down and a green dot means the device is up) one can check on whether this setting has been enabled or not by right-clicking the device and selecting 'Properties'. There's a Server tab on that screen that will reflect the status. If the device is running the selection may not be changed:
If the device is stopped (via right-clicking and selecting 'Stop logical device') the Health Check option will become available:
There are some settings for this functionality that can be reached by right-clicking the device and choosing 'Manager Parameters':
The latter number is in seconds and is how often the processes will be checked (and subsequently restarted if they are down).
Please note that this restart functionality does NOT apply when the processes are stopped deliberately by the user.
Keywords: None
References: None |
Problem Statement: When installing the service pack, the CIM-IO icon is disabled (grayed-out) even though CIM-IO is installed and the service pack has not yet been applied. | Solution: All cio_*.ini files in the \Program Files\Aspentech\Setup\Uninstall directory must reflect the latest major version in order to apply the service pack. Editing an old interface *.ini file to the current version resolves the problem.
For example, a CIM-IO server is at v5 and running both CIM-IO for OPC and CIM-IO for RSLinx. It is then upgraded to v6, but CIM-IO for RSLinx was not upgraded (no longer used) so only CIM-IO for OPC is at version 6.0. When the SP1 install is attempted, the installer will block the CIM-IO upgrade since the CIO-ABD-RSL.ini file indicated that the RSLinx interface is not at version 6.
Edit the second line in the *.ini file so that the version =6.0.0.0
Keywords:
References: None |
Problem Statement: Starting with version 2004 (7.0.0), Cim-IO now supports Cim-IO server redundancy. You can configure two Cim-IO servers on redundant nodes. If communications with the first is lost, the CimIO client will switch to the second. If communications with second is lost, the Cim-IO client will switch back to the first.
When a down network connection occurs, the primary Cim-IO server keeps storing data in the Store file after Cim-IO Redundancy is activated - while the Cim-IO client is reading from the secondary node. | Solution: With aspenONE 2004 Update 1, a new feature is added that will allow the Changeover task to monitor connections. If data is being successfully gathered from one node, and the other node recovers from a network connection break, then the Changeover task can tell the recently reconnected node to stop scanning and clean up its store file(s).
This will return the system to a state where only one node is scanning the end device.
This new feature is called Changeover Cleanup and is set using the Cim-IO Properties utility:
%CIMIOROOT%\code\CimioProperties.exe
The Registry Option is named CIMIOChangeoverStandbyCleanup and can be set to, Use Changeover Cleanup.
Keywords: Changeover Cleanup
Store file
Redundancy
References: None |
Problem Statement: This knowledge base article describes why the IO_DATA_STATUS field in a Put record can show the error
No Permission
during a write operation. This error message is usually accompanied by an IO_LAST_STATUS of
Group Write Only | Solution: This behavior can occur when the IO_GROUP used by the Put record does not have Read/Write permissions. In some cases the problem occurred when the IO_GROUP had 'Write Only' permissions. To work around this problem, select an Io-Groups record occurrence which has Read/Write permissions. To examine the current permission level on each Io-Groups record occurrence do the following:
1. Note which Io-Groups record occurrence is specified in the IO_GROUP field
2. In the Aspen InfoPlus.21 Administrator locate IOGroupDef.
3. Expand IOGroupsDef and select the Io-Groups record. Open the repeat area for Io-Groups to see a list of each possible option which can appear in the IO_GROUPS field in the Put record.
4. Ensure that the IO_GROUP_PERMISSION field is set to Read/Write.
Keywords: write-only
access
permissions
deny
denied
grant
References: None |
Problem Statement: This knowledge base article describes how to resolve the following error:
Invalid value in field IO_ACTIVATION_COS
which is encountered when you attempt to make an Aspen Cim-IO transfer record unusable. | Solution: You can place a 'blank' in the IO_ACTIVATION_COS field to resolve this error.
1. Set IO_RECORD_PROCESSING = OFF
2. Set IO_ACTIVATE? = NO
3. Set IO_#TAGS = 0
4. Use the Aspen SQLplus Query Writer to set the IO_ACTIVATION_COS field to a blank using the following query:
MYRECORD.IO_ACTIVATION_COS = '';
where:
- MYRECORD is the name of your transfer record
- The quotes ( '' ) used in the query are two single quotes with no space in between them
Keywords: None
References: None |
Problem Statement: Setting Aspen Cim-IO redundancy and it's not working as expected.
When forcing Aspen InfoPlus.21 to go to Secondary Aspen Cim-IO system nothing happens, and the Logical Device record in Aspen InfoPlus.21 shows that the IO_Primary_Device and IO_Secondary_Device with a status of OFF.
The CIMIO_MSG.LOG file in the Aspen InfoPlus.21 system may have messages indicating ping failures to the Primary and Secondary systems. | Solution: For proper redundancy operation the Aspen InfoPlus.21 system needs to be able to ping the Primary and Secondary Cim-IO systems, and reverse ping operation from the Primary and Secondary Cim-IO systems to the Aspen InfoPlus.21 system is also required.
See alsoSolution 115616, Configuring Cim-IO redundancy.
Keywords: None
References: None |
Problem Statement: Type Mismatch error occurs when calling the function CreateCalcScriptParams from third party applications.
In the CalcScheduler library the CalcCommands class has a method call:
Function CreateCalcScriptParams(pCalcDisp As Object, AutoBindingHosts As
String, pUnused, pUnbound) As Boolean
Member of CalcScheduler.CalcCommands
pUnused and pUnbound are not defined in terms of their type. When calling this method using a third party application, such as SQL server or Cold Fusion, a Type Mismatch error may occur. | Solution: The key here is that both pUnUsed and pUnbound are out parameters and defined as VARIANT*. As in any COM situation, an out pointer has to be allocated by the client. In SQLPlus, if the local variable type is not defined it will default to VARIANT.
For third party applications, such as ColdFusion or SQL Server, the variable must be defined as VARIANT and passed as an out parameter. Consult the application documentation on how to define this.
SQLPlus Example:
local calcCmd, calcLib, formula, param, params;
local unUsed, unBound;
local i integer;
local script char(100), formName char(20), libName char(20), parameter char(50);
libName = 'OlgaLib';
formName = 'test223';
script = 'alpha = beta + cappa';
calcCmd = createobject('CalcScheduler.CalcCommands');
calcLib = calcCmd.GetLibraryObject(libName);
formula = calcLib.AddFormula(formName);
formula.ScriptText = script;
calcCmd.CreateCalcScriptParams(formula, '', unUsed, unBound);
calcCmd.SaveLibraryFormula(calcLib, formName);
params = formula.Parameters;
for each param in params do
write 'Name: ' || param.Name || ' Type: ' || param.ParameterTypeText;
end
Keywords: COM
References: None |
Problem Statement: Aspen Cim-IO Store and Forward is designed to store data when a break in communication occurs between the Cim-IO client and server. Once communication is restored data from the store file is forwarded to the Cim-IO client. If Cim-IO continues to store data after communication is restored and does not forward It's possible that not all the communication issues are resolved. | Solution: If communication issues still exist, one helpful utility is Trace Route. c:\tracert NodeName
The TRACERT diagnostic utility determines the route taken to a destination by sending Internet Control Message Protocol (ICMP) echo packets with varying IP Time-To-Live (TTL) values to the destination. Each router along the path decrements the TTL on a packet by at least 1 before forwarding it, so the TTL is effectively a hop count. When the TTL on a packet reaches 0, the router should send an ICMP Time Exceeded message back to the source computer. TRACERT prints out an ordered list of the routers in the path that returned the ICMP Time Exceeded message.
Run Trace Route on the Aspen Cim-IO server and pass the NodeName of the Aspen InfoPlus.21 system. TRACERT will print out information on each hop to the destination Aspen InfoPlus.21 system. If any of the hops fail with a timeout error there may be communication issues preventing the Store file from forwarding.
Increasing the timeout values for the Store and Forward processes may allow the Forward process more time to make the connection and forward the data. The Aspen Cim-IO Users Guide provides details on adjusting these arguments or follow the link below to Knowledge Base article 105498
What are the Aspen Cim-IO Store & Forward startup command line arguments?
Keywords: cimio_msg_send_noconnect
no connection
tracert
References: None |
Problem Statement: When configuring TSK_DETECT with io_tagname you get the following error message in the CIMIO_MSG.LOG Device failure : Bad tag status : For device : NODE_NAME: status -13 | Solution: Add the OPC address to the IO_TAGNAME field of the watchdog tag.
Keywords: TSK_DETECT
Bad tag status
status -13
Device failure
References: None |
Problem Statement: This knowledge base article documents the | Solution: to the problem which has the following three symptoms.
1. AspenTech client applications which use Aspen Framework (AFW) or Aspen Local Security (ALS) generate the following error:
Security Initialization Error: ** Init Cache COM Error, number : -2147467259
2. When the security components test tool, SSTest, is run the following error is encountered:
Security Server Connection Test Failed. Server Application Error. The server has encountered an error while loading an application during the processing of your request. Please refer to the event log for more detail information.
3. Around the same time the Windows Event Viewer records the following warning.
The server failed to load application '/LM/W3SVC/1/Root/AspenTech'. The error was '8007053d'. For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.
Solution
You should have a AspenTech virtual directory in Microsoft's Internet Information Server (IIS) on your AspenTech security server as shown below. If you don't have the AspenTech virtual directory then the installation of AFW/ALS was not successful. If your security server does not have the AspenTech virtual directory in IIS you should un-install, reboot, then re-install AFW/ALS.
The following article from Microsoft states that the aforementioned event log error is caused when the changes made to the application, directory, virtual directory, or site were interrupted while they were being written to the metabase. This article says this action likely corrupted the metabase.
http://support.microsoft.com/default.aspx?scid=kb;en-us;238665
Microsoft's recommendation is to remove then re-create the application, directory, virtual directory, or site that was being created when the corruption originally occurred. The following article describes how to restore a metabase backup (even if you didn't make a backup, a backup may still exist on your system.)
http://support.microsoft.com/kb/234429/EN-US
If neither of these suggestions work, you will need to un-install IIS, re-install IIS then re-install all of the AspenTech applications on this server which rely on IIS.
Keywords:
References: None |
Problem Statement: When an IoUnsolDef (Unsolicited) Transfer record is activated, the IO_LAST_STATUS becomes:
Declare/Cancel Error
The IO_LAST_STATUS_DESC is shown as:
USR_DECL_DCONVSZ, Error getting size of | Solution: This has been seen when some of the Occurrences of the Unsolicited Transfer record's repeat area don't have the IO_VALUE_RECORD&FLD attribute configured, but do have the IO_TAGNAME attribute configured. These occurrences also have IO_DATA_PROCESSING turned ON.
These occurrences should either be deleted, configured properly for the IO_VALUE_RECORD&FLD attribute, or at least have the IO_DATA_PROCESSING attribute turned OFF.
Keywords: None
References: None |
Problem Statement: Is there a Cim-IO interface that can interface with EUROMAP.15 messaging protocol? | Solution: Cim-IO hasn?t got an interface that is able to operate with Euromap.15 protocol, however there are two options to get AspenTech software communicating with Euromap.15 protocol:
? You could write a Cim-IO interface to work with Euromap.15 protocol (but AspenTech wouldn?t be able to help you with that).
You could work with a Third Party vendor to get an OPC server, in order to get Euromap.15 protocol connected to OPC, which is the current standard for AMS and APC.
In the past our customers used to write their own Cim-IO interfaces. But this approach led to a very large number of interfaces that can?t be supported. Investing into an OPC Server would enable you to use Cim-IO for OPC interface, which is the most widely used and supported.
Keywords: Cim-IO, Euromap.15
References: None |
Problem Statement: Sometimes the following error message can be returned when trying to use CIM-IO to write to a device.
'CIMIO_USR_PUT_RECEIVE, error receiving a PUT reply from device' CIMIO_MSG_RECV_TIMEOUT, Time-out trying to receive a message
This article will describe the possible causes of this particular error. | Solution: The most frequent cause of the aforementioned error messages is a timeout value which is too short for the PUT record. The timeout can be adjusted in the IO_TIMEOUT_VALUE field for each PUT record.
If the problem is intermittent, and if data transfer problems are also experienced with GET records around the same time period, then the problem may be caused by intermittent network problems. To test for network problems, make sure that the the CIM-IO client and CIM-IO server can successfully NSLOOKUP each other. Also, make sure the roundtrip ping time is normal when the problem occurs.
Make sure the CIM-IO interface is not overloaded. The maximum throughput for each interface is listed in the data sheet for each interface. All data sheets are available for download from the documentation section of the support website.
Another possibility is that the cimio server may not have enough free resources to process all of the requests. When the problem occurs are the CPU and memory usage normal on the cimio server?
This problem has also been noticed when hardware problems have caused a slowdown on the CIM-IO server, such as a hard drive which runs very slowly before it crashes.
Keywords:
References: None |
Problem Statement: The Cim-IO patch installation fails due to locked file:
[EXAMPLE]
Copy cimio.dll
to .....\Common Files\AspenTech Shared\cimio.dll
ERROR, The process cannot access the file because it is being used by another process.
Failed, Installation finished... | Solution: Aspen Cim-IO patch installations require that all applications and services connected to Aspen Cim-IO be shutdown prior to installation. These might include: Aspen InfoPlus.21, Aspen DMCPlus, Aspen InfoPlus.21 Administrator, Aspen InfoPlus.21 Manager, Aspen Cim-IO Manager service, and Aspen CIMIO to OPC Interface service, as well as any third party applications that use Aspen Cim-IO on the system where the patch is to be installed. If unclear about which application are connected to Cim-IO prior to installation then one way to determine this is to download and run Windows Sysinternals Process Explorer.
Windows Sysinternals Process Explorer has more information.
When running Process Explorer use the ?Find? drop down and select ?Find handle or dll...? and type in the name of the file that is locked. [EXAMPLE: cimio.dll] This will display the processes that have the file locked. Then close the identified applications or services and proceed with the installation.
NOTE: The patch files must be extracted again from the *.zip file to re-run the installation.
Keywords: None
References: None |
Problem Statement: In a redundant environment, why doesn't TSK_DETECT delete the scanning list from the primary Cim-IO server when failing to the secondary server after running CIMIOProperties as described in knowledge base article 127278 and set the registry key CIMIOChangeoverStandbyCleanup to Use Changeover Cleanup? | Solution: TSK_DETECT reads the registry keys set by CIMIOProperties when starting.
To solve this problem, stop TSK_DETECT using the Aspen InfoPlus.21 Manager, restart the Aspen InfoPlus.21 Task Service, and resart TSK_DETECT. See Knowledge Base article 115690 entitled Can the Aspen InfoPlus.21 Task Service be stopped and restarted while Aspen InfoPlus.21 is running? for additional details.
Keywords:
References: None |
Problem Statement: When using an OPC client to detect Aspen InfoPlus.21's OPC server, the client may give an error No opc servers detected on this machine or an equivalent message where Aspen.InfoPlus21_DA.1 is unable to be found. | Solution: Check to see if there is a service in Component Services called OpcEnum. It should appear as follows in the services, and the executable should reside as OpcEnum.exe in C:\Windows\SysWOW64\:
To install this service, open a command window and set the directory to C:\Windows\SysWOW64\
After that, issue the following command:
sc create opcenum binpath=C:\Windows\SysWOW64\OpcEnum.exe
This should result in a message: [SC] CreateService SUCCESS
This message means that the service was created successfully. You should now be able to see OpcEnum in the list of defined services and should be able to access the Aspen.InfoPlus21_DA.1 opc server using an OPC client.
Keywords: OPCENUM
No OPC servers detected on this machine
References: None |
Problem Statement: During the startup of a Cim-IO server, the following error occurs: Cim-IO core encountered a problem and needed to close on reboot. The following error may also appear in the Application log of the Event Viewer:
Reporting queued error: faulting application CimioManager.ere [sic] version x.x.x.x
faulting module unknown, version 0.0.0.0 fault address 0x00000000. | Solution: This problem can occur on servers upgraded from an older version of Cim-IO. The Cim-IO Manager service behaves as if it is starting an old version of the Cim-IO Manager executable (CimioManager.exe).
The fix for this is to reregister the Cim-IO Manager service.
1. Open a command prompt and cd to theA .....\ Cim-IO\code folder
2. Type cimiomanager -remove
3. Verify the Aspen Cim-IO Manager service is removed
3. Type cimiomanager -installservice [Username Password]
The username and password you specify should be the account that you use to start the service. This is typically the domain or local administrator account you specified when you did the install.
Keywords:
References: None |
Problem Statement: This knowledge base article discusses whether or not the following message from the cimio_msg.log is indicative of a problem with Aspen Cim-IO.
Ignoring GET reply from node: XXXX | Solution: This message usually indicates that the scanner process is sending a Get reply back to itself. This message has been reported a couple of times. However, it has never been known to cause any communication problems. It simply fills up the cimio_msg.log file. These errors eventually go away on their own and usually do not return.
Keywords: Ignore
References: None |
Problem Statement: A Cim-IO Redundant Switchover might not occur although TSK_DETECT has identified the switchover and seems to perform the necessary actions. This problem can occur when Infoplus.21 is installed on Windows 2008 Server. A side effect is that there are no files with extension LDV created. Their location is the folder for application program files: ...\AspenTech\CIM-IO\io and are usually created at the time of the first switchover. | Solution: This problem is typically caused by the Windows 2008 UAC security settings for the Admin accounts. This has impact on the Admin account used to configure Cim-IO Redundancy and the Admin account that starts the Aspen InfoPlus.21 Task Service.
On the Infoplus.21 server perform following steps:
1. Navigate to Start | Administrative Tools | Local Security Policy;
2. Navigate to Local Policies | Security Options;
3. In the list change User Account Control: Behavior of the elevation prompt for Administrators in Admin Approval Mode. Set it to: Elevate without prompting;
4. In the application program files folder ...\AspenTech\CIM-IO\code run the CimioProperties.exe. This will update the system registry.
5. Restart the Aspen InfoPlus.21 Task Service and the Infoplus.21 database. This way the Infoplus.21 client tasks will have the new Admin privileges and will use the updated system registry.
The Cim-IO redundant switchover should work correctly now.
Keywords: Changeover
Windows 2008
Cim-IO
Redundant
References: None |
Problem Statement: This Knowledge Base article provides a brief description of the main characteristics of Aspen Framework vs. Aspen Local security. | Solution: Aspen Framework provides the integrating infrastructure that enables the development and enterprise-wide implementation of business processSolutions. A role-based Security component is just one aspect of installing and implementing Framework.
Aspen Framework (AFW) is a full blown securitySolution which consists of a single dedicated AFW Security Server and all InfoPlus.21 Servers pointing to it.
Here are the main points that characterize Aspen Framework:
Streamlined security implementation (easy administration - only one server per enterprise to administer)
Uses SQL Server or Oracle as a security database repository (more secure than MS Access)
Could slow down user authentication (especially if InfoPlus.21servers are on a slow WAN)
If this server goes down, users that required authentication (and without AFW Cache) would be locked out.
Attached to this Knowledge Base article please find Aspen Framework Fact Sheet, which describes the purpose of this product in more detail.
Since not all customers will purchase and use Framework, not everyone would have had Framework Security. Therefore, for customers who do not have the full-blown version of Framework, a lighter version of Framework was developed, called Aspen Local Security. This is basically just the Security component pulled out of Framework, with only slight modifications. You can read more about this in the documentation under Aspen Manufacturing Suite, Aspen Local Security. Any of the Installation Manuals has a small section in the front, describing this product.
Here are the main points that characterize Aspen Local Security:
Fast, reliable user authentication
Easy to troubleshooting
Allows for server-specific settings
Can use MS Access as a security database repository (less secure than MS SQL Server or Oracle)
The main disadvantage is that there are many security servers to administer. As an Aspen InfoPlus.21Administrator this can be pretty tedious.
Keywords: None
References: None |
Problem Statement: It's possible to create Aspen InfoPlus.21 database records defined by AspenCalcDef.A Each of these records has a pointer to a pre-existing Aspen Calc calculation, as well as, a Change of State (COS) activation record/field pair.A Meaning that when the field in the record defined by COS activation changes then the Aspen Calc Calculation will be executed.
This article described why the AspenCalcDef record may be activated but the query does not get executed. | Solution: For these records to work successfully, an external task called TSK_CLC1 needs to be started from the Aspen InfoPlus.21 Manager.A However some users have found that the TSK_CLC1 would not stay running, and the .OUT file for the task showed: Error :A Invalid external task recordA A - 46
This was because the TSK_CLC1 record under ExternalTaskdef record family as seen in the Aspen InfoPlus.21 Administrator below was missing;
If the record is missing, you can reload this from the aspencalc.rld file. For information on how to load this see KB 104113 for further details.
Once TSK_CLC1 is running correctly, then calculations activated by AspenCalcDef records should work as expected.
Keywords: None
References: None |
Problem Statement: When using Aspen's Aspen Calc product often times new formulas and calculations are created, are there any restrictions as to where to save these? | Solution: Users can save new formulas or calculations to existing or new folders, but should avoid saving these in the AspenPropertiesFlash, AspenPropertiesGeneral or AspenPropertiesToolkit libraries. These libraries are distributed with the AspenCalc product, and are not saved in the default path, C:\Documents and Settings\All Users\Application Data\AspenTech\Calc\lib folder.
A problem users may encounter when upgrading the Apen Calc product, the upgrade moves only the formulas and calculations the user saved in folders he created, by default these are saved in the C:\Documents and Settings\All Users\Application Data\AspenTech\Calc\lib folder, this does not include formulas and calculations saved in the AspenPropertiesFlash, AspenPropertiesGeneral or AspenPropertiesToolkit libraries.
Also, the upgrade process may overwrite the contents of the AspenPropertiesFlash, AspenPropertiesGeneral and AspenPropertiesToolkit libraries, and would delete any user formulas or calculations saved in them.
Keywords: new formula calculation save folder upgrade
References: None |
Problem Statement: When you add a new node in Aspen Calc, you receive the following error message:
Failed to connect to server <servername>, permission denied | Solution: This is generally due to the permission settings of the DCOM object.
1. Click on Start and click on Control Panel.
2. Click on Administrative Tools and double click to launch Component Services.
3. Expand the Computers container.
4. Expand the My Computer container.
5. Expand the DCOM Config container.
6. Right click on AspenTech Calculator Engine and click Properties.
7. Select the Security tab
For Windows 2003 with the installation of Service Pack 1, DCOM might not work correctly. This is due to the changes in the default COM permissions in Windows 2003 SP1. Please refer to Microsoft knowledge base article ''Programs that use DCOM do not work correctly after you install Microsoft Windows Server 2003 Service Pack 1''.
http://support.microsoft.com/?kbid=892500
Choose Customize and click on Edit.
Under the Launch and Activation Permissions,
1. If the User Group Distributed COM Users is not in there, click on Add and type Distributed COM User and click on OK.
2. Click allow for all the permissions available for the Distributed COM Users, i.e. Local Launch, Remote Launch, Local Activation and Remote Activation.
3. Click on OK two times to accept the changes.
Under the Access Permission,
1. If the User Group Distributed COM Users is not in there, click on Add and type Distributed COM User and click on OK.
2. Click allow for all the permissions available for the Distributed COM Users, i.e. Local Access and Remote Access.
3. Click on OK two times to accept the changes.
In addition, administrators must add the domain user to the Distributed COM Users group by the following steps.
1. Click Start, point to Administrative Tools and then click Active Directory Users and Computers.
2. Expand Domain container.
3. Expand the Built-in container.
4. Right-click on Distributed COM Users and click Properties.
5. Select Members tab and click Add and type the User Group or user name and click on OK.
6. Click on OK two times to accept the changes.
Keywords: DCOM
Failed to connect to server <servername>, permission denied
References: None |
Problem Statement: Analyzer drift does not work on transformed IQ | Solution: When both analyzer and lab measurements are available for an inferential quality (IQ), it is desirable to track the drift of the analyzer from the lab value and take action if the calculated drift is too large, so that appropriate action can be taken to correct the analyzer problem.
In the Aspen IQ Onlines, analyzer drift (ANZRDRIFT) is defined as the difference between a number of averaged validated analyzer values at the time that a lab sample was taken, and the corresponding number of averaged lab values themselves. The validated analyzer values include the effect of a lab-to-analyzer offset (AZULABOFST), which is used to account for the difference in lab sample points and/or calibration techniques.
For inferentials that are not transformed, the calculation is done as specified above and the analyzer drift status is set to BAD if the absolute value of the calculated analyzer drift (ANZRDRIFT) exceeds the allowed analyzer drift (AVMAXDRIFT). This causes the IQ to switch to lab updating until the analyzer again tracks the lab acceptably.
However, for a transformed IQ, the drift validation calculation is bypassed. There is no perfect replacement for the missing drift calculation, although it is possible to use rate of change checks to detect gross errors in lab sample measurement entries which could cause a large value of analyzer drift. This large value of analyzer drift could cause undesirable behavior if the IQ is a CV in a DMCplus controller, and could easily cause an IQ to go off-spec because the drift-corrected analyzer value is continually being used to update the inferential model predictor (the DMCplus CV) even though the analyzer is no longer providing the correct reading due to the lack of drift validation.
When using the rate of change limits for lab values (LVROCLIMI in the upward direction, LVROCLIMD in the downward direction), remember that these limits use percent of range for transformed IQs, and therefore the limits should be set as percent of range limits. These ROC limits are converted to a percent of range in the process domain, and the percent of range is then used in the transform domain to calculate an allowed maximum change in transformed units.
Let's consider an example of an IQ with a maximum limit (LVMAXLIM) of 5.0, a minimum limit (LVMINLIM) of 0.4, and rate of change limits of 0.5 in both directions (LVROCLIMI = LVROCLIMD = 0.5). This represents a maximum allowed change of approximately 10% of the valid range for the inferential. The transform in this case is MLOG, with the Transition parameter (where we switch from log to linear transform) set to 0.3.
First, calculate the two ROC limits as percent of range limits.
LVROCLIMI% = LVROCLIMI / (LVMAXLIM - LVMINLIM) = 10.87%
LVROCLIMD% = LVROCLIMD / (LVMAXLIM - LVMINLIM) = 10.87%
Next, transform the upper maximum and minimum limits and come up with a maximum allowed change in transform units.
LVMAXLIMx = LN(5.0) = 1.609438
LVMINLIMx = LN(0.4) = -0.91629
LVROCLIMIx = LVROCLIMDx = (1.609438 + 0.91629) * 10.87% = 0.27453 (in transform units)
Since both LVROCLIMI and LVROCLIMD have the same value (0.5 in process units), it follows that the rate of change for both in transform units is also the same. However, this means that the effective rate of change limit in process units is both operating point dependent and direction dependent for the case of the MLOG transform (or any non-linear transform, for that matter). Consider the case where the last lab sample was 2.0 (in process units). Let's figure out the equivalent process ROC limits at this point:
First, transform the current lab value: LN(2.0) = 0.69315
Add and subtract the allowable change in transform units to get the maximum and minimum allowed entries for the next lab sample in transform units:
Maximum (transform units) = 0.69315 + 0.27453 = 0.96768
Minimum (transform units) = 0.69315 - 0.27453 = 0.41862
Maximum (process units) = EXP(.96768) = 2.632
Minimum (process units) = EXP (.41862) = 1.520
Effective ROC limit in upward direction (process units) = 2.632 - 2.0 = 0.632
Effective ROC limit in downward direction (process units) = 2.0 - 1.520 = 0.480
This demonstrates the directional dependence!
Next, consider what happens if the last lab value was 2.50, where LN(2.50) = 0.91629
Maximum (transform units) = 0.91629 + 0.27453 = 1.1908, EXP(1.1908) = 3.290 in process units
Minimum (transform units) = 0.91629 - 0.27453 = 0.64176, EXP (.64176) = 1.900 in process units
Effective ROC limit in upward direction (process units) = 3.29 - 2.5 = 0.79
Effective ROC limit in downward direction (process units) = 2.5 - 1.9 = 0.6
This demonstrates both operating point and directional dependence!
What does this mean? It means that the ROC limits for transformed IQs should only be used for gross error detection (such as, a slipped decimal point) on bad lab result data. The entered ROC limits in process units should be close to the values that will actually be applied in transform units, but not exactly equal.
The use of percent of range is also used for the following IQ parameters:
AVROCLIMI (analyzer maximum increase)
AVROCLIMD (analyzer maximum decrease)
AVFRZDB (analyzer freeze deadband)
LVOLRLIM (lab outlier error limit)
Keywords: Aspen IQ
Analyzer drift
References: None |
Problem Statement: How can I correct write errors in Aspen Inferential Qualities that are intermittent and appear at different frequencies? | Solution: A recommendation for occasional Aspen Inferential Qualities write errors that are intermittent and at different frequencies, can be addressed by setting the offset time at which the prediction module and execution module run (IQ online) at different times (seconds) past the minute. They are set to the default value of 0 sec. This seems to have a positive effect for resolving this issue, particularly if the cimio.dll's are current and there are no other cimio difficulties being reported by other applications using the same devices and opc servers.
Keywords: IQ, execution module, prediction module, cimio
References: None |
Problem Statement: Aspen Calc is a product that allows creation of many different kinds of calculations, retrieving data from many different sources.
A user can also execute these calculations in many different ways. Examples may be at regularly scheduled time intervals, on user request, and for events such as InfoPlus.21 database changes. Another feature allows On-Demand ?on the fly? calculations. In addition, if you have Aspen Calc installed along with other Aspen applications on your client or server, both Ad-Hoc Calculations and Stored Calculations are available.
This article is to remove confusion as to exactly which process performs the actual calculation itself. | Solution: An installation of Aspen Calc Server will include the CalcScheduler.exe which is the 'Calculation Execution server'.
Typically it is started via the Control Panel | Services applet as AspenTech Calculator Engine
It has two main functions. Process the Calculation Schedule Groups and Support the Aspen Calc User Interface.
In other words, calculations that are scheduled, or executed from the Interface, will be executed via this service.
When event-driven calculation executions (such as via a change in a value within the Aspen InfoPlus.21 database) are created, then extra things will happen. First a new Aspen InfoPlus.21 record with information about the calculation will be automatically created. That record will be defined by AspenCalcDef. That definition record points to the external task Tsk_CLC1. However that task does not execute the calculation. It only causes the event-driven calculation to be activated.
The AspenCalcDef record has a field called Node_Name. After activation by Tsk_CLC1, the calculation service on the node defined by Node_Name, will be called via DCOM to execute the calculation.
The next kind of calculations to discuss are the shared on-demand calculations. These can be created via the Aspen Calc User Interface, or directly in the Aspen InfoPlus.21 Administrator. Shared on-demand calculations are stored in the Aspen InfoPlus.21 database as IP_CalcDef records, within which you can actually see the calculation syntax, and are used to plot data directly in Aspen Process Explorer.
For shared on-demand calculations, an executable AtSharedOnDemand.exe, is launched by Tsk_Apex_Server on the Aspen InfoPlus.21 Server. When the user specifies a tag (no equal sign) on Aspen Process Explorer, it will make a DA call (via ProcessData) to the Aspen InfoPlus.21 Server and Tsk_Apex_Server receives it. Tsk_Apex_Server just simply makes a local call to get the value or history of the tags referenced in the calculation. Note: If the script has syntax to reference another server?s tag, e.g. {server:tag}, it will also get the values for that tag from that server.
Internally, the local setcim api knows that this is an IP_CalcDef record. So instead of reading it like a regular tag, it packages it and send it over (via local DCOM) call to AtSharedOnDemand.exe. Then AtSharedOnDemand.exe will fetch the script from the database and execute it. Meaning that in this case, AtSharedOnDemand.exe acts on behalf of the calc service.
The final type of calculation under discussion would be an Aspen Process Explorer Ad-Hoc tags such as a user simply specifying, say, ?=atcai*2?. That calculation is actually done locally in client box by Aspen Process Explorer. It passes the whole string including the ?=? sign to ProcessData which sees the ?=? sign and determines that this is an ad-hoc calculation. So, it invokes and passes the whole string and the ADSA source to the ProcessData Calc Data Server. The ProcessData Calc Data server will then fetch the values from Aspen InfoPlus.21 and perform the calculation. All of these ProcessData and ProcessData Calc Data Servers are in-process COM servers. As a result, Aspen Process Explorer is the one which does everything effectively.
Keywords:
References: None |
Problem Statement: When using AspenIQ Online 6.0.1ER2 on a Win2000 machine, and attempting to save the the IQF (attached) from IQ manage generates the message Save failed.
The application was deleted (not the history files), and reloaded, but the message Save failed continues to appear. | Solution: In some rare cases the iqf and/or ccf files in the ACODHome Systems folder get out of synchronization and then prevent manage from saving appliation files.
It is suggested to execute the following:
1. Use the login id used to install the software and configure it (with Admin priv).
2. Use manage stop to stop the iqf application (delete is ok too).
3. Use manage load to read the latest iqf from the applications folder located in:
Drive:\Program Files\AspenTech\AC Online\app\iqappfolder
4. Copy the file you just loaded also to the AspenTech systems folders at:
Drive:\Program Files\AspenTech\AC Online\sys\app\iqappfolder
So both should have the identical files, and this is the same as the context. The sys folder is a replica of all the app folders and this is where we save the context periodically. Thus should the pc unexpectedly crash or reboot, the latest context is saved and gets loaded upon reboot.
5. Start the iq and let it run for a few minutes
6. Try the manage save command
Keywords: IQ, save, manage
References: None |
Problem Statement: 无法运行Aspen Calc，出现如下错误： | Solution: 这是因为Aspen Calc已经在后台运行
1. 运行任务管理器.
2. 选择进程标签.
3. 选择显示所有用户的进程(Show process from all users)
4. 选择AspenCalc.exe.
5. 点击 结束进程
6. 重新运行Aspen Calc
注: 有些情况下在任务管理器中结束 AspenCalc.exe 进程后 Aspen Calc 可以运行，但是会出现闪屏。此时请确认硬盘空间是否足够，如果硬盘剩余空间较少，请尝试删除一些文件释放空间后重新运行Aspen Calc
Keywords: Run-time error '5'
Invalid procedure call or argument
CN-
References: None |
Problem Statement: How do you access Batch.21 characteristics from Aspen Calc? | Solution: You can access Batch.21 using a VBScript formula in Aspen Calc. This is very similar to using the Batch.21 COM objects in SQLplus. Here is an example VBScript formula:
dim data_source, batchquery, batchlist, ch, i
set data_sources = createobject(AspenTech.Batch21.BatchDataSources)
set batchquery = data_sources(batch21).areas(sqlplus_area).BatchQuery
batchquery.timerange.start = 12-jun-03 10:00
batchquery.timerange.end = 12-jun-03 12:00
set batchlist = batchquery.get
returnvalue = batchlist(1).characteristics.item(START TIME)
Keywords:
References: None |
Problem Statement: How can I manually start the iqlinksrv process with V7.3? | Solution: Download the attached iqlinksrv.zip, and move to the C:\Program Files\Common Files\AspenTech Shared directory.
Unzip the file and extract the iqlinksrv_shutdown.cmd and iqlinksrv_startup.cmd.
Double click the iqlinksrv_shutdown.cmd to stop the running iqlinksrv.exe process. Confirm in Task Manager / Processes, that the process is not longer running.
Double click the iqlinksrv_startup.cmd to start the iqlinksrv.exe process. Confirm in Task Manager / Processes that the process is present in the processes list.
Keywords: IQView
References: None |
Problem Statement: It is observed that the value of nDSetting is set as 24 on some clients and as 65560 (i.e. 65536 + 24) on other clients while selecting the same settings in the GUI. Why is it so? As per the documentation, the value of nDSetting cannot be as high as 65560.
Also, the values returned for the formula with nDSetting=65560 were string (though the setting 'Values as String' was unchecked in the GUI). | Solution: In latest version, the nDSetting could be 65560. Please refer to document in V7.1 DVD.
Below is detail about nDseting.
The values for the nDSetting argument are the sum of the following constant values.
Note: Each constant is listed with its value (in parenthesis) and description.
atTagName - (1) Specify the tag name.
atServerName - (2) Specify/display the server name for the tag.
atMap - (4) Specify/display the map for the tag.
atTime - (8) Specify the time/read the time.
atValue - (16) Read/write the value.
atQLevel - (32) Display the quality level (as a number).
atQLevelText - (64) Display the quality level as text (requires at QLevel to be selected).
atQStatus - (128) Read/Write the quality status (as a number).
atQStatusText - (256) Read/Write the quality status as text (requires at Qstatus to be selected).
atSingleTime - (1024) Display a single time for multiple tags. AtSingleTime Does not apply to Actual data.
atFillEmpty - (2048) Display asterisks if data is not found for a given cell.
AtReverseTime - (4096) Display data from most current to oldest.
AtBackRetrieve - (16384) Retrieve data from the most recent date to oldest date.
AtHeadings - (32768) Display headings in the formula.
AtValueAsString - (65536) Display all the values as strings.
Please try below to return resolve string issue.
1. Open the desired spreadsheet in Excel.
2. Go to the Edit | Replace
3. Find what: 65560?
4. Replace with: 24
5. Click on Replace All
6. Now if you double click on the individual Data fields, you'll see that Values as String will be unchecked.
Keywords: nDSetting
'Values as String'
Excel add-in
References: None |
Problem Statement: How do I extract messages thru dmcpmanage and iq_manage in a DOS prompt? | Solution: Go to a DOS prompt, type dmcpmanage msglist [controller name] [> file location] or iq_manage msglist [controller name] [> file location], it will create a file but to finish the process you have to type a??Ya?? and press a??entera?? as many times as a new DOS line appears.
E.g.
dmcpmanage msglist democol12 >c:\democol12.txt
iq_manage msglist refinery >c:\refinery.txt
Keywords: Extract, messages, dmcpmanage, iq_manage
References: None |
Problem Statement: This knowledge base article provides an example which shows how to execute an SQLplus query through an ADO connection then assign the result of the query to Aspen Calc's ReturnValue parameter. | Solution: This Aspen Calc calculation is written in VBScript.
' Begin Example Calculation
dim conn,rs, stat
set conn = createobject(ADODB.Connection)
conn.open HKLAP
stat = SELECT IP_Input_Value from atcai;
set rs = conn.execute(stat)
returnvalue.value=rs(0).value
The line of the query in which the result from the SQLplus query is assigned to the return value parameter is
returnvalue.value=rs(0).value
In this case a single value is returned from the SQLplus query so the record set positional argument of zero, rs(0), is used to access this element. An additional example of how to use the record set positional argument can be found in knowledge base article 115659.
Keywords: Assign
Manipulate
Store
Save
References: None |
Problem Statement: The following error has been seen after some users have upgraded the Aspen Process Data Add-in from version 6.0 to version 2006.5. | Solution: This error has been resolved by removing the 6.0 version of the file AtProcessDataXLA_en.dll located in the path \\Program Files\Common Files\AspenTech Shared\.
Keywords: ATPROC~2;
ATPROC
Aspen Process Data Add-in;
Aspen Process Data;
Add-in;
References: None |
Problem Statement: Calculations are not writing data to InfoPlus.21 database after they were moved to a new server. What's wrong? | Solution: In order for the calculations to be recognized on the new server, they must be updated with the new server name and validated. Below is an excerpt from the Aspen Calc Help file describing the steps that need to be performed to accomplish these tasks.
To simplify moving calculations from one InfoPlus.21 server to another, Aspen Calc provides a Change InfoPlus.21 Server option, which searches all the calculations on the Calculation Execution Server and replaces one InfoPlus.21 server name with another. This option automatically validates all tag references against the new InfoPlus.21 server.
To change the InfoPlus.21 server name:
1. In the Calculation or Formula view, right-click the server that you want to change. A shortcut menu is displayed.
2. Click Change InfoPlus.21 Server. The Change InfoPlus.21 Server dialog box is displayed.
3. In the New InfoPlus.21 Server section, enter the name of the new server in the Host Name text box.
4. Click Change.
Aspen Calc provides a Validate option so that you can validate all InfoPlus.21 tag references in all calculations. This option is useful if an InfoPlus.21 database is reorganized or updated.
To validate all InfoPlus.21 tag references:
1. In the Calculation or Formula view, right-click the server for which you want to validate InfoPlus.21 tag references. A shortcut menu is displayed.
2. Click Validate InfoPlus.21. A message asking you to confirm the validation is displayed.
3. Optionally, select the Validate Engineering Units check box. This checks the engineering units of each tag in the calculation and recalculates engineering unit conversion if necessary.
4. Click Yes.
Keywords:
References: None |
Problem Statement: The IQ message list in web server, is filling up with a Error formatting message.
01/26/2012 10:14:05 appname Error formatting message with format name: IQ: Analyzer bias. Message format or msg Id not found | Solution: Set the P2DBGLVL value in application detail page, of the web server, to 5 or less, to suppress the analyzer update messages.
Keywords:
References: None |
Problem Statement: This knowledge base article outlines the user permissions which are required for the account under which the AspeTech Calculator Engine service starts when this service is used on a client machine. | Solution: If using Aspen Framework (AFW) or Aspen Local Security (ALS) with Aspen InfoPlus.21 (IP.21), the AspenTech Calculator Engine service should be started from a domain account which has access to read/write to the registry on the local client machine.
This account should also be able to read/create/edit files and folders on the local client machine since each calculation, library and schedule is stored as an .atc file on the local drive. The file path used to store the .atc files is:
Program Files\AspenTech\Aspen Calc\Calc
This account should also be in an AFW/ALS role which has access to the IP.21 server. Otherwise the user won't be able to bind to tags on the IP.21 server from calculations created on the client machine.
Keywords: Access
Deny
Denied
Denial
Permission
Credential
Authorized
References: None |
Problem Statement: If the Aspen Configuration Excel add-in will not connect and produces a message like the following:
Failed to connect to IP.21 Server on [<server name>]
How can one correct the problem? | Solution: Look in the Aspen InfoPlus.21 database for a record defined by ProcedureDef called AtXl_DbSchema. The normal repeat area called #QUERY_LINES should have many lines of encoded text. V7.3 has 42 lines. The error message can be produced if the number of lines in that repeat area is zero.
To correct the problem locate AtXl_DbSchema.sql and load the file in the SQLplus Query Writer. The file will probably be located in one of the following places:
\Documents and Settings\All Users\Application Data\AspenTech\InfoPlus.21\db21\group200\sql
\ProgramData\AspenTech\InfoPlus.21\db21\group200\sql
\Program Files\AspenTech\InfoPlus.21\db21\group200\sql
Save the query to the ProcedureDef record AtXl_DbSchema. Make sure not to include .sql on the end of the record name. This will populate #QUERY_LINES with the correct encoded data and the add-in will be able to function correctly.
Keywords:
References: None |
Problem Statement: This knowledge base article describes which Aspen Calc calculation type is more efficient, CalcScript calculations or VBScript calculations. | Solution: The performance limitations you will observe will significantly depend on your server (hardware specifications, disk fragmentation, resource loading, etc.) so it is not possible to give a strict set of performance data that will apply to all machines. However, a given machine will achieve better performance by using CalcScript formulas and calculations instead of VBScript formulas and calculations because VBScript calculations have to use IDispatch interfaces. In general, using CalcScript rather than VBScript in Aspen Calc is preferred unless specific VBScript features are required. In addition to being quicker, CalcScript automatically adds parameters and handles quality statuses better.
Keywords: performance
speed
fast
slow
compare
References: None |
Problem Statement: What is the max value to which IO_MAX_Counts can be set? | Solution: The Max value of IO_MAX_Counts is 2147483647 = 2^(32-1) - 1.
IO_MAX_Counts introduction:
Some devices do not send values to the computer in engineering units (E.U.). Sometimes the hardware sends integer numbers representing raw counts to the computer. For example, a raw count value of 2000 can represent 100
engineering units and a value of 4000 can represent 200 engineering units. During device data read and write operations, the conversion record includes information to:
? Convert raw counts to engineering units.
Convert engineering units to raw counts.
If E.U. value conversion is required on input and output operations, enter values into the fields in this record to enable the Cim-IO software to perform the E.U. conversions.
IO_MAX_Counts holds the maximum value for the incoming counts, for example, 4095 (for 12-bit A/D converters, the value is normally 4095.)
For read operations, the Cim-IO client tasks use the following equations to convert raw counts to E.U. units using the fields of this record:
convertedValue=rangelo+(rangehi - rangelo)/(maxcounts - mincounts) * (readvalue - mincounts)
if (convertedvalue > rangehi) then convertedvalue = rangehi
if (convertedvalue < rangelo) then convertedvalue = rangelo
For write operations, when converting E.U. data to raw counts during output operations, the raw count conversion is performed using the following information:
If (rangehi - rangelo) = 0 or if (maxcounts - mincounts) = 0 then the value
output to the external hardware device is the value in the Setcim data record.
Otherwise, the E.U. value to raw count conversion equation is used:
putvalue= ((setcimvalue - rangelo) * (maxcounts - mincounts) / (rangehi - rangelo)) + mincounts
Why is the max value 2^(32-1) -1:
Because the IO_MAX_Counts field is an integer with 32-bit length.
Therefore, it can be set to 2147483647 = 2^(32-1) - 1
Keywords: IO_MAX_Counts
Engineering Units
Conversion
References: None |
Problem Statement: Aspen Cim-IO server redundancy has been configured but data only flows from one node. Trying to do a 'Force Primary' or a 'Force Secondary' via the IO_RESET field of the TSK_DETECT record is not successful. The following message is observed in the Cim-IO message log on the Cim-IO client (Aspen InfoPlus.21 machine):
18-FEB-2016 11:09:29.452, logged by TSK_DETECT on node XXXX:
TSK_DETECT, monitoring terminated device (name removed), occurrence 1 is OFF.
Turn ON and restart TSK_DETECT
What can be done to achieve a successful failover to the other redundant Cim-IO server? | Solution: Navigate to the record TSK_DETECT in the Aspen InfoPlus.21 Administrator. In the IO_#TAGS repeat area look for a field called IO_DEVICE_PROCESSING. It is currently set to 'OFF'. Change it to 'ON'.
Next, navigate to the Aspen InfoPlus.21 Manager and locate TSK_DETECT, which should be running. Click on it in the lower left 'Running Tasks' list and then press the 'STOP TASK' button. Once it disappears (indicating that it is stopped), locate it in the upper left 'Defined Tasks' list, select it, and then click the 'RUN TASK' button.
Once it restarts, assuming other configuration is correct and complete, then the IO_RESET field in the TSK_DETECT record will correctly allow the 'Force Primary' and 'Force Secondary' commands to work successfully.
Keywords:
References: None |
Problem Statement: Running the CimioSFMonitor.exe utility and selecting the “View First/Last Messageâ€� button may cause the following error; -2147417851 Method '~' of object '~' failed. | Solution: This error occurs because the RICHTXT32.OCX is missing from the system which causes functionality loss for VB 6.0 apps and COM components.Â
To solve this problem, download RICHTXT32.OCX into %SYSTEMROOT%\System32 folder and register it using regsvr32.exe.Â
Note: AspenTech does not provide this Microsoft component on Installation DVDs.
Keywords: store and forward
References: None |
Problem Statement: What tables in the Aspen Supply Chain Connect (ASCC) data base need to be populated so ASCC will recognize a new model from Supply Chain Management (SCM) Configures Applications (CAPs)? | Solution: In order for ASCC to recognize a new model being passed from an SCM CAP (i.e., Demand Manager, Plant Scheduler, etc), the MODEL table in ASCC along with the CUSTOMERFILTER, MATERIALFILTER and the LOCATIONFILTER tables need to be updated with the new model information.
Keywords: Model
Case
ASCC database
References: None |
Problem Statement: What does a combined status indicator of Insufficient Samples signify?A What is the explanation of Insufficient Samples messages for Combined Status Indicator in Aspen Inferential Qualities (IQ)?
Can you bypass the Insufficient Samples messages by setting LVMAXHOURS to zero? Once you go past LVMAXHOURS, is there no way to reestablish a bias other than to reset the LBUNUMVALS back to one? What else might cause Insufficient samples other than having an intended CUSUM LBUNUMSAMPLES set to exceed the LVMAXHOURS? | Solution: What does a combined status indicator of Insufficient Samples signify?
Samples can become obsolete after some time based on the LVMAXHOURS parameter and cannot be used in the average. Samples could be marked bad if they fail some validity limits. In case LBUNUMVALS number of samples are not obtained in LVMAXHOURS hours, the next sample to be entered would be flagged Insufficient Samples.
****************************************
Can you bypass the Insufficient Samples messages by setting LVMAXHOURS to zero? Once you go past LVMAXHOURS, is there no way to reestablish a bias other than to reset the LBUNUMVALS back to one? What else might cause Insufficient samples other than having an intended CUSUM LBUNUMSAMPLES set to exceed the LVMAXHOURS?
Just changing LVMAXHOURS to zero will not get you out of the Insufficient samples problem. This is because the previous data timestamp check is only disabled for samples that are entered after the LVMAXHOURS is changed. For example, if you still have the LBUNUMVALS parameter still set to eight, the status of the samples will change to Good only after eight samples are entered. Setting LVMAXHOURS to zero and LBUNUMVALS to one at the same time will allow you to bypass the Insufficient Samples messages and reestablish the bias.
There are three ways to reestablish the bias after you get the Insufficient samples message-
1. The first method is to set LBUNUMVALS to one and enter a lab sample. This should allow you to reestablish the bias.
2. Second method would be to set LVMAXHOURS parameter to a certain value say 240 for a case of eight samples entered once a day (24 X 8) plus a safety net of two days ( 24 X 2) and wait for the eight lab values to come in (need to be entered within the 240 hours limit), which would reestablish the bias.
Note that the bias predictions are updated when you either have the set number of valid samples obtained in the specified time (LVMAXHOURS) or have the Accumulated Cusum Error (LBUACUMERR) exceed the user specified parameter Cusum Error Limit (LBUCUSUMLIM) at any point of time. The bias predictions will be automatically updated when LBUACUMERR > LBUCUSUMLIM even if the number of samples entered/collected is less than LBUNUMVALS.
Consider a case where you have an IQ application with LBUCUSUMLIM at 0.4, LVMAXHOURS at 48, and LBUNUMVALS at 8. The lab bias for this application will only be updated when either- a) you have 8 good samples within a period of 48 hours, or b) the calculated value of LBUACUMERR exceeds 0.4. The lab bias would not be updated if you do not have the necessary number of good samples in the specified interval and LBUACUMERR is less than the value specified for the Cusum Error Limit (0.4). Note that LBUACUMERR is not an absolute value and the incoming samples might be taking this further away from the Cusum Error Limit parameter you have specified (+0.4 in this example). In such a case, the IQ solver can only update the bias when it has LBUNUMVALS number of Good samples available in the time specified by LVMAXHOURS.
This provides us a third (but not so elegant) way to reestablish the bias in the next available lab sample (without setting LBUNUMVALS to 1). This can be accomplished by checking the LBUACUMERR and setting the LBUCUSUMLIM parameter to a value less than LBUACUMERR. When the next valid lab sample comes in, the solver would notice that LBUACUMERR > LBUCUSUMLIM and thus reestablish the bias. You could reset the LBUCUSUMLIM to the required value once you have reestablished the bias.
Keywords: Insufficient Samples, Cusum, LVMAXHOURS, LBUNUMVALS
References: None |
Problem Statement: Is there information available for Aspen IQ TDC3000 package 1.17? | Solution: The Aspen IQTDC3000 Package V1.17 is a services tool used to provide CL and displays for the Honeywell TDC3000 and AppNode systems. This is not a product and is not supported in the same manner as a product. Version 1.17 is the latest available version.
Keywords: None
References: None |
Problem Statement: This article describes how to deal with bumps caused by analyzers drifting from lab results when changing UPDSRC. | Solution: The bump that you experience when switching Aspen Inferential Qualities (IQ's) UPDSRC between 2 (lab) and 3 (both lab and analyzer) is due to a difference in the bias that has to be applied to the unbiased prediction in the PR (Prediction) module in order to match the prediction to the ?real world? value.
The AZU (Analyzer Update) and LBU (Lab Bias Update) modules independently calculate a bias to be added to the unbiased prediction in order to match the Analyzer or Lab result. If the analyzer and the lab give identical results, then both IQ biases will be essentially the same, and it will basically be bumpless when switching UPDSRC.
The bump occurs because the analyzer and the lab do not match. There are different ways to deal with this depending on what you want to accomplish when the UPDSRC changes.
Analyzer drift correction: the AZU and LBU have parameters that allow them to work together and bias the analyzer readings to ?match? the lab results. Because the ?drift-corrected-analyzer? result is closer to the lab result, it will be ?nearly-bumpless? when UPDSRC changes.
Bias filtering: the bias change caused by UPDSRC can be filtered in over time using parameters in the PR module. In other words, instead of bumping the process with a step change to the prediction, you could filter in the bias change over 30 minutes (or whatever is appropriate for your process).
Calibrate the analyzer and/or the lab equipment to give the same results. This could be done in the instruments or in the DCS. Details for this are outside the scope of this document.
At any time, you can examine the difference in Aspen IQ's AZU and LBU biases to see how far the analyzer is from the lab value and how big the bump will be if UPDSRC changes.
Keywords:
References: None |
Problem Statement: When launching the Integration Framework Windows Service Access Diagnostic tool, the following error message may be received: Could not find the framework.
This Knowledge Base article provides steps to resolve the above error message. | Solution: To resolve the issue, delete the files AppAccQueue.xml and DocExQueue.xml, located in ..\ProgramData\AspenTech\Enterprise\Integration\Framework\Configuration and restart the AspenTech Enterprise Integration Framework service which will recreate the files.
Keywords: Error occurred in verifying that MSMQ Message Queuing could be read
Windows Services Access
References: None |
Problem Statement: Excel calculations return error message (Windows NT only). Error executing calculation: Error Getting Excel Server Dispatch | Solution: Give your account DCOM default launch permissions. To do so, perform the following steps:
Run dcomcnfg. The Distributed COM Configuration Properties dialog box is displayed.
Select the Default Security tab and click Edit Default in the Default Launch Permissions frame. The Registry Values Permissions dialog box is displayed.
3 - Click Add and select your user name from the correct domain.
4 - Click OK on the dcomcnfg dialogs.
5 - Restart the Aspentech Calculator Service from Control Panel.
Keywords:
References: None |
Problem Statement: Where are the Informatica Powercenter license files located? | Solution: The license files are extracted as part of the Aspen Supply Chain Connect (ASCC) installation and will be located on the server where you installed ASCC.
The file names are:
Aspen_Technology_production_Standard.key
Aspen_Technology_production_Standard_REALTIME_Incremental.key
ias_license.xml
Keywords: License Keys
References: None |
Problem Statement: How do I resolve the error: Unable to connect to Aspen CalcAutomation error. The specified service does not exist as an installed service error message when configuring Aspen Inferential Qualities' IC module? | Solution: Go to Control Panel \ Administrative Tools \ Services and check the AspenTech Calculator Engine service status.A If the service is stopped, select it, right click and press Start.
If the AspenTech Calculator Engine service does not appear in the list, go to Program Files \ AspenTech \ Aspen Calc \ Bin and look for a??CalcScheduler.exea??, this is the file related to the a??AspenTech Calculator Enginea?? service.
Go to a DOS prompt, type the path to the folder (i.e. cd C:\Program Files\AspenTech\Aspen Calc\bin), then type CalcScheduler/install. Go back to the Services Panel and now the service must be available.
Keywords: IQConfig, IC, Formula Library, AspenTech Calculator Engine, CalcScheduler.exe
References: None |
Problem Statement: When trying to execute an Excel Calculation in Aspen Calc, the error Class not Registered occurs. | Solution: To fix this problem, add the account that is running the calculation to default access and launch and activation permissions under Component Services. The steps below detail how this is done:
1. Open Control Panel | Administrative Tools | Component Services
2. Expand the Component Services object to the item named My Computer
3. On the My Computer level, right mouse click and select Properties. On the properties menu, select the COM Security tab.
4. In the Access Permissions section, add the user account attempting to execute the Excel calculation under the Edit Default button. Repeat for the Launch and Activation permissions.
5. Restart Aspen Calc and attempt to execute the Excel calculation.
Keywords:
References: None |
Problem Statement: Troubleshooting errors with Excel Add-ins when upgrading to v2006.5, V7.1, Office 2007 or after Microsoft security patches have been applied.
There have been numerous problems reported against the Aspen Process Data and Aspen Batch Excel Add-ins as a result of Microsoft patches or upgrades of Microsoft Excel. This Knowledge Base article is an all inclusive troubleshooting guide. Please follow each step until your issue has been resolved. | Solution: Use the following steps to diagnose and correct problems with AspenTech Process Data or Aspen Batch Add-ins introduced when upgrading Microsoft Office or after applying Microsoft security patches:
1. The location of the Add-in files: Aspentech recommends that only one copy of the Excel Add-in files be loaded on the machine and it should be located in the <drive>:\Program Files\Microsoft Office\Officexx\library where xx is the version of Microsoft Office currently loaded on the client computer. For example Microsoft Office 2003 will be called Office11. Opening Excel gives error: Compile Error in Hidden Module: B21Menus
2. Process Explorer and Aspen Process Data were installed using a Silent Install script. The error message is a result of the TimeDialogs.exe file not being properly registered during the silent install. Aspen Process Data Excel Add-in gives error: Compile error in hidden module: Atglobal
3. The error message Compile error in hidden module: frmGetHandles appears after the user has applied Microsoft Security Advisory: Update Rollup for ActiveX Kill Bits. See MS KB article http://support.microsoft.com/kb/960715 for more details. Excel Addin error Compile error in hidden module: frmGetHandles when trying to launch the Find Batch Handles dialog box
4. The error message Compile error in hidden module: frmGetHandles appears after the Microsoft Security Update for Microsoft Office 2003 (KB974554). Compile error in hidden module: frmTrendData
5. If you install an AspenTech product that installs Microsoft Visual Basic for Applications (VBA) on a computer that has an earlier version of VBA, you may experience problems. Excel spreadsheet using the Aspen Add-ins cannot be opened properly.
6. Microsoft security patches that obsolete Grid32.ocx made it necessary for Aspen to replace Grid32.ocx with MSFlxGrd.ocx in the Aspen Process Data Excel Add-In. Aspen Process Explorer v2006.5 Engineering Release (ER) PE091217-December 2009
7. Across various versions of the Process Data Add-In, the following error may occur: Excel Add-In error 91 object variable or with block variable not set. This error may occur on systems where Regional Settings specify a language other than English. In that case certain registry values are written in the localized language, and the Add-In fails to read them. Excel Add-In error '91 object variable or with block variable not set'
8. If none of the above suggestions resolve the problem that you are having then:
Uninstall MS Office
Uninstall AspenTech products
Rename C:\program files\Aspentech
Rename C:\program files\Microsoft Office
Rename C:\program files\Common files\Aspentech
Opened registry and delete HKey_Local_Machine\Software\Aspentech
Reinstall everything
Keywords: Excel Add-In
VBA
frmTrendData
frmGetHandles
References: None |
Problem Statement: After upgrading from version 2004.2 to 7.1, Aspen Process Data Add-in in Microsoft Excel does not work | Solution: Apply the latest patches for Process Explorer, Process Data and SQLPlus.
Aspen Process Explorer version V7.1.5 ER Patch DT050410C.WIN (May 2010) (128957) (updated 16-Jun-2010)
Aspen Process Explorer version V7.1.5 ER Patch DT060210C (June 2010) (129096) (updated 10-Jun-2010)
Aspen Process Explorer Cumulative Patch 7.1.5 - Nov, 2009 (127717) (updated 25-Nov-2009)
Aspen Process Data V7.1.5 Patch - DT031110D.WIN - April 2010 (128760) (updated 16-Apr-2010)
Aspen Process Data V7.1 Cumulative Patch (7.1.5) - November 2009 (127715) (updated 25-Nov-2009)
Aspen SQLplus V7.1.5 Client Engineering Release IP100303Y (March 2010) (128583) (updated 26-Mar-2010)
Aspen SQLplus Cumulative Patch 7.1.5 - November 2009 (127719) (updated 25-Nov-2009)
Keywords: Excel
Add-in
update
upgrade
data
References: None |
Problem Statement: Why is the time input for a lab update set to one hour in the past?
Even when the online and web server have synchronized system clocks when I enter a lab sample the default time stamp is one hour in the past. | Solution: The default time is intentionally calculated to be 1 hour back from current time (actually the last run time) since IQ requires historical data of the predictions at sample time. This default only applies for the first entered sample. After you have entered one or more samples, IQ will use the previous sample times to come up with a more reasonable default timestamp value for the next sample.
IQ internally maintains all timestamps in UTC. However, the timestamps displayed to user in PCWS are always converted to local time. You do not need to do anything special to align timestamps for IQ.
Keywords: Aspen Inferential Qualities, Lab Sample, PCWS
References: None |
Problem Statement: If Aspen Framework or Aspen Local Security is used to create a database with a version of Microsoft SQL Server which does not use isql.exe to process database commands, creating the AFWDB database will fail with the following error:
Failed to launch isql process: error code=2; the system cannot find the file specified | Solution: The two Microsoft SQL Server programs osql.exe and isql.exe are very similar. Therefore, the problem can be worked around by the following procedure.
1. Make a copy of osql.exe.
2. Rename the copy of osql.exe to isql.exe
3. Restart the Aspen Framework database creation tool to create the AFWDB database
4. After the AFWDB database is successfully created remove isql.exe from the server
An alternative approach is to run the database creation scripts manually according to the following procedure:
1. Run afwdb_tables.sql and podb_tables.sql found in
<DVD Drive>:\aspenone2006admdvd\afw\afw2006
This will create the necessary database tables.
Keywords: None
References: None |
Problem Statement: The error message which is generated when trying to configure a logical device, suggests that the Aspen CIM-IO manager is not running.
The error message contains the following:
There was an error communicating with the CimIO Manager.
This may indicate that windows service is not running.
The Cim-IO Manager is used to help create your server configuration(s). | Solution: The cause for this error is a firewall running on the CIM-IO server machine. Try disabling the local firewall. For a long-termSolution, make sure you have exceptions marked on the firewall for the ports CIM-IO is using. Further information on the firewall ports is included onSolution ID: 110683 Installation of firewall: What is used for communication between IP.21 and CIM-IO server?
Keywords: CIMIO
Firewall
References: None |
Problem Statement: The last step of the Informatica PowerCenter installation gives the following error:
Use the error below and catalina.out and node.log in the server/tomcat/logs directory on the current machine to get more information. Select Retry to continue the installation. | Solution: This error will occur when the previous installation of PowerCenter Server 8.x was not uninstalled properly. The install detects the presence of an existing installation and would not allow further installation. You need to clean the Windows registry entries and allow a fresh installation.
To resolve the issue do the following:
- Click Start, click Run, type regedit, click OK.
- Go to the following registry key:
HKEY_LOCAL_MACHINE\
SYSTEM\CurrentControlSet\Services\InformaticaServices8.x
- Rename the InformaticaServices8.x key (example:
InformaticaServices8.x.old ).
- Reboot the Windows machine.
- Re-install PowerCenter server (Informatica Service).
Keywords: None
References: None |
Problem Statement: How can you enable and collect additional logging for the Aspen Process Data Excel Addin? | Solution: Run one of the two attached registry files depending on if the operating system of the machine is 32 or 64-bit.
Verify that the registry key change exists after running the registry file.
Note that with a 64-bit operating system, the key will be located in HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{0C74D026-0172-11D2-BE0C-00805F710570}\Debug
And with a 32-bit operating system, the key will be located in HKEY_CLASSES_ROOT\CLSID\{0C74D026-0172-11D2-BE0C-00805F710570}\Debug
The Path string that references the C:\Temp\ location is not the location of the log file. The log file will appear in C:\ProgramData\AspenTech\DiagnosticLogs\ProcessExplorer and the name of the log will be in the format of ProcessDataAuto.<username>.log
Keywords: Excel addin
Process Data
logging
Debug
References: None |
Problem Statement: How to declare constants on a high level so every calculation can use them ? | Solution: Use a formula with no parameters to declare constants that can be used by every calculation
This is the way that we used for PI. PI is a built-in formula that you can use in any calculation. Example:
area = Pi()*r^2
You could define other constants the same way. The definition of the formula can be a simple CalcScript. Example
returnvalue=3.141592654
Keywords: aspencalc
calc
constent
References: None |
Problem Statement: After initially loading an IQF with an analyzer-based IQ using the DMCplus Model File (.MDL) option, the prediction information shows up as bad (-9999). | Solution: An inferential quality (IQ) built using the DMCplus Model File (.MDL) option for the Prediction (PR) module requires a good initial value of the actual measurement (generally an analyzer reading) in order to initialize the dynamic model prediction. However, this by itself is not enough - the PR module must be configured with the proper Bias Update Source (UPDSRC) parameter value.
UPDSRC has four legal values:
0 Manual Entry Bias can be updated manually
1 Analyzer Bias is updated with the analyzer value
2 Lab Bias is updated with the lab value
3 Both Analyzer and Lab Use both lab and analyzer values to update the bias
The problem here typically arises because the default value for UPDSRC in IQconfig is 0 (Manual Entry). This value is generally specified as a LOCAL variable in the IQF, which means that it can be changed online using Aspen IQview. Until this value is changed to 1 (if only an Analyzer Update (AZU) module is configured), or 3 (if both Analyzer Update and Lab Update (LBU) modules are configured), the analyzer-based inferential predictions will continue to show as bad. Therefore, if you forget to change UPDSRC from the default value, you will see bad values in your analyzer-based inferential predictions.
UPDSRC can be changed in either the IQF, via Aspen IQconfig, or via Aspen IQview. If the change is done via IQview, make sure to archive the IQ context to an IQF (via an IQmanage Save an application context to an IQF command) to prevent an overwrite of the UPDSRC option the next time that the IQF is loaded. The archival can be done using the Aspen IQ Context Menu in Aspen IQmanage.
Once UPDSRC is properly configured, the analyzer predictions will become good as soon as a new valid analyzer value is received. It is not necessary to initialize the analyzer prediction as well.
Keywords: Aspen IQ
Aspen IQconfig
Aspen IQview
UPDSRC
References: None |
Problem Statement: Aspen IQ is generating an AspenCalc error | Solution: The most common explanation for an AspenCalc error message while working with Aspen IQ is the result of the Aspen Calculator not running. The first recommendation is to go to the Serviced panel, in Control Panel / Administrative Tools and verify that the Aspen Calculator Engine appears in the list. If it is not in the list, there may be have been a problem with the installation and a re-install of the application is warranted. The Service should be running before Aspen IQ attempts to use it. If the service will not start, highlight the service, right click and go to properties and then to the logon tab. Confirm the account and password that should be starting the service. If the user is trying to start it manually, then that user account and password can be provided. The changes should be saved and the service should then start up.
Keywords: AspenCalc, IQ desktop, IQ Online
References: None |
Problem Statement: The .out and .err files are being filled with a recurring message similar to the following:
DSIGNAL::recvfrom() failed Error code: 10038
This has been known to use up all of the available disk space and cause controllers to stop.
The .out and .err files typically associated with a process that is using the Dais Trader,
would include ACOMSGSRV, apollo_viewsrv, dmcp_viewsrv, IQLINKSRV and smartstep_viewsrv.
This symptom may not be limited to these processes, however we have not yet seen this behavior with other process that do not specifically use the Dais Trader. | Solution: Confirm that the network card is set to Full Duplex.
A recommendedSolution is to run ACOBASE Shutdown. Delete the culprit file. Go to the AutoStartList.txt file,
found in the Program Files / AspenTech / AC Online / sys / etc directory.
Add the following entries to the process generating the culprit .out and / or .err file:
STDOUT=NUL
STDERR=NUL
The AutoStartList.txt should look like this:
PROCNAME=IQLINKSRV
SEQNUM=80
STDOUT=NUL
STDERR=NUL
APPPATH=$ACODHOME\bin\iqlinksrv.exe
APPTYPE=1
The addition of these lines can be made to any process that generates an .out or an .err file.
This will not disrupt the running of the process, only prevent the re-occurring message from filling up the file and ultimately the disk.
The AcoBase Startup should then be run to restart the system and the processes with the new NULL settings.
Keywords: null, stdout, stderr, Aspen IQ, PCWS, WebServer
References: None |
Problem Statement: User would like to upgrade to Informatica Powercenter 9.x software for Aspen Supply Chain Connect (ASCC). Is this supported? | Solution: At this time, Informatica Powercenter 8.6.1 is the only supported release for V7.3 ASCC. Please review the installation guide which documents this that is attached.
Keywords: None
References: None |
Problem Statement: You would have to programmatically read the list of values of a SelectDef record but it is not clear how this would be best achieved. | Solution: The following Visual Basic code illustrates a way to enumerate the list of SelectDef items associated with an attribute (IP_ARCHIVING in this example) of a given tag:
Dim myProcessData As New AtProcessData.DataSources
Dim myTag As AtProcessData.Tag
Dim myAttribute As AtProcessData.Attribute
Dim selIdx As Long
Dim attrMsg As String
Set myTag = myProcessData.Item(YourDataSource).Tags.Add(YourTag)
Set myAttribute = myTag.Attributes.AddAttr(IP_ARCHIVING, False)
myTag.Attributes.Read False
If (myAttribute.Format = apdFormatSelector) Then
selIdx = 1
While (selIdx <= myAttribute.SelectorInfo.Count)
attrMsg = attrMsg + CStr(myAttribute.SelectorInfo.Item(selIdx).Number)
attrMsg = attrMsg + :
attrMsg = attrMsg + myAttribute.SelectorInfo.Item(selIdx).String
attrMsg = attrMsg + Chr(10)
selIdx = selIdx + 1
Wend
MsgBox attrMsg, vbOKOnly, Selector Info
End If
Keywords: VBA (Visual Basic for Applications)
AtProcessData library
Documentation for Process Data
References: None |
Problem Statement: You have a requirement to remove LDAP configuration from your ASCC / Informatica environment. How is this done? | Solution: There are a couple of ways to remove LDAP configuration from Powercenter.
The first would be via the Admin console:
For setting up LDAP Authentication, you will have to add the required LDAP Server details and the users/groups information to PowerCenter.
To add the details, do the following:
1. Open the PowerCenter Administration Console and click Configure Security > Configure LDAP Connectivity > Security Domains and Synchronization Properties
2. Clear out the LDAP server details:
3. Under Security Domains tab, Choose Delete under Security Domain.
The second would be via command line:
You can use infacmd setLDAPConnectivity to set the ldap_server_address to an empty string.
Example:
setLDAPConnectivity -dn domain_name -un user_name -pd password -la
Following is the full usage of the command:
setLDAPConnectivity <-DomainName|-dn> domain_name
<-UserName|-un> user_name
<-Password|-pd> password
[<-SecurityDomain|-sdn> security_domain]
[<-Gateway|-hp> gateway_host1:port gateway_host2:port...]
[<-ResilienceTimeout|-re> timeout_period_in_seconds]
<-LDAPAddress|-la> ldap_server_address
[<-LDAPPrincipal|-lp> ldap_principal]
[<-LDAPCredential|-lc> ldap_credential]
[<-UseSSL|-us> use_ssl]
[<-TrustLDAPCertificate|-tc> trust_ldap_certificate]
<-LDAPType|-lt> ldap_types=MicrosoftActiveDirectory, SunJavaSystemDirectory, NovellE-Directory, IBMTivoliDirectory, OpenLDAP
[<-MaxSecurityDomainSize|-ms> Max_Security_Domain_size]
[<-GroupMembershipAttr|-gm> LDAP_Group_Membership_Attribute]
More Information
When the LDAP configuration has been entered incorrectly, the LDAP configuration might no longer be changed using the Administration Console. (Messages 'Loading users...' and 'Loading data...' are displayed, and interface no longer responds)
In these cases, the command line option can be used to correct or disable the settings.
Keywords: None
References: None |
Problem Statement: This | Solution: illustrates the format of Base directory present in syntax of the getcalcobject function in AtAspenCalc.dll .Solution
Following is the procedure to get the function GetCalcObject:
Create a new Visual Basic project from Microsoft Excel (Tools--> Macros-->Visual Basic Editor)
In the new Microsoft Visual Basic workbook created, go to Tools-->
Keywords: COM Object
Function
getcalc
basedir
References: s and add Ataspencalc.dll located at C:\Program Files\Common Files\AspenTech Shared. This references all the COM Objects represented by this dll. Check all the objects related to Aspen Calc (like Aspen Calc, Components, utilities..)
After the objects are added, go to View-->Object Browser in the Tool bar. Select AtAspenCalc Library then AtCalcEnvironment followed by GetCalcObject function.
Function GetCalcObject(Name As String, basedir As String) As AtCalculation Member of AtAspenCalc.AtCalcEnvironment
The basedir (depends on install path) in the above Function is C:\Program Files\AspenTech\Aspen Calc but Not C:\Program Files\AspenTech\Aspen Calc\Calc
For 2006.5 and later the basedir can be queried programmatically. To do this call the IAtCalcBase.GetCalcBase() method from AtAspenCalcUtilities.dll. The IAtCalcBase interface does not exist in versions of this dll prior to v2006.5. |
Problem Statement: Why I am getting Bad Unbiased Prediction in Combined status and Lab bias value of zero for the previous day's samples when its lab update comes on the next day? | Solution: Aspen Inferential Qualities uses previously stored value of predictions (in the IQ history file) in order to perform bias updates. IQ marks the point when the lab sample taken flag is activated. When the lab sample value becomes available, this value is placed in the appropriate location in the history file and the corresponding historical prediction values are retrieved to perform the bias update calculation.
The parameter called DCMAXREC in the IQF configuration file defines the maximum number of records stored in data collection history file. The data collection history file contains synchronous data points stored at the update frequency specified as DCUPDFREQ seconds (data collection update frequency in seconds). The history file stores the information in a cyclic fashion, overwriting the oldest record after the maximum number of records is reached.
The default value for DCMAXREC in an IQF file is 1440 (24*60 min, assuming an execution frequency of once every minute) i.e. data will be stored/read for only a day. This means that if the lab update for any sample is entered 24 hours or 1440 min after it was sampled (sample taken flag activated), the lab value will not be detected and hence the lab bias for the sample will be 0 and combined status for this sample will be Bad Unbiased Prediction.
One way to overcome this problem is to set the value for DCMAXREC to 2880 (2 days) or 4320 (3 days) instead of 1440 depending on how long it generally takes for the lab sample value to be entered after the sample is taken.
Note: The DCMAXREC can only be changed offline, i.e., once the change has been made, the IQF file would need to be reloaded in order for the change to come into effect.
Another reason for a value of 0 in Lab bias could be that CIMIO failed to read some value and thus couldn't generate an unbiased prediction. If the time stamp of the input lab data is of that time when either CIMIO or any other service related to IQ is down, then this message will appear. Input data time stamp has to be for the time when CIMIO is running.
Keywords: Bad unbiased prediction
DCMAXREC
Lab Bias update
DCUPDFREQ
References: None |
Problem Statement: This Knowledge Base article answers the following question:
What are the differences between Use server aggregate methods and Use Process Data aggregate methods in Aspen Process Data (OPC HDA)? | Solution: The Aspen Process Data (OPC HDA) service is used by Process Data applications such as Aspen Process Explorer and aspenONE Process Explorer to access data from OPC HDA servers. It comes with two options for calculating aggregate methods:
· Use server aggregate methods, and...
· Use Process Data aggregate methods
When deciding which option to use, the following should be taken into account:
Select Use server aggregate methods if you want the OPC HDA server to calculate aggregates, such as Average, Minimum, and Maximum. This option offers the most efficient calculation of aggregates, but the OPC-HDA server has to support aggregates.
-OR-
Select Use Process Data aggregate methods if you want Process Data to calculate aggregates, such as Average, Minimum, and Maximum. This option provides consistent aggregate calculations with other Process Data servers and can be used with OPC HDA servers that do not support aggregates.
Additional Information
The aggregate methods supported vary from OPC-HDA server to OPC-HDA server. If the aggregate method not supported by the OPC-HDA server is one of the standard methods that Process Data supports (min, max, avg, good, not good, range, sum, variance, std dev), then Process Data will request actual data from the server and compute the aggregate value from the actual data.
There are some additional aggregate parameters that Aspen Process Data supports, like Integral or Time Method, Start of Day vs Start of Time, and Timestamp Anchors. When Process Data is making the aggregate request directly from the OPC-HDA data server, these additional parameters will not be used. However, if Process Data is computing the aggregate based on the actual data from the OPC-HDA server, these additional parameters will be applied.
For example, if an OPC-HDA server does not support the aggregate method average, when a user requests a 5 min aggregate average over 8 hours, Process Data will request actual data from the server and then perform calculations to get the 5 minute aggregate averages from that data. Under these circumstances, the additional parameters, like Timestamp anchor will be applied. However, if the OPC-HDA server supports the aggregate method minimum, then Process Data will be getting the minimum aggregate values directly from the OPC-HDA server, and the additional parameters, like Timestamp anchor will not be applied. Changing the anchor from Begin to Middle would not affect the results that are returned.
Keywords:
References: None |
Problem Statement: When a spreadsheet that uses Aspen Process Data COM Add-in is published to SharePoint 2010 Excel Service on a Microsoft SharePoint server which is not part of a trusted domain, the following error messages may be received:
- Error:Invalid DataSource, when the Aspen Process Data Service is disabled / stopped in the Aspen InfoPlus.21 (IP.21) server and removed from the ADSA data source of the client PC and SharePoint server;
- Error:The server has rejected the client credentials, when the Aspen Process Data Service is running in the IP.21 server and configured in the ADSA data source of the client PC and SharePoint server.
This Knowledge Base article provides steps to resolve the above error messages. | Solution: The Aspen Excel COM Add-in uses a service in the Aspen Data Source Directory (ADSA) server called Aspen Process Data Service. This service uses Windows Communication Foundation (WCF) framework to send data as asynchronous messages from one service endpoint to another. WCF requires that the user on a client system be authenticated when making calls to the server. This presents a problem when the user credentials on a client system, which is not part of a trusted domain, cannot be verified by the server.
The above-mentioned authentication issue can be resolved by including the tags shown below in the “system.web” section of the Aspen Process Data service configuration file (AspenTech.PME.ProcessData.WindowsService.config), and restarting the Process Data service on the IP.21 server.
<authorization>
<allow users=* />
</authorization>
A sample configuration file is attached to this KB article.
Keywords: Error:Invalid DataSource
Error:The server has rejected the client credentials
References: None |
Problem Statement: Deployment of Aspen CIM-IO software across a WAN (Wide Area Network) link can be problematic due to the latency inherent to these types of connections. | Solution: In this scenario we are discussing a WAN connection between the CIM-IO Server and the CIM-IO Interface, ie. if there is a WAN between CIM-IO Core and the Server running the CIM-IO Interface software and/or DCS.
Users may see error messages in the CIM-IO message log on the CIM-IO Server and CIM-IO Client of the type:
CIMIO_USR_GET_RECEIVE, Error receiving a GET reply from device
CIMIO_MSG_RECV_TIMEOUT, Time-out trying to receive a message
Since it is not possible to rely on CIM-IO Store and Forward to resolve timeouts and connection drops in the above scenario, it is important to design and maintain the WAN link to be as efficient and latency free as possible. Store and Forward is a mechanism which allows for buffering of data if the link between the CIM-IO Server and CIM-IO Client (typically Aspen InfoPlus.21) is lost. In this instance a data file will be created whilst the connection is reinstated and then data is able to unbuffer.
In deploying a CIM-IO Server communicating across a WAN to a DCS, there are baseline factors which must be adhered to:
Latency must be kept to a minimum. Typically a measure of 300ms or more is considered too high for most TCP/IP based communication, and any measure over this may result in loss of connection and ability to receive data from the DCS
Number of network hops should be minimized as much as possible. This strongly ties in to the above as any device, be that a router, ISA server or firewall will add to the latency of the network.
Firewalls must be configured to allow traffic across them for communication from the DCS to the CIM-IO Server and back
There are certain mechanisms within AspenTech software which can assist if deploying CIM-IO connectivity over highly latent networks:
It is strongly advised for GET transfer records within the Aspen InfoPlus.21 database to be set to communicate via Asynchronous communication. This is due to synchronous transfers requiring a response to be received before communication can continue and before any subsequent request can be made. In a highly latent network this will cause communication issues in itself. This feature is turned on in the GET record by changing the IO_ASYNC? field to YES. This is covered in the CIM-IO User's Guide documentation
Settings of the IO_TIMEOUT_VALUE field should be checked. This field allows to specify the timeout value that the main CIMIO client task is to use during synchronous read operations, and by default this is set to 5seconds. As mentioned above if the network suffers from high latency it is recommended to use asynchronous transfers and for asynchronous transfers the time-out value is the expected maximum time the client will need to send the request to the server and receive an acknowledgement.
Every WAN is of course different to the other and the above comments are guidelines for the user to consider. AspenTech relies on the network to be responsive and to not suffer from undue latency, as such we advise our customers to, where possible, deploy across local area networks or networks with low latency.
Keywords: WAN
DCS
CIMIO
References: None |
Problem Statement: Normal data collection from the Aspen Cim-IO server works properly. However when the system goes into Store mode, the Store file is not created. The cimio_msg.log may have the following messages:
CIMIO_SF_STORE_SEND_REPLY_CREATE, Error creating store file
CIMIO_SF_FILE_OPEN_OPEN, Error opening file
System Error, errno=13 Permission denied | Solution: The account running the Aspen Cim-IO Manager service on the Cim-IO server must have Read&Execute, Read, and Write permissions to the folder where the store file resides.
Keywords: None
References: None |
Problem Statement: Enhanced Aspen Cim-IO diagnostics records a large amount of information to the diagnostics log file (C:\Program Files\AspenTech\CIM-IO\log\cimio_diag.log). In many cases, it is desirable to control the type of information that is logged to the file. Category parameters in the configuration file (C:\Program Files\AspenTech\CIM-IO\etc\cimio_diag.cfg) can be used to achieve this goal.
Information in this article is intended to supplement the Aspen Cim-IO diagnostics information in the Aspen Cim-IO User's Guide. | Solution: Syntax for Category parameters in the configuration file (C:\Program Files\AspenTech\CIM-IO\etc\cimio_diag.cfg) is as follows.
Category, Message-DETAIL-MESSAGETYPE-TRANSFERTYPE
Available options for DETAIL include HEADER,CONTENT_HEADER and CONTENT.
Available options for MESSAGETYPE include REQ, REPLY, NOTIF.
Available options for TRANSACTIONTYPE include GET, GETHIST, PUT, DECL, CANC, UNS, STOPPUT, STOPGET, CONNECT, DISCONNECT.
Category parameters accept wildcards (*) as in the example below.
Category, Message-*-*-*
Category parameters also accept any combination of specified parameters, as in the following example.
Category, Message-*-REQ,REPLY-GET,PUT
DETAIL
The DETAIL parameter tells the Cim-IO diagnostic engine the level of detail for messages sent to the cimio_diag.log file. Options for the DETAIL parameter are listed below.
HEADER - Header information logs general information regarding the message being passed by the Cim-IO processes. An example of a message header is below.
+------------------- Message Header ----------------------+
Message Type = REQ Transaction type = PUT Priority = 1 Trans no = 1132207725
Message Size = 610 Header Size = 292 Template Size = 192 Data Size = 126
Message Source Service = TSK_M_MATRIKON_200 Node = HKLAP
Message Destination Service = CIOMATRIKONOPCS Node = HKLAP
Request Source Service = TSK_M_MATRIKON_200 Node = HKLAP
Reply Destination Service = TSK_M_MATRIKON_200 Node = HKLAP
CONTENT_HEADER - In addition to logging the normal HEADER information, the CONTENT_HEADER parameter will log such information as the listid of the transfer record (which will correspond to the recid of the transfer record in the Aspen InfoPlus.21 database), the logical device name, data transfer type and number of tags to be transferred. An example of the extra information that the CONTENT_HEADER parameter will log is pasted below.
+------------------- Content Header ----------------------+
Listid = 2050, Num Tags = 1, Device= CIOMATRIKONOPCS, Unit= 0, Acc Type = SYNC, Intid Flag = 0
CONTENT - In addition to logging all of the HEADER and CONTENT_HEADER information, the message CONTENT flag will allow the specific data contents which are passed between the Cim-IO client processes to be logged. The example below shows that 1 ascii tag, with a size of 6 characters and a value of HELLO! was logged to the cimio_diag.log file. The tag name on the OPC server is write only.String.
NOTE: If each transfer record contains several tags, enabling the CONTENT option will cause the cimio_diag.log to grow large very quickly.
+------------------- Message Content ---------------------+
Tag IntID1 IntID2 Out Flag Type DType Size Value
----
Keywords: None
References: None |
Problem Statement: After stopping and restarting the Cim-IO server, typically at least one history occurrence for tags in the Aspen InfoPlus.21 Administrator will exhibit the following characteristics.
The Timestamp is 1/10th of a second after the last successful entry before the Cim-IO server shutdown
The IP_TREND_QSTATUS = Unavailable
The IP_IP_TREND_QLEVEL = Bad
As a result, when these tags are plotted in Process Explorer, the bad status causes an 'x' and a gap to be placed on the trend plot--representing the Cim-IO server down time.
In other cases, the unavailable occurrences is not written to tag history. | Solution: Cim-IO client tasks run on the Cim-IO client machine (InfoPlus.21 server). If running, the tasks send ping messages to the Cim-IO server to confirm that a connection exists. The ping messages are not a typical network ping. Instead, they are a Cim-IO message--in the same way that a Cim-IO GET or PUT is a Cim-IO message. These Cim-IO messages pass through firewalls whereas network pings may not.
The client tasks that send the Cim-IO ping messages are the main task (TSK_M_xx), the asynchronous task (TSK_A_xx), and the unsolicited task (TSK_U_xx). In version 2004 and above, ping messages are also sent by the TSK_Detect.
The frequency of ping messages can be set as a registry entry on the Cim-IO client (InfoPlus.21 server). The registry entry (HKEY_LOCAL_MACHINE\SOFTWARE\AspenTech\CIM-IO\CimioPingFrequency) has a default value of 60 seconds.
A second registry key--HKEY_LOCAL_MACHINE\SOFTWARE\AspenTech\CIM-IO\CimioMaxPingFailures--is also of interest.
The presence of an unavailable occurrence in a tag's history is dependent upon the product of the two values (CimioPingFrequency and CimioMaxPingFailures). Using the defaults of 60 and 3, the resulting product is 180 seconds. In such a case, if the Cim-IO server has been shutdown or stopped for 180 or more seconds (3 or more minutes), an unavailable occurrence will be written. If the shutdown is less than 3 minutes, the occurrence will not be written.
These registry key values settings can be modified. However, the values should not be set too small. If the product of the two is too small, misleading unavailable IP_TREND_QSTATUS entries (due to brief network glitches) may be recorded.
Keywords: Cim-IO
data
unavailable
IP_TREND_QSTATUS
References: None |
Problem Statement: What can be possible options to handle PIMS Simulator Interface (PIMS-SI) server files when the user wants to switch from the use of PIMS SI to PIMS AO? | Solution: Following are some of the options with PIMS AO depending on the usage of PIMS SI:
1. If the use of PIMS-SI is not critical, then just remove the servers from the model tree and don’t update the model.
2. If PIMS-SI is used to call an Excel workbook for use with SPYRO (a 3rd party steam cracking simulation), then the user can consider using Aspen Olefins Regression Calculator (AORC) with SPYRO to generate regressed furnace models that can be attached as external models with PIMS-AO.
3. If PIMS-SI is used with Excel servers or to call EXE programs, then the user will have to consider using Aspen Custom Modeler (ACM) to create DLL’s that can then be used as external models with PIMS-AO.
4. If the equations that are updated with PIMS-SI are fairly simple, putting equations on the Non-linear Equations branch of the PIMS-AO model tree is also a potential option.
Keywords: PIMS SI
PIMS AO
ACM
External model
References: None |
Problem Statement: The following errors may occur when running the Aspen Cim-IO Test application ( CimIO_T_API.exe)
CIMIO_USR_GET_RECEIVE, Error receiving a GET reply from device CIMIO_MSG_RECV_CHK, Error checking connections
CIMIO_SOCK_CHK_RECV_FAIL, Error peeking at socket
System Error, errno=0 No error
CIMIO_SOCK_RD_BROKEN_PIPE, Connection was terminated by peer System Error, errno=54 Unknown error
WNT Error=10060 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | Solution: The errors above generally indicate that the Aspen Cim-IO client processes cannot access the Aspen Cim-IO server processes. If the configuration is OK and the Aspen Cim-IO server processes are running the problem may be related to the Windows Firewall. If the Windows Firewall is active then one suggestion is to disable it. If for some reason the Windows Firewall must be active then add an exception for all Aspen Cim-IO executables including the CimIO_T_API.
Programs and Services exceptions are added through the Windows Firewall window.
Keywords: CIMIO_T_API
Socket
References: None |
Problem Statement: Sometimes, during Cim-IO configuration or while trouble-shooting Cim-IO issues, it?s useful to turn all IO_DEVICE_PROCESSING and all IO_RECORD_PROCESSING off or on.
How can I stop all Cim-IO devices and all record processing? | Solution: The quickest way of doing this is by using SQLplus.
An update statement is required to turn OFF the IO_DEVICE_PROCESSING and IO_RECORD_PROCESSING.
See example below:
UPDATE IOSIMUL
SET IO_DEVICE_PROCESSING = 'ON'; --
UPDATE AspenChem_Get
SET IO_RECORD_PROCESSING = 'ON';
You can also have a statement to check the current state of the logical device processing and the record processing.
SELECT NAME,IO_RECORD_PROCESSING FROM AspenChem_Get;
select NAME,IO_DEVICE_PROCESSING from iosimul;
IMPORTANT: Please note that it?s not advisable to use SQLplus to start all devices at once, as it might cause issues with Cim-IO Server. We strongly advise to start each device one by one, or followSolution ID: 103176 ?How do I perform a clean restart of a Aspen Cim-IO Interface with Store and Forward??
Keywords: Cim-IO
SQLplus
IO_RECORD_PROCESSING
NAME,IO_DEVICE_PROCESSING
References: None |
Problem Statement: How can one force critical Cim-IO processes (e.g. AsyncDLGP.exe and the Store and Forward processes) to restart if they stop unexpectedly? | Solution: This functionality is available with all of the Cim-IO interfaces but the example in thisSolution uses Cim-IO for OPC due to its widespread usage.
With Aspen Cim-IO for OPC there is a process called AsyncDlgp.exe which is critical in the acquisition of process data. If it or any of the Store and Forward processes (cimio_sf_scanner.exe, cimio_sf_store.exe, and cimio_sf_forward.exe) go down unexpectedly then data loss could result. The following procedure enables some functionality that will detect if any of those processes crash and automatically restart them:
1. The functionality is only available when the Cim-IO interface is set up via the I/O Wizard in the Aspen InfoPlus.21 Administrator. If the device already exists and was set up using the manual method involving OPCProperties.exe, cimio_autostart.bat, and cimio_autostop.bat it will not work. Devices set up via the manual method may show up beneath the I/O container in the InfoPlus.21 Administrator but they will have a question mark symbol next to them and there will not be a corresponding devicename.CSD file in \Program Files\AspenTech\CIM-IO\management on the Cim-IO server machine. Note that for 64-bit versions of Windows that the directory will be \Program Files (x86)\AspenTech\CIM-IO\management . To get them to be able to use this functionality they would need to be removed and then added via the wizard.
2. If the Cim-IO device does not exist use the I/O Wizard to create it by right-clicking on the I/O container and choosing Add new device.... Step through the wizard. The key step that enables the restart functionality is in the third screen. Make sure to check the box which says Health Check - Check server processes:
3. If the Cim-IO device already exists and shows up with a dot next to its name (a red dot means the device is down and a green dot means the device is up) one can check on whether this setting has been enabled or not by right-clicking the device and selecting 'Properties'. There's a Server tab on that screen that will reflect the status. If the device is running the selection may not be changed:
If the device is stopped (via right-clicking and selecting 'Stop logical device') the Health Check option will become available:
There are some settings for this functionality that can be reached by right-clicking the device and choosing 'Manager Parameters':
The latter number is in seconds and is how often the processes will be checked (and subsequently restarted if they are down).
Please note that this restart functionality does NOT apply when the processes are stopped deliberately by the user.
Keywords: None
References: None |
Problem Statement: When installing the service pack, the CIM-IO icon is disabled (grayed-out) even though CIM-IO is installed and the service pack has not yet been applied. | Solution: All cio_*.ini files in the \Program Files\Aspentech\Setup\Uninstall directory must reflect the latest major version in order to apply the service pack. Editing an old interface *.ini file to the current version resolves the problem.
For example, a CIM-IO server is at v5 and running both CIM-IO for OPC and CIM-IO for RSLinx. It is then upgraded to v6, but CIM-IO for RSLinx was not upgraded (no longer used) so only CIM-IO for OPC is at version 6.0. When the SP1 install is attempted, the installer will block the CIM-IO upgrade since the CIO-ABD-RSL.ini file indicated that the RSLinx interface is not at version 6.
Edit the second line in the *.ini file so that the version =6.0.0.0
Keywords:
References: None |
Problem Statement: This knowledge base article describes how to resolve the following error:
Invalid value in field IO_ACTIVATION_COS
which is encountered when you attempt to make an Aspen Cim-IO transfer record unusable. | Solution: You can place a 'blank' in the IO_ACTIVATION_COS field to resolve this error.
1. Set IO_RECORD_PROCESSING = OFF
2. Set IO_ACTIVATE? = NO
3. Set IO_#TAGS = 0
4. Use the Aspen SQLplus Query Writer to set the IO_ACTIVATION_COS field to a blank using the following query:
MYRECORD.IO_ACTIVATION_COS = '';
where:
- MYRECORD is the name of your transfer record
- The quotes ( '' ) used in the query are two single quotes with no space in between them
Keywords: None
References: None |
Problem Statement: Setting Aspen Cim-IO redundancy and it's not working as expected.
When forcing Aspen InfoPlus.21 to go to Secondary Aspen Cim-IO system nothing happens, and the Logical Device record in Aspen InfoPlus.21 shows that the IO_Primary_Device and IO_Secondary_Device with a status of OFF.
The CIMIO_MSG.LOG file in the Aspen InfoPlus.21 system may have messages indicating ping failures to the Primary and Secondary systems. | Solution: For proper redundancy operation the Aspen InfoPlus.21 system needs to be able to ping the Primary and Secondary Cim-IO systems, and reverse ping operation from the Primary and Secondary Cim-IO systems to the Aspen InfoPlus.21 system is also required.
See alsoSolution 115616, Configuring Cim-IO redundancy.
Keywords: None
References: None |
Problem Statement: How do I configure Aspen Cim-IO redundancy with Aspen Cim-IO for OPC when the OPC servers are on remote nodes. | Solution: When configuring Aspen Cim-IO redundancy the I\O wizard assumes the OPC servers reside on the same systems as Aspen Cim-IO for OPC. For environments where the OPC servers reside on remote nodes the DEVICE.CSD files must be edited to establish the remote OPC connection.
Following the guidelines in the Aspen Cim-IO Users Guide to configure the Aspen Cim-IO redundant interfaces using the I\O wizard. Once the configuration is complete modify the DEVICE.CSD files on both the Primary and Secondary Aspen Cim-IO interface nodes for the remote OPC server.
1. Stop the Aspen Cim-IO Manager service.
2. Edit the \Cim-IO\Management\DEVICE.CSD file.
3. On the startup command line for ASYNCDLGP.EXE add the following to the end of the line.
-nodenameOPCSERVERNODE Note: OPCSERVERNODE is the OPC Server node name.
4. Start the Aspen Cim-IO Manager service.
Verify the interface starts and connects to the remote OPC server. Look for the “Ready” message in the cimio_msg.log. If OPC connection errors occur they must be resolved before continuing. If the interfaces connect successfully then go to the Aspen InfoPlus.21 Administrator and verify that both Primary and Secondary nodes are running.
Then Stop\Start TSK_Detect and the Cim-IO client tasks for the new device using the Aspen InfoPlus.21 Manager. Test the redundant configuration by verifying the active redundant node for the device in the TSK_Detect record and then stopping the active Primary or Secondary logical device. Observe the behavior in both TSK_Detect and data records to determine if changeover was successful.
Note: Beginning with V8.4 Aspentech introduced the Aspen Cim-IO Interface Manager, and the Aspen Infoplus21 cim-IO connection Manager. Devices configured with these utilities do not require the manual steps outlined in this article.
Keywords: Keywords
References: None |
Problem Statement: When trying to start Cim-IO Manager service from the Services applet, the following error message is received.
Following the instructions in | Solution: ID 106428 did not resolve the issue. Furthermore, a reinstallation of Cim-IO component also did not resolve the issue.Solution
When checking on the Dependencies of the Cim-IO Manager service, it is shown as having No Dependencies as the screenshot below.
When checking the registry in the Registry Editor, it is showing that the Cim-IO Manager service is dependent on the Service called LanmanServer shown in the key DependOnService of AutoStartCIMIO.
1. Go to Start | Run....
2. Type in regedit in the Run dialog box.
3. Click on the OK button.
4. Browse to My Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AutoStartCIMIO.
However when trying to find the LanmanServer registry entry, it cannot be found. The LanmanServer service will be shown as Server in the Services applet. So if it is not installed, it cannot be found in the Services applet.In order to install it, perform the following steps.
1. Go to Start | Settings | Network Connections or type in ncpa.cpl in the Run dialog and click on the OK button.
2. Right-click on the connection used and select Properties.
3. Select General tab if it is not already selected.
4. Click on the Install button.
5. Select Service and click on the Add... button.
6. Select Client and click on the Add... button.
7. Select File and Printer Sharing for Microsoft Networks.
8. Click on the OK button.
In some cases, DependOnService key of AutoStartCIMIO may show other services other than LanmanServer. As such, you will need to ensure that all the dependent services are correctly installed and are shown in the Services applet.
Keywords: None
References: None |
Problem Statement: When a Cim-IO device is selected in the InfoPlus.21 Administrator, the following error appears.
RDBVALS Invalid field type DEVICE_NAME
After clicking OK to close the error window, properties of the device (IO_MAIN_TASK, Nodename, Service, etc.) may not appear. | Solution: The error occurs because a database snapshot from an older version of InfoPlus.21 has been loaded into the database. To resolve the error, it is necessary to upgrade the snapshot using the InfoPlus.21 Database Upgrade Wizard. To launch the wizard, go to Actions | Upgrade Database in the InfoPlus.21 Manager.
Keywords: RDBVALS
invalid field type
device
References: None |
Problem Statement: This knowledge base article explains why the following message can be written to the Windows Event Log. This article also explains how to prevent this message from being written to the Windows Event Log.
The description for Event ID ( 24557 ) in Source ( W3SVC ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: can't open ok browsers file: c:\inetpub\wwwroot\AspenTech\AFW\Security\rbv\ok_browsers.txt, continuing.
Note: The file ok_browsers.txt will not exist in the directory mentioned in this event message. | Solution: This message is informational and does not indicate a problem. This message is generated by a component of Aspen Framework named Aspen Web-based Single Sign On (Aspen WebSSO). This event message will no longer be logged once Aspen WebSSO is disabled. Aspen WebSSO can be disabled by the following two steps.
1. Add the value Disable under HKEY_LOCAL_MACHINE\SOFTWARE\AspenTech\AFW\WebSSO and set it to 1. The data type is REG_DWORD
2. On the machine having this message in the event log, type in the following in the web browser's Address field and press Enter.
http://localhost/AtWebSSO_Reset
If the steps outlined above do not disable Aspen WebSSO then the Aspen WebSSO HTTP filter can be removed by executing the Delete command using the IIS 6.0 administration script, Adsutil.vbs, as shown below:
cscript //nologo adsutil.vbs DELETE /W3SVC/Filters/AtWebSSO
Keywords: event viewer
References: None |
Problem Statement: Aspen Cim-IO devices do not start automatically after system reboot. | Solution: Configuration information for logical devices added using the I/O wizard (in the Aspen InfoPlus.21 Administrator) can be found in the..\AspenTech\CIM-IO\Management directory of the Cim-IO server. In that directory, a configuration file (Device_Name.CSD) is stored for each device configured using the I/O wizard. You can view the files with a text editor.
Devices configured to start at boot will include Run along with a user name and password if specified.
Example:
CIMIO OPC SERVER,TESTOPC,
Run,DOMAIN\USER,MGNoYXJsaWU1IQ==
0
StoreForward,Default
1
CIMIO OPC ASYNC DLGP,TESTOPC,C:\Program Files\AspenTech\CIM-IO\io\cio_opc_api\asyncdlgp.exe,-tcpserviceTESTOPC-nodenameWESLEYR3-opcserverVendor.OPC.Server.1
The Run command in the second line indicates that the device should start at boot under the specific account. The password is encrypted.
If DontRun appears in the second line, the Start at boot option was not selected when the device was created.
It is possible to create a device that with the Start at Boot option without specifying an account. In this case, the device will run under the account specified for the CIM-IO Manager service. Note the presence of two commas in line two.
Example:
CIMIO OPC SERVER,TESTOPC,
Run,,
0
StoreForward,Default
1
CIMIO OPC ASYNC DLGP,TESTOPC,C:\Program Files\AspenTech\CIM-IO\io\cio_opc_api\asyncdlgp.exe,-tcpserviceTESTOPC-nodenameWESLEYR3-opcserverVendor.OPC.Server.1
NOTE: The Aspen CIM-IO Manager service maintains a copy of the contents of the .CSD file in memory while it is running. When the service shuts down, it writes this data to the file. To ensure that changes to the .CSD file are not overwritten, stop the Cim-IO Manager service in the Services applet (Start | Settings | Control Panel | Administrative Tools | Services) before making the change to the .CSD file.
Keywords: wizard
device
start
reboot
References: None |
Problem Statement: A Cim-IO Redundant Switchover might not occur although TSK_DETECT has identified the switchover and seems to perform the necessary actions. This problem can occur when Infoplus.21 is installed on Windows 2008 Server. A side effect is that there are no files with extension LDV created. Their location is the folder for application program files: ...\AspenTech\CIM-IO\io and are usually created at the time of the first switchover. | Solution: This problem is typically caused by the Windows 2008 UAC security settings for the Admin accounts. This has impact on the Admin account used to configure Cim-IO Redundancy and the Admin account that starts the Aspen InfoPlus.21 Task Service.
On the Infoplus.21 server perform following steps:
1. Navigate to Start | Administrative Tools | Local Security Policy;
2. Navigate to Local Policies | Security Options;
3. In the list change User Account Control: Behavior of the elevation prompt for Administrators in Admin Approval Mode. Set it to: Elevate without prompting;
4. In the application program files folder ...\AspenTech\CIM-IO\code run the CimioProperties.exe. This will update the system registry.
5. Restart the Aspen InfoPlus.21 Task Service and the Infoplus.21 database. This way the Infoplus.21 client tasks will have the new Admin privileges and will use the updated system registry.
The Cim-IO redundant switchover should work correctly now.
Keywords: Changeover
Windows 2008
Cim-IO
Redundant
References: None |
Problem Statement: This Knowledge Base article provides a brief description of the main characteristics of Aspen Framework vs. Aspen Local security. | Solution: Aspen Framework provides the integrating infrastructure that enables the development and enterprise-wide implementation of business processSolutions. A role-based Security component is just one aspect of installing and implementing Framework.
Aspen Framework (AFW) is a full blown securitySolution which consists of a single dedicated AFW Security Server and all InfoPlus.21 Servers pointing to it.
Here are the main points that characterize Aspen Framework:
Streamlined security implementation (easy administration - only one server per enterprise to administer)
Uses SQL Server or Oracle as a security database repository (more secure than MS Access)
Could slow down user authentication (especially if InfoPlus.21servers are on a slow WAN)
If this server goes down, users that required authentication (and without AFW Cache) would be locked out.
Attached to this Knowledge Base article please find Aspen Framework Fact Sheet, which describes the purpose of this product in more detail.
Since not all customers will purchase and use Framework, not everyone would have had Framework Security. Therefore, for customers who do not have the full-blown version of Framework, a lighter version of Framework was developed, called Aspen Local Security. This is basically just the Security component pulled out of Framework, with only slight modifications. You can read more about this in the documentation under Aspen Manufacturing Suite, Aspen Local Security. Any of the Installation Manuals has a small section in the front, describing this product.
Here are the main points that characterize Aspen Local Security:
Fast, reliable user authentication
Easy to troubleshooting
Allows for server-specific settings
Can use MS Access as a security database repository (less secure than MS SQL Server or Oracle)
The main disadvantage is that there are many security servers to administer. As an Aspen InfoPlus.21Administrator this can be pretty tedious.
Keywords: None
References: None |
Problem Statement: This knowledge base article describes the cause of the following message in the cimio_msg.log on the Cim-io server.
Attempt to update with older timestamp for record id XXXX | Solution: This message indicates that the same data record has been specified for data collection in more than one Get record. To prevent this error, ensure that each data record is only listed in a single Get record.
Keywords:
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.