Wonderware Industrial Application Server 2.0 Patch 01 ReadMe

Last revision: 12/14/2004

This document contains important information about WonderwareÒ Industrial Application Server 2.0 Patch 01. Please carefully review this document for known issues in this version and changes to the Industrial Application Server documentation included on this CD.

System Requirements

Installation Information

Before You Begin

Known Issues – Industrial Application Server 2.0 Patch 01

Known Issues – Industrial Application Server_Documentation

Resolved Issues

Release Summary

Industrial Application Server Documentation

 

System Requirements

To run Industrial Application Server, we recommend as a minimum the following software and hardware configurations:

Software Requirements

FactorySuite A² Development seat - IDE with Galaxy Repository (Project Database)

MicrosoftÒ SQL Server 2000 Service Pack 3a and

MicrosoftÒ WindowsÒ Server 2003 or

MicrosoftÒ WindowsÒ 2000 Server with Service Pack 4 or

MicrosoftÒ WindowsÒ 2000 Advanced Server with Service Pack 4

 

Important! Industrial Application Server 2.0 Patch 01 requires installation of Microsoft SQL Server 2000 Service Pack 3a. IAS installation cannot distinguish between SP3 and SP3a of SQL Server. So, you must ensure that the proper service pack is installed for proper functionality.

Important! The Microsoft SQL Server login for BUILTIN\Administrators group must be present and enabled.

Important! Industrial Application Server 2.0 Patch 01 REQUIRES InTouch 9.0 Patch 01 and IndustrialSQL Server 8.0 SP3.

 

FactorySuite A² Development seat - IDE with no Galaxy Repository (Project Database)

MicrosoftÒ WindowsÒ Server 2003 or

MicrosoftÒ WindowsÒ 2000 Professional with Service Pack 4 or

MicrosoftÒ WindowsÒ 2000 Server with Service Pack 4 or

MicrosoftÒ WindowsÒ 2000 Advanced Server with Service Pack 4 or

MicrosoftÒ WindowsÒ XP Professional with Service Pack 2

 

FactorySuite A² Application Server Runtime

MicrosoftÒ WindowsÒ Server 2003 or

MicrosoftÒ WindowsÒ 2000 Professional with Service Pack 4 or

MicrosoftÒ WindowsÒ 2000 Server with Service Pack 4 or

MicrosoftÒ WindowsÒ 2000 Advanced Server with Service Pack 4 or

MicrosoftÒ WindowsÒ XP Professional with Service Pack 2

 

Hardware Requirements

PC with 2 gigahertz (GHz) or higher processor clock speed

1 gigabyte (GB) of RAM or higher (512 MB minimum supported; may limit performance and some features)

8 gigabytes (GB) of available hard disk space

Super VGA (1024 × 768) or higher-resolution video adapter and monitor

CD-ROM or DVD drive

Keyboard and Microsoft Mouse or compatible pointing device

 

While the IDE itself has only been tested on English operating systems, it can be installed on non-English operating systems for use with InTouch in browsing a Galaxy Repository.

< top of document >

Installation Information

It is recommended that you read the Industrial Application Server Deployment Guide (found at www.wonderware.com/support/mmi under the Documentation hyperlink).

The Microsoft SQL Server key is required in order to install the MS SQL Server. When installing the MS SQL Server, you will be asked to enter the 25 digit key number. The Microsoft SQL Server key number is GJDD4-GMYXW-GQR4C-KT4P9-QDQGB.

A prerequisite of the Industrial Application Server is the installation of Microsoft SQL Server SP3. This service pack may be downloaded directly from Microsoft at http://www.microsoft.com/.

If you choose to burn the web-downloaded patch to a CD, you must have the word “Patch” as your CD label in order to install this patch from the burned CD.

Applying the Patch

Both the Galaxy Repository and remote nodes must be patched with the downloadable Industrial Application Server 2.0 Patch 01 prior to deployment or undeployment of objects. Otherwise, you will encounter errors.

The IAS 2.0 Patch 01 can be applied only to an IAS 2.0 installation. The following information specifies in greater detail what occurs when you install this patch:

·         Applied to IAS 1.5 or earlier - Install does not proceed, with message that the version must be at least IAS 2.0.

·         Applied to IAS 1.5 Patch 01 - Install does not proceed, with message that the version must be at least IAS 2.0.

·         Applied to IAS 2.0 - Normal patch install occurs.

·         Applied to IAS 2.0 Patch 01 – Normal patch install occurs.

After applying the patch, all Galaxies on the Galaxy Repository node are automatically updated with Patch 01.

If a backed-up IAS 1.5 Galaxy is restored into an IAS 2.0 Patch 01 system, that Galaxy is automatically updated to Patch 01 when a connection is made to that Galaxy.

< top of document >

 

Before You Begin

Please note the following important issues before you continue:

L00028024: Importing a large Galaxy with template containment takes a long time.

Attempting to import a large Galaxy with multiple levels of template containment may take a long time. Actual time is dependent on the size of the Galaxy and number of template containment associations that must be handled during the import process.

L00021350:  Undeploying WinPlatform from InSQL node inactivates InSQL console.

If you undeploy the WinPlatform from the InSQL node, the InSQL console stops working and the following Error message is displayed:

“Error on server xxxx - interface not registered.”

To recover from this problem, deploy the WinPlatform again to the InSQL node. To safely undeploy the WinPlatform from an InSQL node, use the remove platform functionality in the System Management Console.

L00015386:  Effects of Terminal Services in application mode.

If Microsoft Windows Terminal Services is configured in application mode, creating, importing and deploying Galaxies will be significantly slower.

L00024676:  Industrial Application Server 2.0 Patch 01 output extension functionality has changed.

Output functionality in IAS 2.0 Patch 01 is different from 1.5 functionality. For complete details, see the Output Functionality section of the Enhancing an Object’s Functionality chapter in the IDE documentation (Help in the IDE or the IDE.pdf file in the UserDocs folder off the root of the CD).

L00023099:  History Store Forward Directory only in WinPlatforms.

In Industrial Application Server 1.5, the History Store Forward Directory option was configurable in both AppEngines and WinPlatforms. In IAS 2.0 Patch 01, this option is configurable only in WinPlatforms.

 

Anti-Virus Software Issues

Anti-Virus software should not process files in the following ArchestrA folders:

    C:\Program Files\ArchestrA\Framework\Bin\CheckPointer

    C:\Program Files\ArchestrA\Framework\Bin\GalaxyData

    C:\Program Files\ArchestrA\Framework\Bin\GlobalDataCache

    C:\Program Files\ArchestrA\Framework\Bin\Cache

    C:\Documents and Settings\All Users\Application Data\ArchestrA (default setting,
       specified on WinPlatform editor’s General page, History store forward directory option)

If the Anti-Virus software does so, this may result in slow performance as deploys are performed.

L00031502:  Applying the patch on a system with objects still deployed, undeploying all objects and then deploying only the GR WinPlatform displays a message that the WinPlatform must be redeployed to get the latest updates.

Initially, you should undeploy all objects before installing this patch on your system. But if you encounter this problem, doing a cascade redeploy gets around the issue.

 

< top of document >

Known Issues – Industrial Application Server 2.0 Patch 01

 

Install/Uninstall/Upgrade

L00022082:  System does not correctly detect open applications during installation on a Windows 2003 Server computer.

If you attempt to install Industrial Application Server 2.0 Patch 01 while ArchestrA applications are running, the Files in Use dialog box is displayed. On a Windows 2003 Server computer, the applications shown in this dialog box may be incorrect. For instance, it may list “ArchestrA IDE” three times. You can disregard the specific information provided by this Microsoft operating system dialog, but it does indicate that you must quit at least one ArchestrA application before installation can proceed.

L00022459:  Error messages at end of remote installation using Terminal Services.

If you remotely upgrade Industrial Application Server from 1.5 or 1.5 Patch 01 using Terminal Services, an MSI application error message is displayed at the end of the installation process. Also, errors are sent to the Event Logger. These messages can be safely ignored. Installation has completed successfully.

L00025950:  To avoid IDE lockups, select “Dictionary order, case-insensitive, for use with 1252 Character Set” during SQL Server setup

When setting up SQL Server on the Galaxy Repository node, "Dictionary order, case-insensitive, for use with 1252 Character Set" must be selected. Otherwise, lockups in the ArchestrA IDE may occur.

L00026201:  IDE-related Warning messages after reinstalling ArchestrA.

If you uninstall and then reinstall ArchestrA, starting the IDE logs Warning messages in the Logger. These Warning messages are not indicative of a system problem as everything functions properly.

L00029044:  ArchestrA user account must have read/write permissions if checkpoint directory is on a network share.

The ArchestrA user account that enables node-to-node communication (created during ArchestrA installation in the User Name and Password dialog box) must have read/write permissions to a checkpoint directory location if that directory is on a network share.

< top of document >

IDE Functionality

L00015386:  Effects of Terminal Services in application mode.

If Microsoft Windows Terminal Services is configured in application mode, creating, importing and deploying Galaxies will be significantly slower.

L00021257:  Successful unassignment limit.

Attempting to unassign as many as 700 templates (or 4,000 instances) at the same time may result in only some objects being unassigned and an IDispatch error being displayed in the progress dialog box.

L00021936:  Galaxy Load causes unnecessary set attribute errors for Switch and FieldReference objects.

During a typical Galaxy Load, a set attribute operation does not cause Error messages to be logged when both the set attribute value and the target attribute’s value are the same. This is not true for Switch and FieldReference objects. The Galaxy Load operation is completed successfully, but Error messages will be generated during the operation.

L00022509:  Terminating IDE with Task Manager causes problems.

Terminating the IDE application with Task Manager when a bulk operation is in progress causes Errors to be logged to the Logger, impacts the functionality of other IDE sessions, and requires restart of aaGR service on the Galaxy Repository node. You can restart the aaGR service by rebooting the computer or shutting down and then restarting the service through Control Panel.

L00022604:  Assign To dialog box list incomplete.

In a multi-user environment, right-clicking an object, clicking Assign To in the shortcut menu, and attempting to use the drop-down list in the Assign To dialog box may not display all available objects. This problem may occur even when you created the object expected in the drop-down list. If you type the name of the object in the Assign To box, the object appears in the drop-down list.

L00023181:  IDE Help only shows if Galaxy Repository and IDE nodes are set to English locale.

Attempting to open IDE Help fails if the default locale of the Galaxy Repository/IDE node is set to a non-English language.

L00024662:  While using InTouch SmartSymbols, IDE user is locked out from configuring Security.

Creating objects using InTouch WindowMaker’s SmartSymbol capability will cause an internal IDE session to be created and held open. Consequently, certain actions on other IDE sessions that require exclusive access to the Galaxy Repository may be prevented. For instance, if you attempt to configure security in the IDE, the following message is displayed: “Configure Security : Cannot configure security as more than one session of the IDE is running. Open in read-only mode?” To close the internal IDE session created by WindowMaker, you must quit WindowMaker and WindowViewer (if running).

L00024676:  Industrial Application Server 2.0 Patch 01 output extension functionality has changed.

Output functionality in IAS 2.0 Patch 01 is different from 1.5 functionality. For complete details, see the Output Functionality section of the Enhancing an Object’s Functionality chapter in the IDE documentation (Help in the IDE or the IDE.pdf file in the UserDocs folder off the root of the CD).

L00025735:  No “invalid data” message on UDAs page, when one is appropriate.

An “invalid data” message is not displayed if you enter invalid data for an element of an array on the UDAs page of an object’s editor and then move focus to the UDA name list. “Invalid data” messages are displayed if you move focus to any other control on the page.

L00025809:  Attribute Browser filter does not work with double-byte characters.

If you extend an object with a UDA that contains double-byte characters, attempting to use the Edit Filter function of the Attribute Browser on that attribute does not perform any filtering at all.

L00025902:  Only domain users are presented with list of domain groups in the Select Groups dialog box.

If you select OS Group Based security as your ArchestrA model, the following scenario may arise. When you add a Role on in the Configure Security dialog box, the Select Groups dialog box is displayed. The Available OS Groups list is populated only with those groups that belong to the domain displayed in the Select In box. This occurs because the domain controller does not provide a list of its groups to non-domain users who do not have permission to browse groups on other domains.

L00026458:  Resetting to a lower screen resolution may cause the Application View/Template Toolbox views to disappear off-screen.

If you set the IDE to non-maximized mode, dock the Application View or Template Toolbox windows outside of the IDE client area, and then change the screen resolution on your monitor, the Application View/Template Toolbox windows may disappear from view. Reset the screen resolution to its original value to see these windows again. Re-dock them inside the IDE client area before changing the screen resolution again.

L00026509:  A non-default initial value of a UDA is lost in a Galaxy Dump/Galaxy Load operation.

UDAs of type "OBJECT Writeable" can be configured in the IDE to have a user specified initial value. After doing a Galaxy Dump and Galaxy Load, "OBJECT Writeable" UDAs will be reset to a default initial value.

L00026925:  Deletion hourglass may not go away until the mouse is moved.

Occasionally, deleting a template object results in a sustained hourglass after the object has been successfully deleted. Move the mouse to remove the hourglass.

L00027032:  Importing objects with newer components common with WinPlatforms requires the platforms to be deployed.

When an object is imported that brings in a newer component that is common to the WinPlatform object, no other object can be deployed or redeployed in the Galaxy until its WinPlatforms are redeployed. This problem would apply to importing objects like DIObjects, which contain components like the DAServer Manager that are installed when WinPlatforms are deployed.

L00027959:  Industrial Application Server performance lower when hyper-threading is enabled.

Hyper-threading should be disabled on all ArchestrA nodes. Some computers vendors (for instance, Dell) may enable hyper-threading by default. To disable this feature:

  1. Reboot the computer.
  2. Enter BIOS setup.
  3. Disable hyper-threading.
  4. Save and exit setup.

L00028887:  Reassignment refresh may not work.

If you reassign objects from one host to another, occasionally the IDE may not refresh the screen. If this occurs, the reassignment function was successful, but you should quit and then restart the IDE to refresh the screen.

 

< top of document >

Import/Export/Migration

L00021692:  Some imported C++ libraries do not appear in Script Function Browser.

Imported script function libraries written in Managed (.NET) C++ do not appear in the Script Function Browser.

L00021694: Importing a modified .aaSLIB file into same Galaxy does not register as COM dll.

To manually modify the XML file in an .aaSLIB file to designate a script function library as a COM object requiring registration, follow the procedures in the “Script Functions” section (“Enhancing an Object’s Functionality” chapter) of the IDE documentation. Script library re-import will register the COM dll into the Galaxy file repository. Note that if objects that have scripts referring to the .aaSLIB are already deployed, then nodes where those objects are deployed will not get the latest script library unless you redeploy the platform. Once you have cascade redeployed the platform, objects will use the new script library.

 

< top of document >

Scripting

L00023621:  Array indirects do not work, result in validation error.

Validating an object with a script that uses an array indirect causes an error. An example of an array indirect is the following:

Dim index[5] as indirect;

index[].bindto(“test.float[]”);

Array indirects do not work in this release. Objects using them will not validate and therefore cannot be used.

L00024900:  Memory leak associated with use of an open SqlConnection in scripts.

The following problem occurs when running scripts that use .NET libraries, imported dlls and WDF. Opening a SqlConnection for a long time can cause a memory leak. Microsoft recommends against keeping a SqlConnection open for a long time. If you want to do so, though, you can eliminate the leak by adding “Min Pool Size=2” to the connection string in the script.

L00026314:  Several quality functions do not work with aliases.

The following quality-related script functions do not work with an alias that references a quality function in the hosting object: SetBad(), SetGood(), SetUncertain(), SetInitializing(). When you save the object configuration that contains the script function, a warning is displayed about not being able to resolve the reference. If you deploy an instance of the object, quality is not set as expected (for instance, Bad, Good, Uncertain, Initializing).

L00028374: Error message for invalid script expression is wrong.

If the syntax of a script expression is invalid, an error message is displayed in the Errors/Warnings page of the object’s Properties dialog box. In this release, the message may be wrong. For instance, if you use a semi-colon at the end of a script expression, the error message states “Expected ‘;’ ” when it should state that it is invalid.

 

< top of document >

Deploy/Undeploy

L00021350:  Undeploying WinPlatform from InSQL node inactivates InSQL console.

If you undeploy the WinPlatform from the InSQL node, the InSQL console stops working and the following Error message is displayed:

“Error on server xxxx - interface not registered.”

To recover from this problem, deploy the WinPlatform again to the InSQL node. To safely undeploy the WinPlatform from an InSQL node, use the remove platform functionality in the System Management Console.

L00023029:  Incorrect setting of DCOM impersonation level will cause deployment to Windows 2000 Server to fail.

ArchestrA requires that the DCOMCNFG Default Impersonation Level be set to "Identity" on a Windows 2000 Server node. If the Default Impersonation Level is set to Anonymous, deploying a WinPlatform to the computer will fail. To set this option, run DCOMCNFG from a command prompt on the Windows 2000 Server computer. Select the Default Properties tab and set the Default Impersonation Level to Identity. Deployment of a WinPlatform to the node will now succeed.

L00025276:  Redeployment times out when computer disconnected.

When redeploying objects to a remote node on a slow network, multiple error messages are logged to the Logger if the computer is disconnected from the network. Even if you reconnect the computer to the network, redeployment continues to fail because Microsoft DCOM times out. About 15 minutes after reconnecting the computer to the network, you can redeploy again.

L00025825:  Deployed object that references a deleted object changes state when validated.

Assume a deployed object that references another object, and the latter object is subsequently undeployed and deleted. The state of the referring deployed object changes from Good to Warning. But if you manually validate this object, its state changes to Pending Update. The difference is due to the fact that as soon as the object is deleted, the Galaxy Repository marks all of the referring objects in Warning state whether they are deployed or not. However, the validate operation could mark the objects in Error or Warning states because of other reasons besides a broken reference. That is why the validate operation creates a new version of the object when changes are encountered. In this particular scenario, the issue is the different state of the object caused by the deletion of the referred object.

L00026218:  Deploying multiple engines at a time will skip objects with delta changes.

Deployment in the following procedure fails, assuming two sets of objects hosted by separate AppEngines that are already deployed to the runtime:

  1. Edit the configuration of one of the objects hosted by AppEngine1.
  2. Edit the configuration of AppEngine2.
  3. Deploy these configuration changes by multi-selecting objects across both AppEngines.

The delta configurations of the affected objects are not deployed. To do so, deploy only those hosted by a single AppEngine in one operation, and then deploy the second set of objects.

L00029249:  A customized InTouchAlarmHistoryBufferSize Registry key value is not persisted when undeploying a WinPlatform.

The InTouchAlarmHistoryBufferSize key in the Registry can be used to configure the alarm records available in the Historical mode of the AlarmViewer control. If you change the value of this key from its default and then undeploy the WinPlatform object, that change is not persisted. In other words, when you deploy the WinPlatform again, the key’s value will be the default. You must manually reset this key value each time you deploy the WinPlatform.

 

< top of document >

Historian

L00010226:  InSQL interpretation of Initializing as Bad quality.

PV.Quality changes between Bad and Initializing are not sent to the InSQL historian for instances of AnalogDevice and FieldReference $Float and $Double objects. InSQL stores “NULL” for Bad quality and interprets Initializing as a form of Bad quality. Since there is no change (from “NULL” to “NULL”), nothing is stored in the historian when PV.Quality changes from Bad to Initializing.

L00023099:  History Store Forward Directory only in WinPlatforms.

In Industrial Application Server 1.5, the History Store Forward Directory option was configurable in both AppEngines and WinPlatforms. In IAS 2.0 Patch 01, this option is configurable only in WinPlatforms.

L00025014:  Incorrect log messages about StoreForward block deletion.

When an ArchestrA node goes into StoreForward mode (it has been disconnected from the InSQL node), eventually it will reach its storage threshold. After this point, it begins deleting the oldest blocks of StoreForward data. This operations functions properly, but logged messages tracking this deletion process indicate an incorrect order of deletions.

L00025414:  Date format problem in historizing data to InSQL historian when InSQL and Industrial Application Server are running on different language operating systems.

Tags/attributes are not registered correctly in InSQL when the Industrial Application Server node is running an English operating system and the InSQL node is running a foreign language operating system. This problem is caused by incompatible date formatting on each computer. The InSQL historian should be installed on an English operating system.

L00025504:  Increased private bytes usage exhibited in an OS process does not indicate a leak.

With a memory usage utility like Performance Monitor, you may notice a gradually increasing consumption of private bytes by the Microsoft module, LSASS.exe, on a node sending data to InSQL. According to Microsoft, memory consumption levels off at an amount proportional to the total memory on the computer. Also, the memory manager releases memory when other applications require it. This issue is not a memory leak, and it should not affect your system’s functionality.

L00026137:  ConnectState attribute does not necessarily reflect historization state.

If you set the ConnectStateCmd attribute of the AppEngine to False, historization to InSQL stops, but the ConnectState attribute incorrectly remains True. This attribute should not be used as an indicator of whether ArchestrA components are historizing to InSQL.

L00029018:  Storeforward error log clutter, loss of data.

In rare cases, the InSQL Server error log may contain one or more entries about one or more storeforward blocks failing an integrity check, with accompanying loss of storeforward data. When this happens, the storeforward blocks in question are not automatically deleted but remain in the <storeforward>\MDAS subfolder of the main InSQL data folder. On every future storeforward event, the InSQL Server again tries to process the same blocks and reports the same messages in the error log. To prevent this cluttering of the error log, manually delete the offending storeforward blocks from the <storeforward>\MDAS folder.

 

< top of document >

Redundancy

L00024451:  During Failover, dynamic attribute quality temporarily changes to Initialize.

When a redundancy failover occurs, the quality of a dynamic attribute in a hosted object is set to Initializing until the Standby AppEngine becomes the Active AppEngine.

L00024949:  AppEngine may not be able to access the historian after a failover if the historian had also failed.

Assume the following scenario: The connection to the InSQL historian has failed, causing the Primary AppEngine of a redundant pair to begin StoreForwarding data; and a redundancy failover condition occurs, causing the Standby AppEngine to become Active. In such a scenario, the new Active AppEngine remains in StoreForward mode even if the connection to the InSQL Server is restored. A Microsoft hotfix related to RPC that should fix this problem is in progress.

L00025415:  Undeploying hosted objects during a Redundancy Failover operation fails.

Attempting to undeploy hosted objects during a Redundancy Failover operation results in the objects not being undeployed but marked as undeployed. Note that the failover is successful and everything is running properly on the new Active AppEngine, including the objects you attempted to undeploy. To successfully undeploy them, you must deploy them, selecting the Mark as Deployed check box in the Deploy dialog box, and then undeploy them.

L00025725:  Data quality for DIObject attributes may change during failover.

During a failover, data quality for attributes from DIObjects may change briefly to Initializing and then to Bad before returning to Good. This behavior is particularly important in the scripting environment. In your scripts, you should always test for data quality especially before doing calculations.

L00026594:  Bad quality, Comm? value in InTouch during failover.

During the failover transition period that a Standby AppEngine becomes Active, the value and quality for attributes subscribed for by InTouch views may display as “Comm?” and “Bad”, respectively. This condition is resolved when subscriptions are rebuilt on the new Active AppEngine and the failover process is complete. This problem typically occurs on setups in which the DIObject data source is located on a remote computer from the original Active AppEngine.

L00026930:  Offscan redundant pair WinPlatform causes benign error message during deployment of partner object.

An INVALID HRESULT LINE 76 FILE error message is logged to the ArchestrA Logger when you do the following steps:

  1. Configure Primary and Backup sets of redundant objects.
  2. Cascade deploy the Primary WinPlatform and put all objects onscan.
  3. Put the Primary WinPlatform offscan.
  4. Deploy the Backup WinPlatform.

The product functions normally when you successfully deploy the Backup WinPlatform and place the Primary WinPlatform onscan.

L00028912:  Deploying Primary AppEngine is incomplete when Backup AppEngine node is unavailable.

Deploying a Primary AppEngine when the Backup AppEngine’s node is unavailable (for instance, the computer is powered down) results in an incomplete deployment. To ensure successful deployment of the Primary AppEngine, do the following:

1.      Verify that the Engine Failure Timeout option on the Primary AppEngine’s editor is at least 10,000 ms (the default value).

2.      Unassign the Backup AppEngine from its WinPlatform.

3.      Deploy the Primary AppEngine.

If you have already attempted to deploy the Primary AppEngine, do the following first before doing the procedure above:

1.      Redeploy the Primary AppEngine, selecting the Mark as Deploy check box on the Deploy dialog box.

2.      Undeploy the Primary AppEngine.

L00029251:  Redeploying a Primary AppEngine with pending updates fails if Backup is undeployed.

You cannot redeploy a Primary AppEngine with pending updates if the Backup AppEngine is undeployed and you do not include it in the Primary AppEngine redeployment. If you attempt to do so, redeployment fails. The workaround is to undeploy the Primary AppEngine first and then deploy it again.

L00029524:  Shutting down computers, unplugging the primary and RMC cables and then restarting them results in Active/Active status.

On computers with multiple NICs (3 or more) and hosting a redundant pair of AppEngines, if you shut down the computers, unplug the primary and RMC network cables between the two computers, and restart the computers, the two AppEngines are unable to arbitrate their Active/Standby status and result in an Active/Active scenario. To avoid this problem, do not use DNS to assign flexible IP addressing on multiple NIC computers; rather, use fixed IP addresses.

L00029739:  Shutting down and restarting a redundant pair of AppEngines does not load a new version of script function library onto the Backup.

If you re-import a new version of a script function library used by a redundant pair of AppEngines, you must restart the AppEngines for the new script function library to take effect. When you shut down and then restart the redundant pair of AppEngines, though, the new version of script function library is not loaded into system memory on the Backup computer. To work around this problem, make the Primary AppEngine the Active partner and then redeploy the Backup AppEngine.

L00029782:  WinPlatforms hosting redundancy-enabled AppEngines must run on the same operating system.

For redundancy to function properly, WinPlatforms hosting redundancy-enabled AppEngines must be deployed to computers running the same operating system.

L00031263:  Failover by shutting down a WinPlatform or AppEngine from the SMC triggers a new alarm in the Alarm Summary.

Failover by shutting down a WinPlatform or AppEngine from the SMC triggers a new alarm in the Alarm Summary. This issue does not occur when using the ForceFailoverCmd attribute or by disconnecting the primary network cable.

 

< top of document >

SCADA/ Intermittent Networks

L00026263:  Network traffic increases when WinPlatform is shutdown.

Consider a scenario in which one or more WinPlatforms host objects with subscriptions to attributes on another WinPlatform, P1. For instance, P1 may have been enabled as an InTouch Alarm Provider or FieldReference objects on the other WinPlatform(s) read the ScanState of an object on P1. If WinPlatform P1 is shutdown, network traffic increases due to additional communications from the other WinPlatform(s) attempting to reestablish lost subscription data. The additional communication continues until P1 is started up again.

L00026501:  WinPlatform connection problems if computers cannot be accessed by both Hostname and IP address.

All nodes in your Galaxy must be able to communicate with each other by using both IP address and node name in the Network Address option of the WinPlatform’s editor. This is true no matter which type of Network Address you choose to use. For example, assume two nodes in your Galaxy (host name: NodeA, IP address: 10.2.69.1; host name: NodeB, IP address: 10.2.69.2). NodeA must be able to ping NodeB with both “NodeB” and “10.2.69.2”. The reverse must also be true for NodeB pinging NodeA. Failure in either case, for instance, may result in the following: you may not be able to connect to a remote Galaxy Repository node from the IDE or deployment operations may fail.

L00028044:  Extended log in time due to slow network and OS Group security.

If you are using Industrial Application Server on a network with slow links between your Operator View nodes and your domain controller, and you use OS Group based security in ArchestrA, you may experience long log in times. For instance, an operator logging in to an InTouch View may wait 30 seconds or more before being able to operate the View. To mitigate this problem, either provide additional domain controllers or configure the Login Timeout and Role Update interval options in ArchestrA security.

 

< top of document >

Miscellaneous

Anti-Virus Software Issues

Anti-Virus software should not process files in the following ArchestrA folders:

    C:\Program Files\ArchestrA\Framework\Bin\CheckPointer

    C:\Program Files\ArchestrA\Framework\Bin\GalaxyData

    C:\Program Files\ArchestrA\Framework\Bin\GlobalDataCache

    C:\Program Files\ArchestrA\Framework\Bin\Cache

    C:\Documents and Settings\All Users\Application Data\ArchestrA (default setting,
       specified on WinPlatform editor’s General page, History store forward directory option)

If the Anti-Virus software does so, this may result in slow performance as deploys are performed.

L00010030:  Use of comma in numerical attributes fails on non-English locales.

ArchestrA relies on Regional Settings when dealing with numerical attributes that contain decimals (a period in English language locales, a comma in some non-English locales). InTouch uses only periods as decimal markers. Therefore, writing numerical attributes from InTouch to an ArchestrA Galaxy using a non-English Regional Setting will fail. Nodes in your application must be configured with the Decimal Symbol for Numbers in the Regional Settings set to a period rather than a comma.

L00023766:  Object attribute’s security classification must be parsed from “MxSecurity” prefix.

In order to display the security classification of an object attribute, a client must parse the classification from an “MxSecurity” prefix. The classification that is received is in the following format: MxSecurityXXXX, in which XXXX is the security classification.

L00024333:  String arrays not supported in Alarm Message Attribute.

ArchestrA mistakenly validates as OK an Alarm Extension that contains a string array in the Alarm Message Attribute option (attribute: DescAttrName). This option does not support string arrays. If you do enter a string array in this option, the Alarm Extension will not function properly in the runtime environment.

L00025157:  Any reference with leading or trailing spaces fails to bind.

Ensure that you do not inadvertently add leading or trailing spaces when typing any reference in an object’s editor. References with such spaces fail to bind and their quality is Bad.

L00025214:  Computers with multiple NICs requires special configuration.

If any nodes in your ArchestrA environment have multiple NICs, be aware that proper configuration of those computers is essential to successful communication between ArchestrA nodes. Information about configuring multiple NIC computers is included in the Introduction and ArchestrA Redundancy chapters of the IDE documentation (IDE.pdf). See the “Multiple NIC Computers” section of the Introduction chapter and the Important! notes in the “Configuring Redundancy in the WinPlatform” section of the ArchestrA Redundancy chapter.

L00025453:  Writes fail if new users simultaneously log in on separate nodes.

If two InTouch WindowViewer users simultaneously log in on two different ArchestrA nodes, attribute writes to either node may not succeed until after the nodes synchronize user information. This problem most likely occurs on slow and intermittent networks.

L00026208:  Validation for alarm sub-states not done during configuration.

For the AnalogDevice, validation for alarm sub-states (like LoLo, Lo, Hi, HiHi) does not occur during configuration. For instance, assume you configure the LoLo alarm limit of an object to be 100 and do not enable the Lo alarm. The default value of the Lo alarm (zero) is used, but this invalid relationship between the LoLo and Lo alarm limits is not validated when you save the object’s configuration. In the runtime environment, though, an attempt to change the 100 limit for the LoLo alarm causes the following Error to be displayed:

“Operational error: Attempting to set invalid limit value.  The limit value must maintain the condition: HiHi.Limit > Hi.Limit > Lo.Limit > LoLo.Limit.”

Ensure that these relationships are maintained when configuring alarm sub-states in objects.

L00026352:  Array configuration does not propagate to child object.

Assume a scenario in which an instance has been created from a derived template of the $UserDefined base template. If you extend the derived template’s functionality with a non-array UDA, the change is propagated to the instance object. If you reverse the configuration of the derived template by setting the UDA to be an array, the change is not propagated to the instance.

L00026527:  “Could not access file repository share on GR node” error message.

This error message may occur in one of the two following scenarios:

·         If the time settings on the Galaxy node and a remote node are significantly different (several hours). In this case, if a user on the remote node attempts to connect to the Galaxy Repository through the IDE, the error message is displayed.

L00026637:  Extending CustomStruct attributes.

Extending a CustomStruct attribute with an output extension that writes to another CustomStruct attribute does not write to the output CustomStruct attribute.

L00026895:  FieldReference $String object’s PV does not indicate string data type limitation.

The PV of the $String FieldReference object has a data type of string, and therefore does not read strings greater than 1024 characters. If an input value exceeds 1024 characters, the PV keeps its current value, quality remains Good, and the PV.Input.ReadStatus property does not indicate any problem.

L00026898:  A user-defined attribute (UDA) of string data type improperly reads values greater than 1024 characters.

In this release of Industrial Application Server, a string UDA can read values greater than 1024 characters. It should not do so. This will be corrected in a future release. Do not use string UDAs for this purpose.

L00031171:  Change of security mode does not always display the correct mode on an InTouch security logon within a reasonable timeframe.

The InTouch security logon panel does not always reflect the new security mode (for instance, OS Group Based), which is displayed in the title bar. This occurs if the user changes to several different security settings. This behavior occurs on computers that run different operating systems.

 

< top of document >

 

Known Issues – Industrial Application Server Documentation

The following table describes changes to the documentation.

 

Item

Location of Change

Existing Documentation

Change

1

ObjectViewer.PDF and ObjecViewer.chm: Overview chapter, User Interface section, Edit menu subheading.

Lists Undo, Cut, Copy and Paste commands under Edit menu.

Remove Undo, Cut, Copy and Paste commands. The only remaining command under Edit menu is Find Object.

 

< top of document >

 

Resolved Issues

The following defects were fixed for this patch release. Click on the defect number for a more detailed description of the problem.

L00025941 When the user switches from an active engine to a standby state engine, memory consumption remains at 56MB and 11 threads.

L00028173 Hung AppEngine does not failover.

L00028459 After fifty failovers in a multiple redundant engine pair system with only one engine pair failing over every fifteen minutes, the active engine handle count increases from 500 to 2000.

L00028711 An object with an array attribute with an initial size of zero generates warnings in the Logger on the IDE node during configuration.

L00028731 The PV of an AnalogDevice (Regulator) object displays a value of NaN (Quality Good) after object is redeployed. Value recovers after about 20 minutes.

L00028898 The App Engine appears to leak memory when executing an application object that calls a .net component via COM interop.

L00028965 Export/Import of redundant pair of AppEngines may change Active status property.

L00029066 Errors posted in Logger during a failover: "NotificationDistributorRuntime Couldn't get platform name Unknown error from PlatformInformationClerk2".

L00029082 The script validator rejects overloaded functions from an imported .dll that have an "out" or "ref" modifier on a parameter. The validator only accepts a function with a double parameter when integer, float and string overloads are also present.

L00029088 When the ForceFailoverCmd is invoked, error messages regarding ObjectSyncMgr, CheckpointFileServer, and BaseRunTimeComponentServer are logged in the Logger.

L00029091 An Area with AlarmMode set to "Silent" displays new alarms in the InTouch Alarm View.

L00029094 First-time reference binding takes a while (30 seconds) after shutting down the Active of a redundant pair and a failover transition is complete.

L00029129 An Area on a redundant AppEngine with AlarmMode set to "Silent" or “Disable” displays all alarms in the InTouch Alarm View after failover, and after about 24 seconds, the alarms disappear.

L00029378 In a SCADA environment, redeployment of a non-redundant AppEngine sometimes fails (not responding).

L00029461 Memory leak occurs in the Bootstrap if the wrong IP address is entered in the Platform Redundancy Message Channel IP Address.

L00029500 When the RedundantDIObject is in Disconnected state and you advise an I/O point, Quality for that attribute stays as Initializing rather than going Bad.

L00029514 Redeploying DIObject causes RedundantDIObject to no longer subscribe to its ProtocolFailureReasonCode attribute.

L00029563 After shutting down a WinPlatform and debugging subsequent Object Viewer problem on the Galaxy node, an error is displayed from the InTouch Alarm Provider: MergeAlarmList - encountered invalid message type.

L00029565 Shutting down a WinPlatform and then browsing other WinPlatforms in ObjectViewer may cause comm errors.

L00029567 Attributes AlarmOnCnt and AlarmOnCntTotal of an Area hosted by a redundant AppEngine increment after the Standby becomes Active by the amount of the actual alarms only after a graceful shutdown of the Active engine using the SMC or by powering down the computer gracefully.

L00029682 In a SCADA environment, trend shows gaps for an attribute that does not change value through store-forward events.

L00029712 Slow-changing tags or tags that do not change do not get historized if the AppEngine is stopped and restarted.

L00029738 In a SCADA environment, unexpected network traffic is encountered due to Bootstrap failing to tear down unused client subscriptions.

L00029741 In a SCADA environment, MDAS store-forward was leaking up to 4,000 handles over a 5-day period.

L00029827 A failover about ¼ second after poking a $Vstring value from InTouch to a DIObject sometimes sets attributes status to Pending.

L00029832 Standby-Ready status of a redeployed redundant AppEngine does not immediately allow a failover from its redundant partner.

L00029834 Referencing an invalid item on a DIObject hosted by a redundant AppEngine causes the subscription to be rebind every second.

L00029922 Values on an InTouch display show Configuration Error for 20-30 seconds every time a display is called up.

L00030048 A DDESuiteLinkClient object configured to point to a SuiteLink server on a remote node fails to detect a Disconnected event when the network cable is unplugged.

L00030149 A Boolean UDA is set to True if another float UDA's initial value is negative.

L00030154 After several failovers in a multiple redundant pair environment, one of the redundant pair that is not failing over disappears in Object Viewer and in the SMC.

L00030206 WinPlatform AppEngine in a redundant configuration leaks memory (50 Kb per minute) on a Windows XP SP2 computer.

L00030278 Reapplying Patch 01 (after it has been previously run) causes the Windows installer dialog to display during the registration of modules.

L00030360 Null values written due to a network Disconnect are not masked by the first value from store-forward. As a result, a gap is shown in the trend and the Query Analyzer. Null's should be masked by the first point from the StoreForward stream.

L00030370 After reassignment of an ApplicationObject from one AppEngine to another, a poke to the AppObject in Object Viewer fails and the write status is Pending. The status of the redundant AppEngine hosting the DIObject is in Not Responding state.

L00030377 The AppEnginePrimitive3.dll and AppEnginePrimitivePackage.dll that got installed were old versions.

L00030407 Installing Patch 01 on IAS 2.0 does not replace InSQLManualdata.dll version '830' with the new version of '833'.

L00030460 SystemArea.AlarmOnCntTotal shows Quality Uncertain although none of its sub-areas show Uncertain.

L00030475 InTouch alarm client does not receive alarms after an Area.AlarmModeCmd is enabled. The Area mode was set in the following sequence: Enable to Disable to Silent to Enable.

L00030536 If a Galaxy version is 2.0 and the IDE connects to it, then the Galaxy needs to be patched at that time.

L00030547 Unacknowledged alarms (UnAck Return to Normal state) are not displayed in the InTouch Alarm Viewer if they existed before the Area mode was changed from Silent to Enabled.

L00030700 On AppEngine startup, if input/output extensions are enabled in an ApplicationObject but not configured, errors are logged to the Logger.

L00030728 The InTouch Alarm Provider’s alarm count is not correct (missing some alarms) on a redundant node after repeated failovers.

L00030849 Minor version of some objects whose files have been updated requires changing.

L00031026 If the name of an instance of an object begins with a numeric value, references to that object are not recognized in the scripting editor.

L00031387 If the name of an instance of an object begins with a numeric value and is followed by an underscore, references to that object are not recognized in the scripting editor.

L00031499 After migrating a Galaxy from Industrial Application Server 1.5 to 2.0, attempting to deploy the GR Node platform results in a "GetNodeName Failed" error message.

L00031682 Making rapid changes with an InTouch Vertical Slider, which is tied to AnalogDevice causes data updates to stop.

L00031959 InTouch is receiving out of date data from the LMX internal cache when an InTouch script is triggered from an Industrial Application Server attribute data change.

L00032244 Equations using time type variables do not work correctly if the time type variables are on the right hand side of the equation.

L00032353 Resolution of array references takes more time than expected.

L00032417 CPU usage is too high on the InTouch Node after deploying and it stays high, the AppEngine is not responding on InTouch Node and an error message is generated from the RDI component.

Back to Top

 


Detailed Descriptions for Resolved Issues

L00025941 When the user switches from an active engine to a standby state engine, memory consumption remains at 56MB and 11 threads.

Problem:
When the user switches from an active engine to a standby state engine, memory consumption remains at 56MB and 11 threads. Memory consumption should be 6MB after the user switches to a standby engine as is the case after a clean startup.

Back to Resolved Issues

L00028173 Hung AppEngine does not failover.

Problem:
If an AppEngine hangs, failover does not occur even when its Standby redundant partner is ready. Failover only occurs when an AppEngine crashes. A hung AppEngine is one that, for instance, has a script in an endless loop and has stopped executing scans. In that case, the AppEngine’s separate heartbeat thread with its redundant partner still may be functioning, in which case, the Standby AppEngine would not assume Active status.

Back to Resolved Issues

L00028459 After fifty failovers in a multiple redundant engine pair system with only one engine pair failing over every fifteen minutes, the active engine handle count increases from 500 to 2000. The system test ran for approximately 14 hrs.  Each engine had 2500 objects with eight IO per object.

Problem:
After fifty failovers in a multiple redundant engine pair system with only one engine pair failing over every fifteen minutes, the active engine handle count increases from 500 to 2000.

Back to Resolved Issues

L00028711 An object with an array attribute with an initial size of zero generates warnings in the Logger on the IDE node during configuration.

Problem:
If you import an
object into the Galaxy database that has an array attribute with an initial size of zero, warnings are generated in the Logger when you configure that object in the IDE.

Back to Resolved Issues

L00028731 The PV of an AnalogDevice (Regulator) object displays a value of NaN (Quality Good) after object is redeployed. Value recovers after about 20 minutes.

Problem:
Originally, the PV of the AnalogDevice (Regulator) object displays data from the PLC. When the object is redeployed, t
he PV in Object Viewer displays a value of NaN (Quality Good). In InTouch, the value is –1#R. A new link created in Intouch to the same attribute displays correct data, but the old link is still wrong. Also, the item in the DIObject has the correct value after the deployment. Value in the original object recovers after about 20 minutes.

Back to Resolved Issues

L00028898 The App Engine appears to leak memory when executing an application object that calls a .net component via COM interop.

Problem:
The App Engine appears to leak memory when executing an application object that calls a .net component via COM interop. Using a trace event object from the traceability project, the app engine leaks several hundred meg in less than an hour.

Back to Resolved Issues

L00028965 Export/Import of redundant pair of AppEngines may change Active status property.

Problem:
Both AppEngines in a redundant pair have a property (Redundancy.Identity) that identifies which AppEngine is currently Active in the run-time environment. When you create a redundant pair in the IDE, the value of this property is accurate (that is, the Primary AppEngine’s Redundancy.Identity value is “Primary” and the Backup Appengine’s Redundancy.Identity value is “Backup”). If you export and then import the redundant pair, the value of this property may be switched in each AppEngine. This can be observed on the Attributes page of each object’s Properties dialog box.

Back to Resolved Issues

L00029066 Errors posted in Logger during a failover: "NotificationDistributorRuntime Couldn't get platform name Unknown error from PlatformInformationClerk2".

Problem:
Errors are posted in the Logger during a failover because a synchronization message is not sent to the Standby partner when an InTouch Alarm Provider client unregisters with the Active partner.

Back to Resolved Issues

L00029082 The script validator rejects overloaded functions from an imported script library that have an "out" or "ref" modifier on a parameter. The validator only accepts a function with a double parameter when integer, float and string overloads are also present.

Problem:
The script validator rejects overloaded functions from an imported script library that have an "out" or "ref" modifier on a parameter. The validator only accepts a function with a double parameter when integer, float and string overloads are also present.

Back to Resolved Issues

L00029088 When the ForceFailoverCmd is invoked, error messages regarding ObjectSyncMgr, CheckpointFileServer, and BaseRunTimeComponentServer are logged in the Logger.

Problem:
When the ForceFailoverCmd is invoked, error messages regarding ObjectSyncMgr, CheckpointFileServer, and BaseRunTimeComponentServer are logged in the Logger. The errors are logged on the Standby AppEngine node that transitioned from Active. There is no side effect to the system and the redundant partners work properly.

Back to Resolved Issues

L00029091 An Area with AlarmMode set to "Silent" displays new alarms in the InTouch Alarm View.

Problem:
An Area with AlarmMode set to "Silent" displays new alarms in the InTouch Alarm View. This occurs mainly when the Area is put Offscan or is undeployed from the alarm client, but the alarm itself is not removed from the AppEngine.

Back to Resolved Issues

L00029094 First-time reference binding takes a while (30 seconds) after shutting down the Active of a redundant pair and a failover transition is complete.

Problem:
First-time reference binding takes a while (30 seconds) after shutting down the Primary of a redundant pair and a failover transition is complete. This behavior only occurs when a reference is bound for the first time and the object portion of the reference refers to the Primary AppEngine that is shut down.

Back to Resolved Issues

L00029129 An Area on a redundant AppEngine with AlarmMode set to "Silent" or “Disable” displays all alarms in the InTouch Alarm View after failover, and after about 24 seconds, the alarms disappear.

Problem:
An Area on a redundant AppEngine with AlarmMode set to "Silent" or “Disable” displays all alarms in the InTouch Alarm View after failover, and after about 24 seconds, the alarms disappear. This behavior also occurs if a off-engine parent Area is silenced. In this case, the rebinding of the reference to the off-engine Area will be done asynchronously and results in similar behavior (the delay would be less).

Back to Resolved Issues

L00029378 In a SCADA environment, redeployment of a non-redundant AppEngine sometimes fails (not responding).

Problem:
In a SCADA environment, r
edeployment of a non-redundant AppEngine sometimes fails (not responding).

Back to Resolved Issues

L00029461 Memory leak occurs in the Bootstrap if the wrong IP address is entered in the Platform Redundancy Message Channel IP Address.

Problem:
Memory leak occurs in the Bootstrap if the wrong IP address is entered in the Platform Redundancy Message Channel IP Address.

Back to Resolved Issues

L00029500 When the RedundantDIObject is in Disconnected state and you advise an I/O point, Quality for that attribute stays as Initializing rather than going Bad.

Problem:
When the RedundantDIObject is in Disconnected state and you advise an I/O point, Quality for that attribute stays as Initializing rather than going Bad.

Back to Resolved Issues

L00029514 Redeploying DIObject causes RedundantDIObject to no longer subscribe to its ProtocolFailureReasonCode attribute.

Problem:
After redeploying a data source DiObject, the RedundantDIObject no longer subscribes to the DiObject's ProtocolFailureReasonCode attribute.  As a consequence, the RedundantDiObject does not detect the protocol failure between the DIObject and the end device (PLC, in most cases), which in the case of a protocol failure, the Redundant DIObject will not switch to its Standby data source object. To resolve this problem, do the following: after redeploying the DIObject, redeploy the RedundantDIObject, or redeploy both the DIObject and RedundantDIObject at the same time.

Back to Resolved Issues

L00029563 After shutting down a WinPlatform and debugging subsequent Object Viewer problem on the Galaxy node, an error is displayed from the InTouch Alarm Provider: MergeAlarmList - encountered invalid message type.

Problem:
After shutting down a WinPlatform and debugging subsequent Object Viewer problem on the Galaxy node, an error is displayed from the InTouch Alarm Provider: MergeAlarmList - encountered invalid message type.

Back to Resolved Issues

L00029565 Shutting down a WinPlatform and then browsing other WinPlatforms in ObjectViewer may cause comm errors.

Problem:
When you shut down a WinPlatform with the SMC on the GR node and then select that WinPlatform in the ObjectViewer, comm errors occur (this is normal). Subsequently, browsing other WinPlatforms in the ObjectViewer also causes comm errors (this typically should not occur). A workaround to this problem is shutting down and then restarting the ObjectViewer.

Back to Resolved Issues

L00029567 Attributes AlarmOnCnt and AlarmOnCntTotal of an Area hosted by a redundant AppEngine increment after the Standby becomes Active by the amount of the actual alarms only after a graceful shutdown of the Active engine using the SMC or by powering down the computer gracefully.

Problem:
Attributes AlarmOnCnt and AlarmOnCntTotal of an Area hosted by a redundant AppEngine increment after the Standby becomes Active by the amount of the actual alarms only after a graceful shutdown of the Active engine using the SMC or by powering down the computer gracefully. This behavior does not happen if the computer is completely powered off or during failover (using the ForceFailoverCmd attribute or due to a network cable disconnect). To recover, the Active engine must be shutdown/restarted.

Back to Resolved Issues

L00029682 In a SCADA environment, trend shows gaps for an attribute that does not change value through store-forward events.

Problem:
In a SCADA environment, trend shows gaps for an attribute that does not change value through store-forward events.

Back to Resolved Issues

L00029712 Slow-changing tags or tags that do not change do not get historized if the AppEngine is stopped and restarted.

Problem:
Slow-changing tags or tags that do not change do not get historized if the AppEngine is stopped and restarted. The initial value after the AppEngine is restarted does not gets stored.

Back to Resolved Issues

L00029738 In a SCADA environment, unexpected network traffic is encountered due to Bootstrap failing to tear down unused client subscriptions.

Problem:
In a SCADA environment, unexpected network traffic is encountered due to Bootstrap failing to tear down unused client subscriptions.

Back to Resolved Issues

L00029741 In a SCADA environment, MDAS store-forward was leaking up to 4,000 handles over a 5-day period.

Problem:
In a SCADA environment, MDAS store-forward was leaking up to 4,000 handles over a 5-day period on a Backup redundant AppEngine.

Back to Resolved Issues

L00029827 A failover about ¼ second after poking a $Vstring value from InTouch to a DIObject sometimes sets attributes status to Pending.

Problem:
If a failover between redundant AppEngines occurs about ¼ second of having poked a $Vstring value from InTouch to a DIObject hosted by the Active AppEngine, the status of the $Vstring and $Writests attributes sometimes is set to and stays Pending. This problem only occurs in a very short window of time. If it does occur, do a RE-INIT IO to resolve the problem.

Back to Resolved Issues

L00029832 Standby-Ready status of a redeployed redundant AppEngine does not immediately allow a failover from its redundant partner.

Problem:
If you undeploy the Active partner of a redundant pair of AppEngines (causing a failover to its Standby) and then deploy the undeployed AppEngine, quickly initiating a failover from its currently Active partner fails. This action results in the quarantining of hosted DINetwork objects (ones that host a DAServer) and failed reads and writes. You or any scripts automating this functionality should not rely on the Standby-Ready status of the newly deployed AppEngine, but should wait one minute before initiating the failover. If this problem should occur, redeploy the quarantined DINetwork object.

Back to Resolved Issues

L00029834 Referencing an invalid item on a DIObject hosted by a redundant AppEngine causes the subscription to be rebind every second.

Problem:
Referencing an invalid item on a DIObject hosted by a redundant AppEngine causes the subscription to be rebind every second rather than every 30 seconds, which is normal for a non-redundant scenario.

Back to Resolved Issues

L00029922 Values on an InTouch display show Configuration Error for 20-30 seconds every time a display is called up.

Problem:
Values on an InTouch display show Configuration Error for 20-30 seconds every time a display is called up. There were several references to the same point on the InTouch display, and references in the Anonymous Engine cache were always pointing to the Primary AppEngine even when the Active engine was the Backup engine.

Back to Resolved Issues

L00030048 A DDESuiteLinkClient object configured to point to a SuiteLink server on a remote node fails to detect a Disconnected event when the network cable is unplugged.

Problem:
A DDESuiteLinkClient object configured to point to a SuiteLink server on a remote node fails to detect a Disconnected event when the network cable is unplugged. Using the Reconnect command does not result in the object starting to update.

Back to Resolved Issues

L00030149 A Boolean UDA is set to True if another float UDA's initial value is negative.

Problem:
A
Boolean UDA is set to True if another float UDA's initial value is negative. This does not occur if the float UDA’s initial value is positive.

Back to Resolved Issues

L00030154 After several failovers in a multiple redundant pair environment, one of the redundant pair that is not failing over disappears in Object Viewer and in the SMC.

Problem:
After several failovers in a multiple redundant pair environment, one of the redundant pair that is not failing over disappears in Object Viewer and in the SMC. This problem is related to improper status of redundant pairs.

Back to Resolved Issues

L00030206 WinPlatform AppEngine in a redundant configuration leaks memory (50 Kb per minute) on a Windows XP SP2 computer.

Problem:
WinPlatform AppEngine in a redundant configuration leaks memory (50 Kb per minute) on a Windows XP SP2 computer. This problem does not occur on a Windows 2003 Server computer.

Back to Resolved Issues

L00030278 Reapplying Patch 01 (after it has been previously run) causes the Windows installer dialog to display during the registration of modules.

Problem:
Reapplying Patch 01 (after it has been previously run) causes the Windows installer dialog to display during the registration of modules. Installation completes successfully.

Back to Resolved Issues

L00030360 Null values written due to a network Disconnect are not masked by the first value from store-forward. As a result, a gap is shown in the trend and the Query Analyzer.

Problem:
Null values written due to a network Disconnect are not masked by the first value from store-forward. As a result, a gap is shown in the trend and the Query Analyzer. Nulls should be masked by the first point from the store-forward stream.

Back to Resolved Issues

L00030370 After reassignment of an ApplicationObject from one AppEngine to another, a poke to the AppObject in Object Viewer fails and the write status is Pending. The status of the redundant AppEngine hosting the DIObject is in Not Responding state.

Problem:
After reassignment of an ApplicationObject from one AppEngine to another, a poke to the AppObject in Object Viewer fails and the write status is Pending. The status of the redundant AppEngine hosting the DIObject is in Not Responding state.

Back to Resolved Issues

L00030377 The AppEnginePrimitive3.dll and AppEnginePrimitivePackage.dll that got installed were old versions.

Problem:
The AppEnginePrimitive3.dll and AppEnginePrimitivePackage.dll that got installed were old versions.

Back to Resolved Issues

L00030407 Installing Patch 01 on IAS 2.0 does not replace InSQLManualdata.dll version '830' with the new version of '833'.

Problem:
Installing Patch 01 on IAS 2.0 does not replace InSQLManualdata.dll version '830' with the new version of '833'.

Back to Resolved Issues

L00030460 SystemArea.AlarmOnCntTotal shows Quality Uncertain although none of its sub-areas show Uncertain.

Problem:
SystemArea.AlarmOnCntTotal shows Quality Uncertain although none of its sub-areas show Uncertain.

Back to Resolved Issues

L00030475 InTouch alarm client does not receive alarms after an Area.AlarmModeCmd is enabled. The Area mode was set in the following sequence: enable to disable to silent to enable.

Problem:
InTouch alarm client does not receive alarms after an Area.AlarmModeCmd is enabled. The Area mode was set in the following sequence: enable to disable to silent to enable.

Back to Resolved Issues

L00030536 If a Galaxy version is 2.0 and the IDE connects to it, then the Galaxy needs to be patched at that time.

Problem:
If a Galaxy version is 2.0 and the IDE connects to it, then the Galaxy needs to be patched at that time.

Back to Resolved Issues

L00030547 Unacknowledged alarms (UnAck Return to Normal state) are not displayed in the InTouch Alarm Viewer if they existed before the Area mode was changed from Silent to Enabled.

Problem:
Unacknowledged alarms (UnAck Return to Normal state) are not displayed in the InTouch Alarm Viewer if they existed before the Area mode was changed from Silent to Enabled.

Back to Resolved Issues

L00030700 On AppEngine startup, if input/output extensions are enabled in an ApplicationObject but not configured, errors are logged to the Logger.

Problem:
On AppEngine startup, if input/output extensions are enabled in an ApplicationObject but not configured, errors are logged to the Logger.

Back to Resolved Issues

L00030728 The InTouch Alarm Provider’s alarm count is not correct (missing some alarms) on a redundant node after repeated failovers.

Problem:
The InTouch Alarm Provider’s alarm count is not correct (missing some alarms) on a redundant node after repeated failovers.

Back to Resolved Issues

L00030849 Minor version of some objects whose files have been updated requires changing.

Problem:
Minor version of some objects whose files have been updated requires changing.

Back to Resolved Issues

L00031026 If the name of an instance of an object begins with a numeric value, references to that object are not recognized in the scripting editor.

Problem:
If the name of an instance of an object begins with a numeric value, references to that object are not recognized in the scripting editor.

Back to Resolved Issues

L00031387 If the name of an instance of an object begins with a numeric value and is followed by an underscore, references to that object are not recognized in the scripting editor.

Problem:
If the name of an instance of an object begins with a numeric value and is followed by an underscore, references to that object are not recognized in the scripting editor.

Back to Resolved Issues

L00031499 After migrating a Galaxy from Industrial Application Server 1.5 to 2.0, attempting to deploy the GR Node platform results in a "GetNodeName Failed" error message.

Problem:
After migrating a Galaxy from Industrial Application Server 1.5 to 2.0, attempting to deploy the GR Node platform results in a "GetNodeName Failed" error message.

Back to Resolved Issues

L00031682 Making rapid changes with an InTouch Vertical Slider, which is tied to AnalogDevice causes data updates to stop.

Problem:
Making rapid changes with an InTouch Vertical Slider, which is tied to AnalogDevice causes data updates to stop. After the slider ceases to refresh, if the window is closed and re-opened, the displayed value of the slider is at zero (0). This problem occurs with both the Vertical Mouse Release Slider and the conventional Vertical Slider when the sliders are tied to an AnalogDevice. The problem does not occur if the slider is tied to a UDA.

Back to Resolved Issues

L00031959 InTouch is receiving out of date data from the LMX internal cache when an InTouch script is triggered from an Industrial Application Server attribute data change.

Problem:
InTouch is receiving out of date data from the LMX internal cache when an InTouch script is triggered from an Industrial Application Server attribute data change. A script in InTouch that is triggered from a data change on a Galaxy attribute can use old data from the LMX internal cache because, based on the triggering attribute ID, the script can execute before all of the data chagnes have been sent to the LMX internal cache.

Back to Resolved Issues

L00032244 Equations using time type variables do not work correctly if the time type variables are on the right hand side of the equation.

Problem:
Equations using time type variables do not work correctly if the time type variables are on the right hand side of the equation.

Example

MeDTime is an MXDouble
Dim pTime as Time;
pTime = "00:00:01.000";
Me.DTime  = Me.DTime + (Now() - pTime);

In Industrial Application Server 2.0, this returns a 0.

In Industrial Application Server 1.5 it returns a proper double value.

Back to Resolved Issues

L00032353 Resolution of array references takes more time than expected.

Problem:
Resolution of array references takes more time than expected. In an application that uses arrays extensively, it can take between 3 and 15 seconds to resolve an array element reference on an InTouch window. Non-array attribute references are resolved in a normal length of time.

Back to Resolved Issues

L00032417 CPU usage is too high on the InTouch Node after deploying and it stays high, the AppEngine is not responding on InTouch Node and an error message is generated from the RDI component.

Problem:
CPU usage is too high on the InTouch Node after deploying and it stays high, the AppEngine is not responding on InTouch Node and an error message is generated from the RDI component. The error message from the RDI client is "can not find corresponding transaction object.” In addition, the connection to the OPC Client fails.

Back to Resolved Issues

 

< top of document >

Release Summary

The Industrial Application Server introduces a new era in engineering productivity and scalability for industrial automation applications. It provides an infrastructure for simplifying the development, deployment, lifecycle maintenance, and administration of distributed automation applications. The Industrial Application Server provides a new tier of real-time data acquisition, alarm and event management, data manipulation services and collaborative engineering capabilities that have been designed from the ground up for use in industrial automation applications.

The Industrial Application Server was built from the ground up based on the ArchestrA industrial framework. ArchestrA is a comprehensive plant automation and information architecture designed from the outset to extend the life of legacy systems by leveraging the latest software technologies. Whether automation applications are in discrete manufacturing, process plants, remote SCADA operations, utilities, or any hybrid combination of these types of operations, ArchestrA has it covered.

New Features in Industrial Application Server 2.0 Patch 01

Multiple features and powerful functionality have been added to Industrial Application Server 2.0 Patch 01.

The main items incorporated or enhanced include:

·         High Availability

·         Connectivity

·         Performance

·         Usability

·         Scalability

 

High Availability

Migration

The process to upgrade the software and migrate the configuration database is simple and transparent to the user. It provides minimal downtime when updating current systems to the new version as it basically consists of two steps:

·         A seamless Galaxy migration

Redundancy

Two key features of the system provide built in redundancy:

·         Application execution - redundant AppEngines

·         I/O data source – RedundantDIObject

-- AppEngine Redundancy

A pair of AppEngines can be configured to provide high availability to the system. The pair consists of an Active AppEngine that executes the application and a Standby AppEngine that takes control of the application when the Active one fails.

Configuration requirements are minimal as the system automatically creates the redundant pair, and in runtime it continually synchronizes data, alarms, and history between the pair.

-- RedundantDIObjects

At the I/O data level, a RedundantDIObject can be configured to have a pair of I/O data sources in which one is Active and the other one is in Standby mode. If the Active data source fails the RedundantDIObject uses the Standby data source to communicate with devices in the field.

Improved Store and Forward functionality

Both IndustrialSQL Server 8.0 SP3 and Industrial Application Server 2.0 Patch 01 incorporate major enhancements to the performance of the store and forward capability. This improvement has an important impact on SCADA systems with limited bandwidth and intermittent networks.

 

Connectivity

Industrial Application Server as an OPC Server

Industrial Application Server 2.0 Patch 01 provides support for FactorySuite Gateway (FS Gateway). Using FS Gateway, a Galaxy becomes an OPC server for an OPC client that requires access to Galaxy data.

Additionally FS Gateway allows legacy I/O servers provide data to the Galaxy.

OPC item browsing

A key feature of this release is the ability provided by the OPCClient object to browse OPC servers. The OPC Item Browser allows users to browse the namespace of an OPC server and choose items to add to a scan group, block read group, or block write group.

Also, it is now possible to import/export the items list in the DDESuiteLinkClient object as well as in the OPCClient object.

 

Performance

Support for slow and intermittent networks

Important enhancements have been incorporated in Industrial Application Server 2.0 Patch 01 to support networks with poor performance caused by low bandwidth and intermittent availability.

-- MX protocol Microsoft Message Queue has been replaced by Sockets technology in the protocol to optimize the data transfer over the network.

-- User authentication the mechanism used to authenticate users/groups in a domain has been enhanced to allow for more robust system performance.

-- Store and forward capabilities the store and forward functionality has been optimized to improve data storage to the historian.

CPU and memory utilization

Improvements in the script evaluation mechanism have contributed to the optimization of CPU and memory utilization.

 

Usability

Full support for InTouch SmartSymbols

Industrial Application Server 2.0 Patch 01 seamlessly integrates with InTouch SmartSymbols. It allows browsing the Template Toolbox to simplify linking attributes between both applications. New instances of an existing template can be automatically created from the SmartSymbols feature, making them ready for deployment in the IDE.

Improvements to multi-user environment

Various enhancements have been incorporated into the multi-user capability to simplify concurrent configuration of a Galaxy.

Diagnostics and maintenance

Many new attributes associated with redundant AppEngines and RedundantDIObjects are available to monitor the system status and diagnose problems.

Also, more comprehensive information for maintenance purposes is available in this release. The System Management Console (SMC) provides detailed information on operations such as database restore and database migration, including initializing and completion time.

Documentation

New documents and resources have been created and the existing ones have been updated and improved to assist users defining and configuring FactorySuite A2 systems.

-- Getting Started with Industrial Application Server

Presents an overview of Industrial Application Server that walks you through the steps needed to create a simple working application for a typical plant production facility. This is available as a web-based application at www.wonderware.com.

-- FactorySuite A2 Tutorial One

This shows how to develop an Industrial Application Server-based application from scratch using an example P&ID drawing and easy to follow steps. The Tutorial is distributed on the IAS 2.0 Patch 01 Product CD.

-- IDE User guide

Online help documentation is provided with updated information on new functionality, features, and enhancements. This is available on the Wonderware Tech Support web site and on the Industrial Application Server Product CD.

-- FactorySuite A2 Deployment Guide

New and updated best practices and recommendations on configuring and implementing a FactorySuite A2 system are documented in the latest version of the Deployment Guide. This is a key resource on providing useful information to users that need to implement SCADA systems and redundant configurations. This is available on the Wonderware Technical Support web site under Industrial Application Server Documentation.

Licensing

-- Galaxy I/O count license

New I/O count license sizes are available to implement smaller and larger systems. The I/O count scale is available in the following increments: 250, 2500, 4500, 25K, 50K, 100K, 200K, 500K, and 1 Million I/O. Contact your distributor for ordering information.

-- FactorySuite development license

The FS development license has also been scaled down to support the implementation of smaller systems. For different sizes, please consult your distributor.

 

Scability

Multiple testing has been exercised on large systems to validate the robust and stable operation of Industrial Application Server 2.0 Patch 01. The main variables that have been stressed are number of I/O points, number of platforms, and number of clients in a Galaxy. Some of the configurations tested include 1 million I/O points, 400+ platforms and 400+ clients.

 

< top of document >

Industrial Application Server Documentation

The Industrial Application Server documentation set includes the following guides:

1.      IDE User’s Guide. Provides a reference for configuring and deploying Industrial Application Server applications.

2.      Object Viewer User’s Guide. This guides explains how to acquire runtime data using the Object Viewer.

3.      Platform Manager User’s Guide. This guide details how to start and stop system components.

4.      Galaxy Database Manager User’s Guide. This guide details how to backup and restore the Galaxy database.

5.      Log Viewer User’s Guide.  This guide explains how to use the Log Viewer utility to determine system diagnostics.

6.      Log Flag Editor Utility Guide. This guide details how to turn on and off certain diagnostics logging messages.

7.      Wonderware FactorySuite License Utility Guide. This guide explains how to use the License Utility to manage the license required for the running application.

8.      Wonderware FactorySuite Protocols Guide. This guide provides background information on the main protocols used between components of Wonderware products.

9.      Industrial Application Server Installation Guide. This guide provides information about installing the product.

All of these guides are provided in PDF format (except the Installation Guide) and can be printed. Viewing these user's guides requires installation of Adobe's Acrobat Reader. This utility is not included on this CD, but you can download it for free from Adobe's website at the following web address:

www.adobe.com/products/acrobat/readstep2.html

After downloading the file from Adobe, you must run the executable to install it on your PC. Follow the typical installation routine. After installation, you can either start the Acrobat Reader and open a user's guide from the File menu or double-click a user's guide on the CD in Windows Explorer. The PDF files are located in the UserDocs folder off the CD root and the Installation Guide is located on the CD root.

Also, information included in these guides is provided in online Help, which can be accessed through each utility's Help function.

< top of document >

© 2004 Invensys Systems, Inc. All Rights Reserved.