question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: How to select License Type Backup in Aspen InfoPlus.21 V8.5 to configure an InfoPlus.21 backup server?
|
Solution: Starting in version V8.5 of Aspen InfoPlus.21 there's no License Type of Backup anymore,
The only selections available are Standard, Embedded and OEM,
See KB 140942 for further details.
Users are encouraged to consider using the Aspen MES Clustering product instead. For further details see the Aspen MES Clustering Administration Guide, KB 139239
Keywords: SLM
License
backup
IP.21
References: None
|
Problem Statement: I have two KPIs that are executed every minute. I want to make sure that one of these is executed first. How do I ensure that?
|
Solution: The execution order is determined by the order of the record's name entry in the KPIScheduleDef record. So for example, if the KPIs are set for 1 minute execution, then their record names would be entered in the KPIScheduleDef record 1-Minute KPI. The order in the repeat area called #DATA_BASE_RECORDS determines the execution order.
Keywords: KPI sequence KPIScheduleDef
References: None
|
Problem Statement: The following error appears when attempting to access an application via the web.
|
Solution: This problem can be resolved by removing the line that contains the reference to stdole from the web.config source file.
*** IIS will need to be restarted after the change has been made to web.config ***
Keywords: stdole
Parser Error Message
Parser
References: None
|
Problem Statement: When right-clicking on a Tag in the InfoPlus.21 Administrator, and choosing Show
|
Solution: The enhanced Show
Keywords: section below.)
References: s, the following error may occur:
(The screen-cap is cropped for display purposes, however the entire message is shown in the
|
Problem Statement: Getting error RegQueryValueEx call for order failed with error code 2 in the Application Event Viewer log when starting the Aspen InfoPlus.21 Manager.
|
Solution: The error (RegQueryValueEx call for order failed) suggests a problem with the registry.
In this case the error occurs when starting the Aspen InfoPlus.21 Manager. The likely cause for this error is a problem with the registered tasks under the following registry key.
[HKLM\software\Aspentech\InfoPlus.21\10.0\group200\ Registered Tasks]
Note: The registry key above contains 10.0 which indicates the version. Depending on the version installed this number may vary.
Look for anything that looks out of place with the keys. For example:
Order value not set or the value is a duplicate of another.
Task names or paths that are not correct
In one example it was discovered that some registered tasks listed in the registry did not exist in the Aspen InfoPlus.21 Manager. Removing the tasks cleared the error.
Keywords:
References: None
|
Problem Statement:
|
Solution: The IP_VALUE_FORMAT field for SQLA tags controls numeric display format used for IP_GRAPH_MAXIMUM and IP_GRAPH_MINIMUM fields and does not control the tag format. For more detailed information about this, please refer to the Aspen InfoPlus.21 Database User's Guide, section titled ?SQLA Tag Fields?.
Keywords:
References: None
|
Problem Statement: This technical tip describes how to use the Aspen InfoPlus.21 Health Monitor to check if a record is regularly updating.
|
Solution: The Aspen InfoPlus.21 Health Monitor can check if an Aspen InfoPlus.21 record updates regularly. Here is how to set this up.
The record you want to monitor must have a time stamp field updated on a regular basis. For example, Aspen InfoPlus.21 updates the field IP_INPUT_TIME in records defined by IP_AnalogDef when an application changes the field IP_INPUT_VALUE. Each time Aspen CIM-IO scans the process, CIM-IO revises the field IO_LAST_UPDATE in transfer records defined by IOGetDef.
Suppose an application writes to the IP_AnalogDef record A1113E every minute. To have the Aspen InfoPlus.21 Health Monitor generate a yellow alert if two minutes pass between updates and a red alert after six minutes, first use the InfoPlus.21 Administrator to copy the record ExampleTimeFreshnessTest to a record named A1113ETimeFreshnessTest, and change the field IP_DESCRIPTION to something like A1113E Time Freshness Test. Next, set the fields IP_YELLOW_LIMIT and IP_RED_LIMIT to 120 and 360 respectively. Finally, change the field RECORD_&_FIELD_NAME to A1113E IP_INPUT_TIME and set the field ACTIVE SW. to Auto. After making these changes, the record A1113ETimeFreshnessTest should look similar to:
After making these changes to A1113ETimeFreshnessTest, add a reference to A1113ETimeFreshnessTest to the repeat area #DATA_BASE_RECORDS in the record CustomAppHealthTests.
After making the database changes described above, the Aspen InfoPlus.21 Health Monitor will produce a report that looks similar to:
Keywords: Health Monitor Example
Time Freshness Test
TimeFreshnessTest
ExampleTimeFreshnessTest
References: None
|
Problem Statement: When I run ValidateArchive.exe I can?t see all the details on the DOS prompt, as the output is too long.
How can I output the result of ValidateArchive.exe onto a .log file?
|
Solution: The output of ValidateArchive.exe can be sent to a log file, by adding a ?>? and a filename (something like >ValidateArchive.log), which will be created.
See example below:
C:\Program Files (x86)\AspenTech\InfoPlus.21\c21\h21\bin\ValidateArchive.exe >ValidateArchive.log
Keywords: ValidateArchive.exe
Historian
References: None
|
Problem Statement: Can't start Aspen InfoPlus.21 database, and error log file for the repository has messages like:
|
Solution: This message is coming out of a function that updates the history block with the target file set already identified (that would be file set 123).
Using the steps inSolution 124612, How can I run the Aspen InfoPlus.21 Archive Repair Wizard without starting the database in v2006.5 onwards?, examined the file sets and showed that file set 162 and 123 had the same start date, but different end times.
One scenario where this may occur is if an older copy of config.dat is copied which would result in a mismatch of the start and end time stamps between the file sets and what is contained in the config.dat.
After checking the summary of each of these file sets it was determined that file set 162 had more data collected for tags than 123, so removed the arc.byte, arc.dat and arc.key files from the file set 123 folder.
After removing the files for file set 123 the summary for it shows no data in it, marked this file set as Reserved in the file set Properties menu, to prevent InfoPlus.21 from shifting into this file set, so it can be used for other purposes.
After this InfoPlus.21 started with no problems.
Keywords: start, IP.21, file set
References: None
|
Problem Statement: ERROR 77039 = 'VariantChangeType failed'- in IO_DATA_STATUS_DESC field in Aspen InfoPlus.21 when requesting an array of data using Aspen CIM-IO for OPC.
|
Solution: Typically, this error is due to having the wrong data type specified for the tag. For example, if the tag is an ASCII tag on your OPC server, but you have the data type in the GET record set to something different, this error can occur. The 'VariantChangeType failed' message is also generated when CIM-IO can't translate the data type specified on the OPC server to the type specified within CIM-IO.
However, even before you start trouble-shooting the above error message, please make sure you have created a data record to receive the data from the server (seeSolution # 106106 for more information). The data record must contain enough consecutive fields of the data type being received from the server Name, Description, Timestamp field, value and status followed by n fields where there are enough fields to receive the array being sent. Then you need to specify a data type structure in the GET record and the data field in the GET record should be specified as the first field in the data record.
Below is a DUMPREC of a GET record and one of the data records so you can see how it is set up.
*********contents of dumprec*********(also included as an attachment)
Record Contents OPCArrayGet ID = 4285 13-MAY-03 17:57:24
Definition Record IoGetDef
OPCArrayGet NAME
Test OPC Array data type DESCRIPTION
OFF IO_MESSAGE_SW
NO IO_ACTIVATE?
IO_ACTIVATION_COS
OFF IO_RECORD_PROCESSING
TSK_MOPC IO_MAIN_TASK
0 IO_DEVICE_UNIT
IO Group 1 IO_GROUP
1 IO_PRIORITY
Default IO_DEFAULT_DATA_TYPE
NO IO_ASYNC?
+00000:00:05.0 IO_TIMEOUT_VALUE
+00000:00:05.0 IO_FREQUENCY
03-SEP-02 14:41:24.6 IO_LAST_UPDATE
Record Processing Off IO_LAST_STATUS
Data unavailable due to Record OFF IO_LAST_STATUS_DESC
1 IO_REQUEST_CHANGES
3 IO_#TAGS
TestAI8 1 IO_TAGNAME
ON 1 IO_DATA_PROCESSING
Structure 1 IO_DATA_TYPE
OPCArrayTest Value_0 1 IO_VALUE_RECORD&FLD
No Conversion 1 IO_DATA_CONVERSION
No Deadband 1 IO_DATA_DEADBAND
Data Unavailable 1 IO_DATA_STATUS
1 IO_DATA_STATUS_DESC
TestAI9 2 IO_TAGNAME
ON 2 IO_DATA_PROCESSING
Structure 2 IO_DATA_TYPE
OPCArrayTest2 Value_0 2 IO_VALUE_RECORD&FLD
No Conversion 2 IO_DATA_CONVERSION
No Deadband 2 IO_DATA_DEADBAND
Data Unavailable 2 IO_DATA_STATUS
2 IO_DATA_STATUS_DESC
TestAI8 3 IO_TAGNAME
ON 3 IO_DATA_PROCESSING
Structure 3 IO_DATA_TYPE
OPCArrayDummy Value_0 3 IO_VALUE_RECORD&FLD
No Conversion 3 IO_DATA_CONVERSION
No Deadband 3 IO_DATA_DEADBAND
Data Unavailable 3 IO_DATA_STATUS
3 IO_DATA_STATUS_DESC
Record Contents OPCArrayTest ID = 4291 13-MAY-03 17:57:51
Definition Record Io_OPCArrayDef
OPCArrayTest NAME
Status only on first field DESCRIPTION
29-SEP-00 16:41:44 TIMESTAMP_FIELD
Scan Off VALUE_QSTATUS
42.60 Value_0
43.60 Value_1
44.60 Value_2
45.60 Value_3
46.60 Value_4
47.60 Value_5
48.60 Value_6
49.60 Value_7
50.60 Value_8
51.60 Value_9
Keywords: array
References: None
|
Problem Statement: Can I modify the entries in the database record QUALITY-STATUSES?
|
Solution: You can modify the text of the SELECT_DESCRIPTION and the text of the QUALITY_LEVEL fields of the occurrences.
You should not change the order of the occurrences because they are set for use by the Aspen Cim-IO interfaces. The Aspen Cim-IO standard interfaces returns a number for the quality of the data and that number is used to determine what text should be displayed in the Aspen InfoPlus.21 Administrator.
You can add new occurrences but be sure to make the SELECTOR VALUE be less that -72. This is useful when a custom interface is used to collect data from the field devices and the vendor should be notified that if they have quality statuses that are not included in this list then they will need to return a quality with a value less than -72 for it to appear in the Aspen InfoPlus.21 Administrator.
Keywords: SELECT_DESCRIPTION
QUALITY_LEVEL
References: None
|
Problem Statement: An Aspen InfoPlus.21 history repository stops with the messages
ARCHIVE: SetPrimeArchiveForPoint error point 22345755 and
ARCHIVE: store event failed to determine prime by pointid
in the repository's error log file.
|
Solution: When writing a recording to a history repository, the program h21archive first determines the prime archive for this point; that is, the archive that holds the most recent events for the tag. Usually, h21archive finds the prime archive immediately if there are events for the point in cache.
If there are no events in the cache for the point, then h21archive searches archives on disk to find the prime archive for the point beginning with the most recent archive (the active archive) until finding an archive containing events for the point. For each archive, h21archive determines if the archive contains event(s) for the point by interrogating the .key file.
The error message indicates that h21archive encountered a problem in reading the .key file for one of the archives. Unfortunately, the message does not say which file set has the problem.
To resolve this issue, you should repair all the file sets for the repository using the repair archive wizard started from the Aspen InfoPlus.21 Manager.
Keywords: SetPrimeArchiveForPoint
Prime
Pointid
References: None
|
Problem Statement: Your current Aspen Manufacturing Suite installation runs on AspenTech Old Commercial Model (OCM) perpetual or legacy token licenses. Your company has now moved to the AspenTech New Commercial Model (NCM) token term licensing.
You have received the new token license and the new media, ie. Aspen Manufacturing and Supply Chain DVD2T.
What should be considered when performing an upgrade of these products, ie. Aspen InfoPlus.21 and Aspen Process Explorer?
|
Solution: There are two possible cases:
? The current version is V7.1 (or below) and you want to upgrade to V7.2 (or above)
Use the Aspen Manufacturing and Supply Chain DVD2T and select the Upgrade option.
If you prefer you can un-install the old version and then re-install completely.
N.B. You must ensure that your licensing is in place to allow you to go from OCM to NCM.
? The current version is V7.2 (or above) which you had installed using your perpetual or legacy token license
You do not have to perform any upgrade.
Contact the AspenTech Token Administration team to run the Token Conversion Utility.
Keywords: Aspen Manufacturing and Supply Chain DVD2T
Aspen Manufacturing and Supply Chain DVD2
Old Commercial Model
New Commercial Model
Token
References: None
|
Problem Statement: The history utility, h21arcck, is used to help rebuild potentially corrupt history filesets. What does it do and how does it work?
|
Solution: When h21arcck runs, it deletes the arc.key file and rebuilds it using the information it obtains from the arc.dat file. The arc.key file contains what programmers call a b-tree search tree. This is analogous to a card catalog in a library. Instead of wandering through the library looking for a particular book, one goes to the card file, finds the title, gets the location of the book on the shelf, and then goes to find the book on the shelf. In theory, one can recreate the card file if all the books are in the library. However, if a book is missing from the library or is damaged beyond recognition, one cannot recreate a new card for it. This is what h21arcck does to the arc.key file. While it is checking the data file, it creates new keys (cards) in the key file that point to the data in the data file. If h21arcck finds a history data record in the data file that is damaged or unrecognizable, it will not create a new key for that record. The data that was in that record is technically lost although the bad record's data is still physically located in the data file. H21arcck will never remove data from the arc.dat file.
Keywords: h21arcck
arc.key
arc.dat
References: None
|
Problem Statement: The AspenChem Simulation demo is installed by default when installing Aspen InfoPlus.21. Some users may have not removed this demo from their InfoPlus.21 databases. In some cases, if the demo is still running, users will notice IP_AnalogDef records being updated quite frequently, which could have a potential of filling up and shifting history filesets sooner than expected.
|
Solution: In the Demo Snapshot, a Record called ATC_Calcs (defined by QueryDef) runs every 5 seconds. This query will update the IP_INPUT_VALUE field for every IP_AnalogDef record inside the database if the field IP_STEPPED is set to Stepped, instead of the default value of Interpolated.
It is advisable to not have the Aspen Demo snapshot incorporated into your production snapshot. If the Demo is already present, Knowledgebase Article 108634 provides the necessary steps to remove the Demo after the fact: http://support.aspentech.com/webteamcgi/SolutionDisplay_view.cgi?key=108634
UPDATE: Starting in version 2006, ATC_Calcs was modified so only Aspen Demo Simulation IP_AnalogDef records are updated.
Keywords: AspenChem
Aspen Demo
ATC_Calcs
IP_STEPPED
References: None
|
Problem Statement: The Aspen InfoPlus.21 Manager may display the message Cannot get the database properties list in get profile function.
|
Solution: The V7.3 cumulative patch introduced the concept of Aspen Infoplus21 Profiles. In V8.0, AspenTech added additional fields to the file profiles.xml. Under V8.0, when the Aspen InfoPlus.21 Task Service starts for the first time, it creates a new profile unless one already exists. If upgrading from V7.3 to V8.0 on the same system the error may occur if the V7.3 profile.xml exists.
Too resolve the message:
· Stop InfoPlus.21 and close the Aspen InfoPlus.21 Manager and Administrator.
· Stop the Aspen InfoPlus.21 Task Service.
· Go to ..\ProgramData\AspenTech\InfoPlus.21
or ..\Program Files\Aspentech\Infoplus.21
· Rename or delete the file IP21Profiles.xml.
· Restart the Aspen InfoPlus.21 Task Service.
· Open the Aspen InfoPlus.21 Manager and start Aspen InfoPlus.21 if not already started.
· A new IP21Profiles.xml file will be created.
Keywords: database properties
get profile
failed to load the xml document in upgrade profile function
References: None
|
Problem Statement: Aspen InfoPlus.21 appears to allow duplicate data to be saved in history.
For example, write a simple Aspen SQLplus query to insert a value at a specific time, and you will see results like:
INSERT INTO ATCAI(IP_TREND_VALUE, IP_TREND_TIME)
VALUES (4.5, '29-MAR-13 11:06:33.3');
Now hit F9 five times, executing the query five times in a row
RESULT:
NAME
IP_TREND_TIME
IP_TREND_VALUE
ATCAI
29-MAR-13 11:06:33.3
4.50
ATCAI
29-MAR-13 11:06:33.3
4.50
ATCAI
29-MAR-13 11:06:33.3
4.50
ATCAI
29-MAR-13 11:06:33.3
4.50
ATCAI
29-MAR-13 11:06:33.3
4.50
|
Solution: These values appear to be identical. However the database does not allow duplicate timestamps. The Aspen InfoPlus.21 system pushes each identical timestamp, forward one microsecond, so that they are unique:
Try this Aspen SQLplus SELECT query to see the extended timestamp:
SELECT NAME, IP_TREND_TIME USING 'TS25', IP_TREND_VALUE
FROM ATCAI;
NAME
IP_TREND_TIME
IP_TREND_VALUE
ATCAI
29-MAR-13 11:06:33.300004
4.50
ATCAI
29-MAR-13 11:06:33.300003
4.50
ATCAI
29-MAR-13 11:06:33.300002
4.50
ATCAI
29-MAR-13 11:06:33.300001
4.50
ATCAI
29-MAR-13 11:06:33.300000
4.50
Keywords: None
References: None
|
Problem Statement: McAfee Antivirus Software and InfoPlus.21:
Last month, several ATIMUS members posted emails about anti-virus software and InfoPlus.21. Some of them noticed excessive InfoPlus.21 startups unless they disabled Netshield 4.5.1.
We have recently concluded some internal testing on this issue and have the following advice to offer:
|
Solution: On a Server operating system (ie., Windows 2000 Server), McAfee Netshield 4.5.1 impose a tremendous performance penalty on file access unless it has been configured to scan Selected file types only. This appears to have been fixed in McAfee Antivirus 7.0.0.
On a Windows 2000 Advance Server system, a database load took 32 minutes with McAfee Netshield 4.5.1. Upgrading to McAfee Antivirus Enterprise Edition 7.0.0 brought the database load time down to about one minute --- a 30x improvement.
So, if you have McAfee Netshield 4.5.1 on a Server operating system (i.e, not Windows 2000 Professional), you should see a dramatic improvement by upgrading to McAfee 7.0.0.
Keywords: virus
delay
startup
start-up
References: None
|
Problem Statement: The Aspen InfoPlus.21 I/O device wizard displays the message:
CIMIO_MGNT_SERVER_STOP; Error Stopping Server
when stopping a logical device.
|
Solution: To solve this problem, check if the Aspen Cim-IO Manager service is running under the Local System account on the Aspen Cim-IO Server.
If so, first turn off the logical device using the Aspen InfoPlus.21 Administrator, and stop the corresponding Cim-IO client tasks using the Aspen InfoPlus.21 Manager.
After setting the field IO_DEVICE_PROCESSING to OFF in the Aspen InfoPlus.21 logical device wizard, stop the logical device using the I/O device wizard.
Then, remove the logical device using the I/O device wizard.
Next, change the login properties of the Aspen Cim-IO Manager on the Aspen Cim-IO Server to use an administrator's account and restart the service.
After restarting the Aspen Cim-IO Manager, add the logical device again using the Aspen InfoPlus.21 I/O device wizard. When you see the screen, select Start at boot and enter the user name and password of the account used to start the Aspen Cim-IO Manager service on the Aspen Cim-IO Server.
Use the Aspen InfoPlus.21 I/O device wizard to start the logical device.
Finally, restart the Aspen InfoPlus.21 Cim-IO client tasks for the device using the Aspen InfoPlus.21 manager and turn on device processing by changing the field IO_DEVICE_PROCESSING to ON in the Aspen InfoPlus.21 logical device record.
Keywords: I/O device wizard
CIMIO_MGNT_SERVER_STOP
References: None
|
Problem Statement: This
|
Solution: shows examples of accessing the Aspen object libraries AtProcessData and AtTagBrowserSQLplus using a query and Visual Basic Application. Solutions 105618 and 107019 also have examples.Solution
The AtProcessData library is located in …\Program Files (x86)\Common Files\AspenTech Shared\OPC\AspenDataSource.dll, and the reference name is Aspen Process Data. This library gives you a set of COM objects similar to concepts used while working with the Aspen InfoPlus.21 database. The next code example is taking from the Aspen Calc Help file under the topic “Querying with Ad-Hoc Calculations using SQLplus” and shows some of this objects:
-- Declaraction
--
LOCAL X, I INT, DS, QUERY, HIST, SAMPLES;
--
-- Creating Object DATASOURCES
--
X=CREATEOBJECT('ATPROCESSDATA.DATASOURCES');
--
-- Creating Object DATASOURCE (Substitute the
-- name of your InfoPlus.21 server for
-- 'LocalHost')
--
DS = X('LocalHost');
--
-- The Tags property can receive a tag name list
-- to work with or an Ad Hoc calculation as in
-- Process Explorer trend
--
HIST = DS.TAGS.ADD('=ATCL101+ATCL102+ATCL103').HISTORY;
--
-- Get the query associated to the tag created as
-- a QUERY COM object, so, it is not actually the
-- query code as string
--
QUERY = HIST.QUERY;
--
-- Get value from 1 day in the past to actual time
--
QUERY.BEGINTIME= CURRENT_TIMESTAMP-24:00;
QUERY.ENDTIME = CURRENT_TIMESTAMP;
--
-- Retrieve only 100 values or less
--
QUERY.MAXPOINTS=100;
--
-- Default value time, other conversion are also possible
--
QUERY.TYPE=0;
--
-- Execute the previous query, in this case,
-- an Ad Hoc calculation
--
DS.READHISTORY(FALSE);
--
-- HIST object will hold the result on memory and retrieve
-- this as an Sample COM Object
--
SAMPLES = HIST.SAMPLES;
--
-- Write result using the SAMPLE COM Object
--
WRITE SAMPLES.COUNT;
FOR I = 1 TO SAMPLES.COUNT DO
WRITE SAMPLES(I).TIME||' '||SAMPLES(I).VALUE;
END;
The query uses the following objects:
AtProcessData
àDatasources
àDatasource
à Datasource.Tags
à Datasource.Hist
àHist.Query
àHist.Samples
It is possible to consult the objects, properties and methods associated to the AtProcessData library using SQLPlus Object Browser after adding ATProcessData as a reference:
Notice that Datasource.Tags object can be used to call not only history data for a given tag, but also ad hoc calculations using mathematical or logical operations (seeSolution 110471) and can be used to call store procedures (in ProcedureDef records).
The AtTagBrowserSQLplus library is located in
…\Program Files (x86)\Common Files\AspenTech Shared\Apex\AtTagBrowserSQLplus.dll, and the reference name is Aspen Tag browser PE. Use this library to get tags attributes as ADODB COM objects (see http://msdn.microsoft.com/en-us/library/windows/desktop/ms678086(v=vs.85).aspx) using SQL queries. The next code shows an example on it:
Public Class Form1
Private Sub ReadIP21()
'
'Declaration
'
Dim IP21Connection As New AtTagBrowserSQLplus.TagBrowser()
'
'Create Connection
'
IP21Connection.Connect(Test, APCATM, 10014, , )
'
'Execute query and pass result to a RecordSet COM Object
'
Dim rs As Recordset = IP21Connection.Query(SELECT * FROM DefinitionDEF WHERE NAME LIKE 'Select%')
'
'Adapt the RecordSet with the query result to a DataSet object
'
Dim da As New System.Data.OleDb.OleDbDataAdapter()
Dim ds As New DataSet()
da.Fill(ds, rs, Tags)
'
'Pass the result as a datasource for a user interface object
'
DataGridView1.DataSource = ds.Tables(0)
End Sub
End Class
The AtTagBrowserSQLplus.TagBrowser.Query method can parse a query result to an ADODB object like RecordSet in the example.
The Connect method in the following example will try to connect to node APCATM (can be changed to use IP address) using port 10014. This method can also be used to prompt a connection window as follows:
Public Sub Connect()
Dim MyConnection As New ADODB.Connection
Dim MyTagBrowser As New AtTagBrowserSQLplus.TagBrowser'
MyConnection = MyTagBrowser.Connect(My connection, , , , )
End Sub
Without node and port parameters this method will display this window:
In the previous example the TagBrowser object is converted in an ADODB.Connection object. Used in this way it is not possible to call the Query method (because is a method for AtTagBrowserSQLplus.TagBrowser), but it is possible to call the ADODB.Connection. The method as shown inSolution 108707 can actually parse a query result and also can call stored procedures as is show inSolution 108707. Iit is also possible to create an ADODB.Connection object using any other ODBC driver.
Keywords: AtProcessData
AtTagBrowserSQLplus
COM Object
ADODB
ODBC
References: None
|
Problem Statement: Aspen InfoPlus.21 cannot start: The startup sequence stops when trying to start TSK_DBCLOCK.
Also trying to start InfoPlus.21 one task at a time does not work; in that case the error message below pops up:
|
Solution: This problem happens if the %SETCIMCODE% system variable does not contain the correct path.
Correcting %SETCIMCODE% with the right path (generally C:\Program Files\AspenTech\InfoPlus.21\db21\code) and rebooting the server fixes the problem.
Keywords: Process creation status is FAILED(err=3) for dbclock.exe
References: None
|
Problem Statement: The Tags view in the IP.21 Administrator contains only 3 families of tags by default - IP_AnalogDef, IP_DiscreteDef and IP_TextDef. Customers with custom record families may wish to have a shortcut to view these tags in the Tags view.
|
Solution: To insert tags from custom record definition family into the Tags view in IP.21 Administrator, simply open IP.21 Administrator and navigate to the IP_TagsBranch record. Increase the PE_#_OF_OBJECTS field by 1, and go to the repeat area. Type in the name of the custom definition record in the PE_DESCRIPTION and PE_BRANCH fields. Refresh the admin tool and you should now see your custom definition record in the Tags view.
Keywords: IP.21 Administrator
custom
Tags
view
References: None
|
Problem Statement: When using the SetArchiveDates.exe utility several error codes are possible. What do those error codes mean?
|
Solution: Investigate problem . . . codes 1, 4 and 5 are caused by basic system resource allocation failure. Return codes 2 and 3 have corresponding error message that are produced in the SetArchiveDates log file, found in the Group200 directory, with a filename in the form of h21logYYMMDDhhmmss.out.
Investigate Problem Code
Description
1
Could not create progress status dialog.
2
Could not modify archive dates.
3
Could not creative new archive.
4
InitStepEvent error (If possible, get a screen capture when this occurs.)
5
BeginThread failed
6
No specific error message -- This error occurs if the archive check fails on an archive file. This step would be equivalent to running the archive check on the selected archive file via the h21arcck stand-alone utility.
Keywords: None
References: None
|
Problem Statement: When does the map.dat get modified or changed?
|
Solution: The Map.Dat gets modified when ALL of the following has occurred:
1. A new definition record is created.
2. That new Definition record has a history repeat area that is different to any other history repeat area for which records have been created and history saved.
3. New records are created against the new definition record.
4. Archiving is turned on for one of the new records.
As a result, a new Map Area is created in the Map.Dat with an associated index number. Then each record created against the new definition record will have a pointer in its header containing that index number.
If you have a database where GeorgeDef is created (and used) and later FredDef is created (and used), they may have index numbers of 4 and 5. Then if you move the Map.Dat to a database where FredDef was created and used before GeorgeDef then index numbers in the records would not match. This could lead to strange problems.
However, for the new entry to appear in the Map.Dat, the areas have to be unique. If GeorgeDef used a field in a history repeat area that had identical fields as FredDef, then only one Map Area and corresponding Index would be needed.
Keywords:
References: None
|
Problem Statement: Will Production Management & Execution (PM&E) products work if the licence server is not available?
|
Solution: All PM&E applications like InfoPlus.21 will continue to run even if the SLM server is down (and this is regardless if it is a token system or not.) Advanced Process Control (APC) online applications will run for up to 10 days without a license.
Keywords: Token model
license server
shutdown
license server
References: None
|
Problem Statement: The Aspen InfoPlus.21 Manager contains an option to mark each task as external. (See image below)
This knowledge base article describes what is meant by the term External Task as well as when to select a task to be marked as external.
|
Solution: The external task flag should be checked to start an executable that the user intends to run until Aspen InfoPlus.21 is shutdown or until the user manually terminates the task. An example would be a TSK_IQ# process or a Cim-IO client task like TSK_M_OPC.
When the external task flag is not checked the task will start during Aspen InfoPlus.21's startup sequence, do it's job, then terminate. Examples of tasks which do not have the external flag checked are some of the history tasks which only perform one action during Aspen InfoPlus.21 startup then exit. For example TSK_H21_ARCCK does an archive check during startup then exits when it has completed the archive check.
Keywords: external
internal
process
launch
instance
start
kill
end
References: None
|
Problem Statement: Starting in version V7.1 of Aspen InfoPlus.21, it is possible for Administrators to specify the type of license that is going to be used by a particular database. Starting in V8.5 there are three types: Standard - Embedded - OEM.
How to select the License Key Type in Aspen InfoPlus.21?
|
Solution: In order to configure the proper Aspen InfoPlus.21 license type, follow these simple steps:
1. Shut down the database from the InfoPlus.21 Manager
2. From the Administrator tool, right-click on the database name and select Set License Key Type
3. Select the appropriate license type and click OK. For information on license types, see 140942
4. Start the database
5. Optionally, you can verify that InfoPlus.21 is checking out the correct license by using the WLMAdmin tool:
6.
Keywords: Token
Tokens
Hot Backup
SLM
License Scheme Selector
Selection
Aspen Watch
IP.21
Standard
Embedded
OEM
References: None
|
Problem Statement: How to access custom tag definition records using the Aspen InfoPlus.21 OPC-DA Server.
|
Solution: In order to access custom tag definition records, following configuration has to be done.
1. Put the custom tag definition into the repeat area of IP_TagBranch record.
           Detail is documented in attached file.
2. Create AtMapDef record for the custom tag definition
           Detail is documented inSolution 105326 The Aspen Tag Browser may not return correct list of tags (typically seen with custom tags).
Keywords: IP_TagBranch
IP.21 OPC DA Server
AtMapDef
Custom Definition
References: None
|
Problem Statement: What to do if you get the error:
Error 0193: %1 Not a Valid Windows NT Application or
Could not start the [service name] service on local computer.
Error 193:%1 not a valid Win32 application
after rebooting your PC?
|
Solution: After InfoPlus.21 is installed and running successfully, you may see a message about certain services not starting after a reboot. The following errors may then be seen in the Event Viewer, when examining those services: %1 not a valid Windows NT application or Could not start the [service name] service on local computer.
Error 193:%1 not a valid Win32 application.
This error is a Microsoft error, and it is complaining about the environment variable of %1. It is not able to recognize the file path for the service or services when trying to startup after the reboot. To fix this problem, in the registry, put a double quote ( ) in front and at the end of the image path for each service that is having a problem starting at reboot.
For example, the Imagepath of a service must have:
drive:\Program Files\Aspentech\InfoPlus.21\db21\code\tsk_server.exe
Detailed information regarding this error can be found via Article ID #Q134425 from the Microsoft Support Website (http://support.microsoft.com/support/kb/articles/Q134/4/25.asp). The content of this article is included below:
SYMPTOMS:
When you restart Windows NT and attempt to run an application, service, or install a network protocol, one of the following system events appears in Event Viewer:
Event ID: 7000
Source: Service Control Manager
Type: Error
Description: The <service name> service failed to start due to the following error: <service name>: %1 not a valid Windows NT Application.
-or-
Event ID: 7000 Source: Service Control Manager Type: Error Description: The <service name> service failed to start due to the following error: The system cannot find the file specified.
-or-
When you try to manually start a service from the Services tool in Control Panel, you may receive the following error message:
Could not start the service <name> on \\<computer name> 0193: %1 is not a valid application.
CAUSE:
This problem occurs if a service component required for Windows NT, an application, or a network protocol, is corrupted or missing.
-or-
The problem can also occur if the folder location of the executable contains spaces in the directory name (long filename). An example would be when the executable is located in the \Program files\<service.exe> folder.
Solution
To correct this problem if the file is missing, manually expand the service component file. For example, if the <service name> in Event ID 7000 is MUP, expand MUP.SY_ from the Window NT CD-ROM to MUP.SYS in the %SystemRoot%\SYSTEM32\DRIVERS folder.
To correct this problem if the file is located in a folder with a long file name, modify the registry key containing the executable path to be enclosed in quotation marks or change the executable to use the standard 8.3 (tilde ~) path notation.
WARNING: Incorrect use of Registry Editor can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
For information about how to edit the registry, view the Changing Keys And Values Help topic in Registry Editor (Regedit.exe) or the Add and Delete Information in the Registry and Edit Registry Data Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).
For example:
1. Run Registry Editor (Regedt32.exe), and then navigate to the following key: HKLM\SYSTEM\CurrentControlSet\services\[name of service]
2. Double click the ImagePath value, and then change the Value Data of ImagePath by adding quotation marks around the complete path, including the executable name. For example: C:\Program Files\{executable}.
Keywords: win32
0193
%1
valid application
References: None
|
Problem Statement: The following error is received during installation of AspenTech software.
|
Solution: After verifying that the user is attempting the installation with an account that has Administrative privileges, the following methods can be used to troubleshoot 1601 installation errors.
Method 1
Open the Windows Services Control Panel and make sure that the Windows Installer service is running, and not disabled.
Method 2
Some programs will lock the Windows installer while waiting for the user to either allow the update to complete, or kill the process. Java updates, and Adobe Acrobat are good examples of one of these types of programs. Examine the system tray to ensure that there are no running application that could be locking the Windows Installer application.
Method 3
Un-register Windows Installer, and then re-register Windows Installer. To do this, follow these steps:
1. On the Start menu, click Run:
2. In the Open box, type msiexec /unreg, and then press ENTER.
3. On the Start menu, click Run.
4. In the Open box, type msiexec /regserver, and then press ENTER.
Method 4
This error can also occur when the Microsoft Windows Installer Service has been corrupted on the system. If none of the above procedures work try re-installing the Windows Installer program. The Windows Installer can be downloaded from Microsoft's website or located on your AspenTech software DVD.
Keywords: Windows Installer;
Error 1601;
Windows Installer Service could not be accessed;
Installation errors;
References: None
|
Problem Statement: One of the Aspen InfoPlus.21 history repositories fails to start of shuts down with the following error in the repository's error.log.
ARCHIVE: Store active archive time problem idx 0 point_id 6315035 failure
prime 1 active 1 arcnum 0
store_event() store_active() failure 2, point 6315035
|
Solution: This can be resolved by restarting the Aspen InfoPlus.21 database and running RepairArchive on the file set if necessary.
Keywords: Archive
Prime
Store_event()
Failure
References: None
|
Problem Statement: How to avoid TSK_REP_SUB.OUT from increasing in size when using Aspen InfoPlus.21 Tag Replication.
|
Solution: There are 2 sections in the subscriber's configuration file called ReplicationSubscriber.exe.config that can turn off or minimize the size of the out file. Use the Rolling File Appender section to minimize the size of the output file or the Console Appender section to turn off logging. Edit the desired section below.
Rolling File Appender
<appender name=LogFileAppender type=log4net.Appender.RollingFileAppender >
<file value=${SETCIM}\${SETCIM_GROUP_NAME}\ReplicationSubscriber.log />
<appendToFile value=true />
<rollingStyle value=Size />
<maxSizeRollBackups value=10 />
<maximumFileSize value=1024KB />
<staticLogFileName value=true />
<layout type=log4net.Layout.PatternLayout>
<param name=ConversionPattern value=%d [%t] %-5p [%M] - %m%n />
</layout>
<filter type=log4net.Filter.LevelRangeFilter>
<param name=LevelMin value=WARN />
<param name=LevelMax value=FATAL />
</filter>
</appender>
Console Appender
To turn off the ?console? appender section output, look for the section in the file:
<appender name=ConsoleAppender type=log4net.Appender.ConsoleAppender >
<layout type=log4net.Layout.PatternLayout>
<param name=ConversionPattern value=%d [%t] %-5p [%M] - %m%n />
</layout>
<filter type=log4net.Filter.LevelRangeFilter>
<param name=LevelMin value=WARN /> a <param name=LevelMin value=OFF />
<param name=LevelMax value=FATAL /> a <param name=LevelMax value=OFF />
</filter>
</appender>
Changes to these sections of the configuration file will take effect automatically and do not require a restart of task.
Keywords: invalid field type
field id: 0x2415
References: None
|
Problem Statement: The following error may be encountered when attempting to install AspenTech applications.
Error 1311. Source file not found: X:\...\... Verify that the file exists and that you can access it.
This knowledge base article explains how to resolve the problem once the error has been encountered.
|
Solution: Error 1311 is a Windows Installer problem. Basically, there is restricted access to the installation DVD and so you are not able to access the file, even though the file exists on the DVD media.
As a work around, copy the contents of the installation DVD onto the computer hard drive (create a folder and copy the contents to that folder), and then run the setup.exe file from the new folder on your computer.
If you are installing from a zip file, make sure that you unzip any file first and save it on the hard disk of your computer, then install.
Keywords: Error 1311
Installation problem
References: None
|
Problem Statement: Many InfoPlus.21 related products historize timestamps as UTC and use a Microsoft function to convert them to local time for display purposes. Unless Microsoft provides a patch, the converted timestamps will be off by an hour during some week(s) when looking at past history
|
Solution: Queries that adjust the scheduled time of records and include a hard coded date for 1986 - 2006 DST changes will need to be changed to the new dates in 2007.
UPDATE from JANUARY, 2007
As of December 12, 2006, Microsoft published patches for Windows XP and Windows 2003 to account for the United States DST change. The patch can be found at the following link:
http://support.microsoft.com/kb/931836
Windows 2000 Customers will need to have a special Extended Hotfix Support agreement with Microsoft in order to receive a patch or the system can be updated manually by following techniques documented in the following Microsoft Knowledge Base article.
http://support.microsoft.com/kb/914387
Additional information on configuring DST can be found in the following link.
http://www.microsoft.com/windows/timezone/dst2007.mspx
UPDATE from FEBRUARY, 2007
AspenTech has tested all products and there are no known issues with the exception of the ones we have identified in this advisory. Once the Microsoft patch is applied, then the timestamps of some past history events will appear to be off by one hour starting the second Sunday in March till the last Sunday in April and starting the last Sunday in October to the first Sunday in November.
The Aspentech patches correct the Aspen Time Component used by Aspen InfoPlus.21, Aspen SQLPlus, Aspen Process Explorer, Aspen Process Data, and Aspen Web.21 for versions 6.0.1, 2004.1, and 2004.2. Patches for v2006 will be included in update 1 targeted for release in April.
Aspen eBRS, Aspen DMCplus, Aspen SLM, Aspen Engineering Suite, and Aspen AtOMS customers please refer to the AssociatedSolutions section of this article for additional information.
UPDATE from MARCH, 2007
Aspentech patches are now available that include fixes for the Aspen Time Component. Patches should be installed on appropriate systems by all customers planning to apply the Microsoft DST fixes. Aspentech patches can be installed before or after the Microsoft patches are installed. Any customers in time zones that do not adjust for daylight saving time and installed AspenTech DST patches before March 1 will need to reinstall the latest versions below.
UPDATE from MAY, 2007
Updated Cumulative InfoPlus.21 Server patches were released for v2004.2 and v6.0.l in May 2007
An InfoPlus.21 Cumulative Server patch for v2006 was also released for the first time. It contains the fixes for the Aspen Time Component.
v2006Solution 121051 - Aspen InfoPlus.21 v2006 Server Update Four (2006.0.4) - from v2006 or v2006.0.1 or v2006.0.1 with Cumulative Patch
v2004.2Solution 121355 - Aspen InfoPlus.21 2004.2 Cumulative Server Patch (IP070626Z) - June 2007Solution 120685 - Aspen Process Data v2004.2 Cumulative Patch # 7 - July 2008Solution 124216 - Aspen Process Explorer v2004.2 Cumulative Patch # 5 - July 2008Solution 120681 - Aspen Web.21 2004.2 Cumulative Patch - March, 2007Solution 120687 - Aspen Web.21 Graphic Studio 2004.2 Cumulative Patch - March, 2007
v2004.1Solution 120671 - Aspen InfoPlus.21 2004.1 Server Cumulative Patch (IP070301Z) - March, 2007Solution 122531 - Aspen Process Explorer and Aspen Process Data 2004.1 Cumulative Patch (DT121107A.WIN) - December 2007Solution 120684 - Aspen Web.21 2004.1 Cumulative Patch - March 2007
v6.0.1Solution 121118 - Aspen InfoPlus.21 6.0.1 Server Cumulative Patch (IP070402Z) - May, 2007Solution 124176 - Aspen Process Explorer version 6.0.1 Cumulative Patch - July, 2007Solution 120683 - Aspen Web.21 6.0.1 Patch (DT2007.03.02) - March, 2007
Keywords: time change
daylight savings
dst
day light saving
References: None
|
Problem Statement: This
|
Solution: outlines the details of an option that has been added in V7.2 that allows configuration of SQLplus servers and clients to use encrypted communications.Solution
Beginning with V7.2, Aspen SQLplus can be configured to run in encryption mode.
Running in encryption mode is more secure, however for large data sets with several hundred thousand rows, the encryption/decryption algorithms will introduce some small overhead into the overall retrieval time. This overhead should be evaluated against your business requirements with regard to record retrieval time.
Aspen SQLplus has been enhanced so that it can be configured to run in three different modes, described below:
a) Encryption -aware mode: This is the default mode. In this mode, the TSK_SQL_SERVER will handshake with each client to determine if the client is encryption -capable or not. It will use encryption /decryption communication to encryption-capable clients and not otherwise.
b) No encryption/decryption processing: In this mode, TSK_SQL_SERVER will send/receive non- encryption packages to both types of clients i.e. the encryption-capable (new) and non-capable (existing) clients.
c) Encryption-only mode: In this mode, TSK_SQL_SERVER only responds to encryption-capable (new) clients.
Encryption is enabled or disabled by entering command line parameters to the TSK_SQL_SERVER task in Aspen InfoPlus.21 Manager. This new command line argument determines which mode the TSK_SQL_SERVER should be running in.
no argument: Encryption-aware mode. This is the default.
B or b: Normal mode (No encryption/decryption processing).
E or e: Encryption-only mode
Keywords: V7.2 Overview
Encryption
Security
SQLplus Communication
References: None
|
Problem Statement: Tag replication fails with the error message System.ArgumentException: Primary queue is corrupt. Size is greater than allocated bytes in the file TSK_REPL_PUB.OUT on the publishing Aspen InfoPlus.21 server.
|
Solution: This message means the tag replication buffering files IP21Replication_primary.queue and IP21Replication_secondary.queue stored in Program Files\AspenTech\InfoPlus.21\Group200\Replication are corrupt.
To correct this problem, first stop Aspen InfoPlus.21 on the publishing server. Next, stop all the Aspen related services including those related to the Aspen Enterprise Integration Framework (EIF). After stopping the services, delete the contents of Program Files\AspenTech\InfoPlus.21\Group200\Replication. Then, restart the Aspen related and EIF services. Finally, start Aspen InfoPlus.21 again.
Keywords: IP21Replication_primary.queue
IP21Replication_secondary.queue
Primary queue is corrupt
Replication
References: None
|
Problem Statement: How can you recover history for a point you have deleted?
|
Solution: Every point stored in the Aspen InfoPlus.21 database has a record ID, and Aspen InfoPlus.21 stores historical information using record IDs. Since Aspen InfoPlus.21 does not delete history collected for a tag if you delete the tag, you can recover that historical information for the tag if you know the record ID of the tag you deleted and if the record ID has not been used by another tag.
Aspen InfoPlus.21 has no tool that returns record IDs of deleted tags.
Use the following query to determine if the deleted record ID is used by another tag:
select recid,name from all_records where recid=deleted_recid;
where deleted_recid is the deleted record ID.
If the deleted record ID is used by another point, then you must decide if you want to delete the new point and lose the history collected for it.
If the deleted record ID is still available, then you can used the SQLplus function CREATEREC to create a tag pointing to the deleted record ID.
For example,
CREATEREC('deleted_tagname', 'IP_ANALOGDEF', deleted_recid);
creates a tag named 'deleted_tagname' defined by IP_ANALOGDEF, using the deleted record id.
After recreating the tag, use the Aspen InfoPlus.21 Administrator to compete the definition of the tag. Be sure information pertaining to history repositories are the same as before you deleted the tag.
Finally, you must set the record creation time to before the time you first collected history for the tag. To do this, use the SQLplus function XOLDESTOK as in the following example:
xoldestok('deleted_tagname 1 ip_trend_value', '01-JAN-00 00:00:00');
sets the record creation date for deleted_tagname to January 1, 2000, midnight.
Keywords: XOLDESTOK
CREATEREC
RECID
References: None
|
Problem Statement: The Aspen InfoPlus.21 Manager suddenly won't start on servers running Symantec Endpoint Protection and displays the error message:
Cimmgr.exe - The application is unable to start correctly 0xc00000005
Several other executables in the Aspen InfoPlus.21 code folder also present the same error. This prevents Aspen InfoPlus.21 from starting.
|
Solution: Symantec Endpoint Protection Anti-VirusSolution marks some of the Aspen InfoPlus.21 executables as a false positive. To work around this problem, add all the Aspen InfoPlus.21 executables to the Symantec Endpoint Protection exclusion list as described in our knowledge base article 139438.
Keywords: Symantec
Anti Virus
CIMMGR.EXE
0xc00000005
References: None
|
Problem Statement: This knowledge base article shows the typical architecture of Aspen InfoPlus.21
|
Solution:
Keywords: Architecture
InfoPlus.21
References: None
|
Problem Statement: Aspen InfoPlus.21 will not start. TSK_DBCLOCK fails with error messages like Failed to load snapshot and Database version is too old for Aspen InfoPlus.21. This
|
Solution: is written for users who have V7.3x of Aspen InfoPlus.21 specifically.Solution
There are otherSolutions that deal with the Failed to load snapshot and Database version is too old for Aspen InfoPlus.21 messages. Check on the suggestions provided by those. If you have any V7.3 version of the Production Management and Execution products make sure that if patches have been applied make sure to bring the patch levels of other products or components (like Aspen Process Explorer, Aspen Process Data, and Aspen InfoPlus.21) up to the same level. The problem has specifically been observed when Aspen InfoPlus.21 is at V7.3 and the Aspen Process Data or Aspen Process Explorer is at V7.3.02. The problem is fixed by getting all the products to the same version level and then running upgrade.exe on the Aspen InfoPlus.21 snapshot.
Keywords: None
References: None
|
Problem Statement: What does the message ?Error: failed to create h21 shared-memory, ret =-2504? in TSK_DBCLOCK.err mean?
|
Solution: This message means that Aspen InfoPlus.21 did not stop completely and that a process like h21archive is still running and has not released the H21 shared memory.
Keywords: Error -2504
Shared-memory
Ret =-2504
References: None
|
Problem Statement: Encounter the below error message dialog when click on the Configuration Wizard button in the Aspen Configuration tab.
|
Solution: The above error message occurs for the following reasons:
1. Using Aspen InfoPlus.21 Configuration Excel 2007/2010 Excel add-in to connect to a IP.21 database version such as V7.1 that does not have the ProcedureDef record called AtXl_DbSchema.
2. The role the user belongs to does not have WRITE permission to the database.
When using the Aspen InfoPlus.21 Configuration Excel 2007/2010 Excel add-in to connect to a pre-V7.3 InfoPlus.21, it will attempt to create the ProcedureDef record called AtXl_DbSchema that does not exist in the earlier version. As such, if the user belongs to a role that does not have WRITE permission to the database, the missing ProcedureDef record cannot be created successfully.
Keywords: IP21ConfigUtilities.LoadDataBaseSchemaProcedureDef: InfoPlus.21 record AtXl_DbSchema does not exist
Aspen InfoPlus.21 Configuration Excel 2007/2010
AtXl_DbSchema
References: None
|
Problem Statement: The error message Invalid value in field nn FIELD_NAME_RECORD may be generated by the InfoPlus.21 Definition Editor or the InfoPlus.21 Administrator when making a definition record usable, where nn is a data field number.
For example,
|
Solution: This message indicates two or more data field names in the definition record have the same data field number. Within a definition record, the data field numbers of all the data field names must be unique.
Execute the following query to find the data field names with the same data field number after substituting the name of the definition record for wbbDef:
local defrecname record;
defrecname = 'wbbDef';
select field_name_record,field_name_record->field_number(hex) from definitiondef
where name = defrecname
order by field_name_record->field_number(hex)
Do the following to correct the error:
1. Delete the definition record.
2. Use the Aspen InfoPlus.21 Administrator to find one of the data field names having a duplicate field number and make the data field unusable. Change the hexadecimal field FIELD_NUMBER(HEX) to a number not used but any other data field in the definition record and make the data field usable again. If you cannot make the data field unusable, then it is being used by another definition record. In this case, it may be easier to create a different data field name with the new field number.
3. Create the definition record again.
Keywords: Definition Editor
Administrator
Usable
FIELD_NAME_RECORD
Definition Record
References: None
|
Problem Statement: What are the steps to be able to do demonstrations outside of the office. This includes not having a domain server and changing the IP address of the lap top.
|
Solution: There are two different issues that need to be addressed when using a laptop and travelling between different environments.
Networking connection.
In order to have proper communication between different components of InfoPlus.21 every system has to be able to properly resolve the TCP/IP name to the nodename.
This can be achieved best by putting the name and address in the NT hosts file (C:\WINNT\SYSTEM32\DRIVERS\ETC\hosts) of every system involved. Don''t forget to change this entry whenever you change the TCP/IP address of the server.
Many connectivity problems with the InfoPlus.21 Administrator and Aspen Process Explorer are traceable to problems with these settings.
Security
Make sure that you have installed all Aspen software when logged on as a local user with administrator rights. The same user has to be used when you are travelling abroad from your Domain Controller. If you have not enabled additional security within the Aspen environment you should be able to access even from client systems if you take care of item 1.
Keywords: demos
ip address
References: None
|
Problem Statement: This is a comprehensive overview of ENGCON - the omnipresent engineering console still widely used by many process engineers.
|
Solution: The abbreviation ENGCON stands for ENGineering CONsole. ENGCON is a character-based, rather than a Windows-based, tool originally developed to create, configure, and maintain the Setcim database and subsequently ported over to the Windows platform, to work with InfoPlus.21. Although the IP.21 Administrator is the primary tool of choice to use for IP.21, ENGCON is still available, and still a handy and easy tool to use.
However, there is limited documentation on how to use this tool. The information below can be used as a guideline on how to navigate and utilize all the features of ENGCON.
ENGCON provides the following functions:
Create, modify, or delete records
Create, modify, or delete reports (Setcim only)
Modify database parameters such as size, time format, maximum number of records
Save and restore the database to/from disk
Search for data records by name or record ID
Perform simple mathematical calculations
STARTING ENGCON:
1. Start a session on the host computer by clicking on the Start button.
2. Select the menu option Programs | AspenTech | Aspen Manufacturing Suite | Aspen InfoPlus.21 | Engineering Console
3. When you get a DCL prompt, Press Enter
NOTE: IP.21 users can start ENGCON by pressing and holding Ctrl key and then pressing the letter 'E' key while the IP.21 Manager window is selected as an active window.
ENGCON Key Usage
The procedure for maneuvering through ENGCON menus is described below.
The up, down, left, and right arrow keys move the cursor. There is NO mouse support within this tool.
The ENTER key invokes the selection under the cursor
The ESC key un-invokes the selection made by the ENTER key
The PG UP and PG DN or 'Page Up' and 'Page Down' keys page through RECORD CONTENTS screens
Ctrl+P invokes a HELP display
Data Entry is accomplished as follows:
Position the cursor on the desired field and type in the new value. Terminate with the ENTER key
Pressing the ENTER key twice while the cursor is on a data field causes the current value of the field to be placed on the data entry line for editing
The left and right arrow keys move the cursor in the data entry line
Ctrl+A on a PC alternates between insert and overstrike
The up and down arrow keys scroll through previously entered values
Special ENGCON keys:
The / and NUM LOCK keys on a PC (aka NEXT and LAST keys) move the cursor (as up and down arrow keys) and also scroll through all possible selections for certain fields while performing data entry.
The - and * keys on a PC (aka DO and UNDO keys) invoke/un-invoke menu selections.
General Record Maintenance Screen ---
The General Record Maintenance Screen of ENGCON is used to:
view records
modify records
create new records
delete obsolete ones
There are three commands on the screen:
VIEW
DELETE
CREATE
To invoke one of these commands:
Position the cursor on the selection and press ENTER. Records must be unusable to delete them, so ENGCON does not allow the cursor to be positioned on the DELETE command if the currently selected record is usable.
The first three fields of the screen provide information about the currently selected record, if there is one. The Record Name and Record ID fields can be used to select another record. Enter a specific record name or ID or, scroll through a list of options by pressing Enter, followed by the NEXT and LAST keys.
The Record Status field displays the record's usability status. It is the only field on this screen which changes an attribute of the currently selected record. The other fields select records, but do not change a record.
The Definition Record field serves two functions. When a record name and ID are displayed, this field identifies the record's data structure by giving the name of its definition record. When creating a new record, this field selects the data structure to use for the new record. Like the record name, either enter the name of a specific definition record here, or scroll through a list of definition records.
The Free ID field is used to select the record ID to use for the next record created. ENGCON does not accept an ID that is already used by another record. As new records are created, this field is incremented.
Record Creation
Records are created by using the General Record Maintenance selection from the ENGCON main menu.
To create a record follow the procedure outlined below:
1. Select the correct definition record by entering the definition record name or by using the NEXT and LAST keys to scroll through the available names.
2. Select the desired record ID in the Free ID field. Note that this field defaults to the first free ID and can be left unchanged if desired. By pressing ENTER and NEXT or LAST, the next/previous free ID is selected.
3. Select CREATE and press DO.
4. When prompted, enter the new record name.
5. Select record status and make the record usable - either by entering the word USABLE or by using the NEXT or LAST, keys.
6. Select any of the first four fields and press DO to view the record contents. The record contents can now be modified as described in the following section.
Record Modification
Not all fields in a record can be modified. In general, fields which are maintained by Setcim cannot be changed by a user. The cursor cannot move to fields which a user cannot modify.
For fields which can be modified, follow the procedure below:
1. Invoke the record contents by selecting one of the top four fields of the General Record Maintenance screen and pressing DO.
2. Select the correct page. If there is more than one page, this is indicated by the presence of a Page # in the top right corner of the display. After positioning the cursor on the Page # field, pages are selected in four ways:
a. Pressing DO immediately selects the next page.
b. Entering a number goes directly to that page.
c. Pressing ENTER and using NEXT or LAST scrolls through the available pages.
d. PG DN and PG UP (with the cursor anywhere on the screen) selects the next/previous page.
3. Move the cursor to the field to be modified.
4. Type in the new value. Some fields accept a value only from a predefined list of values. For example, the VALUE FORMAT field contains OFF/ON which specifies the only possible contents of the VALUE field. OFF or ON can be typed directly into the VALUE field or can be selected by pressing ENTER and using the NEXT/LAST keys. These predefined lists of values are created using selector records which are discussed in a later section.
5. Press the ENTER key.
The following editing features are provided:
Press ENTER twice to retrieve the current contents of a field.
Ctrl+A toggles between insert and overstrike.
Pressing the 'up' arrow key retrieves previously entered values.
Record Deletion
Follow the procedure as described below to delete a Setcim record.
1. Eliminate all references to the record by other records, displays and programs. The requirement to eliminate database references to a record before it can be deleted is enforced to ensure the integrity of the database. In other words, a record cannot be accidentally removed from the database if it is still used in an application. To remove a reference by another record, modify the other record using the procedure described in the previous section.
NOTE: Display and external program references cannot be checked when a record is made UNUSABLE. A program which tries to access a non-existing record receives an error return message. A display which accesses a non-existing record cannot be shown.
2. On the General Record Maintenance Display, set the record status to UNUSABLE. This is entered directly or selected by the NEXT/LAST keys.
3. Select DELETE and press ENTER.
4. Type DELETE to confirm and press ENTER.
CALCULATOR
ENGCON provides the ability to perform simple mathemetical calculations via its calculator. To activate this feature, press and hold the CTRL key and then press the L key. To perform a calculation, type in an equasion (without the = sign) and press ENTER.
Examples:
1. type 30+40 press ENTER and you'll get 70.00000000000
2. type 30*(40-30) press ENTER and you'll get 300.00000000000
3. type (.05*5)/25 press ENTER and you'll get 0.01000000000000
Keywords: ENGCON
Engineering Console
References: None
|
Problem Statement: Why do you get an authentication error when attempting to use the AspenONE Update Center?
|
Solution: This issue is usually caused because of having a proxy server which does not pass along authentication credentials.
One possible work-around is just making sure that you click on remember when giving your Support site password (see attached image.)
You can also try: if your local security policy allows, temporarily moving the Security from High to Medium in your browser (not forgetting to put it back to High of course after downloading the patches.)
Typically these two options work fine, but if they do not, you will need to make a note of the patch names and then download them individually from the Patches section of the Support Website.
Keywords: Authentication
Update
Center
References: None
|
Problem Statement: While installing the Aspen MES Products such as, Aspen InfoPlus.21, you might see the installation in a loop. Specifically you would see that the Installation Progress Percentage does not change, and the same message repeatedly flashing across the screen. Then when you look closely at the repeating message, or look in the install log file, you see something like:-
11:6:53 Action 11:06:53: ATLog.BA3F7B28_13D7_4630_902E_55D684AF3A97.
11:6:53 Action start 11:06:53: ATLog.BA3F7B28_13D7_4630_902E_55D684AF3A97.
11:6:53 Action ended 11:06:53: ATLog.BA3F7B28_13D7_4630_902E_55D684AF3A97. Return value 1.
|
Solution: Look in the Control Panel Services Applet to see if the Windows Firewall service is running. If not then start it and watch whether the Progress Percentage eventually increases (maybe wait a minute or two to identify it).
NOTE: For the installation to complete the Windows Firewall does not need to be turned on but the Windows Firewall service needs to be running - at least during the installation.
Keywords: None
References: None
|
Problem Statement: Is the order of the External Tasks in the InfoPlus.21 Manager important?
|
Solution: External Tasks are executable programs or batch files that typically run as a background process.
When you attempt to start the database, irrespective of which way it is done, the Aspen InfoPlus.21 Task Service will start the tasks in the order in which they are listed in the Defined Tasks list in the InfoPlus.21 Manager.
The order of the External Tasks is maintained in the Windows Registry ? HKEY_LOCAL_MACHINE\SOFTWARE\AspenTech\InfoPlus.21\XX\group200|RegisteredTasks
where XX is the version number.
In the example you can see that TSK_DBCLOCK has an order key value of 1 as it is the first task in the list and it runs as a background process (external = TRUE).
So, is the order important? Typically, user defined tasks are added to the bottom of the list.
However, notice that there are 2 buttons marked `move up? and `move down?. It can be tempting to move some of the tasks either accidently or intentionally. Unless specifically requested to do so by Aspen Support you should never do this as there is a dependency in place and during startup, some of the tasks further down the list assume that tasks further up the list have already started.
Keywords: Defined Tasks, External Tasks, Task list
References: None
|
Problem Statement: Infoplus21_api_server, and certain SQLplus queries have been observed to leak memory intermittently in isolated cases. In the past, attributing problems to memory leaks has either been due to circumstantial evidence, as a last resort, or by recommendation of 3rd level support / development. Using the Windows Performance Monitor utility, one can readily discern a memory leak from other potential problem causes.
|
Solution: STEP 1 - WHEN SHOULD I SUSPECT THAT MY SYSTEM IS MARRED BY A MEMORY LEAK?
The first step in thisSolution is to ask oneself a question:
Namely, what is a memory leak and when should I suspect that my system is affected by one?
In order for programs to store and process information, memory space must be allocated. This can happen by a direct variable assignment or dynamically as the program runs. However, when the program is finished using these spaces in memory, they need to be set back to a null value. In the vast majority of cases this happens systematically, but sometimes it does not. When a subroutine in a program fails to NULL used memory allocations, the program executable grows larger and larger. This is called a memory leak.
Two characteristic observations can usually be made regarding system performance that can tip off a user to a potential memory leak problem. These observations are:
The computer works fine after reboot but the system seems to operate less efficiently as time progresses.
Certain individual programs seem to get larger and larger. In other words, the programs seem to use progressively more memory.
If, after this step, one determines that a memory leak could be existent on his/her system, proceed to step 2 below.
STEP 2 - CREATE A PERFORMANCE MONITOR LOG
The Windows Performance Monitor can be found in Start | Programs | Administrative Tools (Common) | Performance Monitor. (In Windows Server 2008 the name was changed to Reliability and Performance Monitor.) After one starts the utility, a system performance log can be generated. Once a log is generated, it can either be viewed by the customer or emailed to AspenTech for analysis. It is true that some of this information can be viewed through the Performance tab in the Windows Task Manager. However, the Windows Task Manager does not allow the functionality of log creation.
1. Select View | Log
2. Select Options | Log . This dialog box will prompt the user to enter a log name. Enter an appropriate name for the log and click Save. This dialog box also allows the user to select the interval time in which system data is collected. For logs which span short time intervals, the periodic update can be set to a few seconds. However, for logs which span overnight or several days, a periodic update of 15 - 30 minutes can be used. This will prevent the log file from growing excessively large.
3. Select Edit | Add to Log . When this dialog box opens one will be able to select from a group of objects to monitor. Pertinent objects to monitor are:
o Memory
o Process
o Processor
o System
o Tcp (if available)
o IP (if available)
It's worthwhile to note that not all of these objects will be used in this particularSolution. However, monitoring these 6 objects can yield useful information regarding CPU time, network loading, and the like.
4. Once objects have been selected, go to Options | Log and select Start Log. Performance Monitor will begin collecting system data and the file size of the log will increase at the specified periodic update interval.
5. To stop the log, go to Options | Log and select Stop Log. Also select Save. The performance log has now been generated successfully.
STEP 3 - ANALYZE THE LOG FOR POTENTIAL MEMORY LEAKS
The performance log is now ready to be analyzed. To view the log, perform the following steps.
1. To open the log, go to Options | Data From... The default source will read perfmon.log. Change this to point to the performance log that needs to be loaded, then select OK.
2. Click on View | Chart if a chart is not selected by default. Then click on Edit | Add to Chart . This brings up a dialog box that will allow the user to select different objects (selected in step 3 above) to view. Select the Process object. In this same dialog box, select Handle Count for the counter. Go to the Instance list box and select the particular instance to view. In this case, the instances will be infoplus21_api_server (it will appear in the list as infoplus21_api_) or an iqtask. The chart will draw a simple graph of handle count vs. time for each instance. It will also display the minimum and maximum handle count for the given time interval.
The Handle Count is the number of open handles associated with each instance of an object. It is important to know that an excessive handle count for a given instance can be detrimental to overall system performance and can directly point to a memory leak problem within the instance. Of course, the number of open handles could depend upon how long the particular instance has been instantiated (in other words, how long the program has been running). For the instance infoplus21_api_server a handle count can be viewed as borderline excessive if it reaches into the lower ten thousands. A handle count significantly over ten thousand could potentially indicate a memory leak problem. However, even if a handle count is not this large, a memory leak cannot definitely be ruled out. This is due in part because a server reboot will close all open handles, and thus reset the handle count. This is why a system reboot will often seem to temporarily solve memory leak-related performance problems. At any rate, it is possible that one must wait a period of time from reboot to observe an increasingly large handle count and thereby trap the potential memory leak.
In order to gain a more complete perspective of a potential memory leak it is a good idea not to consider handle count alone, but rather, also look at the memory usage over the same time span. Memory usage due to a single application can be viewed by selecting the Process object, the Virtual Bytes counter and the specific instance for which memory usage is desired to be monitored. When used in conjunction, memory consumption and handle count for a specific instance of a program can provide enough information to allow an independent assessment of whether or not a memory leak is affecting a particular system.
It is important to keep in mind that one cannot merely consider a single number to conclusively indicate the presence of a memory leak. It becomes equally important to consider the overall trends of 'handle count vs. time' and 'memory usage vs. time' as additional potential memory leak indicators. If these trends seem to increase steadily without levelling off a memory leak is possible.
STEP 4 - CORRECTIVE ACTIONS TO TAKE IF A MEMORY LEAK IS DETECTED
If the memory leak is determined to be related to a particular AspenTech application, check AspenTech Knowledge Base to see if there is a service pack or a patch currently available that would fix it. If no patch is available, the problem should be reported to AspenTech Support so that it can be further investigated by our development team. Once development confirms it to be a defect, a patch will be issued and posted on the AspenTech Support website.
Keywords: hangs
freezes
hang
freeze
virtual memory
leak
handle
performance
resource
References: None
|
Problem Statement: What can cause the status of a tag to alternate and the value to swing?
|
Solution: Aspen Cim-IO may be scanning two signals from the process into the same Aspen InfoPlus.21 tag. To check if this is the case, open the Aspen InfoPlus.21 Administrator, right click on the problematic tag, and issue a Show
Keywords: IP21 administrator
Show
References: s command. Double check if all references are correct and make sure you don't have multiple IO transfer records (e.g. IOGetDef) trying to save data to the same tag.
Also verify that you don't have Aspen SQLplus queries or Aspen Calc calculations modifying the tag.
|
Problem Statement: There is a command line executable (program) to do an orderly shutdown of Aspen InfoPlus.21 (IP.21). This may be useful if you are administering the database from a remote system, and do not have access to the Administrator Tools or the InfoPlus.21 Manager.
Another example of when this may be useful:
This command can be embedded into a batch file, and be executed on demand. For instance, when a power failure occurs, and the UPS only has 15 minutes of reserve power, this batch file could be automatically executed when a signal from the UPS is received that notifies the OS of the impending power failure.
|
Solution: There is a command line executable called tsk_client.exe, which resides in the Aspentech\InfoPlus.21\shared\bin directory. Quite a few things can be accomplished using this utility, including stopping the database, and starting and stopping individual tasks.
Specifically, to stop the InfoPlus.21 database, execute the following command:
C:\Program Files\Aspentech\InfoPlus.21\db21\code>tsk_client /stop_infoplus21
Execute tsk_client with no arguments to get a listing of this and other usage parameters.
(Note: Your drive letter may be different.)
Keywords: command
executable
shutdown
References: None
|
Problem Statement: When InfoPlus.21 starts, application error messages may be generated for both:
TSK_H21T -- The instruction at <memory location> referenced memory at <memory location>. The memory could not be read.
TSK_PD_SERVER -- The instruction at <memory location> referenced memory at <memory location>. The memory could not be written.
Also, data is not being written to history.
|
Solution: NOHIS has probably been entered on the command line parameter for TSK_DBCLOCK and IP.21 is being started up without history. Remove NOHIS from the command line parameter, UPDATE the task, and restart IP.21
Keywords: h21task.exe
pd_server.msql.exe
pd_server.odbc.exe
References: None
|
Problem Statement: We recently had a customer who was getting an Access Denied error, when trying to run the SQLplus Query Writer. Even worse, he stopped the IP.21 database and could not restart it The customer's error on IP.21 restart was regarding a loss of service upon which the Group200 Task Service depended. When we looked in his control panel at the Services, he was missing several important services. Specifically, he could not see the Local AFW Trustee Server, Registry Security Server, SQLplus Authorization Server nor the WWW Publishing Server.
|
Solution: In the last few weeks there have been several viruses circulating and one in particular was IIS related. Thinking that the Web section of IIS was not needed, the customer went into IIS and manually removed some sections. The customer ended up having to reinstall both the OS and the Aspen products to fully recover
Keywords: IIS
Services
Viruses
References: None
|
Problem Statement: Is it possible to link IP.21 data to PowerPoint?
|
Solution: Yes, this is possible by way of using Excel.
Under the Insert Tab, select the Object button
Browse for an existing excel workbook. Be sure to check the Link box if you want values to be updated when PowerPoint is opened and closed.
This is an example of the data that appears in the Excel spreadsheet. Note that the value to the right is displaying the current value.
After closing and reopening PowerPoint, you will be prompted to Update Links. Select the Update Links button if you wish to update the links.
Note the current value has updated to the current time.
The layout of data and trends and the Excel spreadsheet will be maintained when opened in PowerPoint.
Keywords: Excel
PowerPoint
add-in
link
References: None
|
Problem Statement: When using the Data and Configuration Transfer Wizard, how does the Aspen InfoPlus.21history archiver know which archives on the source computer have been updated since the last transfer?
|
Solution: There are times when it is necessary to move an Aspen InfoPlus.21 system from one computer to another. You can either:
? Use the Data and Configuration Transfer Wizard (new feature of Aspen InfoPlus.21 V7.1)
Manually transfer data and configuration information
The functionality of the Data and Configuration Transfer Wizard will automatically transfer the Aspen InfoPlus.21 snapshot, history repositories, configuration and other standard files from a Source server to a Target server.
Note: In order to use the Data and Configuration Transfer Wizard, the source computer and the target computer must have InfoPlus.21 V7.1 or later installed.
After the execution of the Data and Configuration Transfer Wizard a file will be saved on the Target system. This file retains information about the last modified timestamp for the filesets from Source system.
Upon subsequent executions of the Data and Configuration Transfer Wizard this information will be sent to the Source computer to determine if updates are need to the Target filesets. If the timestamps on the Source filesets are different than what the file contains then the Data and Configuration Transfer Wizard will resend the filesets to the Target system. This request only happens when doing an update by selecting the Transfer current database and changed History files option in the Data and Configuration Transfer Wizard.
More information about this new feature can be found in the Aspen InfoPlus.21 Installation Guide V7.1 located via the Aspentech Support Center.
Keywords: Data and Configuration Transfer Wizard
HistoryFilesInfo.xml
References: None
|
Problem Statement: SQLplus Server creates many log entries in:
C:\ProgramFiles\AspenTech\InfoPlus.21\db21\Group200\Subscriptions\logs
for each individual SQLplus_server process. How can these logs be turned off?
|
Solution: The logging function can be turned on/off by editing a registry entry:
HKEY_LOCAL_MACHINE | SOFTWARE | Aspentech | InfoPlus.21| 10.0 | Group200 | Subscriptions | Logging | sqlplus_server
-> ERRORS
-> INFORMATION
The 2 string settings, ERRORS and INFORMATION can be set OFF and ON.
After putting these strings to OFF and restarting IP.21, the logging is gone.
Keywords: SQLplus, log
References: None
|
Problem Statement: Because of the new security features, in order for version 3.1 of InfoPlus.21 to be able to share data and access to databases across a domain network, the individual InfoPlus.21 systems must be installed under a user that is a member of a top-level trusted domain.
In addition, if the systems on which the InfoPlus.21 databases are installed are not a direct member of the top-level trusted domain, it must be a member of a domain that can inherit trust from the top-level domain.
Consider the following simplified diagram:
Top Top-level corporate domain
/ \
A B Local domains
| |
IP.21 IP.21 InfoPlus.21 systems/apps
The top-level domain is a trusted domain for both domains A and B, but A and B do not trust each other. The InfoPlus.21 systems trust only their local domain (A or B) and the top-level domain.
In order for AspenTech application users in domain A to get to the IP.21 database in domain B (or vice-versa), IP.21 must be installed using a login on the top-level domain and the user must also be logged in to a top-level domain account. Since IP.21 is often installed under a local account, it may be necessary to move it to a top-level domain account if data sharing and/or access across domains is desired.
This can be done by backing up all pertinent data, uninstalling the InfoPlus.21 server/database, reinstalling InfoPlus.21 under the new user account, and restoring all the data. However, some clients may not want their operational IP.21 systems removed and reinstalled. In that case, it is still possible to move an installed InfoPlus.21 server/database to a new user account without uninstalling/reinstalling it.
The attached procedure was written to do this at a customer site, but can be easily adapted to accomplish the same result at any client site(s) by simply substituting the appropriate domain and user names, passwords and drive letters.
|
Solution: See the attached document, MovingIP21.doc.
Keywords:
References: None
|
Problem Statement: Values in InfoPlus.21 do not correspond to values in the DCS for the same time period.
|
Solution: Depending on the data compression configuration used in a particular InfoPlus.21 history system, there may be times where the values in InfoPlus.21 do not match the values seen in the DCS. A slight difference in values may be attributed to the data compression routine, but significant or persistent differences are most likely attributable to some other cause.
This difference in values may be due to a corruption or mismatch in the tag mappings between the DCS and the InfoPlus.21 Get records. This can happen when customers make changes to tags in the DCS without re-activating the IOGet records in InfoPlus.21 to regenerate the scan lists.
When someone makes a change to an IOGet record without re-activating the record (turning OFF then ON), or changes have been made to one or more of the DCS tags in the IOGet record, the scan lists may become corrupt. This would cause an incorrect mapping between the IOGet record and the DCS, manifesting itself in a difference in values between the two systems. Re-activating the IOGet record regenerates the mapping correctly. The scan lists may also become corrupt from work or changes to the DCS or plant network, in which case regeneration of the scan lists by reactivation will also be necessary.
Depending on the particular DCS system being connected to InfoPlus.21 through our CIMIO interface, the tags may need to be re-translated to generate the correct mappings between the hardware and InfoPlus.21.
The InfoPlus.21 System Administrator should be informed if anyone changes any tags in the DCS, the IOGet records, or the tags themselves in InfoPlus.21. Proper reactivation will ensure correct mappings between the DCS and InfoPlus.21. For instructions on how to do a clean startup of the interface, seeSolution #103176.
Keywords: incorrect values
scan lists
record mappings
IOGet records
CIMIO
References: None
|
Problem Statement: PlantApDef records in Aspen infoPlus.21 can write to IP_INPUT_VALUE of standard tags. But a new value in IP_INPUT_VALUE causes a compression check and automatically updates the IP_INPUT_TIME and IP_INPUT_QUALITY. This makes it impossible to give a status to a value entered by a PlantApDef record.
|
Solution: The bestSolution is to use Aspen SQLPlus instead. It supports the Qtimestamp, Qstatus aggregate fields that allow IP_Input_Value and IP_Input_Quality to be updated at the same time. This is documented inSolution #102626.
Plantaps do not support the Qtimestamp, Qstatus (Aggregates) method like SQL or 'C' does. If PlantApDef records must be used for some reason, the standard workaround is to write to IP_VALUE then IP_VALUE_QUALITY and finally IP_VALUE_TIME, in that specific order. This bypasses compression, however, and will write much more data to history.
Keywords: None
References: None
|
Problem Statement: Customers often use trial and error to determine a comfortable IP_DC_SIGNIFICANCE value for data records. This process is time consuming as they have to specify an IP_DC_SIGNIFICANE and wait a period of time to collect the data for viewing in plots.
|
Solution: A proposedSolution is to use an SQLplus script to extract a sample based on a specified data compression value that the user had in mind from a pool of uncompressed values. The extracted sample is dumped to a text file which the user can view in a Process Explorer trend and compare with the raw uncompressed data.
A sample query is attached to thisSolution that can be used for a record defined by IP_AnalogDef. Modify the query by changing the values for the tagname, startdate, enddate, and dc. The tagname is the name of the tag which has the uncompressed data. The startdate and enddate are timestamps for the beginning and end time of the data sample. The dc corresponds to the IP_DC_SIGNIFICANCE value. Also the name of the output file can be modified to provide a better description for the tagname and data compression significance value.
The query stores the raw data in a temporary table. The query then loops through the temporary table, selecting data and performing the data compression. Compressed data is stored in a second temporary table. After the loop completes, the compressed data is written to the output file.
The output file can be viewed in Process Explorer by configuring a new data source in ADSA and using Aspen Process Data (File) as described inSolution 115105. Process Data for RDBMS or SQLA Tags can also be used to view the data. In these cases however, the data in the output file would need to be placed into a database like MSSQL or Oracle.
Once the output data is viewed in Process Explorer, the user can do a comparison of the compressed data versus the raw data. A comparison can be made on the amount of deviation between the trends of the compressed and raw data.
Keywords: ip_dc_significance
data compression
References: None
|
Problem Statement: One of the many distributed tests run by the Aspen InfoPlus.21 Health Monitor is called the IP21LicenseTest. As with all tests the results can be seen both from the thin Web client as well as by browsing the record with that name via the Aspen InfoPlus.21 Administrator. The reason for this article is to explain just what that test is looking at, and therefore the reasons this test might indicate errors.
|
Solution: With the release of V7.1 the two products Aspen Real-Time Statistical Process Control Analyzer (originally known as Aspen 'Q', or CIMQ), and Aspen KPI were added to the list of products that needed to be tested for licenses during run-time rather than just during installation. To do this a new field called IP_License_Confirmed was added to the two records TSK_CIMQ and TSK_KPI.
When either or both of these tasks is started, an API call is made via TSK_DBCLOCK to see if the product is licensed and an entry is made in the field Ip_License_Confirmed accordingly.
With the above knowledge, coming back to the HealthMonitor IP21LicenseTest, it performs the following:
1. Check licensing criteria of Aspen InfoPlus.21 itself via a call to TSK_DBCLOCK.
2. Check licensing criteria for Aspen CIMQ by looking in the external task record TSK_CIMQ for the field IP_License_Confirmed
3. Check licensing criteria for Aspen KPI by looking in the external task record TSK_KPI for the field IP_License_Confirmed
'Normally' the results of these three tests are written to the #Statements repeat area of the IP21LicenseTest record and the success or failure is reported in the Aspen Health Monitor.
We say 'normally' because it is possible that the IP21LicenseTests record reports an Error but the #Statements repeat area is blank. This would indicate that the upgrade of the snapshot had been performed incorrectly, such that one or both of the records TSK_CIMQ and/or TSK_KPI do not even have the field Ip_License_Confirmed. If you find this to be the case and want assistance, please call your local AspenTech Customer Support office and mention this knowledge base article 127815.
Keywords: None
References: None
|
Problem Statement: Applying security to a folder restricts access to the folder.A Does the folder's security settings apply to the records listed in that folder?
|
Solution: A folder's security settings do not affect the records listed in that folder.
Configuring security for a folder record does not affect the properties of records listed in the folder.
Keywords: Record Level Security
References: None
|
Problem Statement: How can I increase the maximum number of file sets that can be added to a repository?
|
Solution: By default the maximum number of file sets that can be added to a History Repository is 100. The number of file sets for all History Parameters can be increased by accessing the History Tuning Parameters from within the Aspen InfoPlus.21 Administrator.
1. Right click on and select History Parameters.
2. In the History Tuning Parameters window increase the Max column for the field Number Of Files to the desired number of file sets and click OK.
3. You should now be able to add new file sets as required. ** Important: Though the file sets can be added they will not be active until the InfoPlus.21 database is restarted. Inactive filesets appear grey in color. **
Keywords: Filesets;
Historian;
Repository;
Maximum number of filesets;
Cannot exceed maximum number of filesets;
References: None
|
Problem Statement: Aspen InfoPlus tags defined against older definition records using normal time stamp fields rather than extended time stamp fields may show future times if the tags have not been updated in the past two years as shown below. In this example, D-PMCAnalogDef is defined against PMCAnalogDef. The last update to the record was on 01-MAR-09 14:01:34.6; however, the field LAST_UPDATE (a normal timestamp field) displays 01-MAR-13 14:01:34.6, while the field TREND TIME (an extended timestamp field) shows 01-MAR-09 14:01:34.6.
|
Solution: Usually, updating the record causes current timestamps to appear.
The future dates are the result of the way Aspen InfoPlus.21 displays normal timestamps.
A normal timestamp is a 32-bit value representing the number of tenths of a second since the start of the previous leap year. Since normal timestamps roll over every four years and to allow for legitimate timestamps that are in the future, Aspen InfoPlus.21 treats current time as the middle of a four year period. This means Aspen InfoPlus.21 displays a normal timestamp as a time up to two years in the future if the difference between current time and the contents of the normal timestamp field is greater than two years
An extended timestamp is a normal timestamp with an extra word containing the number of leap years that have elapsed since 1900. Because of the leap year counter, extend timestamps do not roll over every four years.
PMCAnalogDef, PMCRealLabDef, CMLimitDef, and many other older definition records use normal timestamps.
Keywords: normal timestamp
future time
References: None
|
Problem Statement: The Aspen InfoPlus.21 Database API (Application Programmer Interface) is a set of routines, protocols and tools for building software applications that can communicate with Aspen InfoPlus.21 database.
The API server, which is a standard component of Aspen InfoPlus.21, is distributed on the same media DVD as Aspen InfoPlus.21. Whenever Aspen InfoPlus.21 is installed, the API Server is installed, and whenever Aspen InfoPlus.21 starts, the API Server is started.
The Aspen InfoPlus.21 Database API Manual describes that the API is a standard component of Aspen InfoPlus.21 and is installed whenever Aspen InfoPlus.21 is installed.
Will the InfoPlus.21 API get installed on client systems, so it can be used by remote applications?
|
Solution: The InfoPlus.21 API is not installed as part of Aspen InfoPlus.21 client installs, it can not be selected during the installation of client products.
The necessary API components, folders, library and header files can be individually copied from the InfoPlus.21 server system to the client system(s) to make the API components available for remote applications.
The folders to copy from the InfoPlus.21 server system to the client system are:
..\InfoPlus21\db21\include
..\InfoPlus21\shared\inc
..\InfoPlus21\shared\lib
to the client system so they can be used by the C++ or Visual Studio programs.
The AspenTech's KB 116586 Where can I download a sample C++ project which links with the Aspen InfoPlus.21 Application Interface (API)? describes a working example of a C++ project created with Microsoft Visual Studio using several InfoPlus.21 API functions.
Keywords: API
C++
client
server
References: None
|
Problem Statement: How often does the Aspen InfoPlus.21 historian empty in memory cache buckets?
|
Solution: Each point stored in a repository has an in-memory cache bucket. By default, the size of each bucket is 256 bytes, but that size is easily changed. Each history recording for a record defined by IP_Analogdef takes 15 bytes, which means that a default-sized bucket holds 16 historical recordings for records defined by IP_AnalogDef. When a bucket fills, the bucket is dumped to the appropriate file set. A cache bucket cannot span file sets.
Prior to version 2006, the Aspen InfoPlus.21 historian emptied all cache buckets for a repository whenever the repository shifted file sets. The dumping algorithm changed in version 2006. Cache buckets are left intact whenever there is a file set shift. If a new value for a point arrives, H21ARCHIVE checks if the destination file set for the new value is different from the destination file set of the recordings already in the cache bucket (because it is possible the time stamp of the new value places the recording into a previous file set). If the destination file set is the same as the recordings already in the cache bucket, then H21ARCHIVE adds the value to the cache bucket. If the destination file set of the value is newer than the destination file set of the recordings already in the cache bucket, then H21ARCHIVE dumps the cache bucket to the older file set and starts filling the bucket with recordings to be written to the new file set.
Suppose we have the following scenario:
Fileset 1 ranges from February 1 to February 8
Fileset 2 ranges from February 8 to February 15
Fileset 3 ranges from February 15 to February 22
Now suppose a lab sample arrives dated February 1, and this is the first recording made for this sample. Aspen InfoPlus.21 places this sample into a cache bucket associated with Fileset 1. A sample dated February 2 will be placed in the same cache bucket, as will samples dated February 3 and February 4. Aspen InfoPlus.21 will not empty the cache bucket until either the cache bucket fills or until a recording with a timestamp later than February 8 arrives. In either situation, InfoPlus.21 updates Fileset 1 even though the active file set is Fileset 3.
Keywords: cache
References: None
|
Problem Statement: Getting a message when using the Aspen InfoPlus.21 Administrator or Aspen Process Explorer programs after upgrading from V2004.x to V7.1.
|
Solution: This type of of problem is usually resolved using the steps described inSolution 123811, Troubleshooting Aspen InfoPlus.21 run-time license check messages.
If the steps in thatSolution do not resolve the issue, then check if you have the following scenario:
Used the ASPEN SLM (Sentinel License Manager) Configuration Wizard to configure the upgraded V7.1 programs to point to the new license server, but when starting the IP.21 Administrator or Process Explorer programs you reeceive the message.
In this particular scenario the customer was using the Aspen SLM Tools version 7.2 distributed with the 2004.x product, instead he needs to install and use the SLM Tools version 7.3 included in the V7.1 product, as this is a requirement of the new version.
To resolve the issue install the SLM Tools version 7.3 included in the V7.1 DVD and use the SLM Configuration Wizard to configure the products to use the new license server.
Keywords: acquire, ip.21 point license, slm
References: None
|
Problem Statement: This
|
Solution: explains the difference between modifying a value in history vs. inserting data into history and the outcome of each option.
Solution
Lets assume that we already have a data value in history for timestamp ?15-FEB-11 16:00:00.3?, which has a value of 7.64:
If you wanted to modify the value of this occurrence to 1.00 (you can also change the status, but NOT the timestamp), you could use the UPDATE statement in SQLplus. That way, the timestamp will be the same, and the ip_trend_qlevel would be Good/M:
If you want to insert data with the same timestamp of the existing data value, then one microsecond is added to the timestamp to accommodate the new value. You could use the INSERT statement in SQLplus:
Keywords: None
References: None
|
Problem Statement: The following error may be received when attempting to install Aspen Software: Error 1920. Service NobleNet Portmapper for TCP (NobleNet Portmapper for TCP) failed to start. Verify that you have sufficient privileges to start system services.
|
Solution: This error can be caused by other Windows services that rely on NobleNet Portmapper. Typically this error is caused by the Networker Remote Exec Service.
Open the Windows Service Manager
1. Click the Windows Start Button
2. Select Run
3. Type Services.MSC and click the OK button
4. Find the Networker Remote Exec Service
If the Networker Remote Exec Service is running stop or disable the service temporarily and reattempt the installation process.
Keywords: Installation
Error 1920
References: None
|
Problem Statement: The safest method of backing up the Windows server which runs Aspen InfoPlus.21 is to first shutdown Aspen InfoPlus.21. However, for various reasons, some customers do not wish to stop Aspen InfoPlus.21 at given intervals for their Windows server backups. This
|
Solution: outlines which files need to be skipped by the NT backup process to ensure that proper functioning of InfoPlus.21 is not affected.
Solution
Below is a list of files which should skipped during the Windows server backup, a functional description of each file, and the possible consequences if one does not skip this file during the Windows server backup.
Although thisSolution is written for a system backup, it is worthwhile to note that it can be applied to ANY program which accesses these files in such a flagrant manner. The most prevalent of these programs is virus scanning software.
Cache.dat
To understand why external manipulation of the cache.dat file can adversely affect performance of the historical process, one needs to first understand the purpose of cache.dat. The cache.dat is used by the IP.21 historian (h21archive.exe) every 5 minutes when the cache contents in memory are written to this file. This is done to prevent data loss during a power failure or server crash. Since cache.dat is reused every five minutes, the probability of utilization of cache.dat by the h21archive process during a server backup is quite likely (server backups frequently last longer than five minutes.)
The ramifications of an externally occupied cache.dat during system backup are distinct and readily noticeable. The IP.21 historical process will usually stop abruptly while a message is logged into the error.log file. The message in the error log will be to the following effect:
save_cache() open failure
The aforementioned error message indicates that the h21archive process cannot open the cache.dat file because another application has it in use.Solution document number 104466 details how to avoid such a problem as well as how to recover from this problem once it is noticed.
The following error might also be observed in the error.log. It is sometimes noticed to occur with the above error.
comp_mean() cache / key file mismatch
This error usually indicates that the cache.dat has become corrupt.Solution document number 103767 outlines corrective action to take if this message in noticed in the error.log.
Arc.dat
The arc.dat contains most of the historical data for a given file set. It actually contains the data points which have repeat areas that are smaller than 256 bytes. The arc.dat is accessed by the h21archive process whenever a particular cache entry slot is full. Moreover, a slot usually fills up after about 17 occurrences of data. (So arc.dat is accessed frequently!) If the arc.dat is in use by another application and thereby cannot be accessed by the h21archive process the IP.21 history system will shut down.
Archive > # data file open failure (where # is an archive number)
Arc.byte
Whereas the arc.dat holds data for tags with historical repeat areas less than 256 bytes, the arc.byte stores data for tags with history repeat areas greater than 256 bytes. Similarly, if the arc.byte is in use by another application and thereby cannot be accessed by the h21archive process the IP.21 history system will shut down.
Arc.key
The arc.key is simply a binary tree index into the arc.byte and arc.dat files. The h21archive process uses the arc.key for reference as to where to place the next block of data. If the arc.key is occupied while the h21archive process tries to access it the following error will be written to the error.log.
Archive > # key file open failure (where # is an archive number)
In the same way that the h21archive process shuts down when arc.dat and arc.byte are held by another application, an occupied arc.key will also cause the Aspen InfoPlus.21 history system to shut down.
Event.dat
To give a simplified explanation, the event.dat is created and used when the h21archive process has stopped. Event.dat is a buffer that holds data in the event that h21archive process ceases to function. The reasons for h21archive not to function are quite limited. The h21archive process can be paused, manually stopped, frozen, or could have terminated for another reason. Additionally, if one paused the h21archive process to make a backup then an event.dat buffer would usually be created, depending on the length of the backup procedure. Consequently, if one did not exclude event.dat from the backup process, it could effectively be occupied by the backup when Aspen InfoPlus.21 attempts to buffer data. This could result in a corrupt event.dat and the loss of data for the period in which the backup was made.
Snapshot
The current snapshot should be skipped in an Aspen InfoPlus.21 server backup because there is a remote possibility that the backup program can access it during an automated snapshot creation. This would result in a corrupt snapshot. Take frequent snapshots and backup the next to most recent snapshot.
Keywords: historian
backup
file set
archive
References: None
|
Problem Statement:
|
Solution: AWCustomReportFacility.doc (located in the attached zip file) provides readers with the information they need to start creating their own Aspen Watch custom reports. In addition, the document describes the AWChanges and AWHistory SQLplus procedures, which provide ways of retrieving Aspen Watch historical data with SQLplus that are simpler than using the standard SQLplus HISTORY and AGGREGATES tables. Many of the sections were copied from the Aspen Watch version 1.1.0 on-line help facility (hence extra copyright statements and strange formatting).
This application tool has not been reviewed by Aspen Technology's Quality Assurance group, and it it not part of the Aspen Watch product; therefore, it is not officially supported by AspenTech.
Keywords: AppTool
References: None
|
Problem Statement: Sample C++ project file for Visual C++ .NET is not documented.
|
Solution: Sample C++ project resides in %INFOPLUS21_BASE%\shared\samples\infoplus21_api\name2recid_test directory. It is for Visual C++ Ver.6 and it can be used with .NET compilers such as Visual C++ .NET 2003 and 2005.
Keywords: Visual C++ .NET
References: None
|
Problem Statement: If one has been collecting data for a while for a particular record where archiving is off, will enabling archiving allow the possibility for the loss of some data for this record?
The IP.21 Database User''s Manual provides a rather limited explanation on the operation of the archiving process. When IP_ARCHIVING is turned on, data is passed to the history repository. But at what point does data begin to be sent to the repository? Certainly the next data point after IP_ARCHIVING is turned on will be sent to the repository. But what about the current data point or even the previous data points that are in the memory repeat area?
|
Solution: ThisSolution illustrates the ramifications that the Past Time Parameter for a repository can have on the archiving process. The Past Time Parameter can be accessed from InfoPlus.21- Administrator | InfoPlus.21 | Group 200 on SERVER | Historian | then right click on the proper repository and select Properties. The Past Time Parameter will be visible on this window. The Past Time Parameter controls the time period for which old data can be inserted into a currently active repository. Moreover, the past time parameter, measured in hours, has a default value of 24. This means that, by default, data only 1 day old can be inserted into a history repository.
With this in mind, it is only possible to lose data under the distinct condition in which the older data records have timestamps which exceed the past time parameter. This is best understood with an example.
Suppose data for the record, Analog1.PV, is collected once per day for 60 days with IP_ARCHIVING set to OFF. The memory repeat area can be opened up to show the population of all 60 memory occurrences. However, if archiving is suddenly turned on, all occurrences that are older than the past time parameter will be flushed from memory while the occurrences with timestamps newer than the past time parameter will be written to the specified archive file. In this example, if the Past Time Parameter is left to the default value of one day, then all occurrences except the most recent will disappear (be flushed) from the memory repeat area while the newest value is written to the archive file. In order to allow data for all 60 days to be written to the archive file, the Past Time Parameter would have to be set to 1440 (assuming 720 hours in a month) prior to turning archiving on for the record.
When the Past Parameter is changed, it is necessary to completely stop and restart the InfoPlus.21 database before the change will take affect. SeeSolution #103981 for information about the maximum value of the Past parameter.
It is recommended to turn archiving on during initial record creation and configuration. This will prevent the above problem from occurring.
Keywords: File Set
Archive
History
Historian
h21archive
References: None
|
Problem Statement: Suppose, you have to create 100 data records (using the same definition record as a template), each of them slightly different than the other. This
|
Solution: describes how to use Save Records.... and Load Records... procedure outlined inSolution # 103486 (or your database user's manual) to create and mass load data records. You could save some time by following the procedure described below.
Solution
1. Create a data record using the appropriate definition record as a template
2. Save the newly created record to an .rld file (ASCII format) by right clicking on the Group200 in the IP.21 Administrator and selecting the Save Records... option
3. Open this .rld file in any text editor. Select the entire contents of the file, copy once, and then paste 99 times the contents of the .rld file to give you a total of 100 copies of the record within the .rld file
4. Edit each individual record within the .rld file to desired specifications; please remember to give each record a unique name as duplicate names are not allowed; you may also want to change the description of each record to reflect its function or source of data. It is not necessary to change the record ID of each one, as long as when you load, you choose the First Available ID option.
5. Save the file and load it into your database by right clicking on the Group200 in the IP.21 Administrator and selecting the Load Records... option
NOTE: Each data record within the .rld file will be automatically assigned a new Record ID; U character separates each record within the .rld file.
Keywords: RecSave
RecLoad
References: None
|
Problem Statement: The examples for an LDF file (figures 4-2 and 4-3) on page 4-9 of the IP.21 Database User''s Manual use the nonexistent field ip_device_name.
|
Solution: IP_DEVICE_NAME is not a valid field for an IP_DiscreteDef (or any other) record type. There is an IP_DEVICE_TABLE, but this field is a holdover from CIM/21 and is not normally used for an IP.21 system. Remove the reference to the IP_Device_Name before using the example.
Keywords: loadrec
documentation
IP_DEVICE_NAME
IP_DEVICE_TABLE
References: None
|
Problem Statement: By default, IoSummary -> MAX_SUMMARY_LINES will not be editable. This knowledge base article describes how to make this field editable.
|
Solution: To make MAX_SUMMARY_LINES editable, select 'InfoPlus.21', right-click then select 'Properties'.
Check on the box 'Override Operator Changeability'. Click on the <Ok> button.
Go back to the IoSummary record. The lines in 'MAX_SUMMARY_LINES' will now be editable.
KB article 123148 contains a short animation of the Override Operator Changeability feature.
Keywords: IoSummary
MAX_SUMMARY_LINES
Edit
References: None
|
Problem Statement: When installing InfoPlus.21 database on a node connected to a Local Area Network where Aspen Framework Server has previously been installed, you will receive the following error message when trying to install Local Security: Local Security may not be installed on a system with Aspen Framework installed ! This is because the Installation Wizard can see the Aspen Framework Server on the Network and it erroneously assumes that the Aspen Framework Server is installed on the machine where you are attempting to install Local Security. The same error is returned by the Installation Wizard when the 200.key (the Plantelligence license key) is installed on the system. If Local Security is intended for the system then uninstalling the 200.key will allow installation to proceed smoothly. Please see
|
Solution: applies only to a situation where there is an Aspen Framework Server installed on the Network, but the user is choosing to install and use Local Security instead of Aspen Framework Security. It also applies to a situation in which the user chose to install Plantelligence license key (200.key) without the intent of using Enterprise security.
Typically, when Aspen Framework Server is installed on the Network, Aspen Framework Security should be used for IP.21 databases. The scenario described here will most likely be encountered by AspenTech employees, as there are many installations of EIS software around the company.
Applicable Version(s):
Multiple
Keywords: 200.key
200
References: None
|
Problem Statement: Encounter the following error message:
when
1. manually inputting a value into a record
2. update the value of a record through Aspen SQLplus issuing SQL query such as
test.value = 2;
|
Solution: This is generally caused by Aspen InfoPlus.21 started with the NOHIS option in TSK_DBCLOCK. Either of the following actions can be taken:
1. Restart IP.21 without the NOHIS option,
2. Turn OFF archiving for the records in question.
Keywords: History generated but not archived (disk history status -1)
References: None
|
Problem Statement: This technical tip shows how to use the Aspen InfoPlus.21 Health Monitor to indicate if Aspen InfoPlus.21 is running on a remote node.
|
Solution: The health monitor running on an Aspen InfoPlus.21(IP.21) server can detect if IP.21 is running on a different server. Here is how you set this up.
In this example, the Aspen InfoPlus.21 Health Monitor running on a PC named BALCHB01 will check if Aspen InfoPlus.21 is active on a node named QABOX.
First, using the IP.21 administrator, create a record defined by IP21HealthDef named CheckQABOXIP21 by copying the record ExampleApplicationTest. Change the field IP_DESCRIPTION to IP21 Running on QABOX. and set the field ACTIVESW. to Auto.
Next, add a reference to CheckQABOXIP21 in the repeat area #DATA_BASE_RECORDS of the record CustomAppHealthTests as follows:
Next, paste the query attached to thisSolution into the Aspen SQLplus Query Writer to create a record defined by CompQueryDef named CheckIP21Systems. Set the field #SCHEDULE_TIMES to 1 and assign the query a scheduling frequency.
The Aspen InfoPlus.21 Health Monitor will then present a display similar to:
To monitor additional nodes, create a record similar to CheckQABOXIP21, add that record to CustomAppHealthTests, and modify the query.
Keywords: Application Health Tests
TSK_CLIENT
Health Monitor
Health Monitor Example
Health Monitor Application Health Test Example
References: None
|
Problem Statement: It is convenient to use an Aspen SQLplus query to load tags into Aspen InfoPlus.21 (IP21) databases.
|
Solution: This is a query that you can use as a guide to defining points defined by IP_AnalogDef.
The query creates IP_AnalogDef records based on the contents of a comma separated flat file.
The name of the file is:
C:\Program Files\AspenTech\InfoPlus.21\db21\Group200\taglist.csv.
The format of the file is:
tagname,description,engineering units,plant area,repository
The first line of the file contains column headers, and the points to be added start on line 2.
If a point's engineering units do not exist in the selector record ENG-UNITS, or a points's plant area do not exist in the selector record PLANT-AREAS, the query will add the data to the ENG-UNITS or PLANT-AREAS selector records.
You must have the historical repositories defined prior to running the query.
A sample taglist.csv ASCII file is also attached to thisSolution.
Keywords: Sample Query
Database definition
References: None
|
Problem Statement: One may encounter the following error when trying to install the Microsoft .NET Framework components needed by AspenTech products:
Microsoft .NET Framework 3.5 Setup <= Error Box Title
You must use the Role Management Tool to install or configure Microsoft .NET Framework 3.5.
|
Solution: The error box indicates that one needs to install the .NET components in a different way - as opposed to downloading them and running an installation program. Since the operating system already has the components (it ships with them) the desired way is to put them in place via a special tool designed for the job: the Server Manager.
Here is a screenshot of the Windows 2008 Server Manager:
To add the .NET Framework components, navigate to 'Features' on the left side and then click on the 'Add Features' selection (look for a green cross on the icon). A wizard will appear to guide one through the rest of the steps.
Keywords: None
References: None
|
Problem Statement: The error message Attempted to read or write protected memory. This is often an indication that other memory is corrupt appears when using the Show
|
Solution: Change the Aspen InfoPlus.21 Access Service to run under the same account that is running the Aspen InfoPlus.21 Task Service.
Keywords: Aspen InfoPlus.21 Access Service
Aspen InfoPlus.21 Task Service
TSK_ACCESS_SVC
ip21ServiceHost.exe
Show
References: s option for a record in the Aspen InfoPlus.21 Administrator.
|
Problem Statement: The Cim-IO icon does not appear when expanding an InfoPlus.21 node using the Aspen InfoPlus.21 Administrator.
|
Solution: The record PE_MainBranch controls what the Aspen InfoPlus.21 Administrator displays when you expand the InfoPlus.21 node name. Find the record PE_MainBranch, expand the repeat area PE_#_OF_OBJECTS, and verify the repeat area looks similar to:
After correcting the occurrence for CIM-IO, press F5 to refresh the Aspen InfoPlus.21 Administrator to see a screen similar to:
Keywords: blank
missing
install
feature
configuration
References: None
|
Problem Statement: The error No Free Record Id's over 2000 occurs when attempting to create new records in the Aspen Infoplus.21 (IP.21) database.
|
Solution: Generally this error occurs when there are not enough undefined records in the database. Knowledge Base article 104620 describes how to increase the number of records to resolve this issue. However the same error can occur if the Aspen InfoPlus.21 data base is not granted a license.
If the article noted above does not resolve the issue then
1. Go to IP.21 Administrator, right click on the Server name and select Database properties.
2. Go to License Status tab see if the license is granted or not. If a License is not granted then run the SLM Configuration Wizard from Start|AspenTech|Common Utilities to configure the license for this system. After configuring the license stop/restart Aspen InfoPlus.21
Keywords: token
References: None
|
Problem Statement: Aspen InfoPlus.21(IP.21) Administrator returned an error unknown error=-1 when trying to view tag data. At the same time attempts to execute Aspen SQLplus queries and viewing Aspen Tag Browser results in time out. On the whole, IP.21 database appears to be frozen.
|
Solution: The work around to resolve this problem is to stop and restart the following API tasks in Aspen IP.21 Manager
TSK_ORIG_SERVER
TSK_APEX_SEVER
TSK_EXCEL_SERVER
TSK_DEFAULT_SERVER
TSK_BATCH21_SERVER
TSK_SQL_SERVER
By restarting all the above tasks, Aspen IP.21Administrator, as well as other Aspen products, will start to function normally again.
This work around will return your Aspen IP.21 system to normal operating mode but does not pinpoint the problem. One possibility is that there might be an external process that has 'locked' the database. So, monitor the system closely to determine if there is a pattern as to when the database appears to be unresponsive.
An example of this is a failed IQ task. To check this go to 'ExternalTaskDef' record, right click on TSK_IQ1 and select 'Properties' then, go to 'External Task' tab. Look in the queue to see if the 'Currently Processing' field is pointing to any specific query name. If so, locate that query and determine if there is anything that is stopping the query from executing successfully.
Another possibility that is preventing a response from the Aspen IP.21 Administrator could be large number of Operating System handles (1,000 +) coming from another Aspen or third party products. For more information related to this issue please refer toSolution 122573.
Key Words
Unknown error =-1
Administrator
Keywords: None
References: None
|
Problem Statement: Sometimes Aspen Infoplus.21 may show some data with uncorrect time stamp after Daylight Saving time Day begins even after the clock got adjusted to the correct time and with the option automatically adjust clock for daylight savings is checked.
This happens specifically in some countries with no standard date like every second sunday from October, for instance but instead each year the Government decides when it is going to start the daylight saving time
|
Solution: 1) Make sure that the Aspen Infoplus.21 clock on the server machine is adjusted to the correct time and date.
2) Go to the TimeZone tab and check Automatically adjust clock for daylight saving changes
3) Apply the August 2011 cumulative time zone update for Windows operating systems on the Aspen Infoplus.21 server machine.
http://support.microsoft.com/kb/2570791/en
Keywords: daylight
patch
References: None
|
Problem Statement: Aspen InfoPlus.21 does not start correctly because the .IPG is missing or corrupt. How do I recreate a default Group Config .IPG file?
|
Solution: Stop IP.21 database and exit the IP.21 Manager
Regedit to HKLM\SW\AT\IP21\10.00\group200
o HKEY_LOCAL_MACHINE\SOFTWARE\AspenTech\InfoPlus.21\11.1\group200\
Export the entire Group200 branch to a file (backup) and delete it.
Open command prompt
o C:\Program Files\AspenTech\InfoPlus.21\db21\code\AddGroup.exe
o AddGroup.exe username password
o The username and password that must be used for the Aspen InfoPlus.21 Task Service.
? Open InfoPlus.21 Manager, go to File >Restore Group Configuration >Merge to Current Configuration > Keep Existing tasks and select the .ipg file that must be restored (if you have a backup), otherwise just save the Group Configuration
? Now InfoPlus.21 can be started with the default Group Config
Keywords: Group Config
.IPG file
InfoPlus.21
References: None
|
Problem Statement: AspenTech Internal-Technical information about the Data and Configuration Transfer Wizard.
|
Solution: is for viewing by AspenTech employees only
ThisSolution is for viewing by AspenTech employees only!!!
Customer Access is Company Specific
Keywords: Data and Configuration Transfer Wizard
HistoryFilesInfo.xml
References: None
|
Problem Statement: Aspen InfoPlus.21 Definition Editor에서 custom definition record 를 사용(usable) 할때 아래와 같은 오류 발생
|
Solution: 본 오류는 필드(field)를 삭제할때 references를 삭제하지 않았기 때문입니다. 본 오류는 history repeat area를 수정할때 자주발생하는 문제이고 아래와 같은 절차로 문제를 재생할수 있습니다.
1. Aspen InfoPlus.21 Definition Editor 에서 복사(Duplicate) IP_AnalogDef
2. 복사(Duplicate) Definition Record 에 새로운 이름 입력
3. history repeat area IP_#_OF_TREND_VALUES 아래의 IP_TREND_TIME, IP_TREND_QLEVEL, IP_TREND_QSTATUS 와 IP_TREND_VALUE fields를 오른쪽으로 클릭하고 삭제(Delete) 선택
4. IP_#_OF_TREND_VALUES 를 오른쪽으로 클릭하고 삭제(Delete)
5. Record | 저장(Save) 로 수정한 custom definition record 저장.
6. 수정한 Record를 오른쪽으로 클릭하고 사용하기(Make Usable) 선택
오류를 아래와 같은 방법으로 해결
1. rld파일을 다시 로드(Reload)혹은 이미 사용하고 있는 Record를 복사(duplicate)
2. History repeat area field를 오른쪽으로 클릭하고 수정(Modify) 선택 (예: History repeat area field = IP_#_OF_TREND_VALUES).
3. 뜨는 창에서 세부내용(Details) 부분을 보통(Normal) 로 설정
4. OK 클릭
5. Normal repeat area 인 IP_#_OF_TREND_VALUES 아래의 필드(fields)를 각각 선택하고 삭제(Delete)
6. Normal repeat area 인 IP_#_OF_TREND_VALUES 삭제
7. Record | 저장(Save) 로 수정한 custom definition record 저장.
8. 수정한 Record를 오른쪽으로 클릭하고 사용하기(Make Usable) 선택
History repeat area의 전부 필드(fields) 삭제가 불가능하면 아래와 같이 작업 실행
1. rld파일을 다시 로드(Reload) 혹은 이미 사용하고 있는 Record를 복사(duplicate)
2. History repeat area field 확장 (예: History repeat area field = IP_#_OF_TREND_VALUES).
3. 삭제할 IP_TREND_VALUE filed를 오른쪽으로 클릭하고 Special | History Source 선택.
4. 뜨는 창의 History field 에서 <None> 선택
5. OK 클릭
6. 오른쪽으로 filed IP_TREND_VALUE 클릭하고 삭제(Delete) 선택
7. Record | 저장(Save) 로 수정한 custom definition record 저장.
8. 수정한 Record를 오른쪽으로 클릭하고 사용하기(Make Usable) 선택
Keywords: Definition Editor
<Defintion_name> is referenced by <Defintion_name>and can not be made unusable.
KR-
References: None
|
Problem Statement: This Knowledge Base article provides explains the root cause and provides re
|
Solution: to the following problem:
Aspen InfoPlus.21 Administrator does not see local Aspen InfoPlus.21 server, it can only be seen from inside of the Neighborhood option.
Also, that same local Aspen InfoPlus.21 server does not appear in the pull down menu of the Find InfoPlus.21 Record tool.Solution
In versions prior to aspenONE 7.1, Aspen InfoPlus.21 installation created all of the environment variables required for the proper operation of the software. As of aspenONE 7.1, this is no longer the case. However some customers have chosen, for whatever reason, to manually recreate some of those environment variables. Since some of them originated in Aspen SETCIM (an older database which used to run on UNIX), they are case sensitive.
The environment variable that enables Aspen InfoPlus.21 Administrator to see its local IP.21 server is called SETCIM_GROUP_NAME and its value is group200, spelled with the lower case g. If it is spelled with the upper case G, or any upper case characters, the Aspen InfoPlus.21 Administrator will not be able to see its local server outside of Neighborhood.
Keywords: None
References: None
|
Problem Statement: What can cause the error message cannot open cache table file in TSK_DBCLOCK.OUT when starting Aspen InfoPlus.21?
|
Solution: This message appears when repository file paths are incorrect.
To solve this problem, first try to restart Aspen InfoPlus.21 with the VERBOSE flag added to the command line parameters for TSK_DBCLOCK. After the next failure, re-open the TSK_DBCLOCK.OUT. The new output will contain directory location information for every Repository and every Fileset. Examine this output to discover the incorrect settings and then correct the file paths to the repository and file sets using the utility H21CHGPATHS.exe
Keywords:
References: None
|
Problem Statement: P
Knowledgebase article 104056 describes how to add a port number to one of the six api processes such as Tsk_Apex_Server
It explains how a Port number for InfoPlus.21 client application can be fixed by using the command
line option -n(port number) of api server external tasks.
However it is possible that the assigned port number for the api server is not used even if the number is not listed in the IANA registered port number list and netstat does not show the port number is used. So the next free number is used.
|
Solution: Use an unused port number larger than 10000.
Port number 1024~5000 are sometimes used or reserved by existing processes in the system. But, port number larger than 10000 are rarely used or reserved by the processes in the system.
netstat only shows the active port number. It means netstat only shows the port numbers in ESTABLISHED status. It does not show the pot in LISTENING status. Portmapper would not select the port number in LISTENING status also.
netstat -a shows the all the connection including LISTENING status.
Keywords: FIREWALL
port number
infoplus21_api_server.exe
References: None
|
Problem Statement: Applying the Aspen InfoPlus.21 V7.3.0.2 patch requires a database snapshot upgrade.
|
Solution: AspenTech modified the definition records IP_AnalogDef and IP_DiscreteDef to support the generation and storage of best fit data as part of Aspen InfoPlus.21 input processing. This means that you must upgrade your Aspen InfoPlus.21 snapshot after applying this patch. Aspen InfoPlus.21 will not start if you do not upgrade your snapshot after applying this patch.
Keywords:
References: None
|
Problem Statement: The repository turned red and started showing errors such as Invalid ServerIndex 0 was specified. It is not possible to delete the repository using the Aspen InfoPlus.21 Administrator and any Aspen SQLplus query that scans records defined by DiskHistoryDef will fail:
|
Solution: Use the command TestAtIP21HistAdminVC to manually remove the corrupted repository without having to restore the CONFIG.DAT file.
1- Run C:\Program Files\AspenTech\InfoPlus.21\db21\code\TestAtIP21HistAdminVC.exe as an Administrator.
2- Select In Process and click Connect
3- Manually type in the repository name and click on Delete Single Repository
4- Restart Aspen InfoPlus.21.
5- Re-create the same repository and add the same number of file sets. Make sure to point to the same location as before to be able visualize the historical data.
Keywords: TestAtIP21HistAdminVC.exe
Corrupted Repository
Invalid ServerIndex
References: None
|
Problem Statement: Aspen InfoPlus.21 migration to new hardware: How can we do it quickly?
|
Solution: ** This is a customer's in-houseSolution - procedures that they have used internally for major hardware migrations and software migrations (version 2.5 to 2006.0) for their Aspen Infoplus.21. **
Keep in mind that starting with V7.1 a new Data and Configuration Transfer Wizard exists that could be used to help automate some of the following described tasks.
1. Prepare a new machine and configure any domain security/configuration.
2. Install Aspen Manufacturing Suite on the new machine (M_NEW), offline.
3. With this new machine offline, similar machine name can be used without any OS errors or conflict.
- This will also provide added benefits for setups with CIMIO store and forward.
4. Copy and configure the necessary Infoplus.21 settings from the old machine (M_OLD) to the M_NEW.
- Please see Aspen Infoplus.21 Installation Guide 2006.0, Appendix D - Migrating Infoplus.21 from one Computer to Another.
- It is necessary to do a mock startup to ensure that Infoplus.21 can be started properly.
5. When the new machine is fully configured and ready to adopt the latest snapshot and history files, shutdown the Infoplus.21 processes on M_OLD.
- If S&F is configured, new incoming data should be stored on the respective CIMIO servers. There is also no need to delete any store files as the M_NEW machine adopts the same IP and machine name.
6. Isolate both M_OLD and M_NEW in a localized network connected only with cross cable.
- This will isolate any transfers and provide a faster file transfer throughput.
- Similar machine names on M_OLD and M_NEW will not cause any problem since they are connected only by cross cable.
7. Transfer the snapshot and repositories.
- Based on experience, ~10GB of data can be transferred within 10 minutes using cross cables.
8. Bring the M_NEW machine into the network and adopt the M_OLD machine IP address.
9. Test the CIMIO connectivities.
10. Start Infoplus.21 service.
Contributed by:
Hariom Raval, Process Automation
RELIANCE INDUSTRIES-JAMNAGAR
Keywords: None
References: None
|
Problem Statement: How do I resolve the following error message reported in the Aspen InfoPlus.21 historian error log file (error.log):
create_record allocate failure: Invalid argument
|
Solution: This error typically occurs because of the existence of a large file set (over 2 GB). To troubleshoot this error, check the size of the file arc.dat in each file set and look for one larger than 2 GB. If it exists, you must stop Aspen Infoplus.21, delete the file and restart Aspen Infoplus.21 again.
Unfortunately the data in the affected file set(s) is lost.
The problem sometimes could be traced to CIM-IO sending inconsistent data to the database thus corrupting the history file set(s).
AspenTech added support for file sets larger than 2 GB in version 2006.5.
Keyword
History, create record allocate failure, file size
Keywords: None
References: None
|
Problem Statement: When I check the version of an Aspen DLL or .EXE file how can I tell which aspenONE release it came from?
|
Solution: Every new release of the aspenONE suite has a corresponding internal versioning scheme. This table can be useful to determine from which major aspenONE version a particular Aspen .exe or .DLL comes from. Keep in mind that a different internal version is not a guarantee the file contents are necessarily different, since not every single file is changed between releases, but it will confirm what aspenONE version the file belongs to since even files that are not internally changed get new versioning when compiled as part of a particular release.
aspenONE Manufacturing Suite Version
Internal Version
aspenONE V7.2
11.2.x.x
aspenONE V7.1
11.1.x.x
aspenONE Version 2006.5
10.0.x.x
aspenONE Version 2006
9.x.x.x
aspenONE Version 2004.2
8.0.x.x
Note the jump from 10.0 to 11.1, since the Aspen Engineering Products had a V7 release, but Manufacturing went directly from Version 2006.5 (10.0.x.x) to V7.1 (11.1.x.x.)
Keywords: Product release
versioning
internal
References: None
|
Problem Statement: Changing the date on Windows NT causes scheduling problems with InfoPlus.21 schedule records
If an incorrect change is made to the Windows NT system time, it can cause problems with InfoPlus.21 that will continue even after the time is reset correctly. Most notably, records defined by ScheduledActDef will fail to be updated properly after correctly setting the system time.
When an incorrect time shift into the future is made, InfoPlus.21 ScheduledActDef records whose SCHEDULE_TIME is prior to the current time are immediately updated. If the date has been changed far into the future, it could cause all such records to simultaneously update. As part of the update, InfoPlus.21 places the current system time plus the RESCHEDULE_INTERVAL value into SCHEDULE_TIME.
At this point, if the time is changed back to the correct time, then none of the incorrectly activated ScheduledActDef records will update again until they reach SCHEDULE_TIME. Since this could be far into the future, it could be a long time until they activate.
When the time is incorrectly changed to a past time, the ScheduledActDef records will not activate until the value held in SCHEDULE_TIME. Once the time is corrected, however, overdue records will be activated.
|
Solution: Changing the date on Windows NT can cause problems with various InfoPlus.21 systems. It is important that the server's date and time control panel be protected from incorrect changes.
Windows NT's User Manager can be used to protect from such changes by selecting Policies/User Rights? and selecting Change the system time from the selector box, then granting privileges only to appropriate users. As an extra precaution, a server administrator may wish to completely remove all privileges to change the time and date, then add them back only when required.
Should the time be changed into the future causing some of the ScheduledActDef records to stop updating, there are several remedies. One is to manually edit the SCHEDULE_TIME interval to a time when processing is desired. SQL Plus can automate this process with a query such as:
UPDATE (SELECT SCHEDULE_TIME FROM (SELECT * FROM SCHEDULEDACTDEF)) SET SCHEDULE_TIME = '01-AUG-98 12:33:21'
This query simply changes all the SCHEDULE_TIME fields in all the ScheduledActDef records to the desired activation time. This command should be used with caution and users should verify that this is the change they wish to make to all the ScheduledActDef records.
Note that there are other issues which may arise after such a date change, as well as problems with other systems such as History and scheduled QueryDef records. Contact your support resources if you are unsure of how to remedy these problems.
Aspen Technology, Inc.
19204 North Creek Parkway, Suite 104
Bothell, WA 98011 USA
PHONE: (425) 492-2000
Keywords:
References: None
|
Problem Statement: What is the difference between APIConnInfoDef and APIInfoDef?
|
Solution: The APIInfoDef records were created to allow users to monitor usage and troubleshooting information in regards to each API server process which connects to the Aspen InfoPlus.21 database. The distributed set of records defined by APIInfoDef is shown in the diagram below. The individual fields within those records are described in Knowledge Base Article #117176, and are collectively known as the Aspen InfoPlus.21 API task monitoring records.
The APIConnInfoDef Record, in contrast, was discontinued and removed from the Aspen InfoPlus.21 database in version 4.0.1 SP1. The APIConnInfoDef Record was intended to be used to keep statistical information about API Server usage, and was discontinued in favor of using the Windows NT Performance Monitor instead. Due to an overwhelming request from Customers however, it was added back into the database record structure and the name changed to APIInfoDef starting with version 6.0 Build 61.
Keywords: APIInfoDef
APIConnInfoDef
References: None
|
Problem Statement: How to set up an alias name for an Aspen InfoPlus.21 record.
|
Solution: Alias names can be used for Aspen Infoplus.21 records by configuring an IP_AliasDef record.
Create an IP_AliasDef record with the desired alias name
Make the alias record unusable
Populate the Record_Name field with the name of the record to alias
Make the alias record usable
After configuring the alias record data in the original record can be viewed in AspenTech desktop products like Aspen Process Explorer, and Aspen Process Data Addin. Note: IP_AliasDef records do not work with Aspen SQLPlus.
Keywords: alias
References: None
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.