Last revision: 12/12/2007
Important!This document contains important information about Wonderware Application Server 3.0, Patch 1. Review this document for resolved and known issues.
Application Server 3.0, Patch 1 primarily targets Factelligence support features. In addition, Patch 1 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 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
Known Issues – Application Server 3.0
Application Server Documentation
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 1, 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.
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 1, 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.
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
This release of Wonderware Application Server 3.0, Patch 1 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.
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 1 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.
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.
Application Server 3.0 includes the following enhancements and new features.
Updated IDE
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:
Deploy Improvements
Check-in Improvements
Template changes to selected elements are optimized for:
Script Improvements
Incremental Upgrades
Read-Write Performance Improvements
Redundant DIObject Improvement
Redundancy Improvements
Device Integration Improvements
Galaxy Backup
Toolkits
This section describes the recommended hardware and software requirements to install Application Server 3.0.
The following list shows the recommended hardware requirements to install Application Server version 3.0.
Galaxy Repository Platform:
Non-Galaxy Repository Platforms (IDE or Runtime):
All Systems (IDE, GR, Runtime):
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
This section describes the operating system and other software requirements to install Application Server version 3.0.
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 | ||||
| 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:
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.
The following list describes other third-party software requirements to support Application Server version 3.0.
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.
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”.
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:
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.
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.
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.
This section describes all known issues identified in Application Server Version 3.0. The known issues are grouped by function.
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.
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:
Take these steps to restore the correct version 3.0 system objects to your Galaxy:
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.
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).
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.
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.
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.
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.
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.
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 |
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: