question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: Sometimes I get a message about a missing DHFORM or DHAQFM in a reactor, but sometimes I do not.
** ERROR
PHYSICAL PROPERTY PARAMETER DHFORM OR DHAQFM IS MISSING FOR H4SIO4.
ABSENCE OF THIS PARAMETER WILL RESULT IN INCORRECT ENTHALPY CALCULATIONS.
Problem OCCURRED WHILE FLASHING OUTLET STREAM. | Solution: The missing parameter check is made when the specie amount is changed by more than 1e-8 kmol/s. On some sensitivity rows, the change is just above that causing the check and the error. The amount of 1e-8 is applied to absolute difference as it is pretty small, and a relative amount check could cause such small amounts to be picked up as errors, even though they still would not impact the results.
To avoid the error message, the parameter DHFORM needs to be added for the component. If only a small amount of the component is generated, the value entered is not critical.
Keywords: None
References: :CQ00504568 |
Problem Statement: I am developing my Aspen Properties application using the option you suggested: Multiple Property Methods. I can see that I can retrieve the currently active (global) property method OPSET name by calling PPUTL_GOPSET. But, I cannot find a way to
(1) Determine how many Property Methods were specified (in addition to the global Property Method)
(2) Determine the secondary Property Method OPSET names.
(3) Determine the values of HENRY, CHEM, ITRUE, FREEW, ISOLU so that I can call PPUTL_PPSWOP for any of the specified Property Methods. | Solution: Here is an undocumented subroutine PPUTL_LSOPST that you can call to determine the number and names of the Property Methods specified in a simulation..
CALL PPUTL_LSOPST(KOPS, NAME, IST, INUM )
VARIABLE I/O TYPE DIMENSION DESCRIPTION AND RANGE
KOPS O I - number of option sets
NAME O C 8*KOPS OPTION SET NAMES (in character strings;
Each option set name is 8 character long)
IST I I - First property method, set to 1
INUM I I Property method number
For example,
F Call PPUTL_LSOPST (KOPS, op_Names, 1, 1)
f write(nhstry,30) kops
F 30 format(/,'number of option sets KOPS',I4,/)
f do i=1,kops
f Call PPUTL_LSOPST (KOPS, op_Names(I), 1, i)
F write(nhstry,10) i, OP_Names(I)
F 10 format(/,'OP_Names(',I4,') = ',A8/)
f end do
In the attached file that has three property methods H2O-STM, IDEAL, and PR-BM, this will result in the following output in the history file:
NUMBER OF OPTION SETS KOPS 6
OP_NAMES( 1) = SYSOP0
OP_NAMES( 2) = SYSOP12
OP_NAMES( 3) = STEAM-TA
OP_NAMES( 4) = H2O-STM
OP_NAMES( 5) = PR-BM
OP_NAMES( 6) = IDEAL
The additional property methods SYSOP0, SYSOP12, and STEAM-TA were added by Aspen Plus.
The first element of The Property Method array NBOPST is the name bead. The name bead can be retrieved using the utility PPUTL_FIOPST.
CALL PPUTL_FIOPST(NAME ,NBOPST )
VARIABLE I/O TYPE DIMENSION DESCRIPTION AND RANGE
NAME I I 2 OPTION SET ID'S, 8 CHARACTERS
(2 WORDS), MAX.
NBOPST O I - OPTION SET BEAD NUMBER
The other elements of NBOPST (elements 2-6) are Henry Components, Chemistry ID, Use True Components, Free-Water Method, Water Solubility. These are set in the base property method but are not for the other referenced methods. When calling the swap utility PPUTL_PPSWOP, you will need to copy the elements from the base property method.This can be done by calling the get property method utlity PPUTL_GOPSET.
In the example, for the Property method PR-BM, PPUTL_GOPSET retrieves:
NBOPST = 100000147 0 0 1 100000101 3
And PPUTL_FIOPST retrieves:
NBOPST = 100000147 0 0 0 0 0
The attached example file uses a Calculator block to test these calls. They can be used in a similar manner in a user subroutine. A Fortran compiler is required to run the example.
Keywords: None
References: None |
Problem Statement: I have a Hierarchy block in my simulation. Is there a way that I can move everything inside into the main flowsheet? | Solution: You can right-click on the Hierarchy block select Move selection.
You can use the Extract hierarchy contents and delete option. Clicking on OK will prompt you to resolve ID conflicts if there any. Ater you resolve conflicts, all the objects will be transferred into the main flowsheet.
Keywords: Hierarchy
Flowsheet
References: None |
Problem Statement: I was able to define conversion and selectivity through the Calculator block. By using Fortran Write statements, the results are printed in control panel. I was wondering if I can print the output on the flow sheet itself so I won't need to go to the control panel every time I want to check the values. | Solution: You can put the values on the flowsheet using a Custom Table created by clicking on the icon on the Customize ribbon. If you assign a parameter variable to the calculated value, you can place the Define variable result a custom table. The table can be placed on the flowsheet or viewed as a form. In the attached example, the percent conversion of Cl2 in a reactor is calculated in a Calculator block and reported in the table.
Keywords: None
References: None |
Problem Statement: You are unable to add records or folders in the Infoplus.21 Administrator and receiving the error 'Invalid Sever Index 0 was specified after using RECLOAD to add records to your snapshot. | Solution: This problem occurs when you are using the utility RECLOAD to add records to your snapshot and the number of records surpasses the number of free records in the Infoplus.21 database.
To resolve this issue you will need to increase the number of Total records you have in the Record Utilization tab.
1. In the Infoplus.21 Administrator right click on your Infoplus.21 database and select 'Properties'
2. Click on the 'Record Utilization' tab and increase the number of total records.
3. Stop Infoplus.21 from the Infoplus.21 Manager and then restart Infoplus.21.
Keywords: Invalid Sever Index 0
Recload
Infoplus.21 administrator
References: None |
Problem Statement: After successfully installing IP.21 version 3.1, two error messages appear while trying to add a new InfoPlus.21 group. First an Access Denied. message followed by Error while attempting to unregister the security repository for the old group. | Solution: The first step is to check DCOM permissions. To do so, go to Start | Run | dcomcnfg. In the DCOM configuration window, under the Default Properties tab confirm that the default authentication level is Connect and the default impersonation level is Identify.
If DCOM already contains these properties, it may be necessary to uninstall and reinstall all AspenTech products.
Uninstall all AspenTech products
Clear the registry of any AspenTech entries
Delete any remaining AspenTech related folders
Reinstall version 3.1
Keywords: groups
configuration
References: None |
Problem Statement: Microsoft SQL Server installation fails when installed after aspenONE products.
Some Microsoft SQL Server components are installed along with several AspenTech products. Including: Aspen PIMS, Aspen InfoPlus.21, Aspen Operations Reconciliation and Accounting, Aspen Tank and Operations Manager, Aspen Reporting Framework, Aspen Petroleum Scheduler. One of the components Microsoft SQL Server Native Client causes the Microsoft SQL Server installation to fail with the following error.
Microsoft SQL Server xxxx setup: The following error has occurred:
A network error occurred while attempting to read from the file:
[install-device-name?and-root-of-path-here]\x64\setup\x64\sqlncli[1].msi | Solution: 1. Go to Program and Features.
2. Uninstall Microsoft SQL Server Native Client.
3. Install Microsoft SQL Server.
Note: Microsoft SQL Server Native Client will be reinstalled along with SQL Server.
Keywords: Express, SQL, installation, order
References: None |
Problem Statement: How have timestamps changed? What is the re | Solution: , how is it processed, and what will I see in my client applications?Solution
In considering this information it is helpful to note that the IP.21 real-time database is separate from the IP.21 historian.
Millisecond reSolution is new to the IP.21 real-time database in version 3.x. However, even in previous versions the IP.21 historian was capable of storing millisecond reSolution timestamps. However, in these previous versions, comparing two timestamps was done only to the 10th of a second.
If two data points for the same tag are written with identical timestamps (for instance, running an INSERT command in SQLplus multiple times which write a value with identical timestamps), the Historian automatically increments the follow-on inserts by a millisecond apiece, since they must receive unique timestamps to exist in history. However, because the database does not recognize these higher reSolution timestamps, the various client tools show what would appear as identical events (to the 10th of a second) recorded to history (though in reality they are unique, separated by a millisecond.)
Process Explorer and SQLPlus also had the same 10th of a second precision in earlier versions.
In version 3.1 and higher the database allows for new timestamp formats that display up to decamilliseconds. Process Explorer will also show this change.
However, SQL still does not handle the higher reSolution as of version 3.x, so you can still only view and process data to the 10th of a second.
Keywords: sqlplus
timestamp
References: None |
Problem Statement: This Knowledge Base article answers the following question:
Why every four minutes TSK_DBCLOCK sends the following message to the license server:
IP21ServerUpdateLicenseState - *X_GetIP21ServerLicenseState*
The message can be seen in the TSK_DBCLOCK.OUT file when VERBOSE logging is enabled. | Solution: The communication between the TSK_DBCLOCK and the license server is the heartbeat to ensure the database is still in contact with the License Server.
This “heartbeat” message cannot be disabled or its frequency changed.
To remove the messages from the TSK_DBCLOCK.OUT file, switch off VERBOSE logging, and restart Aspen InfoPlus.21.
Keywords: None
References: None |
Problem Statement: The TSK_API_SERVER task might die immediately after an IP.21 database startup. Even after the most recent TSK_API_SERVER executable file has been installed (ER #990830A) and NobleNet Portmapper is running, the task may still die, and the TSK_API_SERVER.ERR log file shows an invalid IO handles, exiting error. | Solution: In the InfoPlus.21 Manager, the Input File field for the TSK_API_SERVER task MUST have nul: filled in for that field. This field normally would default to nul: after the installation of the IP.21 system. However, this field may accidently get blanked out by a user and will cause the TSK_API_SERVER task to die.
Keywords: TSK_API_SERVER
invalid IO handles
References: None |
Problem Statement: Aspen InfoPlus.21 fails to start and DBCLOCK.OUT shows the following error message:
IP21Subscription shared memory already created by some other process - exiting | Solution: Is some rare occurrences, AspenCalc may not release the Aspen InfoPlus.21 shared memory during shutdown. This problem may be resolved by restarting the Aspentech Calculator Engine service and starting Aspen InfoPlus.21 again.
Keywords: IP21SUBSCRIPTION
shared memory
AspenCalc
References: None |
Problem Statement: ScheduledActDef records are used to activate other records in the database on a regular, scheduled basis. A single Scheduling record has one schedule time and reschedule interval but it can activate (process) multiple records in the database. The records to be activated are entered in to the repeat area of the ScheduledActDef record. In which order are these records processed? | Solution: The following shows the Fixed Area of a ScheduledActDef record.
Currently, the new record has nothing to do because the field #DATA_BASE_RECORDS is 0. To have this record schedule other Aspen InfoPlus.21 records, enter a positive integer into the field and expand the repeat area.A Enter the records to be scheduled into the RECORD_NAME column.
In the example above, the Repeat Area has been increased to three occurrences.
Occurrence 1 has a RECORD_NAME of Calc1, occurrence 2 a RECORD_NAME of Calc2 and occurrence 3A a RECORD_NAME of Rep1.
The question is this, in which order are the 3 records activated (processed)?
Normally, they would be processed in the order in which they are listed in the Repeat Area (i.e. by occurrence number) and ideally this is the order we would like them to be processed:A calculation1 followed by calculation 2 and then the report record.
However, depending on the way in which you have created the calculation and report records, they will probably be processed by different external tasks. The scheduling record itself is processed by TSK_PLAN and the records to be processed will probably be processed by other tasks such as TSK_IQ1, TSK_SQLR etc. So it may be the case that the report record is processed before the two calculation records as the external task for the report might not be as a??busya?? as the external task for the calculations.
To ensure sequential record processing, use the fields WAITFOR_PROCESSING_?
Setting WAITFOR_PROCESSING_? to a??YESa?? for the first occurrence would force this record to be processed first, causing the second record, Calc2, to wait. So, the value a??YESa?? in effect means, a??activate the record listed in this occurrence and wait for it to finish being processed before activating the next record listed in the Repeat Areaa??.
Keywords: Activation
Scheduling
References: None |
Problem Statement: When installing or upgrading to a newer version of InfoPlus.21 database, the Aspentech DEMO database is loaded by default. If you don't want this to happen, follow the steps below to get rid of the DEMO database. | Solution: -- stop your database if it's currently running
-- in the Group200 directory (located in
<drive>:\Program Files\AspenTech\InfoPlus.21\db21\Group200) delete the newly created snapshot called InfoPlus21.snp
-- go to the etc directory, and copy the virgin snapshot called InfoPlus21DB.snp and paste it into the Group200 directory -- rename the InfoPlus21DB.snp file in the Group200 directory to InfoPlus21.snp -- start the InfoPlus.21 database
-- manually load cimio.rld and cimiosetcim.rld files which do not come with the virgin snapshot -- continue with your upgrade as usual by following upgrade instructions in the InfoPlus.21 Installation Manual.
Keywords: DEMO
References: None |
Problem Statement: When a IP21HealthDef record belonging to the CIMIOHealthTests group is activated its ERROR? field will be YES if it does not pass all tests. The #STATEMENTS repeat area lists the reasons why the test may have failed. But what needs to be done if the message recorded is:
Health Test Problem - Invalid Limits or Deadband | Solution: IP_LIMIT_DEADBAND must be ????????? since a number in this field is invalid.
Simply type ? key and RETURN key if you have mistakenly put a number here.
You should also make sure that the RECORD_&_FIELD_NAME field is correctly specified. If this field is blank then ERROR?=YES although #STATEMENTS will indicate nothing that would suggest why the test failed.
Keywords: IP21HealthGrpDef
IP21HealthDef
Health Monitor
References: None |
Problem Statement: How to resolve the following error when trying to open Aspen InfoPlus.21 applications after a new install -
The procedure entry point IP21GetSharedDisk could not be located in the dynamic library libc21.dll | Solution: If a machine has had older Aspen InfoPlus.21 products installed before and clean uninstall was performed, sometimes files can remain on the server. Do a search for the libc21.dll as referenced in the error message. If the dll exists in two locations, delete the file that does not reside in
C:\Program Files (x86)\Common Files\AspenTech Shared\ - if running the 32-bit install of Aspen InfoPlus.21
or
C:\Program Files\Common Files\AspenTech Shared\ - if running the 64-bit install of Aspen InfoPlus.21
You can also confirm which is the correct file by checking the file details of both libc21.dll files. For example, if a V8.4 install was performed and there are two instances of libc21.dll, where one version is 12.4 and the other is 11.3, the 11.3 dll version corresponds to V7.3 of Aspen products while 12.4 corresponds to V8.4.
Before being able to delete the old dll, the Aspen Cim-IO Manager service will need to be stopped. Proceed to delete the file and then restart the Aspen Cim-IO Manager service.
After completing these steps, the error message should no longer appear when trying to run Aspen InfoPlus.21 server application (ie Addgroup.exe, CimMgr.exe).
Keywords: libc21.dll
install
clean uninstall
addgroup
References: None |
Problem Statement: Relational Database Error -2147217900 Invalid column parent_char_id.... Batch characteristics don't show up in the Batch.21 Administrator. Batch areas won't appear in BCU Administrator. Characteristics will be empty from wherever you try and view them. | Solution: You will get this error message if you upgrade the Batch.21 software from 6.0.1 to 2004.x or higher, 2004.1 and you forget to upgrade the Batch.21 database. Several new columns were added with Version 2004 of Batch.21 including the Parent_Char_ID field in the Characteristics table. Since this column name does not exist in the earlier versions of Batch.21, the request to read Characteristics fails. You can confirm the Batch.21 database version by looking in the SQLServer Aspenbatch database in the BATCH21_CONFIGURATION table using the SQLServer Enterprise Manager. Right click on the table and select Open Table/Return All Rows. The Batch.21 database version will show up in the first row.
Run the Upgrade Database Wizard to upgrade the Batch.21 database to the current version. This should fix the problem.
Keywords: -2147217900, parent_char_id, upgrade database wizard, area empty, Batch area empty, empty area.
References: None |
Problem Statement: After installing IP.21 v3.1 the local IP.21 node is not listed in the IP.21 administrator. | Solution: Remove the data source in the ADSA config tool and re-add it.
Sometimes you also have to reboot the PC.
Keywords: administrator
References: None |
Problem Statement: How do I prevent Aspen IP.21 Administrator from crashing when tryting to create new tag by right clicking on folder? | Solution: On some specific InfoPlus.21 Snapshot it’s observed that when trying to create a new Tag by right clicking on a Folder, IP21 Administrator will get freeze and then crashes.
This issue is due to incorrect value configured in “Folder_links� for that particular folder.
Please follow below steps to update ““Folder_links� value.
1. Open IP21 Administrator
2. Locate the Particular Folder.
3. Expand the particular folder by clicking on (+) sign.
4. Select “Fields� of that Folder.
5. Update the “Folder_LINKS� to Zero “0�.
After above changes, user should be able to create new Tags by right clicking on a Folder
Keywords: Folder
Tag Creation
IP21 Administrator
Crash
Freeze
References: None |
Problem Statement: Generally an event.dat file is created when the history process, h21archive.exe, is paused or stopped due to file set backups or history system problems. However, there have been cases where an event.dat file is created while the h21archive process is still running. This can happen if data is entering the history system faster than can be processed by the history tasks. For example: if there is excess network traffic. This would generally be a one time occurrence. Once the excess network traffic subsides, the history system catches up and the event.dat file is flushed.
Other times, however, IP.21 systems have been restarted and windows boxes have been rebooted in order to reinitialize the history system and flush the event.dat file. Sometimes this works - but only temporarily. Other times, it does nothing to help. The event.dat file continues to grow. | Solution: 1. Check the fragmentation of the hard drive storing the history file sets. Chances are, this drive is badly fragmented, thus creating a performance bottleneck. Data is being collected faster than the history task is able to write to disk. You will need to stop IP.21 and run a defragmentation utility.
2. If the disk seems to be in good heath there exists the possibility that data is entering the event.dat faster than the h21archive process can un-buffer it. To see a list of the most frequently updated tags for the current file set, click on the repository with the problem, then right click on the current file set (the file set with a start date but no end date.) Select the Summary option. The list of tags at the bottom of the summary form will include information such as the scan rate (Avg. Rate) for each of the tags. The default number of tags displayed is 10, but this number can be adjusted by the user.
If it is determined that a record is scanned too frequently one then needs to determine the source of the data updates. Locating the record in the Administrator then right clicking the record to 'Show
Keywords: defrag
defragmentation
fragment
fragmentation
event.dat
References: s' will display any cimio transfer record or scheduling record which controls frequency of updates for this data record. This update frequency may need to be adjusted. If no references to transfer records or scheduling records are observed, it may be that a value is written to these records from an SQLplus query, AspenCalc script, or another custom application.
3. There also exists the possibility that the number of records scanned into this repository is larger than was originally allocated for this repository. The current number of records allocated for a repository can be determined by examining the Current Number of Points value. This value can be found by right clicking on the repository then selecting Properties. With this in mind, one can determine the number of tags currently scanned into this same repository by right clicking on the current file set, then selecting the Summary option. The value in the Tags field in the upper right hand portion of the form will indicate how many tags are currently scanned into this repository. This number should not exceed the number of configured records allocated for this repository.
4. A fileset shift may temporarily cause an event.dat file to appear. For a complete explanation of what happens during a fileset shift, please refer to |
Problem Statement: ghost field를 추가할때 아래와 같이 드롭다운 목록에 내용이 없음. | Solution: 본 이슈는 ghost field로 추가할 field가 이미 custom definition record에 추가되였기 때문입니다.
1) offending field 삭제
2) fixed area에서 아무 field 나 클릭
3) 메뉴 바(menu bar)에서 Fields 클릭
4) New | Ghost Field를 선택하여 New Ghost Field 창을 오픈.
5) Ghost Selector, Ghost Record 와 Ghost Field 를 선택
6) 확인를 클릭하여 Ghost Field 를 custom definition record에 추가
Keywords: definition editor
ghost field
KR-
References: None |
Problem Statement: When launching the Health Monitor from the Aspen InfoPlus.21 Administrator, the IP21 Tasks Health Tests expand to show three fields, but not the field titled IP21 License Tests. | Solution: Navigate to IP21HealthGrpDef and locate IP21TasksHealthTests from that definition record. Make sure the #DATA_BASE_RECORDS field is set to 4 and open the repeat area. Make sure the 4 record names there are: AllIP21TasksRunningTest, IP21TasksReStartingTest, AllIP21ServicesRunTest, and IP21LicenseTests as follows:
Keywords: IP21LicenseTests
Health Monitor
References: None |
Problem Statement: Upon trying to start Aspen InfoPlus.21, TSK_DBCLOCK never gets started and there is an error in the TSK_DBCLOCK.OUT file that reads The timestamp in one of the cache.dat files does not match that of the snapshot. | Solution: This issue may occur due to corruption in either the database snapshot, the cache.dat file associated with one of the repositories, or the file sets within the repositories reporting an invalid timestamp. There are three knownSolutions that have been used to resolve this problem:
1. When starting Aspen InfoPlus.21, update the command line parameters in TSK_DBCLOCK such that the first word is SYNC. The command line should look something like SYNC DOUBLE 1000000 SNAPSHOT=C:\ProgramData\AspenTech\InfoPlus.21\db21\group200\InfoPlus21.snp
2. Go to the directory where all the repositories exist and delete each instance of cache.dat. There should be one such file associated with each repository. The default locations for TSK_DHIS and TSK_DHIS_AGGR are C:\ProgramData\AspenTech\InfoPlus.21\c21\h21\arcs and C:\ProgramData\AspenTech\InfoPlus.21\c21\h21\TSK_DHIS_AGGR, respectively.
3. Run the SetArchiveDates utility from C:\Program Files\AspenTech\InfoPlus.21\c21\h21\bin (or Program Files (x86) for a 32-bit install) and validate that none of the repositories contain any future time stamps. If any future time stamps are found, make sure to use the utility to edit the time stamps associated with the respective file sets to show a past time stamp instead.
Keywords:
References: None |
Problem Statement: The find references tool in IP.21 administrator is not working and throws the following error message:
Type System.Threading.Tasks.Task1[AspenTech.InfoPlus21.Access.Contracts.TagldentifiersByDefinitionTag]’ cannot be serialized. Consider marking it with the DataContractAttribute attribute, and marking all of its members you want serialized with the DataMemberAttribute attribute. If the type is a collection, consider marking it with the CollectionDataContractAttribute. See the Microsoft .NET Framework documentation for other supported types. | Solution: This issue can be resolved by reinstalling Microsoft .Net 4.5.2
Keywords: Show references
Type System Threading Tasks
References: None |
Problem Statement: Why does the snapshot size increase after upgrading to V7.3? | Solution: During an upgrade process from earlier versions of Aspen InfoPlus.21 to V7.3, there will be a point in time where space is needed for the new variable length name segment that provides for the increase of the 24-character name space in the record to 256 characters. Because of this, upgrade needs a lot of space and this is the reason why the snapshot size is larger after the upgrade to V7.3. This increase in size is mostly free space which can be manually adjusted by users.
Keyword
grow
Keywords: None
References: None |
Problem Statement: This is listed as step #2 on page 22 of the InfoPlus.21 Database and History Migration manual. Migrating data (i.e. adding more points) to InfoPlus.21 from another IP.21 node or CIM/21 using Aspen''s ASCTOARC conversion program could produce the following error message:
find_cache () free pointer corrupted
This error condition can occur during the migration, stopping the migration.
Note: This migration tool is provided through the Global Services department for customers performing data migrations to InfoPlus.21. This migration tool can be used for Setcim as well as Cim/21. A point is an tag in the database that has a history repeat area to it. | Solution: Check the ''number of points'' configured for the repository on the migration system. You may need to increase this number for the migration program to behave. Although the code is supposed to handle when the configured ''number of points'' is less than the number of points in the migration file, it is still a potential failure point.
Increase the NUM_OF_ POINTS in the repository from 1000 to a number greater than the sum of existing points in the target repository, plus the number of points you are migrating. For example, if you have a repository with 3,000 points, and you are adding 2,000 more points in your migration, ensure that NUM_OF_POINTS is > 5000.
Keywords: find_cache
migration
References: None |
Problem Statement: If you are experiencing communication problems between InfoPlus.21 OPC DA Server and an OPC client, then a log file for the OPC server could be helpful. Is such a log file generated? | Solution: A log file called IP21OPCServer.log is generated by the InfoPlus.21 OPC DA Server. This log file will created the first time that a message is produced that matches the filter criteria. The log file can be found at:
C:\ProgramData\AspenTech\InfoPlus.21\db21\group200\IP21OPCServer.log
The filter criteria for the logging can be found in IP21DaServer.dll.config. See the parameters of LevelMin and LevelMax. The config file can be found at:
32-bit IP.21: C:\Program Files (x86)\AspenTech\InfoPlus.21\db21\code\IP21DaServer.dll.config
64-bit IP.21: C:\Program Files\AspenTech\InfoPlus.21\db21\code\IP21DaServer.dll.config
Keywords: IP.21 DA Server
IP21OPCServer.log
InfoPlus.21
log
References: None |
Problem Statement: When creating SQLADef tags, users might want to set the value of the IP_STEPPED field to either Interpolated or Stepped to use this setting as a default for Process Explorer (checked on unchecked Stepped column). However, in order to accomplish this task, the map record for SQLA tags (IP_SQLAMap) must be modified. | Solution: To modify the SQLA map record, follow these simple steps:
1. Locate IP_SQLAMap, defined by AtMapDef.
2. Set the filed MAP_#Maps to 1 to add an occurrence.
3. Go to the first occurrence and add 'STEPPED' to Map_Attribute and 'IP_STEPPED' to MAP_FieldName. This step allows IP_SQLAMap to match the IP_AnalogMap record and Process Explorer to default to the value specified by IP_STEPPED.
4. Go the IP_SQLADef tag and set IP_STEPPED to either 'Stepped' or 'Interpolated'
5. Now the default setting can be seen in Process Explorer.
Keywords: SQLA
Stepped
IP_STEPPED
References: None |
Problem Statement: 왜 rate-based distillation column 플래시계산에서 온도가 서로 다른가? | Solution: Rate-based stage에서 증기성분과 액상성분은 상평형을 이루지 않는다. 기액상평은 오직 경계면에서만 발생한다고 가정하기에 이를 화학평형으로 볼 수 있다. 때문에 rate-based stage에서는 플래시 온도가 다를 수 밖에 없고 출구유체에서 기액상평형과 화학평형을 이루어질 수 없다.
Keywords: None
References: : CQ00357921
Please find |
Problem Statement: If I have to repair file sets from many repositories, can I run multiple copies of H21ArcckWizard.exe (History Arc Check Wizard) at the same time? | Solution: If you have to repair file sets from multiple repositories, you can start concurrent copies of the history archive checking wizard (H21ArcckWizard).
Keywords: repair file set
References: None |
Problem Statement: Listed here are the two most likely occasions when you might see the error:
Licensed Point Count must be 'nnnnnn' Minimum
(where 'nnnnnn' might be any number between 1 and 2097151)
You might see this in the Output file for Loaddb when the Aspen InfoPlus.21 startup fails at loaddb.
Another time might be when trying to create a new tag, a record which has one or more History Repeat areas. | Solution: Shutdown the Aspen InfoPlus.21 database if it is currently running - the problem cannot be solved with it running.
From the Left hand pane of the Aspen InfoPlus.21 Administrator, under InfoPlus.21, right click on the name corresponding to the database in question.
Choose Set Point Count
It is the number seen here that needs to be changed to a value at least as large as the number in the error message.
Note - typically, you would set this value to the number of licensed points that you purchased for this system. That is why you will only see the problem when trying to use more 'tag' records than the defined setting.
Keywords: None
References: None |
Problem Statement: How do I check the license status on my Aspen InfoPlus.21 server? | Solution: The License Status tab displays the current status of the InfoPlus.21 server.
To view license information:
1. In the InfoPlus.21 Administrator, right-click the InfoPlus.21 database and select Properties from the context menu.
2. On the Database Properties dialog box, click the License Status tab. The following license status information is displayed.
· License State - Displays one of the following:
— License Granted – The license server confirms the checkout of the requested license units.
— License Timeout – The license has been granted but InfoPlus.21 is no longer able to contact the license server. If contact with the license server is not restored, then the License Timeout period can last for a timeout period specified in the license key. The default timeout period is 900 minutes (15 hours).
— License Grace Period – The license has been granted at least once, the license server cannot be contacted and the license timeout, if any, has elapsed.
— License Denied – Either the license server denies the request checkout or the license server cannot be contacted and the license grace period, if any, has elapsed.
· State Transition Time - The start time of the current state.
3. If in License Denied mode, the Details button is available. Click Details to view more information about why the license was denied.
For additional information on License State and functionality, visit knowledge base article 139153.
Keywords: License Status, InfoPlus.21, IP.21
References: None |
Problem Statement: How does Aspen InfoPlus.21 use the field FIELD_NUMBER (hex) in records defined by FieldNameDef and FieldLongNameDef? | Solution: Aspen InfoPlus.21 uses records defined against FieldNameDef and FieldLongNameDef to create data field names for Aspen InfoPlus.21 records. The only difference between data field names defined against FieldNameDef and FieldLongNameDef is the maximum length of the data field names defined against them. Data field names defined against FieldNameDef have a maximum length of 12 characters, while records defined against FieldLongNameDef can be used to create 20-character data field names.
Aspen InfoPlus.21 connects a record's data fields to data field names using the field FIELD_NUMBER (hex).
This 16-bit field number has two parts:
· Bits 15 to 10 contain a field check code (which is largely unused today)
· Bits 9 to 0 contain a field pointer
The bottom 10 bits (bits 9 to 0) are used to map a data field name to a data field number in a definition record.
As an example, the field number of IP_INPUT_VALUE is 7459 (hex). Masking off the bottom 10 bits gives 1011001 (binary) = 89 (decimal).
Using the Aspen InfoPlus.21 Administrator, expand IP_AnalogDef, the icon Fields, and finally the repeat area MAX_FIELD_POINTER
Find occurrence 89 and see the value in the field FIELD_NDX_vs_POINTER is 10. This means that IP_INPUT_VALUE is field number 10 in the definition record.
There are two implications with this structure:
· A definition record can have a maximum of 1024 data fields
· You cannot place data field names in the same definition record having the same values in the same bottom 10 bits. For example, you cannot put the following fields in the same definition record
o IP_TREND_VALUE [FIELD_NUMBER (hex) =2419]
o DISPLAY_LENGTH [FIELD_NUMBER (hex) =1019]
o MAX_NUM_POINTS [FIELD_NUMBER (hex) =7419]
o #TIME_STAMP_VALUES [FIELD_NUMBER (hex)=2419]
o #SUMMARY_DESCS [FIELD_NUMBER (hex)=1419]
o ACTUAL_VALUE_FLD [FIELD_NUMBER (hex)=2419]
o Q_CONDITION_TIME [FIELD_NUMBER (hex)=5019]
o IO_DEVICE [FIELD_NUMBER (hex)=4019]
o TREND VALUE [FIELD_NUMBER (hex)=2419]
Keywords:
References: None |
Problem Statement: How can I delete a file set to recover disk space without first stopping Aspen InfoPlus.21? | Solution: Aspen Technology strongly recommends stopping Aspen InfoPlus.21 before deleting the contents of file sets (arc.dat, arc.key, and arc.byte); however you can following these steps if it is not possible to stop Aspen InfoPlus.21.
1. Open the Aspen InfoPlus.21 Administrator and stop the repository with the file set to be deleted.
2. Right click over the fileset, select properties, uncheck the Mounted checkbox, and click on Apply and then Ok. The fileset status should change to None.
4. Using Windows Explorer, navigate to the folder containing the file set and remove the files arc.key, arc.dat, and arc.byte. (Don't delete the folder, just the files).
5. Go back to the Aspen InfoPlus.21 Administrator, right click over the repository node and select Start.
Keywords: Fileset
Repository
Delete
References: None |
Problem Statement: TSK_DBCLOCK hangs at 50% during startup, then quits. Error messages found in TSK_DBCLOCK are:
h21_arck_local failed with ret = -1040
CreateFile failed
The problem appears to be related to the history filesets. For V7.1 and later, a new utility exists that attempts to validate the path to each fileset. For history startup problems after a migration, it is a great tool to find problem filesets that may have corrupt data preventing a good startup (this tool is installed in V7.3 and later automatically. For Version 2006.5 and later the tool is added to a system by applying the latest InfoPlus.21 cumulative patch for that version.) However when running the tool under some circumstances, it stops and exits before starting to validate the individual filepaths, with a failure to read a cache file: | Solution: In this case customer had run h21chgpaths.exe to change the UNC path for all the filesets in config.dat. Since the directory structure was unchanged on the new server, the change of nodename in config.dat seemed to be enough. However in addition to the fileset locations, config.dat also specifies the repository backup path, and in this case, it was specified by drive letter on the old system, for example as:
E:\History\backup\
Re-running h21chgpaths.exe, changing all E:\ references to C:\, then making sure to create the actual backup folder along the correct path, resolved the problem. At that point ValidateArchive.exe ran successfully, and more importantly, the system started up without a hang of TSK_DBCLOCK.
Keywords: ERROR: Failed to check archives.
ERROR: Cannot open cache.dat file.
References: None |
Problem Statement: When using standard IP_AnalogDef records, normal behavior is that values written to the IP_INPUT_VALUE field will propagate to the IP_VALUE field, and then be written to history. You might see a situation where the values updating in IP_INPUT_VALUE do not propagate to IP_VALUE. | Solution: One possible cause of this behavior is that compression is activated for the record. If this is not the case then there could be a problem with the IP_BoxcarSlope record. The IP_BoxcarSlope record must be configured for data to propagate from IP_INPUT_VALUE to IP_VALUE even though compression is not being used. The IP_BoxcarSlope record should be configured like the following example.
Example IP_BoxCarSlope record defined by BoxCarSDef.
NAME
IP_BoxcarSlope
NEXT_PROCESS_RECORD
(empty field)
DEFAULT_BASE_RECORD
D-IP_Analog
LAST_RECORDING_FIELD
D-IP_Analog 1 IP_TREND_VALUE
SIGNIFICANCE_FIELD
D-IP_Analog IP_DC_SIGNIFICANCE
SIGNIFICANCE_VALUE
??????????????????????
MAX_INTERVAL_FIELD
D-IP_Analog IP_DC_MAX_TIME_INT
MAX_TIME_INTERVAL
+00000:00:00.0
UPDATE_TIME_FIELD
D-IP_Analog IP_INPUT_TIME
RECORDING_TIME_FIELD
D-IP_Analog 1 IP_TREND_TIME
STATUS_FIELD
D-IP_Analog IP_DC_STATUS
SLOPE_FIELD
D-IP_Analog IP_DC_SLOPE
LAST_UPDATE
18-AUG-00 16:29:12.7
BCS_STEPPED_FIELD
D-IP_Analog IP_stepped
Keywords: ip_input_value
ip_value
history
References: None |
Problem Statement: This knowledge base article explains how to remove duplicate tasks from the Aspen InfoPlus.21 Manager defined task list. | Solution: Duplicate tasks can appear in the Aspen InfoPlus.21 Manager task list when there is more than one task registered in the registry with the same order number. Try to remove the extra task using the 'Remove' button. If that does not work go to the following location in the registry:
32 bit systems :-
HKEY_LOCAL_MACHINE\Software\AspenTech\InfoPlus.21\<version number>\Group200\RegisteredTasks
64 bit systems :-
HKEY_LOCAL_MACHINE\Software\WOW6432NODE\AspenTech\InfoPlus.21\<version number>\Group200\RegisteredTasks
Edit the task that is duplicated and notice that the order number is the same as the order number of another task in the list. Check one by one through the other entries to find the task with the duplicate order number and change it to a non-existent number in the list. This order numbering is consecutive and must correspond with the order shown in the Aspen InfoPlus.21 Manager defined task list.
Keywords: Duplicate Defined tasks
IP.21
References: None |
Problem Statement: The example for INSOCCS in the manual is for inserting new occurrences into history. The following example shows how to do this for a non history occurrence such as ENG-UNITS. | Solution: NOTES: modify the #define for ARRSZ for the number of occurrences to insert, INSERT_AT for the occurrence number to begin inserting, the recid variable for ENG-UNITS on your system and the description array values for the actual units to write.
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <setcim.h>
#define TRUE 1
#define FALSE 0
#define NUMTAGS 1 /* Number of Fields to update in each occurrence inserted*/
#define ARRSZ 2 /* Number of occurrences to insert - modify as needed */
#define INSERT_AT 38 /* Insertion occurrence - modify as needed */
#define DBCHAR_8 8 /* Db data type of byte array 8 bytes long - for character type */
main()
{
long recid = 892; /* Record ID for ENG-UNITS record on test system */
long fts[NUMTAGS] = {0x10080000}; /* field tag of SELECT_DESCRIPTION field */
long ft = 0x10080001; /* field tag of 1 SELECT_DESCRIPTION field */
char description[ARRSZ][8] = { NewUnit, OldUnit }; /* new eng units to write */
long numoccs = ARRSZ,
occnum = INSERT_AT; /* First occurrence number to insert */
short i,
occsok,
occsinserted,
numfts = NUMTAGS,
ftsok,
datats[NUMTAGS] = { DBCHAR_8 },
*ptdatas[NUMTAGS] = { (short *)description },
error_len;
ERRARRAY error_msg;
ERRBLOCK err;
if ( INISETC())
{
for (i = 0; i <= NUMTAGS; i++)
{
printf (\nDescription to load is %s\n, description[i]);
}
INSOCCS(recid, ft, numfts, fts, datats, numoccs, occnum,
ptdatas, &occsinserted, &occsok, &ftsok, &err);
if (err.ERRCODE != SUCCESS)
{
ERRMESS(&err, error_msg, &error_len);
error_msg[error_len] = ''\0'';
printf(***Error: %d - %s...\n, err.ERRCODE, error_msg);
}
printf(\n\n%d occurrences inserted.\n,occsinserted);
printf(%d occurrences OK.\n,occsok);
printf(%d field tags OK.\n,ftsok);
}
else
{
printf(Database is not up...\n);
}
ENDSETC();
}
Keywords: INSOCCS
LOCAL API
code
References: None |
Problem Statement: Users who develop large custom applications which rely on Aspen Batch.21 data prefer to use the fastest method of data retrieval possible to optimize performance in their custom applications. This knowledge base article describes which method of data retrieval is faster. | Solution: Assuming the user interacts with the Aspen Batch.21 API and the web service identically the performance will be faster in the Aspen Batch.21 API as the web service is just an extremely thin wrapper around the API datasource's XML method. If the web service is used, the application will see the performance impact of the Aspen Batch.21 API plus the marshalling that occurs through http and the web service.
Keywords: None
References: None |
Problem Statement: I am using a transfer block to copy a stream, why does Aspen Plus say that the input for the stream I am trying to transfer to is incomplete? | Solution: If you want to transfer stream S1 to stream S4, you can do this by adding a Transfer block, like in the following screenshots:
However, the flowsheet input is incomplete, and I won’t be able to run the simulation.
To fix this, input any values in the stream S4 Input form. These values will not be used for the calculations, but will allow the simulation to run.
After running the simulation, you will not find the copied values in the Stream Input, but on the Stream Results.
Keywords: Transfer block, copy
References: None |
Problem Statement: By default, Aspen Plus uses the ideal gas enthalpy to calculate the pure component vapor and liquid enthalpies. There are instances that the user may need to use liquid based enthalpies for the simulation and values obtained from the default Aspen Plus setting would not be right. There are options available to set at a global level the liquid reference state for the enthalpy calculation (refer to | Solution: ID 3100). These techniques have the drawback that the enthalpy calculations will be liquid based for all the components in the simulation which obviously will be incorrect for gaseous components.
Solution
In situations where the user needs to selectively specify the liquid reference state for a component in a mixture then the following options are available:
1) For Ideal and activity based models, activate the route DHL09 for the property DHL (liquid phase enthalpy departure) on the Properties Property Methods Routes sheet. Then, create a new scalar pure component property in the parameters tab in the data browser. Scroll down for COMPHL (component for which liquid enthalpy is calculated by the integration of liquid heat capacity polynomial when the route DHL09 is selected) and then enter the value of 1 for components for which liquid reference state is required.
2) The liquid enthalpy component flag, COMPHL parameter, can also be fixed for any components in the Properties Data Base. Since you cannot modify the default databases, you need to create a new one that you can modify. Open the Aspen Properties Database Manager from the Windows start menu. Right click on Aspen Physical Properties Database V*.* and select create new database. The option Clone a source database can be used if a copy of the existing database such as APV73 is required. The user name for V7.3 is Apeduser and the password is Aprop100 (for other versions refer toSolution ID 124817). After creation of the new database select the components for which the liquid enthalpy flag is required. Select Pure under Properties and Parameters and the components selected will appear on the panel with view and edit options being available. Select edit and scroll down for COMHL in the Properties panel. Write in a value of 1 for COMPHL and then click the add button and this new property will be added to the selected component.
Keywords: None
References: None |
Problem Statement: Several aspenOne Manufacturing Suite products contain an embedded Aspen InfoPlus.21 license. | Solution: The following products contain an embedded Aspen InfoPlus.21 License (pre-V7.1 name between parenthesis) :
Aspen Nonlinear Controller (Aspen Apollo Online)
Aspen PID Watch Performance Monitor (Aspen PID Watch)
Aspen Polymer Production Control Online
Aspen Process Controller (and variants)
Aspen RTO Watch Performance Monitor (Aspen RTO Watch)
Aspen Watch Performance Monitor (Aspen Watch Server) (and variants)
Aspen Online Deployment
Keywords: Aspen InfoPlus.21 embedded License
References: None |
Problem Statement: TSK_H21_PRIME may not start successfully. The task itself may stop with an error 1 and the following will appear in the output or error file:
Message Can NOT Be Found: -2506
What is causing this problem and what can one do to correct it? | Solution: This problem is caused because the tasks in the 'Defined Tasks' list have been moved out of their proper order. In aspenONE 2006.5 there are fewer important startup tasks (and the order of the remaining ones has changed). Here is an excerpt from the 2006.5 Aspen InfoPlus.21 Release Notes:
Consolidation of Multiple Tasks into TSK_DBCLOCK
The following tasks have been subsumed into TSK_DBCLOCK:
* TSK_C21_WIN_INIT
* TSK_H21_INIT
* TSK_H21_ARCCK
* TSK_H21_MNTTAB
* LOADDB
Furthermore, TSK_H21_PRIME now starts after TSK_DBCLOCK.
These changes were implemented as part of the enhancement to eliminate history synchronization after a graceful shutdown.
*******************************************************************************************************************************
To correct the problem, make sure that TSK_DBCLOCK is the first task in the Defined Tasks list, followed by TSK_H21_PRIME. The error message is produced when TSK_H21_PRIME is moved before TSK_DBCLOCK.
Keywords: None
References: None |
Problem Statement: Having a custom record with more than one historical repeat area, it is possible to use AtMapDef record to create trend plots of the values for each repeat area. This | Solution: provides an example of the configuration of the AtMapDef record needed for this as well as the consideration while building the custom record to properly work for it.
Solution
For this example we're going to use a custom record defined as follow:
in which CST_TrendValuesArea represent the historical repeat area which hold live values while CST_LabValuesArea represent the historical repeat area which hold values taken by laboratory test.
As explained onSolution 120047, Aspen Infoplus21 history is ordered according to the key timestamp of the history events, so that, the custom record definition should ensure that each of the repeat areas have a key timestamp field defined:
The field defined here as the Key Timestamp is the one that is going to be used as the time axis when plotting the data from this historical repeat area. This is important specially if a custom historical repeat area have more than one timestamp field, in this case, only the one defined as the Key timestamp field will be the one used to plot trends.
Once each historical repeat area have a key timestamp field, is possible to set the custom record enable and configure new AtMapDef record for each repeat area, in this case the configuration is as follow:
For the Trend values:
For Lab values:
Notice that just the first map (CST_MapTrendVal) is set as Default by using TRUE on the field MAP_IsDefault.
Having this minimum configuration on the map records it is possible to trend values from both repeat areas:
Keywords: Custom records
Process Explorer
AtMapDef
References: None |
Problem Statement: In the Aspen InfoPlus.21 Administrator, the record utilization tab of the database displays two properties.
Records and Licensed Points.
The utilization of both the properties is displayed in the Record Utilization Tab. As both the properties are essential in interpreting the database utilization,very often the users confuse the two.
This KB explains the difference between the two properties. | Solution: The total number of Licensed Points in an InfoPlus.21 database equals the number of records with history repeat areas. Whereas, Records group box displays the number of available records in various states.
For example, based on the screen shot below,
Total number of records with History Repeat Areas- 438
Total number of Usable & Unusable Records- 3424
The free space available for record creation is:
Number of Records with History Repeat Area: 14562.
Number of undefined records: 5576
The total number of available records i.e. 9000 can be increased up to 62,516
Keywords: Licensed Point
Record Utilization
InfoPlus.21
References: None |
Problem Statement: In some cases, when opening the InfoPlus.21 Manager after an install or upgrade, there are no tasks appearing in the Defined Tasks list. As such, AddGroup.exe will need to be run following the instructions in | Solution: id 108434.
However upon running the AddGroup.exe executable, the following error messages is encountered as per the screenshot below.
Solution
In this case, perform the following steps:
1. Launch Windows Task Manager.
2. Click on the Processes tab.
3. Sort by Image Name.
4. Look for orphaned dbclock.exe process. There may be a need to tick the checkbox beside Show processes from all users.
5. HIghlight dbclock.exe process by selecting it.
6. Click on the End Process button to kill the orphaned process.
7. Re-run AddGroup.exe executable.
Keywords: CreateDBSharedMemoryObjects: Create FileMapping failed
Error:Cannot create a file when that file already exists
CRDBSETC: Error in CreateDBSharedMemoryObjects
References: None |
Problem Statement: Using the IP.21 v3.1 Administrator tool, an IoGetDef record is selected. If the Properties of that record are selected for viewing, the Administrator utility crashes with a Dr. Watson error. A document depicting the error has been included as an Attachment to this Tech Tip. | Solution: Install InfoPlus.21 v3.1 Service Pack 1. Installing Service Pack 1 for InfoPlus.21 v3.1 resolves this problem. This was not mentioned in the SP1 release notes. This Service Pack is downloadable fromSolution #104117.
Keywords:
References: None |
Problem Statement: What does the number (50) mean when I try to activate a record manually in the IP.21 Administrator? | Solution: This is a priority setting, related to the external task that runs the activation. All external tasks are assigned a priority and when more than one record tries to use it at the same time, the higher Activation number, the higher the priority the record has, so the sooner it will execute. Most of these priorities are assigned on the definition record level during creation. This is simply one that can be changed manually. However, it would only be necessary to increase this priority if it was taking a while for it to activate when you clicked okay due to other automatic activations taking place. In other words, almost never! The Activation range is between 1 and 4,095.
Keywords: activation
fifty
50
administrator
References: None |
Problem Statement: What are some general guidelines for applying replication when using custom definition records? | Solution: 1. Each Aspen InfoPlus.21 system (publishing and subscribing) must be at the same patch level.
2. The custom definition record must exist on both the publishing and subscribing systems.
3. Pre-version 11 only: You can only replicate fields located in the fixed area of a record. You cannot replicate repeat area data fields.
4. You may want to use the fields in IP_AnalogDef as a starting point when setting up the replication-related fields to see which fields are and are not using replication. Here's some details about how to do that:
In the Aspen InfoPlus.21 Administrator expand IP_AnalogDef.
Click on the green box called 'Fields' then click on '#_Of_Fields_In_Rec'.
Now scroll all the way to the right. You will see two new columns Incl_in_Tag_Creation and Publish_Updates. You will see that some are set to YES and some are set to NO.
A 'Yes' in the column Incl_in_Tag_Creation means that when the new tag is created on the Target, then the value of the field is copied from the Source to the Target record.
A 'Yes' in the column Publish_Updates means that when new data arrives in the Source record, it will be published to the Target record.
In a similar manner, modify your custom definition record to identify the fields you want to create and publish.
5. Before activating replication with the custom records make sure to save a snapshot on both machines first so you can put them back to their previous state in case something goes wrong.
Keywords:
References: None |
Problem Statement: Project won't start up when Office 2007 is in place
For example, a typical error is that engine fails to start up even though the steady state detection starts up just fine. | Solution: Access 2007 requires trusted locations to be configured to allow access to the Access database file. The Aspen OnLine project folder should be added to the trusted location list. To do so:
1. Run Access 2007
2. Click on the Office button on top left corner and select Access Options button at right bottom corner
3. Click on Trust Center category and then Trust Center Settings button on right side window.
4. Click on Trusted Locations category and then click on Add new location... button to add the project folder, remember to check on the Subfolders of this location are also trusted option since the Access database files that Aspen OnLine uses are actually inside the project folder.
Keywords: Office 2007, 2007, Access 2007, Excel 2007, Engine fails, Engine
References: None |
Problem Statement: Need to copy data directly from Process Explorer into an Excel file. | Solution: For 2.5.x
Zoom the plot to set the data you want to retrieve. Note that all the data for the displayed timeline will be copied. Highlight the tag of interest.
Right-click to display the context menu and select Copy.
A new window, Enter Delimiter, appears and provides the options of Tab, Comma and Space. Space or Tab allow the data (Timestamp, Value and Status) to be directly pasted into an open Excel plot. Comma allows an Excel CSV file to be created.
Open Notepad and paste the data.
Save the file with the .csv extension and All files selected in the Save as type field.
The file will now open as an Excel worksheet.
Note that the timestamp column will need to be formatted to display the expected timestamp. (Format > Cells... > Number > Custom > Type: m/d/yy hh:mm:ss.0)
For 3.x and above
Zoom the plot to set the data you want to retrieve. All the data for the displayed timeline will be copied. Highlight the tag of interest.
Right-click in the plot to display the context menu and select Show Data Table.
As desired, select the Display Strings for Level, Status and Valid check box.
Click in the data window and copy the data (drag and drop) into Excel.
Note that the timestamp column will need to be formatted to display the expected timestamp. (Format > Cells... > Number > Custom > Type: m/d/yy hh:mm:ss.0)
Keywords:
References: None |
Problem Statement: There is a message in the STATE field that RTO is DOWN DUE TO FAILURE. | Solution: Sometimes this problem can be caused by a locked or corrupted history file (hist.dat) in the \HIST folder, which prevents the Online system from running through its cycle.
This type of problem can often be resolved by:
Stopping the RTO program
Issuing the ?histdel? command via a Simulation Engine window, which deletes the contents of the \HIST folder
Restarting the RTO program
Keywords: aol
References: None |
Problem Statement: Do we have any restrictions on the number of characteristics a batch can have in Aspen Production Record Manager (formerly called Aspen Batch.21)? | Solution: There are no limitations to the number of characteristics you can have for the batch .
Keywords: Limit
Characteristics
Batch
References: None |
Problem Statement: This article describes the reason why the Process Explorer legend and the Process Data Add-in can return the value of
Unknown Status (-32768)
for the quality status when the quality status data is requested for a custom record. A procedure to fix this problem by modifying the definition record is also provided. | Solution: The root cause of this problem is an incorrect association of the quality status field within the history value field of the custom record.
When looking at the properties on the history status field in the Definition Editor for a working IP_AnalogDef record, one notices that the history status field lists QUALITY-STATUSES as both its format record and its Search Key record. However, for records which return the aforementioned error, the custom record won't show QUALITY-STATUSES for the Search Key record. Instead, it will list QUALITY-STATUSES as the format record and as a Ghost Record. Like this:
(Note: In the Definition Editor, expand the history repeat area, right click on the status field, then select Properties to see this information.)
Type : Signed Integer 16-bit
Format: QUALITY-STATUSES
Write Level: General
Field Number: 02DF (hex)
Changeability: Always Allowed
Operator Changes: Never Allowed
Activation Type: Normal
Activation Criteria: No Activation.
Ghost Record: QUALITY-STATUSES <--- QUALITY-STATUSES listed as a Ghost Record.
Repeat Area Key Status Field
.........
To fix this:
Right click on the history value field (usually IP_TREND_VALUE), select Special | Quality Status. Make sure the quality status record is referenced here.
Right click on the repeat area count field (usually IP_#_OF_TREND_VALUES), select Special | Key Fields. Make sure that the quality status record is referenced here.
After the change, the Properties of the quality status record should look like this:
Type : Signed Integer 16-bit
Format: QUALITY-STATUSES
Write Level: General
Field Number: 02DF (hex)
Changeability: Always Allowed
Operator Changes: Never Allowed
Activation Type: Normal
Activation Criteria: No Activation.
Search Key Record: QUALITY-STATUSES <-- Now listed as 'Search Key Record'
Repeat Area Key Status Field
.......
Note: These procedures require a change to be made to a definition record. Prior to IP.21 v.6.0 there was no easy way to change a defintion record without losing the history for the tags defined under the definition record. As of IP.21 v.6.0, there exists a utility called the RedefineWizard which will allow a user to replace an existing definition record with an updated definition record without losing the history data associated with the tags. The RedefineWizard can be found in
Program Files\AspenTech\InfoPlus.21\db21\code
The documentation for the RedefineWizard can be found in a help file called Redefine, which is located in the same folder.
Keywords:
References: None |
Problem Statement: This knowledge base article describes how to work around the following error
Cannot load Aspen Process Data XLA resources! Please try reinstallation
which can be observed when attempting to load the Aspen Process Data add-in into an Excel worksheet. | Solution: 1. Versions 2004.x are dependent on a resource file named AtProcessDataXLAResources.dll. This file should be located in this folder:
Program Files\AspenTech\Apex\Pe\Addin
As of v2004 this file is now a registered component. The first suggestion is to manually register AtProcessDataXLAResources.dll using regsvr32.exe.
2. If registering AtProcessDataXLAResources.dll does not resolve the problem then perform a clean reinstallation of Aspen Process Explorer on the affected PC. To perform a clean reinstallation please follow these steps.
a) In Excel go to
Tools | Add-ins...
then uncheck the 'Aspen Process Data' add-in
b) Search all drives on the affected PC for all versions of AtData.xla. Delete all existing versions of this add-in file.
c) Uninstall Process Explorer
d) Reboot
e) Reinstall Process Explorer
3. This error message will be returned if one attempts to copy a v2004.x or newer AtData.xla add-in file on to an older (v6.x or earlier) system. Some fundamental changes were made to AtData.xla in v2004.x. Therefore, the newer versions of AtData.xla are not compatible with older Aspen Process Explorer installations.
Keywords: PD
Addin
Add In
References: None |
Problem Statement: This knowledge base article provides an example of Visual Basic script that shows how to upload XML data to an Aspen Production Record Manager (APRM) server using the APRM Application Programming Interface (API). | Solution: The following is a Visual Basic script that will load one of the xml files (?BDataImportWithAutoConfig.xml?) and call the 'ImportBatchDataXMLForScripting' method to submit it to APRM. This example assumes that the XML file is located in the following directory ?D:\Temp\BDataImportWithAutoConfig.xml?. Also, data will be stored in the ?Batch Demo Area? area and uses the autoConfig flag.
Private Sub Form_Load()
strDataSourceName = W2K8S-DEV1-EN
strAreaName = Batch Demo Area
Set batchDataSources = CreateObject(AspenTech.Batch21.BatchDataSources)
strXmlContentToSubmit =
nNumberOfDataSources = batchDataSources.Count
blnDataSourceFound = False
For nDSIndex = 1 To nNumberOfDataSources
Set batchDataSource = batchDataSources(nDSIndex)
If batchDataSource.Name = strDataSourceName Then
blnDataSourceFound = True
nNumberOfAreas = batchDataSource.Areas.Count
For nAreaIndex = 1 To nNumberOfAreas
Set batchArea = batchDataSource.Areas(nAreaIndex)
If batchArea.Name = strAreaName Then
blnAreaFound = True
Open D:\Temp\BDataImportWithAutoConfig.xml For Input As #1
Do While Not EOF(1)
Line Input #1, TextLine
strXmlContentToSubmit = strXmlContentToSubmit + TextLine
Loop
Close #1
Call batchDataSource.ImportBatchDataXMLForScripting(strXmlContentToSubmit, xmlResult)
MsgBox xmlResult
Exit For
End If
Next
If blnAreaFound = False Then
MsgBox The area was not found
End If
Exit For
End If
Next
If blnDataSourceFound = False Then
MsgBox The datasource was not found
End If
End Sub
Executing the script produces a message box with the value of xmlResult, shown here:
The integer value (597) inside the Handle element shown in the message box is the id assigned to the batch just inserted in the area. The string ?W2K8S-DEV1-EN? is the name of the datasource from the script - the one containing the ?Batch Demo Area? area.
Keywords: VB Script
xml
Batch.21
API
References: None |
Problem Statement: Why is it impossible to UNDO previous commands in Microsoft Excel? | Solution: Here are the reasons that the UNDO capability cannot be implemented:
1. For pure Microsoft Excel, most changes via Macro cannot be Un-done. Execution of those macro also purges actions that were available for undo.
2. Each of the AspenTech MES Excel Add-Ins references dozens of other components including 4 components from Microsoft Excel. Some of the functionalities from those components are used and cannot be recorded as actions to be un-done.
3. For actions that can be recorded for undo, it will take a lot of coding to keep track of the change list. At the end, the code will be error-prone and will almost certainly lead to performance problems.
4. Some Excel Add-Ins automatically update values on worksheet at certain frequency for reflect real-time data from plant data. For such applications, undo is not allowed.
5. Therefore, implementing UNDO capability during and after execution of macro (and/or Add-In components) is clearly beyond what Microsoft Office technologies can support. It will almost certainly lead to poor quality results (including bad performance problems) for AspenTech's customers.
Keywords: MS Excel
Worksheet
Excel AddIn
Undo
Process Data
References: None |
Problem Statement: Sometimes, when using the Aspen Batch and Event Extractor tool to put batch data into Batch.21 (which means that the characteristics are auto configured before the data is inserted into a batch), the following error is received when using the batch detail display to open one of these batches:
B21BAI.60175 Specified characteristic is not defined
Unspecified error
Fatal error
Normally a refresh will return all the data. However, sometimes it is necessary to restart the Batch.21 service to resolve this problem. Why is this happening? | Solution: This happens only when using the Aspen Batch and Event Extractor tool to put batch data into Batch.21. However, the error message 'Specified characteristic is not defined' isn't an Extractor error. It's Batch.21 saying that it doesn't know about the new characteristic. This happens when a characteristic is created with auto-configuration (i.e. not created using the Batch.21 Administrator tool). It's not a bug or an error other than client tools will report this when their cache isn't updated. It takes the Batch.21 service a little while to catch up with configuration changes made outside the Administrator. To force an update, restart the Batch.21 service.
There have been some improvements made to the way the Batch.21 client tool cache is refreshed, based on the input from defect CQ00223904, documenting the above-mentioned error message. Please make sure you have the latest Batch.21 cumulative patch for your system version installed on your Batch.21 server.
Keywords:
References: None |
Problem Statement: The following message can be returned from the aspenONE installation when installing on Windows 2003 SP1.
1603: Error installing Windows Installer engine. A file which needs to be replaced may be held in use. Close all applications and try again.
This knowledge base article explains why this message is generated. | Solution: Windows 2003 SP1 includes a newer version of the Windows installer than the aspenONE media distributes. This error is encountered because the installation of the Windows installer from the aspenONE media fails. The reason the Windows installer fails is because there is already a newer version of the installer on the server which came with Windows 2003 SP1. If this error is encountered with Windows 2003 SP1 the error can safely be ignored (click OK then continue with the installation). The Windows installer distributed with Windows 2003 SP1 will work fine with the aspenONE product installation.
Keywords: Win2003
SP1
SP2
References: None |
Problem Statement: Under certain circumstances it is possible for TSK_DBCLOCK to use up to 50% of the CPU time, which could lead your InfoPlus.21 database to become unresponsive or appear to hang. This could occur if, for example, TSK_DBCLOCK was continually kept busy by the timestamp rescheduling configured by the database administrator.
Here is an example of such a situation:
Let's say that the XYZ database has twenty thousand records defined by xyz_analogdef, a custom definition record. Each of these records has three scheduling timestamp fields and three corresponding reschedule interval fields (IP_HIST1_RESCHED_INT, IP_HIST2_RESCHED_INT, IP_HIST3_RESCHED_INT.)
The IP_HIST1_RESCHED_INT field indicates that its corresponding scheduling timestamp (IP_HIST1_SCHED_TIME) should be rescheduled every hour. What if you mistakenly configured IP_HIST1_RESCHED_INT to have one-minute reschedule intervals instead of one-hour intervals?
Here is what would happen:
Let's say that the XYZ database has ten thousand scheduling timestamps configured at one minute reschedule intervals. This means that TSK_DBCLOCK has to activate and reschedule all ten thousand records every minute. The problem is that TSK_DBCLOCK requires more than a minute to process, trigger, and reschedule ten thousand scheduling timestamps. By the time it finishes one pass, it discovers that they all need to be retriggered and rescheduled all over again, ad infinitum. | Solution: InfoPlus.21 really is not intended to handle such a HUGE number of scheduling timestamp fields, regardless of the reschedule interval. This is perhaps 100x the number at a more typical site. The CPU time required to trigger and reschedule a single scheduling timestamp field is roughly proportional to the total number of schedule timestamp fields. The rescheduling of a single timestamp can be CPU intensive when there are large numbers (i.e. more than a few hundred) scheduling timestamps.
TSK_DBCLOCK would keep up without any problem if you reconfigured IP_HIST1_RESCHED_INT to have one-hour reschedule intervals instead of one-minute intervals.
If one minute rescheduling is really required, then perhaps a different mechanism could be used for scheduling the activations of all these records. For example, one record defined by ScheduledActDef could be configured to activate all these records. This might be a nice way to approach the problem if TSK_DBCLOCK is not handling it.
Keywords: 50%
unresponsive
hanging
References: None |
Problem Statement: This knowledge base article explains why a single value entered into an Aspen InfoPlus.21 database record may seem to be able to trigger more than a single alarm state for the database record. | Solution: The way the deadbanding works with the alarm states is that the data value must actually exceed the alarm limit for the alarm state to change. For example, if the alarm limits were configured in the database record as follows:
IP_HIGH_HIGH_LIMIT = 30
IP_HIGH_LIMIT = 20
IP_LOW_LIMIT = 10
IP_LOW_LOW_LIMIT = 0
and if the following data values are then entered into the database record in the following order, the value of 20 may seem to cause two different alarm states.
IP_INPUT_VALUE = 15 --> IP_ALARM_STATE = OK
IP_INPUT_VALUE = 20 --> IP_ALARM_STATE = OK
IP_INPUT_VALUE = 25 --> IP_ALARM_STATE = HIGH
IP_INPUT_VALUE = 20 --> IP_ALARM_STATE = HIGH
If the value is initially 15 (OK) and the value 20 is then typed in, the alarm state won't actually change to High because the IP_HIGH_LIMIT of 20 has not been exceeded. In order for the High alarm to be activated a value in excess of 20 (ie. 20.01) must be entered.
The same applies when changing from a high alarm state back to an OK state. The value in IP_HIGH_LIMIT (20) must be crossed again for the alarm state to change. This means that a value below 20 (ie. 19.99) must be entered for the alarm state to change back to OK.
Keywords: cross
pass
boundary
References: None |
Problem Statement: Aspen MES cluster is a redundancy | Solution: offered by AspenTech. While adding a cluster, you may receive the error:
Failed to open cluster <CLUSTER NAME>.Could not contact the specified cluster.
Followed by the error message:
Retrieving the COM class factory for component with CLSID {F2E~...}failed due to the error:80040154.Solution
AspenTech’s MES redundancySolution is based on Microsoft’s Failover Cluster feature,therefore a cluster must exist before enrolling an Aspen MES server application.
The computers hosting the clusters must meet the minimum requirements which involves enabling the Microsoft's Failover Cluster feature.
The Failover Cluster Feature is available with Windows Server 2008 R2 and above.
Follow the steps mentioned below to enable clustering.The steps mentioned are for Windows Server 2012
1. Log onto the first VM that will become a cluster node, then launch the Server Manager.
2. Select Dashboard from the left panel, then click Add other servers to manage.
3. Specify the name of the second VM and click Find Now. After the computer appears in the lower panel, click the right arrow to add it to the list of managed servers, and then click OK to finish.
4. From the dashboard, click Add roles and features, click Next, then select Role-based or feature-based installation, and then click Next.
5. Select Select a server from the server pool, then select the first VM in the list, and then click Next.
6. Click Next to skip roles, then enable Failover Clustering.
7. Click Add Features when prompted to add additional features.
8. Under the Remote Server Administration Tools feature, enable both the Failover Cluster Automation Server, and the Failover Cluster Command Interface options.
9. Enable the check box to restart the destination server automatically, then answer yes to confirm.
10. Perform the same steps to add the cluster feature to the other VM. Since we added that VM into the server pool, the feature can be added without leaving the current VM.
11. Click Add Roles and Features, follow the wizard, but instead select the second VM from the sever pool list, skip roles, select Failover Cluster feature, then add the additional remote administration options, then click Install, and then click Close.
12. Create snapshots of the two VM's at this point (if you want).
With this, the VM's are ready to be enrolled as clusters
Keywords: Failed to open cluster
Clustering
80040154
References: None |
Problem Statement: You may want to load on a production Aspen InfoPlus.21 system some custom records developed on a test Aspen InfoPlus.21 system. Rather than exporting a snapshot, which will overwrite the production database when being loaded there, you would prefer to export a list of specific records.
Is there a simple way to pick a group of records and extract them all to a single RLD file? | Solution: Yes, this is possible. In the Aspen InfoPlus.21 Administrator right-click on the database object and select Save Records from the context menu. In the GUI, select Find and the Aspen InfoPlus.21 record finder will appear. Query the records you like and drag and drop them to the Save Records window. Then save it in one file.
Keep in mind that customized definition records and their customized fields need to be saved as well. On the destination machine, save your snapshot before attempting to load your RLD file, in case there are errors or problems. Then do a test load to see if the RLD file loads successfully.
Refer toSolution # 106305 for information on the range of hexadecimal numbers that should be used when creating a custom definition record.
Keywords: recload
recsave
.rld
save records
find records
export
References: None |
Problem Statement: While trying to install AMS software, the user has a logon failure and cannot complete the installation. | Solution: When performing an AMS install, the account being used to install the software must be a member of the local administrator''s group. The reason for this is that the administrators group has particular user rights and policies that allow the appropriate permission for the activities required during an installation. If for some reason the user rights and policies of the local administrator''s group have been changed, a user may encounter a logon failure during the install.
To ensure the proper user rights assignment on a Windows 2000 machine:
Go
to Start | Settings | Control Panel | Administrative Tools | Local Security
Policy
Expand ''Local Policies''
Click on ''User Rights Assignment''
Check that the following Local Settings and Effective Settings specify the Administrator account (or an account that belongs to the Administrator''s group):
-- Access this computer from the network''
-- Log on as a service
-- Log on locally
To ensure the proper user rights assignment on a Windows NT machine:
Go to Start | Programs | Administrative Tools | User Manager
Select the Policies menu item, and the User Rights sub item
Check that the following User Rights specify the Administrator account (or an account that belongs to the Administrator''s group):
-- Access this computer from the network''
-- Log on as a service
-- Log on locally
Keywords: network logon failure
invalid account
References: None |
Problem Statement: InfoPlus.21 cumulative patch V7.3.0.3 provided a basic application that allowed the user to relocate the InfoPlus.21 folder locations (Defect ID: CQ00461057). IP21ProfileConfiguration could redefine the InfoPlus.21 Data Root folder and some additional child folders by creating the IP21Profiles.xml file.
This handy application is not installed in any other version of InfoPlus.21. You will not find it anywhere in V8.0, V8.4, V8.5 etc. | Solution: Since V8.0, the new InfoPlus.21 Server System Profiles Manager has completely replaced IP21ProfileConfiguration. It offers much improved functionality as listed below:
An InfoPlus.21 system profile specifies the location of certain InfoPlus.21 folders that hold configuration files: history system files, SQLplus query files, Cim-IO definition files, InfoPlus.21 group files (i.e., group200 folder). A profile also persists other configuration settings such as the defined task list and access control.
For example, you might want one InfoPlus.21 system profile for the InfoPlus.21 demo system and another profile for the production system. On startup, the InfoPlus.21 server will work with whichever profile is active.
Or you might need to move the InfoPlus.21 system folder, like group200, to another disk. Simply moving the folder using Windows Explorer will not work because InfoPlus.21 will not know about their new locations.
The InfoPlus.21 Server System Profiles Manager provides this capability and can be invoked from the Actions menu of the Aspen InfoPlus.21 Manager. Detailed instructions are included in the Aspen InfoPlus.21 Administration Tools Help.
Keywords: InfoPlus.21 Profile Configuration application
IP21ProfileConfiguration.exe
IP21ProfileConfiguration missing
IP21ProfileConfiguration not found
Where is IP21ProfileConfiguration?
References: None |
Problem Statement: The following error(s) may be received when attempting to install and application that requires the use of IEWebControls on a Windows Vista client.
Error 1: There was a problem with installing IEWebControls. The error return Code was 1603. Installation cannot proceed
Error 2: The specified path http://Nodename/Webctrl_client folder is unavailable. The Internet Information Server might not be running or the path exists and is redirected to another machine. | Solution: The Vista Metabase Compatibility component of IIS 7 must be installed on the server where Aspen Online will be installed. ** This component is not installed by default.**
To install the compatibility component
1. Open the Programs & Features page from the Windows Control Panel
2. Select Turn Windows Features On or Off
3. Then Select Internet Information Services > Web Management Tools > IIS 6 Management Compatibility > IIS Metabase and IIS 6 Configuration Compatibility.
Keywords: Error Code 1603;
Aspen Online;
IEWebControls;
IEWebControls.msi;
IEWebControls.exe;
References: None |
Problem Statement: When I try to update a QueryDef or CompQueryDef record to run at a certain time, the value of SCHEDULE_TIME does not update. | Solution: The #SCHEDULE_TIMES repeat area either in QueryDef or CompQueryDef record is used to store queries that need to run at a regular rate, not for a single instance. To activate this for a single instance, consider adding an activation method in the #WAIT_FOR_COS_FIELDS record, or toggling the value of the EXECUTE field to 'YES' for a one time activation. Otherwise, update the value of RESCHEDULE_INTERVAL to a value other than 0:00:00.0 so that the query will schedule on a regular basis.
Keywords: SCHEDULE_TIME
Querydef
CompQueryDef
References: None |
Problem Statement: This knowledge base article describes why the Aspen Batch.21 web service may not return data when the other Aspen Batch.21 client tools return data when the same batch or time frame is queried. | Solution: Queries executed under the Aspen Batch.21 web service run under the account which is authenticated in IIS. This behavior can occur when the authenticating user for the Aspen Batch.21 web service hasn't been granted permission to the areas from which data is requested. If your site uses anonymous authentication in IIS please ensure that the anonymous user account (IUSR_MachineName by default) has been given permissions to access the batch areas. If your site uses basic authentication or integrated windows authentication the user who runs the client application will need permission to the batch areas being queried.
Keywords: Access
Deny
Denied
Permissions
Allow
Blank
Empty
References: None |
Problem Statement: How do I view data in the same time zone as the server, even though the client is in a different time zone? | Solution: TheSolution to this issue is extremely easy in practice, however, the conceptual part can get a little confusing.
Simply put, you will use the Shift column in the legend of Process Explorer to push the data into the correct time . First, make sure the time zone service is configured in ADSA for the datasource you are trying to connect to. Then go to control panel --> services and make sure the Aspen Timezone Information service is started. You should then be able to go in to Process Explorer, and in the plot''s legend, you''ll see under TZ the time zone the server is in. Keep in mind, this is really just a display to help you decide how you should shift.
Then you just use the pull down menu, or type in the difference between the timezones in hours in the Shift column of the specific tag you are concerned with. Please note that it will highlight the sign of the number for you.
Here is an easy rule of thumb to determine the direction in which you will shift
If the client is west of the server''s time zone make the shift time negative (-).
If the client is east of the server''s time zone make the shift time positive (+).
Here is an example:
You are on a client PC in Houston and the server you are trying to view data on is in Seattle. This means the client will be in CST (Central Standard Time) and your server is in PST (Pacific Standard Time) time zone. There is a 2 hour difference between them.
Initially, when you add the tag to the plot you''ll notice when you are looking at their data, and that it looks as if it is currently updating. However, if you look closely, the time near the plot and on the scooters is the client''s time! It looks as if they are getting a data point of 0 at noon, when it actually happened at 10 am their time. This is not the way the data was stored, so you need to shift your view of it in order to see accurate time stamps associated with values. To do this you would type + 2:00:00 into the column named Shift in the legend of the Process Explorer Plot.
Immediately, it will look like there isn''t any data updating. But the thing to remember is that the time in the time line will always be the CLIENT''s time. You are two hours ahead of them, so you need to move your timeline 2 hrs. back to see accurate data. You should also notice that the time near the plot (and on the scooters) will display the SERVER''s current time.
All these principles apply for going east as well. The only difference is that after you change the Shift column, you will see data initially, and you''ll have to move it 2 hours forward to see current data.
NOTE: Because this shift column is configurable for each tag you are plotting, each tag you are plotting can have different timezones so that you view all the data at the actual time in which its happening. However, you will note that they won''t be updating right next to each other. One will be updating hours behind the other. There is no way to make them update next to each other since they still share an over all time line in the Client''s current time.
Keywords: timezone
TZ
shift
display
References: None |
Problem Statement: Your MS SQL Server database will continue to use more and more system memory until it eventually takes up all the memory on your NT system. Obviously, this can cause problems with all the other applications running on that node. | Solution: This happens because when SQL Server is installed, it determines the amount of physical memory on the computer, and sets the maximum parameter to that number. Once set, however, this can be changed via the Enterprise Manager. Highlight the server name, right mouse click, select Properties, and go to the tab labeled Memory.
The default memory settings are:
Dynamically configure SQL Server memory
Maximum = <size of RAM>
If you are using the database with Batch.21 (or any other database application), it will grow until it hits the maximum. If this is a problem, which it likely will be if you are running other applications on this computer, you may want to change it to something less. A suggestion is to only allow SQL Server to allocate up to half of the RAM on the PC. If your system has 128 MB of RAM, change the SQL Server Max memory to 63. In a production environment you may want to look at what other applications are there, what their memory needs are, how much you need in SQL Server to get acceptable performance etc., and then decide what would be a good size for this figure.
Keywords:
References: None |
Problem Statement: Using the Process Explorer or the Production Record Manager Administration tool you are unable to see or manage the existing Golden Batch Profiles. | Solution: This issue may occur when the amount of profiles has taken or exhausted memory using the Batch21services.exe.
When you open Process Explorer or the Administration tool you may notice that there are no profiles Visible or clicking on a Profile makes the program Non responsive.
If you have BCU , APRM, Batch Extractor and client tools running it may create a load on the Batch21services.exe and you will see that this service on the server is using large amounts of memory.
Run this query on the SQL APRM database.
select count(*) from profile_alarms;
select count(*) from profile_bands;
select count(*) from profile_context_values;
select count(*) from profile_envelopes;
select count(*) from profile_process_values;
select count(*) from profile_tags;
select count(*) from profiles;
select count(*) from profiling;
This will show you how many profiles and objects you have. There is no hard coded amount of memory set for the profiles however you may need to remove a profile that can be causing trouble. For instance if you have 70 profiles and 250,000 envelopes this could cause issues.
Normally a profile envelope should not need to poll an Infoplus21 Tag ever 1-10 seconds for the life of the batch. Be careful on how you set the envelopes so you dont overload the Batch21service.
It maybe possible to restart the service although this will only be very temporary fix as the service will start processing again and go back to using memory causing same issue.
If this does not work you will need to remove the profile from the SQL database. Ensure that you backup the database and then the Sql database administrator can then remove the profile manually.
If you need assistance with the removal of the profile please contact the Support helpdesk.
Keywords: APRM
Batch21services.exe
Memory
Profiles
Golden Batch
Profiling
Administrator
References: None |
Problem Statement: How many relational database client licenses are needed to work with Aspen Batch.21 clients? | Solution: The number of licenses for a relational database server (such as SQL Server or Oracle) is irrelevant, since all our requests to the Batch server are performed as impersonated requests by the account that the Aspen Batch.21 Service is running under. Of course the Batch.21 server needs to be on an actual server (not a workstation), because Aspen's Batch.21 server may be handling multiple concurrent client requests (Microsoft Windows 2000 and XP workstation installs allow a maximum of 10 connections).
Because the Batch.21 server makes all of the actual calls to the relational database, you will need only one license for the InfoPlus.21 Server to act as a relational database client.
Keywords:
References: None |
Problem Statement: How can you share templates created in the Aspen Add-In under the Aspen Process Data menus? | Solution: Templates allow you to save workflow configurations for future use. Once they're created they're saved in a folder under the user’s directory; for example, for user Administrator, the templates he’s created are stored in a XML file, ExcelFormulaTemplates.xml in the folder C:\Users\Administrator\AppData\Roaming\AspenTech\PME\ExcelAddin
You can share the templates of one user with other users by copying the ExcelFormulaTemplates.xml file of one user and replacing it with the one in other users’ folder.
For example, for user USER1, replace the ExcelFormulaTemplates.xml from user Administrator for the one for user USER1 under his folder C:\Users\USER1\AppData\Roaming\AspenTech\PME\ExcelAddin.
When USER1 starts Excel he'll see the templates in the Aspen Process Data menus and will be able to use them.
For further information on how to create templates see Process Data Excel Add-In HELP included with the product.
Keywords: Excel, COM, Add-in, template, share
References: None |
Problem Statement: How does the Heartbleed OpenSSL bug affect Aspen InfoPlus.21 and related products? | Solution: Heartbleed is a security bug affecting the OpenSSL cryptography library. Most Aspen InfoPlus.21 and related products requiring secure sockets use Microsoft IIS which is not affected by Heartbleed.
The Aspen CIM-IO to OPC-UA interfaces uses the .NET API from the OPC Foundation, which supports the SSL protocol, but is not based on OpenSSL. Therefore, it is not affected by Heartbleed. (Note: only OPC’s C++ and ANSI C APIs are affected, which Aspen does not use).
Some of our products work with Apache Tomcat which can be configured to use OpenSSL; however, standard Aspen installations connect to Apache Tomcat using Microsoft IIS.
In summary, the Heartbleed bug does not affect Aspen InfoPlus.21 and related products.
Keywords: Heartbleed
OpenSSL
References: None |
Problem Statement: Users may receive the following error when performing a 'Show | Solution: This is caused by DCOM being locked down. On the Aspen InfoPlus.21 machine click on Start => Run => type DCOMCNFG => click 'OK'.
Expand 'Component Services' => 'Computers' and right-click 'My Computer' => choose 'Properties'.
Switch to the 'COM Security' tab. Beneath 'Access Permissions' click 'Edit Limits'. Check the users and groups that are there and if any of them have 'Deny' checked consider removing the 'Deny' and/or make sure that the user who is experiencing the error is not that user and not part of the affected group.
If the 'Distributed COM Users' group is not listed please add it and give it Allow for 'Local Access' and 'Remote Access'. Click 'OK'.
Still on 'Access Permissions' click 'Edit Default'. Check the users and groups that are there and if any of them have 'Deny' checked consider removing the 'Deny' and/or make sure that the user who is experiencing the error is not that user and not part of the affected group.
If the 'Distributed COM Users' group is not listed please add it and give it Allow for 'Local Access' and 'Remote Access'. Click 'OK'.
Perform these same actions for both 'Edit Limits' and 'Edit Default' beneath the 'Launch and Activation Permissions' section.
Finally, add the user who is experiencing the problem to the 'Distributed COM Users' group on the InfoPlus.21 system.
Keywords:
References: s' in the Aspen InfoPlus.21 Administrator:
Text of the message: Error - Retrieving the COM class factory for remote component with CLSID {CA2C4C34-11E1-11D2-A739-00E02900BE0C} from machine <machine name> failed due to the following error: 80070005.
Note that the CLSID may be different than what is displayed here. |
Problem Statement: The following error message may be displayed during boot up after installing InfoPlus.21 v3.1: A dialog box appears with the following message: Error 2186 The service is not responding to the control function. In the NT Event Viewer the following error message appears:
The NobleNet Portmapper for TCP service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
In the Services folder under Noblenet Portmapper for TCPIP, it is not running. It can not be started at this point. InfoPlus.21 will not start up at this point. | Solution: The Portmapper is corrupt, which is preventing InfoPlus.21 from starting up. You have to uninstall the Portmapper executable and then reinstall it. Once the portmapper is installed then you can start InfoPlus.21.
Go to: C:\Program Files\Common Files\AspenTech Shared\Portmapper
Select PORTINST.exe, and double click on it.
This will launch NobleNet Portmapper Utility. In this dialog, select Remove Noblenet Portmapper, and hit OK.
Close and reopen this utility, and then select Install NobleNet Portmapper, and hit OK.
Return to Control Panel > Services > Noblenet Portmapper for TCPIP and it will have started at this point. InfoPlus.21 will start now with no error messages.
Keywords: 2186
Noblenet Portmapper
TCPIP
IP21
References: None |
Problem Statement: Existing code is often ported to newer software versions. Sometimes slight enhancements will cause an application to not work with the newer software version. This is such the case when using AspenTech''s 3.x Visual Basic controls to access an InfoPlus.21 v2.5x database. This does not reflect a bug in either version of the software, but rather, a progression in software architecture. | Solution: With the 2.5.x version of InfoPlus.21 and Process Explorer, the hostname or servername is specified in the VB control to direct the program to access data from the proper database. This servername is what gets defined via the Configure Servers dialog box when configuring Process Explorer 2.5.x to view data from an InfoPlus.21 2.5.x database.
With the inception of the new security features of InfoPlus.21 3.x, this has changed. To use the 3.x version of the VB control with a 2.5.x version of InfoPlus.21, one must now specify the ADSA datasource name instead of the hostname or servername.
The example below uses the GetAttributeData() function to illustrate this point. This particular function takes the following form:
GetAttributeData(Server, Map, Tag)
The 2.5.x version of GetAttributeData requires the Server argument to point to the hostname of the InfoPlus.21 server. However, the 3.x version of the GetAttributeData function requires the Server argument to be the ADSA datasource. Please see below for an explicit example.
Function GetAttributeData(sServer As String, sMap As String, sTagName As ''sServer should refer to the ADSA datasource, not the hostname!
String, sAttribute As String) As Variant
Dim b As Boolean
Dim vData As Variant
Dim tag1 As AT_TAGLib.Tag
Set tag1 = New AT_TAGLib.Tag
tag1.SetSource sServer, sMap, sTagName ''sServer should refer to the ADSA datasource, not the hostname!
b = tag1.GetAttributeData(sAttribute, vData)
tag1.Disconnect
GetAttributeData = vData
End Function
Keywords: Control
ActiveX
Data Source
Security
References: None |
Problem Statement: When invoking the Aspen InfoPlus.21 Health Monitor how can one fix this message which appears after one selects the system name and clicks 'Go':-
Last update time for health task is invalid. Error: String was not recognized as a valid DateTime.
Note: The Aspen InfoPlus.21 Health Monitor was introduced in Aspen InfoPlus.21 v2006 and is present in that and subsequent versions. | Solution: Please do the following:
1. Find TSK_HLTH in the 'Defined Tasks' list in the upper left corner of the Aspen InfoPlus.21 Manager. Double-click on it. This will fill in the task's details on the right side of the screen. Assuming that one wants the Health Monitor to run all the time, uncheck the 'Skip during startup' box. Click the 'Update' button on the bottom of the Manager so that the change is applied to the task.
2. Click the 'RUN TASK' button beneath the 'Defined Tasks' list. A message stating
TSK_HLTH is started successfully should appear in the lower left of the Manager
3. In the Aspen InfoPlus.21 Administrator navigate to the record IP21SystemHealthTests and look for the 'SCHEDULE_TIME' field in the fixed area. It is probably set to undefined (a series of question marks ?????????? )
4. Change the field to either be a time in the past or a time in the future when it should run. If using a time in the past one can simply specify a time (no date needed) and the system will run things immediately (it will replace the time entered with an appropriate one). For example, to use a past time of 4:00 AM on today's date simply enter 04:00. If specifying a future time please include the date as well if the time is something other than today. For example, to specify June 06, 2009 at 7:44 PM (assuming that is a future date and time) use '06-JUN-09 19:44.
Note: The above example assumes that the time and date are formated as DD-MMM-YY HH:MM:SS, The format is changeable on a system-by-system basis.
Keywords: None
References: None |
Problem Statement: Why might I see multiple instances of my Aspen InfoPlus.21 Database (IP.21 Server) in the scope pane of the Aspen InfoPlus.21 Administrator (IP.21 Administrator) ?
Does my IP.21 Server have a problem ? | Solution: Nothing is wrong with the server.
What you see are multiple data sources providing access to the same database.
Each instance is called by the name of the data source defined in Aspen Data Source Architecture (ADSA).
In the IP.21 Administrator, you can expand any of these data sources to view or modify the database, it will produce the same effect.
There can be good operational reasons why multiple data sources need to be created for a single database. A typical situation is when multiple Aspen Process Data services are required on the IP.21server. For instance, Aspen Process Data (Calc) to allow on-demand calculations and Aspen Process Data (IP.21) to retrieve IP.21 values in Aspen Process Explorer. Because an ADSA data source can only contain one Aspen Process Data service, it's necessary to create 2 data sources.
You must open the ADSA client on the machine running the IP.21 Administrator to find where it gets its data sources from.
Aspen DA for IP.21 is the service in ADSA that makes an IP.21 datasource appear in the IP.21 Administrator.
After carefully checking what data sources and services are really required for your applications, remove the redundant data sources in ADSA or eliminate the redundant Aspen DA for IP.21 services pointing to the same database among multiple data sources.
Keywords: ADSA duplicate Data Sources
References: None |
Problem Statement: Can I create my own Display Format in Aspen InfoPlus.21? | Solution: Yes, you can create a format that better meets your requirements. On your InfoPlus.21 Administrator you need to go to the building blocks, where you?ll find the Display Formats.
If you want to create a Real Format F5.4, the easiest way is to duplicate the F 5.2 format and call it F 5.4. Then you will need to change the DISPLAY_WHOLE_DIGITS and the DISPLAY_LEGHT accordingly.
F 5.2 means that you have 5 display digits (including the + or ? sign), whole digits, the decimal point, and the decimal digits.
+ / -
1
.
1
2
=
1.12
Once the real format is created, it can be selected for your tags.
Keywords: InfoPlus.21
Display Format
Selector tags
References: None |
Problem Statement: Can a snapshot created using a 32-bit Aspen InfoPlus.21 server be upgraded to a 64-bit server? | Solution: A snapshot created using a 32-bit Aspen InfoPlus.21 server can be upgraded to a 64-bit server provided the version of Aspen InfoPlus.21 is the same version or later.
Keywords: Snapshot
32 bit
64 bit
References: None |
Problem Statement: When Aspen InfoPlus.21 is in a stopped state, how is the value in the SCHEDULE_TIME field of a ScheduledActDef record handled upon startup? | Solution: When stopping and starting IP.21 the SCHEDULE_TIME field is taken into account. For instance if InfoPlus.21 is stopped at 08:30:00.1 and started at 10:15:43.1 for an hourly query scheduled at the top of the hour, the next record activation will be at 11:00:00.0. So it is re-scheduled based upon the ORIGINAL SCHEDULE_TIME and RESCHEDULE_INTERVAL.
Furthermore, because a SCHEDULE_TIME has been passed, the associated records will be activated once, directly on startup of InfoPlus.21. The number of SCHEDULE_TIMES that have passed (in this example, 09:00:00.0 and 10:00:00.0) has no bearing on the number of activations upon startup.
Keywords: None
References: None |
Problem Statement: Is Aspen InfoPlus.21 (IP.21) multithreaded and will it run on dual processors? | Solution: Yes, InfoPlus.21 can run on a multiprocessor. InfoPlus.21 is a system of multiple processes. That alone means there is some potential benefit in having multiple processors. Some of the InfoPlus.21 processes are multithreaded. So this provides additional advantages.
Having multiple processors can help, but it does not help nearly as much as having a faster single processor. Because the database is locked during every database update, a faster processor is helpful.
However, because InfoPlus.21 is not a truly multi-threaded application in its entirety, you will realize greater performance from a 2 GHz single processor machine than a 1.3 GHz dual processor machine, even though the latter has more combined power (2.6 GHz). Since our development and testing is also primarily in single processor environments, it's also possible that having multiple processors might trigger problems that need to be addressed.
Keywords: MULTI-THREAD
MULTI-THREADED
MULTI CORE, MULTI CORED
CPU
CENTRAL PROCESSING UNIT
PROCESSORS
SYSTEM REQUIREMENTS
SPECIFICATIONS
References: None |
Problem Statement: Are the records that begin 'D-' used by Aspen InfoPlus.21? | Solution: When browsing the Aspen InfoPlus.21 database using the Aspen InfoPlus.21 Administrator tool one may observe many records that begin withA 'D-', for example D-IP_Analog and D-IP_Discrete. When looking at the contents of these records they don't contain any process data. Is it OK then to delete them or are they actually used by the system in any way?
These records are used by Aspen InfoPlus.21, and it would be a mistake to delete them from the database.
If one looks at the description field of these records it will probably say 'Default Base Record.'A What exactly is a default base record, and how are they used?
Let's use data compression as an example:
When a value arrives in the IP_INPUT_VALUE field of an analog tag record from the interface, field processing (which is part of the internal processing carried out by Aspen InfoPlus.21) asks several questions, such as:
What is the timestamp of this value?
Does this value violate any alarm limits?
Does this value exceed any compression settings in the field IP_DC_SIGNIFICANCE?
To check whether any compression settings have been violated, a message is sent to a data compression record, IP_BoxCarSlope, defined by BoxCarSDef. This record has to handle compression requests from any analog (or discrete) record one may have in the database.
Now, before this data compression record can determine what has happened, it needs to go back to the data record and extract some information, such as the last recorded value, the timestamp of the last recorded value, the boxcar/backslope value, etc. In fact if one looks at the fixed area of the compression record one can see the information it needs.
This what the fixed area of the compression record looks like:
Notice the use of the D-IP_Analog reference. It's being used here as a temporary place-holder. When a data record requires processing, the actual name of the record replaces the reference to D-IP_Analog. So, in the example above, when Ana1 needs to have its data compression checked, the fields will read:
LAST_RECORDING_FIELD Ana1 1 IP_TREND_VALUE
SIGNIFICANCE_FIELD Ana1 IP_DC_SIGNIFICANCE
MAX_INTERVAL_FIELD Ana1 IP_DC_MAX_TIME_INT
Then, when data compression processing has been completed, the field values will revert to their default settings of D-IP_Analog.A In fact the compression record behaves in a similar way to an External Task.
As you can see, if you delete these default base records, data compression will no longer work; neither will the InfoPlus.21 alarming functionality or indeed anything that uses these base records.
Keywords: None
References: None |
Problem Statement: Aspen InfoPlus.21 fails to start at boot, and the following message appears in the output file for TSK_H21_PRIME:
chdir to <C:\Program Files\AspenTech\InfoPlus.21\c21\bin>
Message Code NOT Found: -2506
You may also see the following message in the Windows Application log:
Error during auto start of InfoPlus.21.
C:\Program Files\AspenTech\InfoPlus.21\c21\h21\bin\h21prime.exe exited with error code = 1
Note: The file path in the error messages may vary depending one installation location of Aspen InfoPlus.21.
Aspen InfoPlus.21 then starts normally using the Aspen InfoPlus.21 Manager. | Solution: After TSK_DBCLOCK completes, the program TSK_H21_PRIME starts a copy of h21archive.exe for each repository. Before starting the archiver programs, TSK_H21_PRIME changes the default directory location to the one containing h21archive.exe. Sometimes, especially in a virtual environment, that folder is not available to TSK_H21_PRIME immediately after a reboot.
TheSolution is to change the startup type of the Aspen InfoPlus.21 Task Service from Automatic to Automatic (Delayed Start).
If you have the box STARTUP @ BOOT checked in the Aspen InfoPlus.21 Manager, then the Aspen InfoPlus.21 Task Service starts Aspen InfoPlus.21 when the service starts. Switching the startup type of the Aspen InfoPlus.21 Task Service to Automatic (Delayed Start) delays starting Aspen InfoPlus.21 until hopefully resources are available after rebooting.
Keywords:
References: None |
Problem Statement: How to determine the rate at which scanned data is stored into Aspen InfoPlus.21 history.
Here is an Aspen SQLPlus script that provides how fast tags are being historized within a repository. The benefit of this script it that it is configurable per repository, number of tags, and the fileset. The results can then be output to Microsoft Excel for further viewing. The same information can be viewed using the fileset summary in the AspenTech InfoPlus.21 Administrator. | Solution: This script is designed to provide the Aspen InfoPlus.21 admin with a list of the point tags in a given repository which use the most disk space.
Note: This script may take several minutes to execute, depending on the size of the specified fileset, because the h21summary procedure executes very slowly with large filesets.
The user is required to enter three variables:
1. Repository name (variable name repos)
2. Fileset number (variable name fileset)
3. Number of tags to summarize (variable name number)
On some systems, this query may time out on the following line:
(SELECT recid, name from ALL_RECORDS)..
If this happens, substitute ALL_RECORDS for IP_AnalogDef or any other Definition Record to limit the tag summary to a specific record type.
*****************************************************************************
LOCAL repos CHAR(32), fileset INT, number INT;
-- Enter the Repository Name here. Must be in single quotes.
repos=PROMPT('Repository','TSK_DHIS');
-- Enter the fileset number here
fileset=PROMPT('Fileset number',1);
-- Enter the number of records to return here
number=PROMPT('Number of records to return',10);
WRITE local.repos||' fileset #'||local.fileset;
WRITE 'Total size of the top '||local.number||' tags is '||
(SELECT SUM(Size) FROM (select substring(7 of line) as Size from (system 'C:\Progra~1\AspenTech\InfoPlus.21\c21\h21\bin\h21summary -r'||local.repos||' -a'||local.fileset||' -t'||local.number||'')WHERE linenum > 17))||' Kbytes';
WRITE 'Total size of entire fileset (arc.dat) is '|| (TRIM('M' from (select substring(5 of line) from (system 'C:\Progra~1\AspenTech\InfoPlus.21\c21\h21\bin\h21summary -r'||local.repos||' -a'||local.fileset||' -t'||local.number||'')
where linenum = 2)))||' Mbytes';
(SELECT recid, name from ALL_RECORDS) INNER JOIN (select cast (substring(2 of line) as INT)/1024 as recid, substring(3 of line) as Avg Data Collection Rate, substring(5 of line) # of Data Points, substring(7 of line) as Size FROM (system 'C:\Progra~1\AspenTech\InfoPlus.21\c21\h21\bin\h21summary -r'||local.repos||' -a'||local.fileset||' -t'||local.number||'') WHERE linenum > 17) USING (recid) ORDER BY # of Data Points DESC;
Keywords: Data Rate
History
SQLplus
References: None |
Problem Statement: After installing IP.21 v3.1 the local IP.21 node is not listed in the IP.21 administrator. | Solution: Remove the data source in the ADSA config tool and re-add it.
Sometimes you also have to reboot the PC.
Keywords: administrator
References: None |
Problem Statement: How do I prevent Aspen IP.21 Administrator from crashing when tryting to create new tag by right clicking on folder? | Solution: On some specific InfoPlus.21 Snapshot it’s observed that when trying to create a new Tag by right clicking on a Folder, IP21 Administrator will get freeze and then crashes.
This issue is due to incorrect value configured in “Folder_links� for that particular folder.
Please follow below steps to update ““Folder_links� value.
1. Open IP21 Administrator
2. Locate the Particular Folder.
3. Expand the particular folder by clicking on (+) sign.
4. Select “Fields� of that Folder.
5. Update the “Folder_LINKS� to Zero “0�.
After above changes, user should be able to create new Tags by right clicking on a Folder
Keywords: Folder
Tag Creation
IP21 Administrator
Crash
Freeze
References: None |
Problem Statement: Generally an event.dat file is created when the history process, h21archive.exe, is paused or stopped due to file set backups or history system problems. However, there have been cases where an event.dat file is created while the h21archive process is still running. This can happen if data is entering the history system faster than can be processed by the history tasks. For example: if there is excess network traffic. This would generally be a one time occurrence. Once the excess network traffic subsides, the history system catches up and the event.dat file is flushed.
Other times, however, IP.21 systems have been restarted and windows boxes have been rebooted in order to reinitialize the history system and flush the event.dat file. Sometimes this works - but only temporarily. Other times, it does nothing to help. The event.dat file continues to grow. | Solution: 1. Check the fragmentation of the hard drive storing the history file sets. Chances are, this drive is badly fragmented, thus creating a performance bottleneck. Data is being collected faster than the history task is able to write to disk. You will need to stop IP.21 and run a defragmentation utility.
2. If the disk seems to be in good heath there exists the possibility that data is entering the event.dat faster than the h21archive process can un-buffer it. To see a list of the most frequently updated tags for the current file set, click on the repository with the problem, then right click on the current file set (the file set with a start date but no end date.) Select the Summary option. The list of tags at the bottom of the summary form will include information such as the scan rate (Avg. Rate) for each of the tags. The default number of tags displayed is 10, but this number can be adjusted by the user.
If it is determined that a record is scanned too frequently one then needs to determine the source of the data updates. Locating the record in the Administrator then right clicking the record to 'Show
Keywords: defrag
defragmentation
fragment
fragmentation
event.dat
References: s' will display any cimio transfer record or scheduling record which controls frequency of updates for this data record. This update frequency may need to be adjusted. If no references to transfer records or scheduling records are observed, it may be that a value is written to these records from an SQLplus query, AspenCalc script, or another custom application.
3. There also exists the possibility that the number of records scanned into this repository is larger than was originally allocated for this repository. The current number of records allocated for a repository can be determined by examining the Current Number of Points value. This value can be found by right clicking on the repository then selecting Properties. With this in mind, one can determine the number of tags currently scanned into this same repository by right clicking on the current file set, then selecting the Summary option. The value in the Tags field in the upper right hand portion of the form will indicate how many tags are currently scanned into this repository. This number should not exceed the number of configured records allocated for this repository.
4. A fileset shift may temporarily cause an event.dat file to appear. For a complete explanation of what happens during a fileset shift, please refer to |
Problem Statement: ghost field를 추가할때 아래와 같이 드롭다운 목록에 내용이 없음. | Solution: 본 이슈는 ghost field로 추가할 field가 이미 custom definition record에 추가되였기 때문입니다.
1) offending field 삭제
2) fixed area에서 아무 field 나 클릭
3) 메뉴 바(menu bar)에서 Fields 클릭
4) New | Ghost Field를 선택하여 New Ghost Field 창을 오픈.
5) Ghost Selector, Ghost Record 와 Ghost Field 를 선택
6) 확인를 클릭하여 Ghost Field 를 custom definition record에 추가
Keywords: definition editor
ghost field
KR-
References: None |
Problem Statement: When launching the Health Monitor from the Aspen InfoPlus.21 Administrator, the IP21 Tasks Health Tests expand to show three fields, but not the field titled IP21 License Tests. | Solution: Navigate to IP21HealthGrpDef and locate IP21TasksHealthTests from that definition record. Make sure the #DATA_BASE_RECORDS field is set to 4 and open the repeat area. Make sure the 4 record names there are: AllIP21TasksRunningTest, IP21TasksReStartingTest, AllIP21ServicesRunTest, and IP21LicenseTests as follows:
Keywords: IP21LicenseTests
Health Monitor
References: None |
Problem Statement: Can the Aspen InfoPlus.21 OPC-DA server display the contents of folders to an OPC client? | Solution: The Aspen InfoPlus.21 OPC-DA server cannot display the contents of folders to OPC clients even though you can add folder records to the record IP_TagsBranch.
Keywords: Aspen InfoPlus.21 DA OPC server, Aspen.InfoPlus21_DA.1, PE_BranchDef, IP_TagsBranch, FolderDef, Folder
References: None |
Problem Statement: Snapshot Upgrade Wizard fails to upgrade a snapshot with the following error message when trying to upgrade to an existing target snapshot file:
ERROR in saving output snapshot, code=-11, name=InfoPlus.21.snp, length=14 | Solution: The above error message sometimes occurs when the user doesn't have a permission to overwrite the target snapshot file or it cannot be overwritten for some other reason such as being locked by another process or application.
PossibleSolutions:
Run the Snapshot Upgrade Wizard again and give the target snapshot a new name, such as IP21New.snp.
Turn OFF the User Access Control (UAC) for Windows Server 2008 for the duration of the snapshot upgrade
Keywords: None
References: None |
Problem Statement: Sometimes when upgrading the Aspen InfoPlus.21 database snapshot from older versions to V7.3, upgrade fails with the error error in creating new long names segment, code=-9 | Solution: In order to resolve this error the Free Space should be increased on the source snapshot by loading it on the older IP.21 version you are upgrading from. Use the following procedure in order to increase the Free Space :
1. Log in to the Aspen InfoPlus.21 (IP.21) server machine (older version you are upgrading the snapshot from).
Note: Please contact Aspentech Support for assistance in case you don't have server available that has older version of software installed.
2. Right click on the node name within Aspen InfoPlus.21 Administrator and select Properties from the context menu.
3. In the Memory Utilization tab please change the 'Total' memory to maximum number. The maximum number is highlighted in green in the screen capture below.
4. Once you have this changed save the snapshot and use this snapshot to upgrade the database to V7.3.
5. In case the total number defined is about the same as maximum number, stop IP.21, change the DBClock (Version 2006.5 and higher)/ loaddb (versions prior to 2006.5) memory parameter from Command line parameters to something higher. Restart the database and then increase the number in the Total field.
6. Repeat Step 3 and Step 4 to successfully upgrade the database.
Keywords: long names segment, upgrade
References: None |
Problem Statement: The external task used for Aspen KPI is called TSK_KPI. As with all external tasks there is an Error file associated with the task called TSK_KPI.ERR
Sometimes an error (or warning) message is generated with a number, such as
Failed in .\KPITask.cpp , line 151, record Unknown, error number -37.
Where can you find the meaning of some of the error messages with numbers that appear in TSK_KPI.ERR (or any other Error Message file) ? | Solution: Look in ...\Infoplus.21\db21\include folder for file setcim.h. This is a header file that defines numerous system variables that are used within the Aspen InfoPlus.21 system.
Open setcim.h in Notepad and then search for the error code that was returned when a problem was encountered.
An example would be:
06-18-2012 08:59:17 Failed in .\KPITask.cpp , line 151, record Unknown, error number -37.
The entry in setcim.h that corresponds to this error code is:
#define STOPTSK (-37) /* Task requested to stop */
Keywords: .\KPITask.cpp
ERR
TSK_KPI
setcim.h
References: None |
Problem Statement: We have had a few cases where, for some data records only, the users cannot see any History Repeat Area fields via the Administrator tool, nor via Process Explorer, but they can with some other tools such as SQLplus. This would typically only be seen with records defined by a Custom Definition record. The problem is that Process Explorer, the Excel Addins, Batch21, and the IP21 Administrator all require history repeat areas to have key timestamp fields explicitly defined. This symptom is because the Definition Record was incorrectly built, and no key timestamp field has been designated.
This missing key timestamp field may be verified as follows:
Within Definition Editor, select your Custom Definition Record and duplicate it using Definition => Duplicate
Select the duplicated record and make it unusable using Definition => Make Unusable
Choose Definition => Modify on the duplicated, unusable definition record
Choose Area and choose the History Repeat Area (e.g. #_of_Trend_Values)
Select any one of the fields in the History Repeat Area and choose FROM THE MENUBAR Special => KeyFields
If the Key Timestamp Field is empty, then this confirms the problem. | Solution: TwoSolutions:
1. Delete all data records defined by the Custom Definition Record, Make the Definition record Unusable, and modify it to explicitly contain a Key Timestamp field. Finally, make the Definition record Usable and re-create the data records. Warning, this will cause you to lose all of your old history for all records defined by the bad Definition record.
2. The InfoPlus.21 UPGRADE.EXE program is used to upgrade from an earlier version of IP21 to a later version of IP21. A full upgrade procedure could be used to fix the problem as well as preserve your old history. Perform the steps as follows:
Save all files normally saved during an Upgrade (Snapshot, History and Dat files etc..)
Delete all data records defined by the bad Definition Record
Make the Definition Record Unusable, add the Key Timestamp Field, and make it Usable again
Run Upgrade, where the database with the corrected Definition record is the Target and the previously saved Snapshot is the Source.
Once Upgrade is complete, restore all History and Dat files as normal
Keywords: key timestamp
history
empty
References: None |
Problem Statement: What causes the error h21 shared-memory size is too big in TSK_DBCLOCK.ERR when trying to start Aspen InfoPlus.21? | Solution: This error indicates a problem in the file config.dat. TSK_DBCLOCK reads the contents of config.dat and allocates the memory required by the historian. Look at KB 124960 entitled What are the command line parameters for TSK_DBCLOCK and what does TSK_DBCLOCK do when starting Aspen InfoPlus.21?.
To work around this problem you can restore the file C:\ProgramData\AspenTech\InfoPlus.21\c21\h21\dat\config.dat from a backup.
If you do not have a backup of config.dat, then delete the corrupted copy of config.dat. Next, start a minimal InfoPlus.21 by starting only the tasks TSK_DBCLOCK, TSK_H21_PRIME, TSK_SAVE, TSK_H21T, and TSK_ADMIN_SERVER by opening the Aspen InfoPlus.21 Manager, double clicking on each of these tasks, and clicking on the RUN TASK button.
After starting the five tasks, your Aspen InfoPlus.21 Manager should look like (note, TSK_H21_PRIME is not an external task and will not appear in the Running Tasks list):
TSK_DBCLOCK loads the Aspen InfoPlus.21 snapshot into memory, TSK_SAVE will save the Aspen InfoPlus.21 database to a snapshot when you stop Aspen InfoPlus.21 later, TSK_H21T will save the changes made to history configuration to config.dat, and TSK_ADMIN_SERVER allows you to run the Aspen InfoPlus.21 Administrator.
Starting Aspen InfoPlus.21 without config.dat creates another copy of the file and starts Aspen InfoPlus.21 with the default repositories:
Now, you can use the Aspen InfoPlus.21 Administrator to add your repositories again.
After adding the repositories, stop Aspen InfoPlus.21 to save your work.
Keywords:
References: None |
Problem Statement: The Data Source Configuration Tool will not offer MS Access as a database option if MS SQL was previously selected or the registry keys for a previously installed Aspen Framework version are present. This document describes a workaround to this problem which will be fixed in the next release. | Solution: Three parameters in the AFW Registry folder should be deleted.
1. Using the Regedit utility, expose the AFW folder by expanding HKEY_LOCAL_MACHINE\SOFTWARE\AspenTech and selecting AFW.
2. After selecting the PROVIDER, DATABASE and DATASOURCE parameters in the right pane, choose the delete right click option to remove.
3. Rerun the Data Source Configuration Tool and select MS Access. The tool will recreate the deleted parameters.
Keywords: Local Security
Data Source Configuration Tool
MS ACCESS
References: None |
Problem Statement: After installing InfoPlus.21, the machine must be rebooted. During the the reboot, the following messages may be displayed:
Couldn''t create service ''AtLocalAFWTrusteeServer''. Error Code= 0x80070241.
Couldn''t create service ''AtRegistrySecurityServer''. Error Code= 0x80070241. | Solution: The installation must be performed using a Domain\User account. When prompted for information in the Windows NT Service Configuration dialog box, a Domain\Username is required.
Even when an account on the local machine is used for the installation, a Domain is required. In this case, the Domain would be the local NT Machine name.
Keywords:
References: None |
Problem Statement: During the installation of the AMS 4.0 or 4.1 CD, generally during an upgrade from earlier versions, there have been cases of the following error at step 1 or 2:
the installation of core component Aspen License Manager fails. Set up cannot continue. | Solution: Open the registry by going to Start | Run | Regedt32.
Go to the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\
The keys under User Shell Folders should have the data type of REG_EXPAND_SZ. If not already set, set the values to:
Common Admin Tools - %ALLUSERSPROFILE%\Start Menu\Programs\Administrative Tools
Common AppData - %ALLUSERSPROFILE%\Application Data
Common Desktop - %ALLUSERSPROFILE%\Desktop
Common Documents - %ALLUSERSPROFILE%\Documents
Common Favorites - %ALLUSERSPROFILE%\Favorites
Common Programs - %ALLUSERSPROFILE%\Start Menu\Programs
Common Start Menu - %ALLUSERSPROFILE%\Start Menu
Common Startup - %ALLUSERSPROFILE%\Start Menu\Programs\Startup
Common Templates - %ALLUSERSPROFILE%\Templates
Keywords:
References: None |
Problem Statement: How can I change the database name displayed in the Aspen InfoPlus.21 Administrator? | Solution: The database name displayed in the Aspen InfoPlus.21 Administrator is taken from the Aspen Data Source configuration tool. In other words, you can just edit the data source name of your Aspen InfoPlus.21 using the ADSA Client Config Tool and refresh the Aspen InfoPlus.21 Administrator window to see the new name.
Note: Changing the database name means that you will have to update plots, graphics, and spreadsheets to reference the new database name.
Keywords: ADSA Configuration tool
Data Source name
IP.21 Administrator
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.