This ReadMe file
describes the defects fixed in this patch and known issues.
Detailed
installation instructions are included in the Industrial Application Server
Installation Guide. It is recommended that you read the Industrial Application Server Deployment Guide (found at www.wonderware.com) and Industrial Application Server Installation Guide (Install-AppServer.chm in the root directory
of the product CD) prior to beginning the installation process.
IMPORTANT: Applying this patch modifies the
Galaxies contained in the Galaxy Repository. If you then restore a Galaxy that
was backed up previous to applying the patch, you must apply the patch again. Likewise,
you must apply the patch again if you import templates that a) do not already
exist in the Galaxy Repository and b) come from an ArchestrA implementation
that was not patched.
A
prerequisite of the Industrial Application Server install is the installation
of Microsoft SQL Server SP3 but this service pack is not delivered on the
Industrial Application Server CD. This service pack is located on the
Prerequisite CD. Before installing this patch, it is strongly
recommended that you exit all FactorySuite® programs, including
executable (.exe) files and services.
To
run Industrial Application Server, we recommend as a minimum the following
software and hardware configurations:
Software
Requirements
FactorySuite A² Development seat - IDE with Galaxy
Repository (Project Database)
MicrosoftÒ SQL
Server 2000 Service Pack 3 and
MicrosoftÒ WindowsÒ Server
2003 or
MicrosoftÒ WindowsÒ 2000
Server with Service Pack 3 or
MicrosoftÒ WindowsÒ 2000
Advanced Server with Service Pack 3
Important! The Microsoft SQL Server login
for BUILTIN\Administrators group must be present and enabled.
FactorySuite A² Development seat - IDE with no
Galaxy Repository (Project Database)
MicrosoftÒ WindowsÒ Server
2003 or
MicrosoftÒ WindowsÒ 2000
Professional with Service Pack 3 or
MicrosoftÒ WindowsÒ 2000
Server with Service Pack 3 or
MicrosoftÒ WindowsÒ 2000
Advanced Server with Service Pack 3 or
MicrosoftÒ WindowsÒ XP
Professional with Service Pack 1
FactorySuite A² Application Server Runtime
MicrosoftÒ WindowsÒ Server
2003
MicrosoftÒ WindowsÒ 2000
Professional with Service Pack 3 or
MicrosoftÒ WindowsÒ 2000
Server with Service Pack 3 or
MicrosoftÒ WindowsÒ 2000
Advanced Server with Service Pack 3 or
MicrosoftÒ WindowsÒ XP
Professional with Service Pack 1
Hardware
Requirements
PC with 2 gigahertz (GHz) or higher processor clock
speed
1 gigabyte (GB) of RAM or higher (512 MB minimum
supported; may limit performance and some features)
8 gigabytes (GB) of available hard disk space
Super VGA (1024 × 768) or higher-resolution video
adapter and monitor
CD-ROM or DVD drive
Keyboard and Microsoft Mouse or compatible pointing
device
While the IDE itself has only been tested on English operating systems it can be installed on non-English operating systems for use with InTouch in browsing a Galaxy Repository.
The following defects were fixed for this patch release. Click on
the defect number for a more detailed description of the problem.
L00016641 Platform deployment timeout
issue.
L00018021 Galaxy
Load fails if a description contains a double quote.
L00018057 Errors
reported to the logger when restoring a Galaxy.
L00018182 OS Group
Authentication does not seem to work if GR node is down.
L00018645 Creating
UDA names that contain German or French characters.
L00018741 Using a comma
(“,”) in an OPC Item address of an AnalogDevice object doesn’t work.
L00018782 View not
re-binding to objects hosted on a local platform when the GR is not present and
the Platform node is rebooted.
L00018957 InTouch
requires about 20 minutes to rebind references when engine/areas/objects are
moved to a new platform.
L00018959 Alarms
are not displayed when engine/area/objects are reassigned to a new platform.
L00019178 Doing
galaxy load of multiple files with long names did not work.
L00019300 Doing a
Galaxy Dump and Galaxy Load of an OPCClient object with an attribute that has a
comma (“,”) in its name fails to properly load the object.
L00019361
Communication problems between nodes with different subnet masks.
L00019449
Undeploying and moving a failed engine from one platform to another causes
errors and corrupts the GR.
L00019538 When the
Historian.ConnectStateCmd attribute is set to false, a reconnection is
automatically attempted after 86,400 scan cycles.
L00019544 Updating
a UDA’s value with a discrete value touch pushbutton is unreliable.
L00019545 Doing
multiple deploys in the unassigned area causes errors in the logger.
L00019546
Importing objects and creating a new Galaxy in the same Galaxy Repository
causes both IDEs to hang.
L00019548
Attempting to view dialog boxes from a restored Galaxy of a user with a large
monitor.
L00019549
Validation on an instance shows inaccurate “updates pending” status after
migration of a restored galaxy.
L00019550 Delete
Galaxy and other operations fail when BUILTIN\Administrators group is removed
from SQL Security.
L00019551 Memory
leak in the ArchestrA Bootstrap.
L00019552 Creating
an object with vendor name that is not ArchestrA causes problems with opening
editor and deployment.
L00019659 Memory
leak in aaEngine.
L00019706 No way
to propogate inheritance on an object’s PV.Input.InputSource Security
Classification.
L00019808
AppEngine not going onscan after reboot or restart.
L00019941 Minor
version of aaDEF not updated for IAS 1.5 P01.
L00019996 Errors
reported to the logger the first time GR platform is deployed.
L00019998 User
name and password are displayed in the logger when you start the IDE and have
the Trace log flag turned ON.
L00019999 IAS 1.5
does not display the appropriate value or status for .Value and #VString.
L00020001 You
cannot enter a historian nodename even though "Enable storage to
historian" is checked.
L00020003 A “The
local installation's version is different from the one on the remote node” error
message is displayed when the same version of ArchestrA is installed on both
nodes.
L00020008 On a
remote node, the Platform Manager’s "Remove Platform" feature works
the first time after the node is brought online or after a reboot, but
subsequent tries result in an "Engine Communication" error.
L00020029 When
exporting DIObjects, then importing them back into the Galaxy, editors for the DIObjects
contained garbage entries in the Associated Attribute field.
L00020045
Restoring an IAS 1.0 Galaxy fails.
L00020071 A node
that is historizing data and then loses power does not resume storage of
history data when power is restored.
L00020140 Failed
to create a new Galaxy on a computer running Windows 2003 that has the latest
security patch installed.
L00020158 Second
attempt to apply the patch fails.
L00020243 Applying
the patch on a remote node with about 900 active I/O points causes errors.
L00020478 After an
AppEngine that was historizing data is stopped and restarted, historization to
InSQL does not resume.
L00020582 German
ASCII character ü and single French character è are not allowed in script
names.
L00020800 An
InputOutput or Output extended attribute should not display a
"bounce" when set to a new value.
L00016641 Platform
deployment timeout issue.
Problem:
If Galaxy does not receive return notice that a newly deployed platform has
been started, a message is displayed and, even though the platform was
successfully deployed, the Galaxy does not reflect that status. Timeout for
return notice increased to four minutes.
L00018021 Galaxy Load fails if a description contains a
double quote.
Problem:
Manually adding single quotes to a short description when editing a .csv file
caused Galaxy Load to fail. Any single quote must now be entered as double
quotes in the .csv file. Load now strips leading and trailing quotes from a
description, and treats double quotes in the description as a single quote.
When editing a .csv file, take care in using quotes in the short description
field. The entire string must be placed inside of opening and closing quotes,
and any single quote must be entered as a double quote. Therefore, the number
of quotes in any short description field must be even.
L00018057 Errors reported to the logger when restoring a
Galaxy.
Problem:
An "ADODB.Command Requested Operation requires OLE DB Session
object, which is not supported by the current provider." message is
reported when restoring a Galaxy. Problem has been fixed.
L00018182 OS Group Authentication does not seem to work if
GR node is down.
Problem:
When using OS Group mode, you must log into a remote computer at least once
before security will properly work in the case of a down GR node.
L00018645 Creating UDA names that contain German or French
characters.
Problem:
When creating a UDA, German and French characters were not allowed in the UDA’s
name. This problem no longer exists. Like Asian characters, German and French
characters are now allowed.
L00018741 Using a comma (“,”) in an OPC Item address of an
AnalogDevice object doesn’t work.
Problem:
When you add an OPC Item address in an AnalogDevice object (for instance, “PV
input source”) and use a comma (“,”) in the address, the entry is not saved.
This action is now supported.
L00018782 View not re-binding to objects hosted on a local
platform when the GR is not present and the Platform node is rebooted.
Problem:
Assume a GR node with locally-hosted objects and a remote InTouch view. If you
shut down the GR node, restart the InTouch node and start view, binding
functions properly on that node. If you restart the GR node, binding does not
occur. This works properly now.
L00018957 InTouch requires about 20 minutes to rebind
references when engine/areas/objects are moved to a new platform.
Problem:
Rebinding takes about 20 minutes when the engine/area/objects are marked as
undeployed on failure from a platform that is not available on the network
anymore and are now assigned to a running platform. This operation now occurs
in about 30 seconds.
L00018959 Alarms are not displayed when engine/area/objects
are reassigned to a new platform.
Problem:
When engine/area/objects are reassigned, they are "marked as undeployed on
failure". Alarms are now displayed properly when these objects are
reassigned to a new platform.
L00019178 Doing galaxy load of multiple files with long
names did not work.
Problem:
When doing a galaxy load of multiple files with long names, the Galaxy Load
dialog box is not displayed. The buffer limit for .csv filenames is now 10240
characters. If the total length of each .csv filename in a multiple file load
operation exceeds 10240 characters, a message is displayed alerting the user of
the problem.
L00019300 Doing a Galaxy Dump and Galaxy Load of an
OPCClient object with an attribute that has a comma (“,”) in its name fails to
properly load the object.
Problem:
If you add an attribute to a scan group of an OPCClient object that has a comma
(“,”) in it, a Galaxy Dump/Galaxy Load operation does not properly replicate
the object. This operation now works properly as commas are accepted characters
in attribute names.
L00019361 Communication problems between nodes with
different subnet masks.
Problem:
Assume two computers in different workgroups with static IP addresses using a
cross over cable and no DHCP, DNS, WINS or Default Gateway is involved. One
computer is used as an IAS platform and the other as an InSQL node. The two
computers have different subnet portions of their IP addresses. The IAS
computer got disconnected from the InSQL node. The workaround for this problem
is to ensure that the “hosts” file on the IAS node contains an entry for the
InSQL node’s computer name and IP address mapping.
L00019449 Undeploying and moving a failed engine from one
platform to another causes errors and corrupts the GR.
Problem:
Assume that you undeploy a failed engine, move it to new platform, start
the previously-shutdown engine, and mark it and all its instances as deployed.
These actions previously caused errors in the logger and corrupted the GR.
They work properly now.
L00019538 When the Historian.ConnectStateCmd attribute is
set to false, a reconnection is automatically attempted after 86,400 scan
cycles.
Problem:
From the ObjectViewer, you can set the Historian.ConnectStateCmd to false,
which stops historization to the InSQL Historian. After a period of time
(86,400 scan cycles), the attribute automatically changes to true, attempting a
reconnect with the Historian. This behavior no longer occurs. This attribute is
only initialized as true after deployment, not after checkpointing. Therefore,
if the engine is stopped when the attribute is false, restarting the engine
(without redeployment) maintains that value of false.
L00019544 Updating a UDA’s value with a discrete value touch
pushbutton is unreliable.
Problem:
Assume a touch pushbutton discrete value (direct) script from
InTouch that sets a discrete UDA (with an OPC inputOutputextension). When the
button is touched (1) and released (0), the value of the UDA is not updated
reliably. This is due to different methodologies for
setting values between InTouch and IAS. InTouch updates the variable as soon as
the button is pressed and then sends the value to the IAS. IAS sends the value
to the I/O Server but does not update itself immediately. Instead, it only
updates itself when the value returns from the I/O Server. Hence, there is a
small delay. In other words, the delay hinders the quick update that the touch
pushbutton action requires.
L00019545 Doing multiple deploys in the unassigned area
causes errors in the logger.
Problem:
When
you perform multiple deploys in the unassign area, errors are displayed in the
logger. This no longer occurs, as do this action causes the
progress dialog box to display the reason for each selected object.
L00019546 Importing objects and creating a new Galaxy in the
same Galaxy Repository causes both IDEs to hang.
Problem:
Assume a Galaxy Repository and a single Galaxy that two users have connected
to, one locally and another remotely. One user begins importing objects into
the Galaxy and the other user begins a Create Galaxy operation. Both IDE nodes
hang. These two operations can now occur simultaneously.
L00019548 Attempting to view dialog boxes from a restored
Galaxy of a user with a large monitor.
Problem:
Assume a user has created and uses a Galaxy on a computer with a large or high
resolution monitor, and another user attempts to restore that Galaxy (having
been previously backed up) on a computer with a smaller or lower resolution
monitor. Some dialog boxes do not appear onscreen due to the stored user
preference settings of the previous user. The display positioning of dialog
boxes now is tested for current monitor capabilities and adjusted if required.
L00019549 Validation on an instance shows inaccurate
“updates pending” status after migration of a restored Galaxy.
Problem:
Assume that you restore a Galaxy that was backed up from a previous version of
IAS. The Galaxy migration operation occurs. Validation on instances with
“me” references show “updates pending” status when no updates should be
pending. This no longer occurs.
L00019550 Delete Galaxy and other operations fail when
BUILTIN\Administrators group is removed from SQL Security.
Problem:
Removing the BUILTIN\Administrators group from SQL Security disables IAS
operations like Delete Galaxy. A workaround is to add an Admin User ArchestrA
account as a valid user in SQL Server with administrator rights.
L00019551 Memory leak in the ArchestrA Bootstrap.
Problem:
Memory leak in Bootstrap process consuming up to 124,000 bytes a day. This
condition has been corrected.
L00019552 Creating an object with vendor name that is not
ArchestrA causes problems with opening editor and deployment.
Problem:
If you created an object in Visual Studio .NET 2003 and provided a vendor name
that is not ArchestrA, after importing the object, you cannot
open its editor or deploy it. This problem has been fixed.
L00019659 Memory leak in aaEngine.
Problem:
Memory leak in aaEngine process consuming up to 4K each scan. This condition
has been corrected.
L00019706 No way to propagate inheritance on an object’s
PV.Input.InputSource Security Classification.
Problem:
Changing a template’s PV.Input.InputSource Security Classification (for
instance, from Secured Write to Verify Write) does not get propagated to the
template’s children. Previously, Security Classification was propagated only in
the case of MxCategoryWriteable_US. This limitation no longer exists.
L00019808 AppEngine not going onscan after reboot or
restart.
Problem:
Caused by two AppEngines requesting a file from global data. Problem resolved
as global data files now have ReadAccess permissions.
L00019941 Minor version of aaDEF not updated for IAS 1.5 P01.
Problem:
Minor version of aaDEF had not been updated. Minor version updated to 2.
L00019996 Errors reported to the logger the first time GR
platform is deployed.
Problem:
The
first time you deploy the GR Platform, errors are reported to the logger
beginning with "xxSecurity, CSecurityChecker::InitilaizeSecurity -
IGlobalDataRepository::GetFile GalaxyData\data1.txt FAILED".
Problem no longer exists.
L00019998 User name and password are displayed in the logger
when you start the IDE and have the Trace log flag turned ON.
Problem:
If you turn on Trace log flags in the Log Flag Editor and then start the IDE, user name
and password data are displayed in the logger. This condition no longer exists.
L00019999 IAS 1.5 does not display the appropriate value or
status for .Value and #VString.
Problem:
Previously, when you changed in InTouch the .PV of an object pointed to an I/O
point, the value would change to the new value. Currently, you see new value,
then the old value, and then after a period of time (seconds), the new value.
If you were changing the #VString of this same item, you would see it go to
?Pending. Currently, it blinks to ?Pending, then shows the old value, then
after a period of time (seconds), shows the new value. If you were changing the
#VString, and you had security applied, you would see ?Security if there was a
problem. Currently, it shows ?Pending and then the old value. This scenario has
been fixed. If the poke is to .Value from InTouch, the old value is shown until
a good read has returned. If the poke is to #VString, ?Pending is shown until
the new value is returned. If the poke is to #VString and it has Security
issues, ?Security is shown.
L00020001 You cannot enter a historian nodename even though
"Enable storage to historian" is checked.
Problem:
This problem has been corrected. After selecting “Enable storage to historian,”
you can now enter a historian nodename.
L00020003 A “The local installation's version is different
from the one on the remote node” error message is displayed when the same
version of ArchestrA is installed on both nodes.
Problem:
More descriptive error messages required when one node fails to communicate
with another node, fails to create a remote interface for the version
information from Bootstrap, or deploy has failed because the server is
unavailable. These error messages are now available.
L00020008 On a remote node, the Platform Manager’s
"Remove Platform" feature works the first time after the node is
brought online or after a reboot, but subsequent tries result in an
"Engine Communication" error.
Problem:
On
a remote node, the Platform Manager’s "Remove Platform" feature works
the first time after the node is brought online or after a reboot, but
subsequent tries result in an "Engine Communication" error when
undeploying the platform with "On failure mark as undeployed"
checked. When this occurs, the IDE is not updated reflecting that the objects
are undeployed. A second set of systems
causes errors when simulating a crash of an OPC Server on a remote node (OPC
Server not the node that "Remove Platform" was done on).
L00020029 When exporting DIObjects, then importing them back
into the Galaxy, editors for the DIObjects contained garbage entries in the
Associated Attribute field.
Problem:
This problem occurs in the DDESuiteLinkClient, OPCClient and InTouchProxy
objects. After importing an aaPKG file that contains those objects, open the
editors for these objects and garbage entries are displayed in the Associated
Attributes fields. This problem is related to the use of commas (“,”) in those
fields. Problem has been fixed.
L00020045 Restoring an IAS 1.0 Galaxy fails.
Problem:
Restoring
an IAS 1.0 application fails. It just hangs at the stage in which it removes
temporary files. Also, errors are reported in the logger.
Problem has been fixed.
L00020071 A node that is historizing data and then loses
power does not resume storage of history data when power is restored.
Problem:
Assume a node is historizing data and then loses power. Power is
restored but historization does not resume.
"Engine.Historian.ConnectStatCmd" has been set to false, so the
AppEngine does not try to reconnect. This occurs only on
the first power failure after deploying a Platform/AppEngine to the node.
Problem has been fixed.
L00020140 Failed to create a new Galaxy on a computer
running Windows 2003 that has the latest security patch installed.
Problem:
This was an OS problem related to the latest security patch from Microsoft for
Windows 2003. Problem has been fixed.
L00020158 Second attempt to apply the patch fails.
Problem:
Attempting to reapply the patch should work. This action works now.
L00020243 Applying the patch on a remote node with about 900
active I/O points causes errors.
Problem:
Attempting to apply the IAS 1.5 P01 patch to a remote node with 900 active I/O
points causes errors to reported to the logger. The following workaround
should be used: Undeploy the entire remote platform before proceeding with the
upgrade on the remote node.
L00020478 After an AppEngine that was historizing data is
stopped and restarted, historization to InSQL does not resume.
Problem:
When an AppEngine that is historizing data to InSQL is stopped and restarted
from the SMC, it does not resume sending data to InSQL. Checkpoint logic was
not notified of a change in value of the ConnectStateCmd attribute and so the
attribute was not checkpointed. When the engine is restarted, the
ConnectStateCmd is set to false and the engine does not reconnect to the
Historian. Problem has been fixed.
L00020582 German ASCII character ü and single French
character è are not allowed in script names.
Problem:
Only on computers running Windows 2000 Server OS, German and French characters
are not allowed in script names. Problem has been fixed.
L00020800 An InputOutput or Output extended attribute should
not display a "bounce" when set to a new value.
Problem:
When the user sets a new value for an InputOutput or Output extended attribute,
the new value is immediately set, then reset back to the old value after the
next scan cycle, and finally sets the new value after several scan cycles. This
behavior has been fixed, with the exception of attributes that have runtime set
handlers.
L00018440
Exporting more than 32,768 objects at a time is not supported.
Problem:
If you export more than 32,768 objects at a time, the process appears to work
fine. If you import those objects, those objects beyond the allowed number are
null objects. Export objects in groups smaller than 32,768.
L00020157 Applying IAS 1.5 P01 patch does not
work on IAS 1.0 installation.
Problem:
Patches are intended to be applied to specific versions. This patch will not
work with IAS 1.0.
©
2003 Invensys Systems, Inc. All Rights Reserved.