Wonderware Application Server 3.0 Service Pack 2 Readme

Last revision: 01/09/2009

About This Readme

This Readme combines information from Wonderware Application Server 3.0 Service Pack 2 (SP2) with previous Readme files included with Wonderware® Application Server 3.0 and its prior service pack and patches:

Wonderware Application Server version 3.0.100 (SP1)
Wonderware Application Server version 3.0.003 (Patch 03)
Wonderware Application Server version 3.0.002 (Patch 02)
Wonderware Application Server version 3.0.001 (Patch 01)
Wonderware Application Server version 3.0.000 (No Patch)

The information from these Readme files is in order based on when the Wonderware Application Server 3.0 versions were released.

Important!

Before installing the service pack:
- Ensure that you create good known backups of all Galaxies.
- If you are using an InTouch application with ArchestrA Symbols, run the ArchestrA Symbol Analysis and Repair Utility and ensure all issues reported by the utility are addressed.
Wonderware provided base default Galaxies are replaced during the service pack installation.
Installing Wonderware Application Server 3.0 Service Pack 2 automatically undeploys any platform that is currently deployed in the node that is being updated. (See L00085220 in the Known Issues section for special circumstances.)
If InTouch 10.0x and Application Server 3.0x are installed on the same node, they both must be upgraded to Application Server 3.0 SP2 and InTouch 10.0 SP2.
If the ArchestrA IDE connects remotely to the Galaxy Repository on another computer, apply Service Pack 2 to both nodes. A remote connection between the ArchestrA IDE and the Galaxy Repository fails if the nodes are at different versions of Wonderware Application Server.
A Galaxy Database Scrubber utility is available for download from the Wonderware Technical Support website. The utility is an off-line tool to clean up unused information in the Galaxy and reduce the overall Galaxy database size.
The Antivirus Software Issues list has been updated. Click this Antivirus Software Issues link for details.

Review the section Applying Wonderware Application Server 3.0 SP2 for full details.

This Readme explains how to apply SP2 to Wonderware Application Server 3.0 and its previous service pack and patches. This Readme lists all resolved issues in Wonderware Application Server 3.0 and the service pack and patches. It also includes descriptions of any known product issues that remain unresolved and possible interim solutions.

Use the following links to the various sections of this Readme.

Requirements to Apply Wonderware Application Server 3.0 SP2

This section describes the hardware and software requirements to install Wonderware Application Server 3.0 SP2. Use the following links for information about the original hardware and software requirements when Wonderware Application Server 3.0 was released in August 2007.

Hardware Recommendations:
Hardware requirements remain unchanged since the initial release of Wonderware Application Server 3.0.
Software Requirements:
Several service pack updates have been distributed for Windows operating systems since the initial release of Wonderware Application Server 3.0. Wonderware Application Server 3.0 SP2 also supports Windows XP Pro Service Pack 3 and Windows Vista Service Pack 1.
Important:

Wonderware Application Server 3.0 SP2 does not support .NET Framework 2.0 SP1 or .NET Framework 3.5. Wonderware Application Server 3.0 SP2 only supports the versions of .NET Framework described in the original Wonderware Application Server 3.0 Readme. Wonderware Application Server 3.0 SP2 requires Microsoft .NET Framework 2.0 at version CLR 2.0.50727.42, or .NET Framework 3.0.

< top of document >

Antivirus Software Issues

Configure the antivirus software such that the antivirus software does not process files in the following ArchestrA folders:

C:\Program Files\ArchestrA\
C:\Program Files\Common files\ArchestrA\
C:\Program Files\FactorySuite\ (may not exist in newer installations)
C:\Program Files\Wonderware\
C:\InSQL\Data\

From Application Server Platform objects:

History Store Forward directory: (if not default)

From Application Server Engine objects:

Checkpoint directory location (if not default)

<InTouch Application folder path> including:
C:\Documents and Settings\All Users\Application Data\ArchestrA\

<SMC Logger Storage file path>. The default is:
C:\Documents and Settings\All Users\Application Data\ArchestrA\LogFiles\

SQL Server database type files:

.mdf
.Ldf

< top of document >

Compatibility Requirements for Application Server 3.0 SP2

All InTouch 10.0x or Application Server 3.0x components that belong to the same Galaxy must be updated to SP2. InTouch must be at version 10.0 SP2 and Application Server at version 3.0 SP2.

< top of document >

Applying Wonderware Application Server 3.0 SP2

Wonderware Application Server 3.0 SP2 can be applied to a new system or it can upgrade the following pre-existing versions:

Current Installed Version of Wonderware Application Server	Description	Direct Update with SP2	Special Update Requirements
Wonderware Application Server version 2.0.001	Base install of Wonderware Application Server version 2.0 updated with Patch 01.	Yes*	None
Wonderware Application Server version 2.1.000	Base install of Wonderware Application Server version 2.1	Yes*	None
Wonderware Application Server version 2.1.001	Base install of Wonderware Application Server version 2.1 updated with Patch 01.	Yes*	None
Wonderware Application Server version 2.1.002	Base install of Wonderware Application Server version 2.1 updated with Patch 02.	Yes*	None
Wonderware Application Server version 3.0.000	Base install of Wonderware Application Server version 3.0	Yes	None
Wonderware Application Server version 3.0.001	Base install of Wonderware Application Server version 3.0 updated with Patch 01.	Yes	None
Wonderware Application Server version 3.0.002	Base install of Wonderware Application Server 3.0 or Wonderware Application Server 3.0.001 updated with Patch 02	Yes	None
Wonderware Application Server version 3.0.003	Base install of Wonderware Application Server 3.0, Wonderware Application Server 3.0.001, or Wonderware Application Server 3.0.002 updated with Patch 03	Yes	None
Wonderware Application Server version 3.0 SP1	Base install of Wonderware Application Server 3.0, Wonderware Application Server 3.0.001, or Wonderware Application Server 3.0.002, or Wonderware Application Server 3.0.003 updated with SP1	Yes	None

Yes* implies that the update is possible as long as the software is installed in a system with appropriate hardware and software requirements. Software update is not supported where operating system versions must be updated. If the operating system version must be updated, the existing Application Server software version must be uninstalled first and the supported version installed after the operating system is upgraded to the supported version.

Important SP2 Update Note:

You must apply a Wonderware Application Server 3.0 product license to upgrade a version of Wonderware Application Server prior to version 3.0 with the SP2 re-mastered CD.

To update Wonderware Application Server 3.0 with SP2

Install the service pack on the Application Server nodes after installing the service pack on the Galaxy Repository node. A non-updated Application Server node cannot connect to the Galaxy Repository node after the Galaxy Repository node is updated.
Where possible, exit all applications that are running. To avoid potential platform and engine shutdown issues during the service pack installation, we recommend the engines and platform be set to "off-scan" then manually shut down before to running the installer.
To install Service Pack 2:
1. Open the ArchestrA System Management Console (SMC).
2. Expand Platform Manager.
3. Log in to the Galaxy.
4. Select the Platform for which Service Pack 2 is to be installed.
5. From the Right pane, select one engine at a time. Engines hosting DIObjects should be set off-scan and shut down last.
6. Right-click the engine and set it off-scan.
7. Right-click the engine and shut it down.
8. Shut down the platform.
9. Exit the System Management Console before installing the patch.
10. After Service Pack 2 is applied, the local platform is removed. The Platform must be redeployed.
11. Redeploy the platform.
Do not deploy objects marked with software upgrades until the Galaxy nodes have been updated. To properly track which nodes have been updated, you may want to undeploy an individual platform, update the node in question, and deploy the platform again. This ensures that all Galaxy nodes are properly updated.
Platforms containing redundant engines must be updated together. To clear the software upgrade icon status on the patched Galaxy Repository, the redundant pair must be undeployed and then redeployed instead of only redeployed.
Platforms containing InTouch 10.0 and Application Server 3.0 must be updated together. The service pack for InTouch and the service pack for Application Server must be applied. Ensure the computer is restarted after applying each service pack, even if it is not requested.

To verify Wonderware Application Server 3.0 has been updated to Service Pack 2

Start the ArchestrA IDE.
The watermark in the IDE should read: IDE 3.0 SP2.
On the Help menu, click ArchestrA IDE. The ArchestrA IDE dialog box shows the Wonderware Application Server version installed on the computer.
You should see Version: 3.0.200 listed in the dialog box after SP2 is installed.

< top of document >

Migrating Applications to Wonderware Application Server 3.0 SP2

All applications created from Wonderware Application Server version 2.0 Patch 01 through Wonderware Application Server 3.0 SP1 can be migrated directly to Wonderware Application Server 3.0 SP2. Applications created with Wonderware Application Server prior to version 2.0 Patch 01 must be first converted to a version 2.0 Patch 01 application, and then migrated to Wonderware Application Server 3.0 SP2.

< top of document >

Resolved Issues - Wonderware Application Server 3.0 SP2

Wonderware Application Server version 3.0 SP2 resolves the following issues. The issues are listed by their Change Request number:

L00079295:	An active network connection must exist to the Network Access Device master location when InTouchViewApp restarts. (See SR19815415)
L00083820:	After you upgrade to SP1 from Application Server 3.0 Patch 03, you are unable to open the object editor, and the SQL Server process on the GR node is consuming the maximum working memory allocation. The SQL Server database and transaction log files are large for the Galaxy size. (See SR24513634)
L00083917:	Multiple IDE connections, as well aslong check-in and check-out times can cause aaGR to stop. In the SMC LogViewer, the CRLinker unknown error message is constantly generated. (See SR103113459)
L00084012:	When the AppEngine starts OnScan with deployed objects containing embedded ArchestrA symbols, the AppEngine shuts down and hangs in the "Shutdown failed" mode. (See SR19416250)
L00084205:	After the Galaxy is upgraded to Application Server 3.0 SP1, the error message "Unknown error 0xC0000005 (c0000005) raised" appears in the SMC LogViewer. (See SR33810549)
L00084206:	The initial value of the UDA changes to NULL when the AppServer 3.0 SP1 aaPkg file is imported. (See SR10415019)
L00084362:	Error message 'mscorlib: Exception has been thrown by the target of an invocation.' appears in the SMC LogViewer, when the InBatch Material Server COM library script functions are used in Automation Objects. (See SR23516503)
L00084500:	After 49.7 days, the OPCClient stops updating values. There are no error messages in the SMC LogViewer. (See SR24110024)
L00084897:	Customer's SAP library script and the CreateObject script both work on Application Server 2.1 P02. The scripts do not work in Application Server 3.0 P02. (See SR24513402)
L00084898:	It takes 15 to 17 seconds for a platform scan to time out even though the scan period is set to 1000 milliseconds. This occurs on a system that is on a domain that has an Active Directory, but does not have a domain controller. (See SR19713145)
L00084899:	When you create an instance of $OPCClient, it is assigned to the Area_001 objects not the default object.
L00084955:	The wrong ArchestrA symbol may be shown in a window when a managed InTouch application is not gracefully shut down and synchronized with the Galaxy Repository. After the symbol is re-opened from the checked out package, the VERL can be corrupted.
L00084957:	String values defined for UDA attributes in a UserDefined Object are lost when imported from the aaPKG file. (See SR10415019)
L00085031:	The wrong symbols are shown at run time upon deploy changes.
L00085876:	There is an inconsistent icon shown during configuration and run time of the IDE after upgrading from Application Server 3.0 version to Application Server 3.0 SP2. Specifically, the icon representing objects that are deployed (both on the Galaxy Repository node and on remote nodes) are marked as "software upgrade required" on the IDE. The same objects are shown "without software upgrade" required icon inside ObjectViewer and the SMC.

< top of document >

Known Issues - Wonderware Application Server 3.0 SP2

This section describes known issues identified in Wonderware Application Server 3.0 SP2. The issues are listed by their Change Request number:

L00084299:	The error message "Retrieve style definition(s) in XML document are invalid" appears when validating ArchestrA symbols using aaTrendControl if ActiveFactory is not installed on the system. Install ActiveFactory before validating ArchestrA symbols or importing an aaPKG using graphics containing the aaTrendControl.
L00085220:	Upgrading, then patching the Galaxy from WAS 3.0x to WAS 3.0 SP2 marks deployed objects of the Galaxy Repository as "software upgrade pending" when they are really "upgraded and undeployed." You must undeploy, and then redeploy the objects.
L00085806:	The font used for graphics in ArchestrA symbols does not render properly on the graphic editor and on the printout, if the DPI of the screen or printer is less than or greater than 96-DPI.
L00086172:	MX references should read and write values, when the application is running on a TSE client session and the application is restarted on the Console.
L00086242:	Unable to connect to the Vista server nodes only. Connection is successful to the XP and 2003 nodes.
L00086377:	Un-deploying an ABCIP DAServer object when deployed causes "An unhandled win32 exception error" error message to appear after the un-deployment is complete.
L00086625:	When upgrading nodes from Wonderware Application Server 3.0 Patch 03 to 3.0 SP2, the following warning from msiexec appears: "GetArchestrAInstallPath(): Failed to Read the Registry ArchestrA install path Key".
L00087046:	An embedded symbol is lost after swapping symbol names. VERL (Visual Element Reference List) corruption is artificially causing a circular reference.
L00087166:	When you try to export an InTouchViewApp, the following error message appears from the Microsoft Cursor Engine: "Out of memory. Not enough storage is available to complete this operation. (8007000e)" (See SR 30711041). Remove the .wvw and *.?bk files from the application folder.
L00087247:	InTouchViewApp fails to undo a checkout when there is a file-lock within the CheckOut folder. You should not attempt to check-in the InTouchViewApp. Fix the file-lock issue, and perform the "undo-checkout" again.
L00087305:	When you rename a referenced symbol while an object editor is open, the reference to the renamed symbol may be lost.
L00087310:	There is a loss of the Visual Element Array in managed applications. After running the Graphic Analyzer, only two of the three attributes were populated. Applications must be free of corruptions prior to installing Wonderware Application Server 3.0 Service Pack 2. Use the ArchestrA Analysis and Repair Utility and follow Tech Note 548 prior to installing WAS 3.0 SP2.
L00087699:	When importing an "aapkg" file, the import process is not recognizing the containment relationship of objects, and the import is not handling instances of the object being replaced regardless of their undeployed or deployed status.
L00087968:	The message "ArchestrA graphic could not be loaded. Win file contains invalid index 2143. Embedded symbol array index is out of bounds of the VERL array. Forcing the symbol reference name to Symbol:---" indicates the pointer to the VERL array is pointing to an index entry that is larger than the array itself. Remove the ArchestrA symbol from the window and re-embed the symbol.

< top of document >

Wonderware Application Server 3.0 Service Pack 1 Readme

Last revision: 08/19/2008

About This Release

This Readme combines information from Wonderware Application Server 3.0 Service Pack 1 (SP1) with previous Readme files included with Wonderware® Application Server 3.0 and its prior patches:

Wonderware Application Server version 3.0.003 (Patch 03)
Wonderware Application Server version 3.0.002 (Patch 02)
Wonderware Application Server version 3.0.001 (Patch 01)
Wonderware Application Server version 3.0.000 (No Patch)

The information from these Readme files is in order based on when the Wonderware Application Server 3.0 versions were released.

Important!

Before installing the patch, ensure good known backups of all installed Galaxies are created.

Wonderware provided base default galaxies will be replaced during the service pack installation.

Installing Wonderware Application Server 3.0 Service Pack 1 automatically undeploys a platform that is currently deployed in the node that is being updated.

In a node with both InTouch and Application Server installed, they both must be upgraded to the Service Pack (Application Server 3.0 SP1, and InTouch 10.0 SP1) level.

If the ArchestrA IDE connects remotely to the Galaxy Repository on another computer, apply Service Pack 1 to both nodes. A remote connection between the ArchestrA IDE and the Galaxy Repository fails if the nodes are at different versions of Wonderware Application Server.

Please review the section Applying SP1 to Wonderware Application Server 3.0 for full details.

This Readme explains how to apply SP1 to Wonderware Application Server 3.0 and its patches. This Readme lists all resolved issues in Wonderware Application Server 3.0 and the patches. It also includes descriptions of any known product issues that remain unresolved and possible interim solutions.

Use the following links to the various sections of this Readme.

Wonderware Application Server 3.0 SP1 Information

Requirements to Apply Wonderware Application Server 3.0 SP1

Applying SP1 to Wonderware Application Server 3.0

Migrating Applications to Wonderware Application Server 3.0 SP1

Resolved Issues - Wonderware Application Server 3.0 SP1

Known Issue - Wonderware Application Server 3.0 SP1

Wonderware Application Server 3.0 Patch 03 Information

About This Release

Before You Install Application Server 3.0, Patch 03

Installation Instructions - Application Server 3.0, Patch 03

Resolved Issues - Application Server 3.0, Patch 3

Known Issues - Application Server 3.0, Patch 3

Wonderware Application Server 3.0 Patch 02 Information

About This Release

Before You Install Application Server 3.0, Patch 02

Installation Instructions - Application Server 3.0, Patch 02

Resolved Issues - Application Server 3.0, Patch 2

Known Issues - Application Server 3.0, Patch 2

Wonderware Application Server 3.0 Patch 01 Information

About_This_Release

Before You Install Application Server 3.0, Patch 1

Installation FAQs - Application Server 3.0, Patch 1

Installation Instructions - Application Server 3.0, Patch 1

Resolved Issues - Application Server 3.0, Patch 1

Known Issues - Application Server 3.0, Patch 1

Wonderware Application Server 3.0 Information

About This Release

System Requirements

Installing Application Server

Known Issues - Application Server 3.0

Application Server Documentation Issues

Application Server Documentation

< top of document >

Requirements to Apply Wonderware Application Server 3.0 SP1

This section describes the hardware and software requirements to install Wonderware Application Server 3.0 SP1. Use the following links for information about the original hardware and software requirements when Wonderware Application Server 3.0 was released in August 2007.

Hardware Recommendations:
Hardware requirements remain unchanged since the initial release of Wonderware Application Server 3.0.
Software Requirements:
Several Windows operating systems have distributed service pack updates since the initial release of Wonderware Application Server 3.0. Wonderware Application Server 3.0 SP1 also supports Windows XP Pro Service Pack 3 and Windows Vista Service Pack 1.
Important:

Wonderware Application Server 3.0 SP1 does not support .NET Framework 2.0 SP1 nor .NET Framework 3.5. Wonderware Application Server 3.0 SP1 only supports the versions of .NET Framework described in the original Wonderware Application Server 3.0 Readme. Wonderware Application Server 3.0 SP1 requires Microsoft .NET Framework 2.0 or .NET Framework 3.0, which are both at version CLR 2.0.50727.

< top of document >

Compatibility Requirements for Application Server 3.0 SP1

If Application Server 3.0 SP1 will be installed on a computer that belongs to a Galaxy, InTouch must be updated with SP1 too. All InTouch or Application Server components that belong to the same Galaxy must be updated to SP1. InTouch must be at version 10.0 SP1 and Application Server at version 3.0 SP1.

< top of document >

Applying SP1 to Wonderware Application Server 3.0

This section explains how to apply SP1 to existing instances of Wonderware Application Server 3.0 installed at your site. SP1 is distributed on a re-mastered Wonderware Application Server 3.0 product CD.

Wonderware Application Server 3.0 Requirements to Apply SP1

The following table shows the pathways to apply SP1 to Wonderware Application Server 3.0 and earlier versions of Wonderware Application Server.

Current Installed Version of Wonderware Application Server	Description	Direct Update with SP1	Special Update Requirements
Wonderware Application Server version 2.0.001	Base install updated with Patch 01.	Yes*	None
Wonderware Application Server version 2.1.000	Base install of Wonderware Application Server version 2.1	Yes*	None
Wonderware Application Server version 2.1.001	Base install updated with Patch 01.	Yes*	None
Wonderware Application Server version 2.1.002	Base install of Wonderware Application Server version 2.1 updated with Patch 02.	Yes*	None
Wonderware Application Server version 3.0.000	Base install of Wonderware Application Server version 3.0	Yes	None
Wonderware Application Server version 3.0.001	Base install updated with Patch 01	Yes	None
Wonderware Application Server version 3.0.002	Base install of Wonderware Application Server 3.0 or Wonderware Application Server 3.0.001 updated with Patch 02	Yes	None
Wonderware Application Server version 3.0.003	Base install of Wonderware Application Server 3.0, Wonderware Application Server 3.0.001, or Wonderware Application Server 3.0.002 updated with Patch 03	Yes	None

Yes* implies that the update is possible as long as the software is installed in a system with appropriate hardware and software requirements. Software update is not supported where operating system versions must be updated. If the operating system version must be updated, the existing Application Server software version must be uninstalled first and the supported version installed after the operating system is upgraded to the supported version.

Important SP1 Update Notes:

You must apply a Wonderware Application Server 3.0 product license to upgrade a version of Wonderware Application Server prior to version 3.0 with the SP1 re-mastered CD.

To update Wonderware Application Server 3.0 with SP1

Where possible, exit all applications that are running. To avoid potential platform and engine shutdown issues during the patch installation, we recommend the engines and platform be set off-scan then manually shutdown prior to running the installer.
To install Service Pack 1:
1. Open the ArchestrA System Management Console (SMC).
2. Expand Platform Manager.
3. Login to the Galaxy.
4. Select the Platform for which Service Pack 1 is to be installed.
5. From the Right pane, select one engine at a time. Engines hosting DI objects should be set off-scan and shutdown last.
6. Right-click the engine and set it off-scan.
7. Right-click the engine and shut it down.
8. Shutdown the platform.
9. Exit the System Management Console prior to installing the patch.
10. After Service Pack 1 is applied, the local platform is removed. The Platform must be redeployed.
11. Redeploy the platform.
Do not deploy objects marked with software upgrades until the Galaxy nodes have been updated. To properly track which nodes have been updated, you may want to undeploy an individual platform, update the node in question, and deploy the platform again. This ensures that all Galaxy nodes are properly updated.
Install the service pack on the Application Server nodes after installing the service pack on the Galaxy Repository node. A non-updated Application Server node cannot connect to the Galaxy Repository node after the Galaxy Repository node is updated.
Platforms containing redundant engines must be updated together. To clear software upgrade icon status on the patched Galaxy Repository, Redundant pair needs to be Undeployed and deploy instead of redeploy.
Platforms containing InTouch 10.0 and Application Server 3.0 must be updated together. The service pack for InTouch and the service pack for Application Server must be applied. Ensure the computer is rebooted after applying each service pack, even if it is not requested.

To verify Wonderware Application Server 3.0 has been updated to version 3.0.100

Start the ArchestrA IDE.
Click Help from the menu bar.
Click ArchestrA IDE. The ArchestrA IDE dialog box shows the Wonderware Application Server version installed on the computer.
You should see Version: 3.0.100 listed in the dialog box after SP1 is installed.

< top of document >

Migrating Applications to Wonderware Application Server 3.0 SP1

All applications created from Wonderware Application Server version 2.0 Patch 01 through Wonderware Application Server 3.0.0 Patch 03 can be migrated directly to Wonderware Application Server 3.0 SP1. Applications created with Wonderware Application Server prior to version 2.0 Patch 01 must be first converted to a version 2.0 Patch 01 application, and then migrated to Wonderware Application Server 3.0 SP1.

< top of document >

Resolved Issues - Wonderware Application Server 3.0 SP1

Wonderware Application Server version 3.0 SP1 resolves the following issues. The issues are listed by their Change Request number:

L00064667:		Changing a template UDA to an "array" data type and deploying the template generates a warning message and the changes are not deployed.
L00068678:		When creating an instance of a derived template, which has been renamed, the instance does not show the correct template name.
L00069119:		Red error messages are logged into logger when ShowSymbol animation is started from a ShowSymbol dialog whose parent InTouch window is closed and WindowViewer is configured to load window from memory.
L00071046:		An InTouch tag name containing a dash " - " cannot be used in an ArchestrA graphic.
L00071055:		Using the "-1" syntax Me.Array_Name[-1] to extract data from the entire array does not work.
L00071285:		Propagating changes of a locked script from a derived template to the instances is not showing up in the deployed runtime version of the object.
L00072013:		In the AlarmViewer control, an alarm comment that is referencing an array element Me.Alarm_Array[1] does not display the text contained in the array element, but the array element name itself.
L00072210:		Changing the graphic X,Y coordinates at runtime is not affecting (recalculating) the client control docking.
L00072222:		When the FSGateway is deactivated on an Application Object Server Node, the SMC stops, the ObjectViewer locks, and platform communication is disrupted.
L00072934:		While trying to export an IntouchViewApp got the error: From Microsoft Cursor Engine. Out of memory.. Not enough storage is available to complete this operation. (8007000e) (See SR 30711041).
L00072935:		You cannot access, use, or validate more than two levels of classes in the scripting library.
L00073042:		Deployment of attribute changes to a deployed object is not sent to the run-time object instance if the value is changed back to the default.
L00073147:		When a client engine issues a Supervisory Set request and the target engine shuts down after sending a Pending status, the client engine never receives the completion status and remains in a pending state forever.
L00073245:		You must undeploy and redeploy object templates to migrate scripts from Industrial Application Server version 2.1, patch 2 to Wonderware Application Server version 3.0.
L00074908:		The PackageServerNet application times out waiting on an I/O operation to complete and the data is not saved. (See SR 19713124)
L00074932:		The Symbol Browser does not preview graphic symbols. The "not found" crossed rectangle appears. (See SR 14831934)
L00075189:		A Galaxy containing a large number of InTouchViewApp instances times-out during deployment.
L00075207:		Embedded graphics behave erratically. The selection frame and the halo in InTouch runtime are both too big.
L00075268:		Exporting all of the objects in a Galaxy and then re-importing them into a new galaxy changes the location, or anchor points of some of the graphics.
L00075456:		Template with more than 100 derived graphic objects require an extended amount of time to check in
L00075537:		An extended amount of time is required to start a managed application in WindowMaker from the ArchestrA IDE.
L00075568:		Opening the Graphics Browser is too slow.
L00075632:		Opening a managed InTouch ViewApp from the IDE and selecting "No – Will not convert the application" converts the application, resaves WIN files, and deletes WVW files.
L00075789:		Pressing the Shift + Tab keys crashes the Graphic Editor.
L00075949:		Opening an ArchestrA graphic in the IDE, or a window in WindowMaker that has an embedded ArchestrA graphic using "ShowSymbol" animation will also load the referenced symbol from the animation.
L00076518:		Clicking OK or Cancel in the ArchestrA Graphics Browser may take extended time if thumbnails need validation (hashed thumbnail).
L00077312:		In a VISTA operating system, the IDE crashes when opening the OPC Item browser.
L00077371:		In a VISTA operating system, the TagBrowser cannot be opened from the InTouchProxy object. The IDE is stalled.
L00077460:		In a French or German version of the VISTA operating system, the IDE will crash when trying to connect to the Galaxy.
L00077812:		The Alarm Viewer control does not show Application Server alarms, and the status shows 0% complete on a Vista SP1 Node. The same alarms are visible in Windows Server 2003 SP2 operating system.
L00077922:		Editing values in an object UDA array or an instance of an object are not saved. (See SR 33410279)
L00078020:		The ArchestrA IDE shows a blank Galaxy. Views and toolboxes appear empty. (See SR 14831969)
L00078480:		Microsoft Word crashes after attempting to save changes to object help. (See SR 31710839)
L00078954:		"Deploy Pending" is not marked for the InTouchViewApp on any change made to the derived templates of a UDO (User-Defined Object).
L00079077:		A circular reference is encountered when the names of symbols with embedding references are swapped.
L00079652:		Attempting to publish a large InTouch application template from the IDE fails with the following error “exception in CreateDisplayFilesForInTouchForExport=The transaction log for database tempdb is full.” (SR 103113807)
L00079951:		Some animations are lost when you export all objects from the Galaxy and reimport them in to a new galaxy.
L00080565:		Graphic element reference list is incomplete or corrupted. Failed to get Graphic element reference list. (SR 23515471)
L00081755:		IDE editor appears blank and toolboxes appear empty once the Windows\TEMP folder in the GR Node fills up with temp files created when opening managed applications. No additional IDEs can connect to the Galaxy until the Windows\TEMP folder files are deleted. (See SR12610487)
L00082823:		A total of 52 new symbols were added to the ArchestrA library. The new symbols are located in the ArchestrA Symbol Library under the toolset "Static Symbols." The new ArchestrA symbols are available only after creating a new Galaxy with Application Server version 3.0 SP1 that has been upgraded from Patch 01, Patch 02, or Patch 03. The symbols are not available for existing Galaxies.

< top of document >

Known Issue - Wonderware Application Server 3.0 SP1

This section describes known issues identified in the Wonderware Application Server 3.0 SP1. The issues are listed by their Change Request number:

L00081503:

The "Deployed objects are running..." screen appears while installing Wonderware Application Server SP1 over a Wonderware Application Server 3.0 installation. After SP1 installation completes, only the GR Node platform will show the state of previously deployed objects as deployed pending software updates, even though any previously deployed objects have been undeployed. Redeploying the platform and objects corrects the issue.

< top of document >

Wonderware Application Server 3.0, Patch 03 Readme

Last revision: 6/6/2008

About This Release

This document contains important information about Wonderware® Application Server 3.0, Patch 03. Review this document for installation instructions and a description of the issues resolved by Patch 03.

< top of document >

Before You Install Application Server 3.0, Patch 03

Close any anti-virus programs running on the computer before you update Wonderware Application Server with Patch 03.

Apply this patch only to Application Server version 3.0, Application Server 3.0 Patch 01, or Application Server 3.0 Patch 02. You can check the version number in the Control Panel. See the Add or Remove Programs section under Wonderware Application Server. The support information should list version 3.0.0, 3.0.001, or 3.0.002.

< top of document >

Installation Instructions - Application Server 3.0, Patch 03

Important!
This patch installs files related to the ArchestrA® Integrated Development Environment (IDE) editor. It is imperative that the Galaxy Repository (GR) node as well as every node that has the ArchestrA IDE or InTouch® installed must have Patch 03 applied. InTouch 10.0 Patch 03 and Application Server 3.0 Patch03 must be installed on nodes where both software versions coexist.

Before installing the patch, ensure good known backups of all installed Galaxies are created. To create a backup of your Galaxy, access the Galaxy Database Manager in the SMC – ArchestrA System Management Console. Expand the Galaxy Database Manager and select the Galaxy. On the Action menu, click Backup. Follow the prompts to complete the backup operation for each Galaxy.
If the ArchestrA IDE connects remotely to the Galaxy Repository on another computer, apply Patch 03 to both nodes. A remote connection between the ArchestrA IDE and the Galaxy Repository fails if the nodes are at different versions of Wonderware Application Server.

An ArchestrA IDE node still at version 3.0, 3.0 Patch 01, or 3.0 Patch 02 cannot connect to a remote GR node updated with Patch 03.
An ArchestrA IDE node updated with Patch 03 cannot connect to a remote GR node still at version 3.0, 3.0 Patch 01, or 3.0 Patch 02.

Note: Even though Patch 03 is not required for run-time only systems (systems with only the ArchestrA Bootstrap installed), we recommended that you update all nodes to the same software version.
Prior to running the patch installer, exit from all applications including the ArchestrA IDE, InTouch WindowMaker, and InTouch WindowViewer.
Prior to applying Patch 03 on the GR node, ensure any active remote IDE sessions are disconnected. Patch 03 requires ArchestrA-related processes be shut down and may require a reboot.
You apply Patch 03 with the same installation steps used to install Patch 01. Refer to Installation Instructions - Application Server 3.0, Patch 01.

< top of document >

Resolved Issues - Application Server 3.0, Patch 03

Wonderware Application Server 3.0, Patch 03 resolves the following issue:

L00078228:

When an InTouchViewApp instance having an unbound ArchestrA symbol is deployed to a client computer, the "Not Found" symbol should be shown as a placeholder for the unbound symbol in the run-time application. This is not happening. Instead, some other symbol is shown in the place of the "Not Found" symbol.

If you look at the symbol in the source InTouchViewApp template on the Galaxy Repository node, you see the "Not Found" symbol.

< top of document >

Known Issues - Application Server 3.0, Patch 03

Wonderware Application Server 3.0, Patch 03 has the following known issue:

L00077893:

You have two symbols embedded in an object. For example, "Symbol_1" and "Symbol_2". You "swap" the names of the symbols. For example, you rename "Symbol_1" to "Symbol_1Rename", rename "Symbol_2" to "Symbol_1", and then rename "Symbol_1Rename" to "Symbol_2". In WindowMaker and in WindowViewer, the symbol you renamed first (the original Symbol_1) is incorrectly shown for both symbols.

This problem does not occur if you save between each renaming.

For more information about this issue, see "Duplicate Symbols in Managed Applications After Swapping Symbol Names" in the ArchestrA Symbol Analysis and Repair Utility Guide.

L00078848:

Embedded ArchestrA symbols that appear in an InTouch managed application window can be swapped if the symbols are deleted from WindowMaker without undeploying the application afterwards. For example, symbols S1 and S2 can be embedded into a derived InTouchViewApp template from WindowMaker. After the changes are saved and WindowMaker is closed, derive an instance of the template and deploy it. Delete the two symbols and then save and close WindowMaker. Open the window again from WindowMaker and embed the two symbols to the window again, but in the reverse order: S2 is added before S1. Save your changes and close WindowMaker. Deploy the instance of the InTouchViewApp derived template and run the managed application in WindowViewer. The two symbols are reversed in the InTouch window.

This issue results from the VERL being unable to maintain the correct list item order if symbols are changed while the instance is deployed. If you undeploy the instance after deleting the symbols from WindowMaker and then redeploy the instance, the symbols appear correctly in the managed application window.

< top of document >

Wonderware Application Server 3.0, 3.0 Patch 01, and 3.0 Patch 02 Readme Information

Version 3.0 Patch 02 Information

About This Release

Before You Install Application Server 3.0, Patch 02

Installation Instructions - Application Server 3.0, Patch 02

Resolved Issues - Application Server 3.0, Patch 02

Known Issues - Application Server 3.0, Patch 02

Version 3.0 Patch 01 Information

About This Release

Before You Install Application Server 3.0, Patch 01

Installation FAQs - Application Server 3.0, Patch 01

Installation Instructions - Application Server 3.0, Patch 01

Resolved Issues - Application Server 3.0, Patch 01

Known Issues - Application Server 3.0, Patch 01

Version 3.0 Information

About This Release

System Requirements

Installing Application Server

Known Issues – Application Server 3.0

Application Server Documentation

< top of document >

Wonderware Application Server 3.0, Patch 02 Readme

Last revision: 04/19/2008

About This Release

This document contains important information about Wonderware Application Server 3.0, Patch 02. Review this document for installation instructions and a description of the issue resolved by Patch 02.

< top of document >

Before You Install Application Server 3.0, Patch 02

Close any anti-virus programs running on the computer before you update Wonderware Application Server with Patch 02.

Apply this patch only to Application Server version 3.0, or Application Server 3.0 Patch 01. You can check the version number in the Control Panel. See the Add or Remove Programs section under Wonderware Application Server. The support information should list version 3.0.0 or 3.0.001.

< top of document >

Installation Instructions - Application Server 3.0, Patch 02

Important!
This patch installs files related to the ArchestrA Integrated Development Environment (IDE) editor. It is imperative that the GR node as well as every node that has the ArchestrA IDE installed must have Patch 02 applied.

Before installing the patch, ensure good known backups of all installed Galaxies are created. To create a backup of your Galaxy, access the Galaxy Database Manager in the SMC – ArchestrA System Management Console. Expand the Galaxy Database Manager and select the Galaxy. From the Action Menu, select Backup. Follow the prompts to complete the backup operation for each Galaxy.
If the ArchestrA IDE connects remotely to the Galaxy Repository on another computer, apply Patch 02 to both nodes. A remote connection between the ArchestrA IDE and the Galaxy Repository fails if the nodes are at different versions of Wonderware Application Server.
- An ArchestrA IDE node still at version 3.0 or 3.0 Patch 01 cannot connect to a remote GR node updated with Patch 02.
- An ArchestrA IDE node updated with Patch 02 cannot connect to a remote GR node still at version 3.0 or 3.0 Patch 01.
Note: Patch 02 is not required for run-time only systems (systems with only ArchestrA Bootstrap feature installed).
Prior to running the patch installer, exit from all applications including the ArchestrA IDE, InTouch WindowMaker, and InTouch WindowViewer.
Prior to applying Patch 02 on the GR node, ensure any active remote IDE sessions are disconnected. Patch 02 requires ArchestrA-related processes be shut down and may require a reboot.
You apply Patch 02 with the same installation steps used to install Patch 01. Refer to Installation Instructions - Application Server 3.0, Patch 01.

< top of document >

Resolved Issues - Application Server 3.0, Patch 02

Wonderware Application Server 3.0, Patch 02 resolves the following issue:

L00076163

Graphic elements within an ArchestrA Graphic symbol can have duplicate element IDs if the element is part of a group that is copied or duplicated and later ungrouped. When graphic elements have duplicate IDs, their substituted strings or custom property overrides can be potentially lost.

Tech Alert 107 "Potential Safety Issue When Using ArchestrA Symbols Embedded in InTouch® 10.0 Applications" provides a detailed explanation of the problem. This Tech Alert also describes how to use a pair of utilities to identify and repair ArchestrA symbols with duplicate element IDs in InTouch applications and your Application Server Galaxies.

The AAGraphics Application Scanner utility is available from the Wonderware Technical Support website. You can use this utility to determine if your managed or published InTouch applications on a run-time node have ArchestrA symbols embedded in windows. Tech Alert 107 "Potential Safety Issue When Using ArchestrA Symbols Embedded in InTouch® 10.0 Applications" contains a link to the tool.
The Duplicate ID Detection and Repair utility is available from the Wonderware Technical Support website and is also distributed on the Patch 02 CD. You use this utility to analyze your Galaxies to determine if they contain any ArchestrA symbols with duplicate element IDs. This utility can also repair symbols that contain duplicate element IDs. The Wonderware Technical Support website and the Patch 02 CD include a short guide titled ArchestrA Symbol Analysis and Repair Utility Guide that explains how to use this utility.
After repairing symbols with the Duplicate ID Detection and Repair utility, opening an ArchestrA symbol from the ArchestrA IDE may set an object to warning state. If the ArchestrA Graphic Editor encounters a graphic element that contains duplicate IDs with custom property overrides or string substitutions, it surrounds each override with double brackets [[ ]]. After the object is saved, it will be set to a warning state.

Important Considerations of the Duplicate ID Detection and Repair utility

Analyzing a large Galaxy for ArchestrA symbols containing duplicate element IDs may be a lengthy and resource intensive process. The ArchestrA Symbol Analysis and Repair Utility Guide lists a set of tasks you must complete to minimize the time required to analyze your Galaxy and repair symbols.
After you complete the preliminary tasks listed in the ArchestrA Symbol Analysis and Repair Utility Guide, disable security for the Galaxies you intend to analyze and repair with the Duplicate ID Detection and Repair utility.
It is highly recommended that you update with Patch 02 before using the Duplicate ID Detection and Repair utility. You must apply Patch 02 to the Galaxy Repository before using Fixup Graphics feature of the Duplicate ID Detection and Repair utility. Although you can analyze your Galaxies with Patch 01 applied, Patch 02 enables the repair portion of the utility to operate. Without Patch 02 applied, the utility cannot repair duplicate element IDs in ArchestrA symbols.

< top of document >

Known Issues - Application Server 3.0, Patch 02

L00076412:		The ArchestrA IDE Import utility does not validate or find the duplicate element ID issue when symbols are a part of importing AO Instance. After importing the contents of an aaPKG file, the imported templates and instances must be manually validated from the IDE.
L00076514:		Running the Duplicate ID Detection and Repair utility against the Application Server Reactor_Demo application shows there are 69 changed symbols although there are no symbols with duplicate IDs, substituted strings, nor symbols with custom property overrides in the application. The LastUsedID number is an internal symbol property assigned a usage count. The count increments with symbol usage. As part of the solution for the duplicate element ID issue, Patch 02 increments the LastUsedID count to prevent duplicate element IDs from assigned to symbols. The utility is reporting the number of symbols modified because of a change to the LastUsedID count.

L00076602:		The Application Server version 3.0 Patch 01 re-mastered CD does not autoboot to install or remove Application Server installable options after Patch 02 is applied. Insert the Application Server version 3.0 Patch 01 re-mastered CD into the CD drive. Then, you must manually modify installed Application Server features using the Windows Control Panel Add or Remove Programs utility. Select Wonderware Application Server from the list, and then click Change to add or remove features.
L00076690:		The analysis process of the Duplicate ID Detection and Repair utility does not find all symbols containing duplicate element IDs in Galaxies still at Application Server version 3.0. It is highly recommended that you update with Patch 02 before using the Duplicate ID Detection and Repair utility. You must apply Patch 02 to the Galaxy Repository before using Fixup Graphics feature of the Duplicate ID Detection and Repair utility. Although you can analyze your Galaxies with Patch 01 applied, Patch 02 enables the repair portion of the utility to operate. Without Patch 02 applied, the utility cannot repair duplicate element IDs in ArchestrA symbols.
L00076692:		The Duplicate ID Detection and Repair utility does not prompt the user for credentials if OS security is active. Disable security for all Galaxies that you intend to analyze and repair with the Duplicate ID Detection and Repair utility. The ArchestrA Symbol Analysis and Repair Utility Guide includes a section that describes the tasks you must complete before using the utility. Refer to that section for instructions to disable OS security.

< top of document >

Wonderware Application Server 3.0, Patch 01 Readme

Last revision: 12/12/2007

Important!
Read the following sections before proceeding with the Application Server 3.0, Patch 01 Installation!

About This Release

This document contains important information about Wonderware Application Server 3.0, Patch 01. Review this document for resolved and known issues.

Application Server 3.0, Patch 01 primarily targets Factelligence support features. In addition, Patch 01 resolves field reported issues and other software defects including a potential safety issue with the read-only run-time licenses. Additional details are included in the resolved issues and in Tech Alerts 100 and 101 posted in the Technical Support website.

Before You Install Application Server 3.0, Patch 01

We recommended that you disable antivirus software before you install the patch.

Apply the patch to Application Server version 3.0.0. You can check the version number in the Control Panel. See the Add or Remove Programs section under Wonderware Application Server.

The patch install follows a similar behavior to that supported in Application Server 3.0.

The Galaxy platforms can remain deployed during the patch installation. For patch 01, it is recommended that you manually shutdown the engines and platform in the node where the patch will be applied. Please see details in the installation instructions.

Nodes can be upgraded one at a time. An exception to this is for nodes that have the Application Server installed. You must upgrade these nodes to allow the Application Server to connect to the Galaxy Repository node. An un-patched Application Server node cannot connect to the Galaxy Repository node after the Galaxy Repository node is patched. The message "IDE cannot connect to remote GR node <nodename> because it is an older version 2860 than this IDE version supports" is shown when an un-patched IDE node attempts to connect to the GR node.

< top of document >

Installation FAQs - Application Server 3.0, Patch 01

Does the patch require a restart of the node? – The node where the patch is installed may require a restart if a platform is deployed on it.

Does the patch remove the deployed platform? – No, the deployed platform remains unchanged. It must eventually be redeployed to update the software version changes marked in the Galaxy Repository node.

Does software upgrades require redeploy? – Eventually. A deployed platform does not automatically undeploy when the patch is installed. After the node restarts, it operates normally. You must eventually redeploy the platform to update the software version changes marked in the Galaxy Repository node.

Can I deploy objects to an unpatched node? – Yes, you can deploy objects to an unpatched node, but we do not recommended it. To properly track which nodes have been patched, you may want to undeploy an individual platform, patch the node in question, and deploy the platform again. This ensures that all Galaxy nodes are properly patched.

Does the patch install require the original Application Server 3.0 CD? – If you have multiple products installed, the patch install may prompt you to insert the original Application Server 3.0 CD.

What services or processes are stopped during the patch install process? – aabootstrap.exe, aalogger.exe, aaengine.exe, and aagr.exe

Is the platform set off-scan or stopped during the installation of the patch? – Platform and Engines (AppEngine, View Engine) are stopped without first being set off-scan. For patch 01, we recommend the engines and platform be set off-scan then manually shutdown prior to installation.

If the patch installation fails, does it roll all install changes back? – Yes

Can the patch be uninstalled after it has been installed? – No, it requires full uninstall of the software using the Add or Remove programs in Control Panel.

< top of document >

Installation Instructions - Application Server 3.0, Patch 01

Before installing the patch ensure a good known backup of the Galaxy is created. To create a backup of your Galaxy, access the Galaxy Database Manager in the SMC – ArchestrA System Management Console. Expand the Galaxy Database Manager and select the Galaxy. From the Action Menu item select Backup, or right-click to select the Backup option.

Where possible, exit all applications that are running.

Install the patch in the Galaxy Repository node first. It is important to follow, this step as the objects in the Galaxy will be marked as requiring software upgrade. The Application Server help contains details on the icon states in the section Instance Icon States.

Do not deploy objects marked with software upgrades until the Galaxy nodes have been patched. You can deploy objects to an unpatched node, but is not recommended. To properly track which nodes have been patched, the user may want to undeploy an individual platform, patch the node in question, and deploy the platform again. This will ensure all Galaxy nodes are properly patched.

Install the patch in the Application Server nodes after installing the patch in the Galaxy Repository node. An un-patched Application Server node will not be able to connect to the Galaxy Repository node once the Galaxy Repository node is patched. The message "IDE cannot connect to remote GR node <nodename> because it is an older version 2860 than this IDE version supports" will be displayed when an attempt to connect to the GR node from an un-patched Application Server is attempted.

Platforms containing redundant engines must be patched together. To clear software upgrade icon status on the patched Galaxy Repository, Redundant pair needs to be Undeployed and deploy instead of redeploy.

To install the patch

Where possible, exit all applications that are running. To avoid potential platform and engine shutdown issues during the patch installation, we recommend the engines and platform be set off-scan then manually shutdown prior to running the patch installer.
To install patch 01:
1. Open the ArchestrA System Management Console (SMC).
2. Expand Platform Manager.
3. Login to the Galaxy.
4. Select the Platform for which patch 01 is to installed.
5. From the Right pane, select one engine at a time. Engines hosting DI objects should be set off-scan and shutdown last.
6. Right click the engine and set it off-scan.
7. Right-click the engine and shut it down.
8. Shutdown the platform.
9. Exit the System Management Console prior to installing the patch.
10. After patch 01 is applied and the system is rebooted (if required) start the platform again. If you will be redeploying the platform at this point, then start the platform Off-Scan.
11. If you want to synchronize the Application Server with the runtime environment this will be the best time. The objects in the Application Server are marked for software upgrade and require redeploy.
12. Redeploy the platform.
Do not deploy objects marked with software upgrades until the Galaxy nodes have been patched. You can deploy objects to an unpatched node, but we do not recommended it. To properly track which nodes have been patched, you may want to undeploy an individual platform, patch the node in question, and deploy the platform again. This ensures that all Galaxy nodes are properly patched.
Install the patch on the Application Server nodes after installing the patch on the Galaxy Repository node. An un-patched Application Server node cannot connect to the Galaxy Repository node after the Galaxy Repository node is patched. The message "IDE cannot connect to remote GR node <nodename> because it is an older version 2860 than this IDE version supports" is shown when an un-patched IDE node attempts to connect to the Galaxy Repository node.
Platforms containing redundant engines must be patched together. To clear software upgrade icon status on the patched Galaxy Repository, Redundant pair needs to be Undeployed and deploy instead of redeploy.
Platforms containing InTouch 10.0 and Application Server 3.0 must be patched together. The patch for InTouch and the patch for Application Server must be applied. Ensure the computer is rebooted after applying each patch, even if it is not requested.

< top of document >

Resolved Issues - Application Server 3.0, Patch 01

This release of Wonderware Application Server 3.0, Patch 01 resolves the following issues:

L00064166 When associating a UDA array to another array in a script of "timetype," the message “cannot convert (…)" displays.

L00065948 When the I/O change rate is ramped 10 100%, "ScanGroupRuntime2 Access Denied" errors are posted to the logger on two nodes.

L00066292 Working on a remote application server, the check in dialog box is delayed by 40 seconds when creating a new ViewApp, Creating one Window, and adding one ArchestraA Symbol from the Symbol Library.

L00066603 An embedded Graphic toolbox symbol using a relative reference Show-Symbol animation fails to find the symbol during run time.

L00066609 A virtual memory leak occurs in aaGR after repeated Deploy/UnDeploy operations of the attached package.

L00066733 The Analog Field Attribute Limit "HiLimit" is constrained by the "HIHI Limit" setting.

L00066809 Errors occur when propagating a FieldAttribute if its description is locked and a script has a reference to this attribute.

L00067039 AppEngine memory leak increases linearly by 2Mb/hour over 2.5 day testing.

L00067203 When you start the Galaxy browser from the Object editor, the Relative Reference option is unavailable.

L00067305 The same set of ArchestrA attribute references in two different windows (overlay and popup) require different times to resolve and sometimes the reference binds after a 10 second delay in one of the windows.

L00067426 When two asynchronous scripts are created on a UDObject and they try to read a UDA value from the hosting platform, only one script retrieves the value in a single scan.

L00067597 Deleting a step which has a “While True Only” step condition and a trigger pointing to an alias which is locked in the parent template, causes an unhandled exception.

L00067688 When importing "aapkg" to a Galaxy using overwrite and skip options creates objects with _1 in the object name.

L00067949 When client event scripts ignore the specified timeout, the View will hang.

L00068044 When browsing ArchestrA graphic symbols (for embedding), the Galaxy browser crashes.

L00068095 When undeploying the Galaxy Repository, "WaitForMultipleObjects" errors are logged. The Galaxy Repository platform should be stopped before undeploying.

L00068120 In an OS group, User profiles are not created during login from the SMC and the OV when the previously created OS user "details" are deleted from the Security editor before login. The Application Server is working properly in this scenario.

L00068123 When stopping and restarting the Application Server, the last value set is lost.

L00068194 When your Galaxy has a large number of templates, scrolling vertically in the template toolbox is very slow.

L00068320 When you configure a custom property or UDA for the title, the title is not shown in the pop-up show symbol window.

L00068373 When a new symbol is added to the parent template of an instance whose symbols are embedded in ITVA, a template marks the deployed instance of ITVA as "pending changes."

L00068387 When creating symbols using the Graphics Toolbox editor, and the symbols are embedded in a nested object instance, the relative reference is broken, and the symbol is shown as “Not Found”.

L00068391 Exporting the selected symbol also exports an instance if the instance has the same name.

L00068401 The Quality and Status overrides will not display after checking the “Enable Quality and Status Display” checkbox unless a configuration change is made.

L00068437 The Galaxy and Attribute Browsers do not retain the last selection of view style selected by the user.

L00068448 The Application Server crashes when rotating the H/V Line with another primitive.

L00068497 The line and H/V line's RelativeOrigin property changes by manual input and cannot be saved.

L00068597 When the hierarchical relationship/myplatform relationship is broken, the object which refers to the relationship remains in "good status."

L00068686 When a block write is performed on a Redundant Device Integration Object (RDIObject) using InTouch, the values of the attributes on which Block Write are performed return a value of zero and not the poked value.

L00068701 Checkin of a checked out and deployed ITVA instance which is in pending changes status, removes the pending change status of the instance.

L00068711 In some situations, the Duplicate function will create the wrong embedded symbol.

L00068742 User information is not created or updated in the Galaxy Repository (and other remote nodes) after disconnecting and reconnecting the Galaxy Repository even though logins are successful on the remote node.

L00068765 The symbol reference in the ShowSymbol animation changes when an element with the animation is copied and pasted across symbols and the destination symbol has at least one embedded symbol.

L00068862 Sometimes event scripts associated with .Net Controls used in ArchestrA graphics are lost.

L00068975 A subscription from an InTouch window to a dynamic Device Integration (DI) attribute returns bad configuration quality data for several seconds when another InTouch window has a subscription to the same DI attribute, using a different subitem, is reopened.

L00069399 When using the GRAccess utility, an "Unknown error 0xC0000005 (c0000005) raised" message is generated on the SMC logger.

L00069506 "Deploy change" doesn't deploy changes in a locked script defined in an ArcestrA template.

L00069822 Creating a new galaxy crashes after installing Microsoft Office 2007. This occurs after a reboot of the system.

L00069828 Using a place holder reference in a custom property of an ArchestrA symbol will generate warnings in the instance of an object, after the reference in the object template is substituted with a valid reference.

L00069928 When an object is imported, the relative anchor point moves.

L00070012 The Client Control container does not set the DesignMode property during configuration or runtime.

L00070013 The BeginInit and EndInit events are not being fired by the container during the initialization sequence of a .NET Client Control.

L00070014 .NET Client Controls are unable to find other controls, in the same symbol or window.

L00070016 Docking client controls within an ArchestrA graphic symbol causes the client area to be malformed.

L00070017 Some dependent DLL's (.NET Assemblies) are not included when deploying an InTouch application containing an ArchestrA Symbol with a .NET Client Control.

L00070018 Serialization issues are related to how/when the container sets Client Control properties at design and runtime.

L00070045 You are "Unable to access "current user"" information from within a .NET Client Control in an ArchestrA Symbol.

L00070431 Client controls with child controls are not drawn correctly at design time. The z-order of the child control is reversed.

L00070626 An attempt to import a UDObject created with Application Server 2.1 crashes Application Server 3.0. The error is "Connection to the Galaxy Repository has been lost." The Application Server and InTouch shutdown.

L00070764 When a client control tries to write data to an InTouch Tag, error messages are written to the System management Console logger.

L00070772 Error messages are sent to the System Management Console logger when there is a Failure to close Window Maker in "OnIDEClosing." The Object reference not set to an instance of an object.

L00070778 When calling a library function that uses a "ParamArray" parameter type, omitting the optional ParamArray parameter works in Application Server 2.1; however, it causes a validation error in Application Server 3.0

L00070909 When client control properties write to InTouch Tags (through CAL, InTouch), they do not update InTouch Tags.

L00071056 Using a place holder reference in a custom property of an ArchestrA symbol generates warnings in the instance of an object, after the reference in the object template is substituted with a valid reference.

L00071241 Cascade check-in causes the WWFsObject.dll to generate error messages.

L00071492 In some .NET script, attributes are passed as a reference instead of a value.

L00071749 In show symbol animation if upper case letters are used to reference the symbol, the show symbol animation is unable to locate the symbol. An error message displays "Symbol not found."

L00071795 When you click on the shape of a userdefined instance, the message "symbol not found" appears. Using relative referencing, symbol A1 configured with show symbol animation points to the same userdefined instance of symbol A2 in a deployed application.

L00071901 Licenses "InTouch Remote Tag Read-only" and "InTouch for Service Pack Read-only w/Trend/Analysis" allow Archestra Graphics to write data back to the Galaxy.

< top of document >

Known Issues - Application Server 3.0, Patch 01

L00071881 Selecting an alternate symbol retains the override text of an embedded symbol.

L00072421 When using the silent install for Application Server 3.0, Patch 01 on a Galaxy Repository node, the silent install fails to launch the Galaxy Patcher routine before reboot.

L00072430 If you have an application with ArchestrA Graphics running on multiple Terminal Server sessions on the same node and connected to the same Terminal Server, the data associated with the graphics is not consistent for all Terminal Server sessions.

L00072513 WWCdi errors appearing in the System Management Console logger are incorrectly reported. The Galaxy Repository database is not corrupted.

L00072521 Following the patch of Application Server 3.0 and InTouch 10, the redeployment of the Galaxy does not complete when there is no reboot following the InTouch 10 patch.

< top of document >

Wonderware Application Server 3.0 Readme

Last revision: 08/20/2007

This document contains information about Wonderware® Application Server version 3.0. Review this document for descriptions of new features, installation requirements, and any known issues with version 3.0.

About This Release

Application Server 3.0 includes the following enhancements and new features.

Updated IDE

Improved organization tools in Template toolbox, including sub-toolsets
Views that you can auto-hide and pin
Floating and dockable views

ArchestrA Symbol Editor

The ArchestrA Symbol Editor is available from within the IDE. You can create graphic symbols that you can use within your InTouch applications. The Symbol Editor:

Includes all features and functions of InTouch WindowMaker.
Includes drawing elements not available in WindowMaker, such as curves, closed curves, arcs, pies, chords, text box, status indicators, and Windows Controls.
Includes element properties not available in WindowMaker, such as colors, transparency, rotation, lock, and fill.
Supports scripting.
Supports custom properties.

Deploy Improvements

For a single user, multiple objects can be deployed to two or more platforms simultaneously.
Multiple threads are used for deployment, thus increasing performance.
All objects that are being undeployed from an engine are taken off-scan first, freeing up time for the undeploy.

Check-in Improvements

Template changes to selected elements are optimized for:

Scripts (locked)
UDAs (locked)
Visual elements (graphics)

Script Improvements

Data change scripts can be triggered by either value or quality changes. If you select quality, data change will include both value and quality changes. The default data change will be a value change trigger.
Instead of always firing on object startup, a data change script only triggers if the expression changed since the last run before the object shutdown.

Incremental Upgrades

Deployed Platforms can be left running during a Galaxy Repository or IDE node upgrade.
Run-time Platforms can be a mix of old and new versions.

Read-Write Performance Improvements

Improved speed of reads and writes to the field, especially total turnaround time of a write from the InTouch HMI.
New functionality where external input/output between engines and to/from the field is processed during the engine idle phase.
New ReadWrite Interrupts functionality where external input/output between engines and to/from field can optionally be processed within the engine's execution phase. Two options exist, Standard and Full modes.
In standard mode:
- DIObjects send writes to the field (DAServers or I/O Servers) multiple times within a scan, as objects are executing, rather than waiting until the idle period. This allows writes to the field to occur more quickly, allowing for faster turn-around and confirmation.
- Updates are published to visualization nodes (HMI) multiple times within a scan, as objects are executing and changing, instead of just during the idle period after all objects execute.
In full mode includes the functionality of standard mode, plus:
- DIObjects get updates from the field (DAServers or I/O Servers) multiple times within a scan, as objects are executing, rather than waiting until the idle period.
- ApplicationObjects receive write requests that come in during the middle of the execute phase, and process them if the object has not already executed within this phase.
- ApplicationObjects receive subscription updates from other engines that arrive during the middle of the execute phase, if the object has not already executed within this phase.
- Changes to ApplicationObjects that occur within middle of execution phase are published to objects that reside on other engines without waiting until end of a scan.
- Writes by ApplicationObjects that occur within middle of execution phase are sent to all objects on other engines without waiting until end of a scan.

Redundant DIObject Improvement

A configurable ping item attribute is now available to detect connection status of inactive DIObject. This ensures the true status of the physical link to the field.

Redundancy Improvements

Upon a switch from active to standby, the AppEngine process can be restarted automatically. This frees all memory and other resources.

Device Integration Improvements

DIObjects are supported in load sharing environment. This allows two DI network objects of same type (for example, ABTCP) to run on same node.
In a redundancy scenario, references to an off-engine DIObject’s dynamic attributes are not removed. The dynamic attributes remain in the DIObject while the failover is occurring, or until a timeout occurs.
During shutdown, failover, or undeploy of DIObjects:
- Item removal for scan groups is optimized in blocks.
- All objects are shutdown in reverse of execution order, independent of whether DIObjects are involved or not. An exception is for Areas. They are shutdown after their objects.

Galaxy Backup

You can use an existing Galaxy as the base for a new Galaxy when created with the IDE.

Toolkits

Enhancements have been added to the GRAccess Toolkit, such as the ability to browse and configure security.
A new MxAccess Toolkit allows you to create a program that:
- Connects to an ArchestrA Galaxy.
- Subscribes to one or more attributes and receives data updates from these attributes.
- Writes new values to these attributes, subject to user authentication.

< top of document >

System Requirements

This section describes the recommended hardware and software requirements to install Application Server 3.0.

Recommended Hardware Requirements

Software Requirements

Recommended Hardware Requirements

The following list shows the recommended hardware requirements to install Application Server version 3.0.

Galaxy Repository Platform:

Dual core PC with 2 gigahertz (GHz) or faster processor clock speed, or single core PC with 3 gigahertz (GHz) or faster processor clock speed
Dual core processor recommended for optimal performance
2 gigabytes (GB) or more of RAM. (1 GB minimum supported; may limit performance of some features) The Galaxy Repository locks the SQL Server maximum memory usage to 65% of the physical memory.

Non-Galaxy Repository Platforms (IDE or Runtime):

PC with 2 gigahertz (GHz) or faster processor clock speed
1 gigabyte (GB) or more of RAM

All Systems (IDE, GR, Runtime):

30 gigabytes (GB) of available hard disk space
Super VGA (1024 x 768) or higher resolution video adapter and monitor
CD-ROM or DVD drive
Keyboard
Mouse or compatible pointing device

The Windows Vista operating system imposes hardware requirements that may exceed the minimum requirements for Application Server version 3.0. If you intend to run Application Server 3.0 with Windows Vista, see the following Microsoft web site for hardware requirements:

www.microsoft.com/windows/products/windowsvista/editions/systemrequirements.mspx

Software Requirements

This section describes the operating system and other software requirements to install Application Server version 3.0.

Operating Systems

The following table lists the supported operating systems that can be installed on computers running server, client, and run-time components.

Operating Systems	Application Server Components
Operating Systems	ArchestrA IDE	ArchestrA Run Time	Galaxy Repository
Windows Vista Business (See Vista Restrictions)	●	●	●
Windows Vista Enterprise (See Vista Restrictions)	●	●	●
Windows Vista Ultimate (See Vista Restrictions)	●	●	●
Windows Server 2003 Standard Edition SP2	●	●	●
Windows Server 2003 Enterprise Edition SP2	●	●	●
Windows Server 2003 Standard Edition R2 SP2	●	●	●
Windows Server 2003 Enterprise Edition R2 SP2	●	●	●
Windows XP Professional SP2	●	●	●
Windows XP Tablet 2005		●

Notes:

Windows 2000 Professional, Windows 2000 Server, and Windows 2000 Advanced Server are not supported operating systems for Application Server version 3.0. If you attempt to install or upgrade Application Server on a computer running one of these operating systems, an error message appears.
Windows Server 2003 Standard Edition SP2 is the recommended operating system to run server components.
Windows XP Professional SP2 is the recommended operating system to run client components.
If you plan to run Application Server version 3.0 on computers running Windows Vista, all editions except for Home Basic and Home Premium are supported. The Business Edition is recommended.
Windows XP Professional SP2 and Windows Vista may be used on a Galaxy Repository Node for only single-node solutions.

The Bootstrap, IDE, and Galaxy Repository are supported on the following language versions of Microsoft operating systems: English, Japanese, Chinese, German, and French. The Galaxy Repository is also supported in English, Japanese, Chinese, German, and French versions of Microsoft SQL Server 2005.

Other Software Requirements

The following list describes other third-party software requirements to support Application Server version 3.0.

Microsoft SQL Server 2005
- SQL Server 2005 with SP2 (Standard or Enterprise) is the only database supported by Application Server version 3.0. The Compact, Express, and Workgroup editions of SQL Server 2005 are not supported for the Galaxy Repository.
- The SQL Server 2005 SP2 database must be installed on the same computer as the ArchestrA Galaxy Repository.
- TCP/IP must be enabled on the computer running SQL Server. The TCP/IP protocol setting can be verified from the SQL Server 2005 Network Configuration under SQL Server Configuration Manager.
Microsoft Visual Studio 2005 (toolkits only)
.NET Framework Common Language Runtime (CLR) 2.0.50727

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

Important! Application Server 3.0 requires installing Microsoft SQL Server 2005. You cannot use Microsoft SQL Server 2000 with this version. You also cannot install and use Application Server on a computer that has both Microsoft SQL Server 2000 and Microsoft SQL Server 2005 installed.

Vista Restrictions

Application Server version 3.0 can run under Windows Vista Enterprise, Windows Vista Business, or Windows Vista Ultimate. The Windows Vista Home Basic and Home Premium editions are not supported.
Users must log on as a Windows Vista administrator to run Application Server version 3.0. You cannot run Application Server as a Windows Vista standard user or power user.
You can run Wonderware 32-bit software only with a 32-bit version of Windows Vista. Running Wonderware 32-bit software with a 64-bit version of Windows Vista on 64-bit hardware is not supported
The Windows Vista User Account Control (UAC) must be disabled when running Application Server. Refer to Microsoft Windows Vista documentation for instructions to disable UAC.
When you disable Windows Vista UAC, you must restart the computer before attempting to install the ArchestrA IDE or Wonderware Application Server. A Galaxy connection error occurs if you attempt to install the ArchestrA IDE or Wonderware Application Server and you did not restart the computer after you disabled the UAC.
Windows Vista does not support a traditional Application Server 3.0 single-node configuration that includes Wonderware Historian (formerly IndustrialSQL Server).
A Vista Platform cannot be configured to be an alarm provider and also have InTouch WindowViewer on the same computer configured to generate alarms. Only one of the two will function properly as an alarm provider.
Windows Vista does not support NetDDE. ArchestrA graphics make use of the client layer when accessing InTouch tags, and appear as a third-party client trying to access WindowViewer as a data server. As a result, ArchestrA symbols cannot communicate with InTouch tags. Windows Server 2003 and Windows XP Pro still support NetDDE.
Application Server 3.0 cannot be configured to run as a service under Windows Vista. Windows Vista security prevents started Windows services from interacting with desktop objects. When Application Server 3.0 is installed on a computer running Vista, scripts do not run correctly if they include the InTouch ActivateApp() and SendKeys() functions. These functions interact with desktop objects by starting Windows programs and sending keystrokes to these programs.
The Galaxy Repository is only supported on Vista for single-node systems. For multiple-node Galaxies, Windows Server 2003 is the preferred operating system for the Galaxy Repository node.

Using Multiple Network Interface Cards with Vista

If you are using multiple network interface cards (NICs), you must configure certain settings for the firewall or else a remote Vista node cannot connect to a Galaxy Repository node.

A connection in Vista is a term used to define a network interface card (NIC), its settings and the settings of whatever the NIC is connected to. Under certain circumstances, the connection on your computer can change if, for example, the IP address on the computer to which you are connected changes. Your computer's connection can be affected by external factors. During boot, and each time a connection changes, Vista goes through an "Identifying" process to determine which profile should be assigned to the connection.

A profile is a collection of firewall settings that can be applied to a connection. There are three profiles currently defined in Vista: “Domain”, “Public” and “Private”.

The Domain profile is assigned automatically to a connection if a domain controller for the domain to which the computer is a member is found on the connection.
The Public profile is designed to keep the computer from being visible to other computers on the network. Network discovery is turned off for the Public profile.
The Private profile is used for a more trusted environment. Network discovery is turned on for a Private profile. Firewall exceptions and rules can be created on any or all of these profiles.

This is important because the OS Configuration utility and the Vista Firewall utility apply their firewall exceptions to the Domain and Private profiles only.

As previously noted, you can specify which profile you want assigned to a connection as long as that connection is not a Domain connection. This is done through the "Network and Sharing Center". Click on the Network icon in the right-hand side of the task bar and then click on one of the networks that is displayed. You can change a connection from a Public profile to a Private profile. The firewall calls these settings "Profiles" but the network calls them "Location types".

On computers using dual NICs, the first NIC is normally connected to the domain and is assigned the Domain profile automatically. The second NIC is typically assigned the Public profile.

The first issue is that your entire computer (all connections) is restricted to the most restrictive of the profiles assigned to any connection. So if the second connection was assigned a profile of Public, none of the firewall exceptions set by the OS Configuration or Vista Firewall utilities will be allowed. The exceptions were set for Domain and Private only, not Public. You must set the second connection to the Private profile for any of the firewall exceptions to work.

The second issue is that it appears that a re-boot of your computer, or even a re-boot of a computer to which you are connected, can change your connection back to the Public profile. Once again the firewall exceptions will not be effective. You'll have to change the connection back to the Private profile after each re-boot or a re-boot of the connected computer.

To avoid these NIC issues and prevent the “Identifying” process from taking place on a connection and changing the assigned profile, certain items must be present in the definition of the connection. Follow the rules below:

If you have only one NIC, no action is required. The profiles and firewall rules are automatic.
If you have two NICs follow the actions below:

If the second NIC is not physically connected to anything (that means no wire in it), no action is required. The profiles and firewall rules are automatic.
If the second NIC is connected, it MUST be configured. Follow the rules for configuring a normal redundancy setup, Vista will identify this NIC and assign it a Private profile. If the NIC is not configured, Vista will assign a profile of Public to this NIC and cause all of our firewall exceptions to be deactivated on all NICs. For the NIC to be configured properly, give it an IP address, sub net mask and gateway address. The gateway address can be the same as the IP address. Usually these addresses will be the internal, non-routable addresses like 192.168.0.x or the 10.x.x.x range.
If you have more than two NICs, make sure all connected NICs are configured with an IP address and default gateway address and have been assigned a profile of Private.

< top of document >

Installing Application Server

Before You Start

Note the following important issues before you continue:

Antivirus Software Issues

Configure the Antivirus software so that archive files are not scanned. Also, Antivirus software should not process files in the following ArchestrA folders:

C:\Program Files\ArchestrA\Framework\Bin\CheckPointer (a default setting, specified in WinPlatform editor's Engine page, Checkpoint Directory Location option)

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 Antivirus software does scan the above folders, this may result in slow performance as deploys are performed.

Installation

For detailed installation instructions, see the Application Server Installation Help (Install-AppServer.chm) that is available on the installation CD.

You must have Microsoft SQL Server 2005 SP2 installed before you install Application Server on the GR node.

The Galaxy Repository locks the SQL Server maximum memory usage to 65% of the physical memory.

Upgrading from a Previous Version

You can upgrade from the following versions of Application Server: Version 2.0 Patch 01 or later, and Version 2.1, including all patches and service packs. For more information, see the Application Server Installation Help (Install-AppServer.chm) that is available on the installation CD.

< top of document >

Known Issues–Application Server Version 3.0

This section describes all known issues identified in Application Server Version 3.0. The known issues are grouped by function.

Install/Uninstall/Upgrade

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 do not mean a system problem happened. Everything should function 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.

L00056999: The Rainbow Sentinel driver does not install correctly if an ArchestrA product is installed on a computer running the Vista operating system and a second ArchestrA product is installed.

An error can occur by running setup.msi to install a second ArchestrA product on a computer that already has an ArchestrA product installed on it. Do not use setup.msi to installed the second ArchestrA product. Install the second ArchestrA product by running setup.exe instead.

L00062633: When the ArchestrA License Manager installs a new license file from a CD, the file remains read-only. Any subsequent attempt to add licenses fails indicating "Read/write access denied to file."

Once the license file is installed, manually remove the "read-only" attribute.

L00064271: Installing Legacy components (version 7.x or earlier) after ArchestrA components (version 8 or greater) creates duplicate common components that causes installation errors.

If you wish to continue using legacy Wonderware products, install the FactorySuite 2000 common components from the Device Integration product CD prior to installing the ArchestrA components.

L00064546: InTouch application on a non-upgraded remote node cannot see alarm generated data on an upgraded remote node.

When a Galaxy Repository (GR) Platform is upgraded while it has current active alarms on its hosted objects, it is minimally possible that these alarms may not display on remote InTouch Alarm Provider Platforms following the upgrade and redeploy of the GR Platform.

To recover the alarm data on the remote node, restart the Platform on the remote node

L00065667: The ArchestrA License Manager appends new feature lines to the end of the license file. This is a change in behavior.

Open the license file using Microsoft Notepad and manually move the new feature line added to the top of the file, save and close the file.

L00066339: The License Utility becomes unusable when ActiveFactory 9.2 and IAS 3.0 co-exist on a machine and ActiveFactory 9.2 is uninstalled later.

In order to make the License Utility usable, perform the following steps:

1. Locate and remove the "LicView.exe" file (dated Thursday, August 03, 2006, 9:20:20 PM, size 68.0 KB) from C:\Program Files\Common Files\ArchestrA folder.

2. Run the product installer repair (this may require the original product CD).

Depending on the order of products installed, or uninstalled, the license utility menu option may, or may not appear under start/programs/Wonderware/Common. If the shortcut is not available, the License Utility can be launched by locating licview.exe file in c:\program files\common files\ArchestrA folder.

L00067185: Upgrading the Galaxy Repository node and another remote node simultaneously, "SetObjStatus.exe - Common Language Runtime Debugging Services" displays the error message: "Application has generated an Exception that could not be handled."

1. Click OK. The debugging Runtime Visual Studio dialog appears.

2. Click Cancel to proceed with the upgrade.

L00067207: Application Server 3.0 upgrade fails because DASABTCP.exe does not shutdown.

Before upgrading Application Server to version 3.0, first upgrade the existing DIABTCP to the 1.5 release or later. This is done by importing package DiABTCP_1.5.aaPKG. Once the DIABTCP upgrade is complete, proceed with the Application Server 3.0 upgrade.

L00068743: Repair installation of the GR node does not copy the Galaxy backup files.

1. Insert the original product installation CD/DVD into the computer CD/DVD drive.

2. Manually copy the files from CD/DVD, Framework\Bin\BackupGalaxies directory to the "<drive>:\Program Files\ArchestrA\Framework\Bin\BackupGalaxies" on your computer.

3. Restart the GR node.

< Top of document >

IDE Functionality

L00021257: Successful unassignment limit.

If you try to unassign up to 700 templates (or 4,000 instances) at the same time, only some objects are unassigned. An IDispatch error appears 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 are 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 -> Administrative Tools -> Services.

L00022604: Assign To dialog box list incomplete.

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

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

Creating objects using InTouch WindowMaker’s SmartSymbol capability causes 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 example, if you try to configure security in the IDE, the following message appears: “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).

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

An “invalid data” message does not appear if you enter invalid data for an element of an array on the UDAs page of an object’s editor and then move to the UDA name list. “Invalid data” messages appear if you change 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, trying 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 happen. When you add a Role on in the Configure Security dialog box, the Select Groups dialog box appears. The Available OS Groups list is populated only with those groups that belong to the domain shown 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 make the Application View/Template Toolbox views 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 resets to a default initial value.

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

Occasionally, deleting a template object results in an hourglass that won’t go away after the object is 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.

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.

L00032651: Japanese: Duplicate objects are added in the Security Group.

If you are running Application Server on Japanese Windows system, don’t mix Half-width Katakana or Full-width Katakana when naming Security groups. If you do mix them, you may see duplicate objects.

L00041087: Opening a HTML help file for an object crashes the IDE.

If you edit the HTML help file for an object in Word 2000, the IDE crashes when you try to open the edited help file in the IDE. To prevent this from happening, use Word 2003 or an HTML editor to edit the file.

L00055637: Inconsistency among fonts supported by Windows Controls.

Different fonts are supported by different Windows Controls. If you select a font that is not supported, a substitute font appears.

L00057722: If you rename and save a symbol in an ApplicationObject instance that is directly referred to by a show symbol animation in another symbol of the same object (an absolute reference), the reference in the show symbol animation is not updated.

Close the editor to propagate the change.

L00061529: Deleting a galaxy on the GR node creates a mini-dump and generates error messages when the remote node connected to the IDE enters into a hibernation, sleep, stand-by, or suspend mode.

OS hibernation, Sleep, Standby or suspend modes should be disabled on the remote nodes.

L00062074: The IDE cannot connect to a Galaxy if the Galaxy is located on a computer having a name longer than 15 characters.

L00062229: In radio group array page, selecting a valid UDA array doesn't populate the array elements view until the object is checked in.

L00067290: SuiteLink communication with InControl is broken after installing InTouch.

If you install software in the order of: InControl, Application Server 3.0, then InTouch, on a single computer, SuiteLink communication with InControl is broken. Restart the computer; SuiteLink communications with InControl is restored. From the command line interface, you may use the command “slsping localhost RTENGINE” to verify that communications has been restored with InConrol.

L00068320: When configuring a custom UDA property or UDA title, the title does not display.

You are limited to using the default title text, "Use Symbol name for Window Title." You can also use static text for the windows title. However, using "Reference for title of Show Symbol" (Custom Property, graphic's runtime property, InTouch tag/ArchestrA UDA) for window title will not work.

There is one exception. If you use a reference (InTouch Tag/ArchestrA UDA) for window title and the same reference has been used somewhere else, such as in an animation on a graphic in the symbol, then that reference will work. This is because that animation will do the work for Show Symbol Title.

L00068324: Properties of graphic elements within a symbol are not resetting to the default values on “hide” of the symbol when "Always load windows from disk" is not checked within the Window viewer configuration.

When the “Always load windows from disk” box is checked, each time a window is opened all graphic element properties and custom properties display with the default value(s).

When the “Always load windows from disk” box is not checked, the first time a window is opened all graphic element properties and custom properties display with the default value(s). Subsequent openings of a graphic element retain the last graphic element property and custom property value(s).

L00069271: Migration of older aaPKG files to a Galaxy created with the Base_InTouch.cab file fails.

A Galaxy created from the Base_InTouch.cab file provides only the InTouchViewApp base template to run the sample applications included with InTouch HMI version 10. This unique Galaxy does not provide the other standard system objects needed to support ArchestrA applications.

If you attempt to import or migrate the contents of aaPKG files created with earlier versions of Wonderware Application Server (2.0, 2.1, or 2.5) to a Galaxy created with the Base_InTouch.cab file, the older ArchestrA objects are assigned because no version 3.0 templates are part of the Galaxy. When you attempt to deploy an instance of an application, a failure occurs because the Galaxy's required version 3.0 automation objects are missing.

Important:

Do not attempt to import/migrate older version aaPKGs files to a Galaxy created using the Base_InTouch.cab file.
If you accidentally delete ArchestrA templates, then reimport the version 3.0 aaPKG file from the Wonderware Application Server \bin folder to your Galaxy.

Take these steps to restore the correct version 3.0 system objects to your Galaxy:

Delete all the objects in the Galaxy.
Import the version 3.0 templates in the aaPKG file located in the Wonderware Application Server \bin folder.
Import the earlier version aaPKG file with the migration option.

69296: The month and day of a time type custom property gets swapped when you poke a value at run time on non-English OS if custom property's default value was configured with a constant string (ex: "08/10/2007 12:30:59").

Create a UDA in ArchestrA and use the UDA to initialize the custom property.

< 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 are 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 appears about not being able to resolve the reference. If you deploy an instance of the object, quality is not set as expected (for example, Bad, Good, Uncertain, Initializing).

< Top of document >

Deploy/Undeploy

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 skips 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 is the default. You must manually reset this key value each time you deploy the WinPlatform.

L00035603: A misconfigured CheckpointPath can cause a deploy mismatch between the GR and the runtime.

Create an instance of $AppEngine and set its CheckpointPath to a node that does not exist. When you deploy, you see several deploy error messages in the Deploy dialog box and in the Logger.

The errors in the logger are:

aaEngine - CApplication::InitializeCheckpointer - AppEngine_002. Failed to open checkpointfile. FsEngine exiting ...

aaEngine - WinMain exiting error code 80004005

The GR marks the object as undeployed and the SMC indicates the engine exist in the runtime and is shutdown (startup failed).

Correct the $AppEngine to specify a CheckpointPath does exist and redeploy.

L00043922: Parent area AlarmMode state does not propagate to child areas after rename parent area.

If you rename an area without redeploying all its child areas and objects, the child areas and objects will have incorrect Area value and hierarchical names. To solve this problem, undeploy and redeploy all the child areas and objects of the renamed area.

L00044431 - Undeploying an OPCClient object that points to an OPC server on a remote node that is shutdown causes AppEngine to hang for 1 minute.

An OPCClient object on NodeA is connected to an OPC Server on NodeB and then NodeB is shutdown. Undeploying the OPCClient object hangs the AppEngine for one minute before the AppEngine recovers. Not all OPC servers hang the OPCClient on the AppEngine.

L00044575: Deploying to nodes in fail over

We don't recommend that you deploy to:

• a node while it is failing over

• deploying to a node that is currently being failed over to

Always deploy to nodes that are not involved in a fail over event.

L00058705: Deploy fails because of the name server resolution error. The reverse lookup didn't work.

To resolve the DNS:

1. On Galaxy Node G1, use the hosts file C:\windows\system32\drivers\etc\hosts, add the hostname and ip address of the node, P1.

For Application Server, use the machine name (right click MyComputer->Properties->ComputerName) of the node P1 as your hostname in the hosts file. If you use a hostname which is not the same as machine name of that node P1, then the deployment will fail.

2. On the node, P1, use the hosts file C:\windows\system32\drivers\etc\hosts, add the hostname and ip address of your Galaxy node, G1.

To resolve the DHCP issue:

1. When the computer is connected to the network and assuming your Galaxy node has a static IP, edit the hosts on Galaxy node G1 to the new ip address the computer gets.

2. Before G1 can access the node P1, try to restart the node P1 or restart NmxSvc so the Galaxy makes the appropriate connections correctly.

L00066957: Cannot deploy any objects if Data Execution Prevention (DEP) configuration is set to /noexecute=AlwaysOn.

This problem only occurs when 1) the computer has a CPU that supports DEP at the processor level, AND 2) the operating system has been configured, through the boot.ini file, to have DEP set to /noexecute=AlwaysOn. Reset the DEP setting to "/noexecute=OptOut."

L00067245: Deployment of remote platform fails (after upgrade/migrate) when objects are in the software update pending state. This happens when the remote node is disconnected from the Galaxy Repository during the upgrade.

Undeploy the primary node by selecting the "On Failure Mark as Undeployed" option on the Undeploy dialog box, then redeploy the node.

L00068373: A deployed instance of an InTouchViewApp object may be marked as having pending changes, even though changes to a parent Template of an embedded symbol's instance do not affect the InTouchViewApp.

For example, if you change a symbol in an ApplicationObject template, but an InTouchViewApp object instance does not use that symbol but does use another symbol in the Template, the object may be marked as having pending changes. Template changes can be related to symbols, UDAs, scripts, extensions, and so on. If you know the template changes do not affect a particular InTouchViewApp, you can ignore the pending changes indicator.

< 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.

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 reaches 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.

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.

< 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.

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

Trying 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 tried 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 appear 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 example, 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 tried 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 try 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 (three or more) and hosting a redundant pair of AppEngines, if you shutdown 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 reimport 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 shutdown 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.

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 example, 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 P1 is shutdown, network traffic increases due to additional communications from the other WinPlatform(s) trying 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 host name and IP address.

All nodes in your Galaxy must be able to communicate with each other by using both IP address and host 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 example, 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.

< Top of document >

Miscellaneous

Anti-virus Software Issues

Configure the Antivirus software so that archive files are not scanned. Also, Anti-virus software should not process files in the following ArchestrA folders:

C:\Program Files\ArchestrA\Framework\Bin\CheckPointer (a default setting, specified in WinPlatform editor's Engine page, Checkpoint Directory Location option)

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 (a default setting, specified on WinPlatform editor’s General page, History store forward directory option)

If the Anti-virus software does scan the above folders, this may result in slow performance as deploys are performed.

L00010030: Using commas 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 fails. 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 show 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 does 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 example, 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 appear:

“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 is 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.

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 show any problem.

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

In this release of 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.

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

Trying to import a large Galaxy with multiple levels of template containment can 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.

L00031171: Change of security mode does not always show 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 example, OS Group Based), which appears 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.

L00036073: Time won’t synchronize.

An Application Server node on a separate network from the other Application nodes and the Wonderware Historian 9.x does not time sync with the Historian node.

1. Install the WindowsServer2003-KB823456-x86-ENU.exe patch on several machines.

2. Install InSQL 9.x on one node.

3. Install GR, the IDE, and Bootstrap on another node.

4. On the third node install Bootstrap.

5. Configure the third node to be on a separate network via a router.

6. Create a two node galaxy and configure the remote node to the third machine.

7. Set the time master of the galaxy to be the InSQL 9.x node.

8. Deploy the two nodes.

9. Set the time of the third node to be out of sync from the InSQL node. The time won’t synchronize.

L00044355: The size of the tempdb.mdf file is too large.

Deploying objects in a system with a large number of Areas (more than 1000) can cause the SQL Server tempdb database on the InSQL node to consume a sizable amount of disk space on the historian system. This disk space can be released through a manual procedure on the InSQL node. Please contact Wonderware Technical Support for details.

L00050082: Unable to connect to existing Galaxies or create new ones.

McAfee Desktop Firewall 8.0 may prevent SQL TCP/IP connections, causing problems connecting and deploying Galaxies. Turn off the firewall to solve these problems.

L00053855: Precision issue displaying calculated/scaled analog UDA value from Application Server in InTouch.

The InTouch HMI uses the IEEE 32-bit floating point format to show real numbers in an application. The IEEE floating point format is only an approximation of an actual real number. Unless the real number is an even power of two, it cannot be represented exactly using the IEEE 32-bit floating point format. The precision of an IEEE 32-bit floating point number is approximately eight decimal places.

When you want to show a real number in an InTouch application, make sure the number does not exceed eight digits. The following floating-point number formats show valid real numbers within an InTouch application:

#.#######

###.#####

######.##

Any floating-point numbers with more than eight digits are subject to rounding errors.

Example:

An InTouch application should show the real number 2.3. But, the number 2.3 is not an even power of two and cannot be precisely represented by the IEEE 32-bit floating point format beyond 8 decimal digits.

To ensure the value 2.3 is shown from the application as the ASCII characters 2.3, the number must not exceed eight digits. If the number exceeds the eight digit maximum, the resulting number may be shown as 2.29999999 or 2.30000001 instead.

L00057894: The WinPlatform.CPULoadAvg attribute is not calculated correctly for a platform running on a dual core processor.

If you have a constant load on system running on a dual core processor, the WinPlatform.CPULoadAvg value stays consistently higher than the WinPlatform.CPULoad value.

L00068862: When importing an object package containing ArchestrA graphics with .Net client control Event scripts, the user finds that the Event scripts are empty or non-existent in the graphics.

Perform the following steps, to import an aaPKG package containing Client Controls.

1. Create a new galaxy.

2. Import the original aaPKG.

3. Export just the client controls to cc.aaPKG.

4. Change to the galaxy in which you want to import.

5. Import cc.aaPKG.

6. Import the original aaPKG.

< Top of document >

Application Server Documentation Issues

The following table lists all documentation corrections to Application Server 3.0 documentation.

Item	Location of Change	Existing Documentation	Change
1	AAGraphics.pdf: "Status Element" section, page 26 IDE.chm: "Status Element" topic	"The element prioritizes according to an order, as shown in the following table: Communication Error (highest priority), Configuration Error, Bad, Uncertain, Initializing, Operational Error, Software Error, Security Error, Warning, Pending (lowest priority)"	"The element prioritizes according to an order, as shown in the following table: Communication Error (highest priority), Configuration Error, Pending, Operational error, Software error, Security error, Warning, Bad, Uncertain, Initialization (lowest priority)"
2	Scripting.pdf: "SetBad()", "SetGood()", "SetInitializing()", "SetUncertain()" topics, pages 32-34 IDE.chm: "SetBad()", "SetGood()", "SetInitializing()", "SetUncertain()" topics	--	Add the following paragraph: "These script functions must be used in server scripts. They are not for use in client-side scripts."
3	AppEngine object help (help.html): "Redundancy Configuration" topic	In the table, the entry for the label and attribute are shown as: Restart on Transition to Standby Redundancy.RestartOnTransitionToStandby	The entry for the label and attribute should be shown as: Restart engine process when transitioning from Active to Standby Redundancy.RestartOnStandbyTransition
4	(Install-AppServer.chm) Topic: Upgrading from a Previous Version of Application Server	Application Server Installation Help	In the first paragraph add a third bullet: Version 3.0, including all patches and service packs

< top of document >

Application Server Documentation

The Application Server product library consists of a set of Portable Document Files (PDF) located in the UserDocs\English folder of the Application Server installation CD. You need Adobe Reader installed on your computer to view Application Server documentation. You can download the latest version of Adobe Reader from the Adobe Corporation web site:

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

After installing Adobe Reader, double-click on a PDF file with your pointing device to view the book with Adobe Reader. You can also open a book with the Adobe Reader Open command from the File menu.

Application Server installation instructions are located in the root folder of the Application Server installation CD as an online help file. You can view these instructions by clicking the Installation Guide button in the Application Server installation program.

Product documentation is also available with Application Server online help.

Documentation Set

The Application Server documentation set includes the following guides:

Application Server User’s Guide. Explains configuring and deploying Application Server applications.
Creating and Managing ArchestrA Graphics User’s Guide. Explains how you create and manage graphical symbols using the ArchestrA Symbol Editor within the Integrated Development Environment (IDE).
Application Server Scripting Guide. Reference for the scripting language in Application Server.
Object Viewer User’s Guide. Explains how to acquire runtime data using the Object Viewer.
Platform Manager User’s Guide. Explains how to start and stop system components.
Galaxy Database Manager User’s Guide. Explains how to backup and restore the Galaxy database.
Log Viewer User’s Guide. Explains how to use the Log Viewer utility to determine system diagnostics.
Log Flag Editor Utility Guide. Explains how to turn on and off certain diagnostics logging messages.
Wonderware FactorySuite License Utility Guide. Explains how to use the License Utility to manage the license required for the running application.
Wonderware ArchestrA Protocol Guide. Explains background information on the main protocols used between components of Wonderware products.
Application Server Installation Guide. Explains information about installing the product.
InTouch HMI and ArchestrA Integration Guide. Explains how you can use the ArchestrA Integrated Development Environment (IDE) to manage InTouch applications so that you can use symbols you create in the ArchestrA Symbol Editor. This guide is available on the InTouch HMI installation CD.

Information included in these guides is provided in online Help, which can be opened using the Help menu options in each utility.

During product installation, you can choose to install the documentation PDF on your local hard drive.

Searching Application Server Books with Adobe Reader

The Application Server version 3.0 books are delivered as an Adobe PDF package, which provides a master index of all books. Using Adobe Reader, you can simultaneously search for a specific topic across all books that belong to the Application Server product library.

To search for information across all Application Server books simultaneously

Open Adobe Reader.
Press CTRL+SHIFT+F or select Search from the Edit menu. The Search dialog box appears.
Type the word or phrase that you want to search for in the Application Server books.
In the Where would you like to search area, select the option to search all PDF books.
If necessary, locate the the Application Server version 3.0 PDF package located on your Wonderware CD or on a network folder containing copies of the Application Server PDF book files. After product installation, these files can be found at: <dive letter>:\Program Files\ArchestrA\Framework\Docs.
Click Search. Adobe Reader lists the Application Server books that contain a match for your search criteria.
Click on the links to open the Application Server book to the topic containing the information that meets your search criteria.

< Top of document >

Application Server 3.0 SP2

Wonderware Application Server 3.0 Service Pack 2 Readme

About This Readme

Wonderware Application Server 3.0 SP2 Information

Wonderware Application Server 3.0 SP1 Information

Wonderware Application Server 3.0 Patch 03 Information

Wonderware Application Server 3.0 Patch 02 Information

Wonderware Application Server 3.0 Patch 01 Information

Wonderware Application Server 3.0 Information

Requirements to Apply Wonderware Application Server 3.0 SP2

Antivirus Software Issues

Compatibility Requirements for Application Server 3.0 SP2

Applying Wonderware Application Server 3.0 SP2

Migrating Applications to Wonderware Application Server 3.0 SP2

Resolved Issues - Wonderware Application Server 3.0 SP2

Known Issues - Wonderware Application Server 3.0 SP2

Wonderware Application Server 3.0 Service Pack 1 Readme

About This Release

Wonderware Application Server 3.0 SP1 Information

Wonderware Application Server 3.0 Patch 03 Information

Wonderware Application Server 3.0 Patch 02 Information

Wonderware Application Server 3.0 Patch 01 Information

Wonderware Application Server 3.0 Information

Requirements to Apply Wonderware Application Server 3.0 SP1

Compatibility Requirements for Application Server 3.0 SP1

Applying SP1 to Wonderware Application Server 3.0

Wonderware Application Server 3.0 Requirements to Apply SP1

Migrating Applications to Wonderware Application Server 3.0 SP1

Resolved Issues - Wonderware Application Server 3.0 SP1

Known Issue - Wonderware Application Server 3.0 SP1

Wonderware Application Server 3.0, Patch 03 Readme

Wonderware Application Server 3.0, 3.0 Patch 01, and 3.0 Patch 02 Readme Information

Version 3.0 Patch 02 Information

Version 3.0 Patch 01 Information

Version 3.0 Information

About This Release

About This Release

Wonderware Application Server 3.0 Readme

About This Release

System Requirements

Recommended Hardware Requirements

Software Requirements

Operating Systems

Other Software Requirements

Vista Restrictions

Using Multiple Network Interface Cards with Vista

Installing Application Server

Before You Start

Installation

Upgrading from a Previous Version

Known Issues–Application Server Version 3.0

Install/Uninstall/Upgrade

IDE Functionality

Scripting

Deploy/Undeploy

Historian

Redundancy

SCADA/Intermittent Networks

Miscellaneous

Application Server Documentation Issues

Application Server Documentation

Documentation Set

Searching Application Server Books with Adobe Reader

Навигация

Поиск