I/A Series® System

RemoteWatch V3.1
Release Notes

B0860RE

Rev A
February 11, 2011
Invensys, Foxboro, I/A Series, and the Invensys logo are trademarks of Invensys plc, its subsidiaries, and
affiliates.
All other brand names may be trademarks of their respective owners.

Copyright 2011 Invensys Systems, Inc.

All rights reserved

SOFTWARE LICENSE AND COPYRIGHT INFORMATION

Before using the Invensys Systems, Inc. supplied software supported by this documentation, you
should read and understand the following information concerning copyrighted software.
1. The license provisions in the software license for your system govern your obligations
and usage rights to the software described in this documentation. If any portion of
those license provisions is violated, Invensys Systems, Inc. will no longer provide you
with support services and assumes no further responsibilities for your system or its
operation.
2. All software issued by Invensys Systems, Inc. and copies of the software that you are
specifically permitted to make, are protected in accordance with Federal copyright
laws. It is illegal to make copies of any software media provided to you by
Invensys Systems, Inc. for any purpose other than those purposes mentioned in the
software license.
Contents
Figures..................................................................................................................................... v

Tables.................................................................................................................................... vii

Preface.................................................................................................................................... ix

1. Overview ........................................................................................................................... 1

2. Enhancements ................................................................................................................... 3
2.1 RW 50 Series Data Acquisition Software ............................................................................ 3
2.2 RW 70 Series Data Acquisition Software ............................................................................ 3
2.3 RemoteWatch Server Software ............................................................................................ 3
2.3.1 RemoteWatch DCS Monitoring Applications ............................................................. 3

3. Operational Recommendations ......................................................................................... 5

3.1 RW 50 Series Data Acquisition Software ............................................................................ 5
3.2 RW 70 Series Data Acquisition Software ............................................................................ 5
3.2.1 RW_WinExec_Service ................................................................................................ 5
3.2.2 distribute_mbxCfg.vbs File Not Found Error .............................................................. 5
3.2.3 Operating System Resource Usage Data ...................................................................... 5
3.3 RemoteWatch DCS Monitoring Applications ..................................................................... 6
3.4 Station Access Manager ....................................................................................................... 6
3.4.1 Discovery Files ............................................................................................................ 6

4. Installation Notes .............................................................................................................. 7

4.1 RW 50 Series Data Acquisition Software ............................................................................ 7
4.2 RW 70 Series Data Acquisition Software ............................................................................ 7
4.2.1 Set the Default Scripting Interface to CScript .............................................................. 7
4.2.2 70 Series DAS Version 1.0 Uninstallation ................................................................... 8
4.2.3 70 Series DAS Version 2.0 Uninstallation ................................................................... 8
4.2.4 Miscellaneous DAS 2.0 Uninstall Notes .................................................................... 10
4.2.5 70 Series RW DAS 3.0 for Pre-I/A Series Version 8.5 Uninstall Notes ...................... 10
4.2.6 70 Series RW DAS 3.0 for I/A Series Version 8.5 Uninstall Notes ............................ 12
4.3 RemoteWatch DCS Monitoring Applications ................................................................... 12
4.4 Station Access Manager ..................................................................................................... 13

5. Problems Resolved .......................................................................................................... 15

5.1 50 Series RW Data Acquisition Software .......................................................................... 15
5.1.1 50 Series RW DAS on I/A Series V8.3 Stations (CAR 1013931, CAR 1013887) ...... 15
5.1.2 Use of FTP in Place of RCP for File Transfer (CAR 1012884) ................................. 15

iii
B0860RE – Rev A Contents

5.1.3 50 Series AWs Hosting Multiple LAN Modules (CAR1011264) .............................. 15

5.1.4 Success or Failure Message for 50 Series Installation (CR FM#29785) ...................... 15
5.1.5 Error Messages When Installing on 50 Series Solaris Station (CR FM# 29709) ........ 16
5.1.6 Mailbox and Manual Entry of Two Configuration Files (CR FM#30031) ................ 16
5.1.7 Linking Multiple I/A Series Systems with Non-Unique
Station Names to a Single RWS (CR FM#30032) ............................................................. 16
5.1.8 Removal of Old Data Files on Each RW DAS Execution (CR FM#30037) .............. 17
5.2 70 Series RW Data Acquisition Software .......................................................................... 17
5.2.1 RW DAS File Transfer Mechanism To Use FTP To Replace
Microsoft® Mapped Drive (CAR 1012875) ...................................................................... 17
5.2.2 I/A Quick Fix 1009256 (CR FM#29907) ................................................................. 17
5.2.3 70 Series RW DAS Collection of FCP270 and ZCP270
Database Resource Information (CR FM#30000) .............................................................. 18
5.2.4 70 Series RW DAS Installation D: Drive Access (CAR 1013288) ............................. 18
5.2.5 frev.exe Not Correctly Releasing OM Objects (CAR1013351) ................................. 18
5.2.6 P92 Style J (Dell T3400) and 70 Series RW
DAS File Transfer to RW Server Failure (CR FM#29957) ................................................. 18
5.2.7 The diag_dbvu.vbs Data Probe Reports Incorrect Number
of Local and Remote Linkages (CR FM#29999) ................................................................ 19
5.2.8 RW DAS Installation Failure on Standard I/A Series V8.5
Terminal Server (CAR 1018223) ....................................................................................... 19
5.2.9 RW_WinExec Service Startup Failure on a Standard
I/A Series V8.5 Terminal Server (P91/P90) after a Reboot (CR FM#30167) ..................... 19
5.2.10 Windows Operating System Resources Collected by
70 Series RW DAS (PER3346) .......................................................................................... 19
5.2.11 RW DAS Re-install Failure on I/A Series V8.5 AWs (CRs FM#29982, FM#29992) 20
5.2.12 das_frevinfo.vbs Data Probe Failure on I/A Series V8.1
and V8.1.1 P92 Stations (CAR 1013746) .......................................................................... 20
5.2.13 70 Series Mailbox and Fist Configuration Data Files
Manually Updated on Each 70 Series Station (CR FM#30031) ......................................... 21
5.2.14 Linking Multiple I/A Series Systems with Non-Unique
Station Names to a Single RWS (CR FM#30032) ............................................................. 21
5.2.15 Removal of Old Data Files on Each RW DAS Execution (CR FM#30037) ............ 22
5.2.16 Archive File Transfer to RW Server Failure (CR FM#30067, FM#30129) .............. 22
5.3 RemoteWatch Monitoring ................................................................................................ 22
5.3.1 Linking Multiple I/A Series Systems with Non-Unique
Station Names to a Single RWS (CR FM#30032) ............................................................. 22
5.3.2 ISFService Improper Processing of Multiple diagfist Files (CR FM#29885) .............. 23
5.3.3 XML Data Files for 50 Series Station Contain Incorrect
Timestamp Values (CAR 1013402) ................................................................................... 23
5.3.4 Improve Efficiency of 70 Series Data File Processing by
Extracting Archive to RW Server DAS Center Repository Folder (CAR 1013760) ............ 23
5.3.5 IFS Error Handling and Reporting (CR FM#29979) ................................................ 24
5.3.6 IFS Services Logging Level for Each Service (CR FM#30091) ................................... 24
5.3.7 svc_cpy.cmd Cannot Copy Folders ........................................................................... 24

iv
Figures
4-1. CScript Confirmation ................................................................................................... 8
4-2. After Installation Dialog .............................................................................................. 11
4-3. Finish Admin Install Dialog ........................................................................................ 11

v
B0860RE – Rev A Figures

vi
Tables
1-1. Release Media for RemoteWatch 3.1 ............................................................................ 1
1-2. Release Documentation for RemoteWatch 3.1 .............................................................. 1

vii
B0860RE – Rev A Tables

viii
Preface
This document provides the release notes for RemoteWatch 3.1.

Revision Information
This is the initial release of the document.

Reference Documents
In addition to the information presented herein, you should be familiar with the following
I/A Series® documents:
 RemoteWatch I/A Series Data Acquisition System (DAS) Version 3.1 Installation and
Configuration (B0860AQ)
 RemoteWatch Server Day 0 Restoration Guide (B0860AG)
 RemoteWatch Server DCS Monitoring Version 3.1 Upgrade (B0860AR)
 RemoteWatch Server Software Version 3.1 Installation Guide (B0860AS)
 RemoteWatch User's Guide (B0860AJ)
 Station Access Manager User's Guide (B0860AF)
Most are available on the I/A Series RemoteWatch Electronic Documentation CD-ROM
(CG500DM). The latest revisions may also be available through the IOM Global Customer Sup-
port Center at http://support.ips.invensys.com.

Glossary of Terms
$DAS $DAS is used to abbreviate the folder used as the root of the RW DAS
application. For 50 Series stations $DAS equates to
/opt/fox/bin/remote/tools/DAS. For 70 Series stations $DAS
equates to D:\opt\fox\bin\remote\tools\DAS.

RemoteWatch RemoteWatch is a service that provides a diagnostic and dispatch interface

for Distributed Control System resource usage issues. This service allows
Invensys Operations Management (IOM) engineers to remotely trouble-
shoot issues before they become more serious problems. In addition,
RemoteWatch provides the capability for end-users to view and report
DCS information and resource usage, as well as the ability to download
additional files to be deployed on your RemoteWatch Server.
The name RemoteWatch supersedes the previous name “Device Relation-
ship Management (DRM).”

RemoteWatch The RemoteWatch Server is the central point of control for the Remote-
Server Watch system at your site. The RemoteWatch Server collects data from an

ix
B0860RE – Rev A Preface

I/A Series system, which are then historized and transferred to the IOM
Global Customer Support Center where RemoteWatch engineers can
monitor the health of the system.
The RemoteWatch Server also provides a connection between IOM and
your site that allows IOM experts to remotely view and troubleshoot
issues from the IOM Global Customer Support Center. Using the remote
connection, it is possible navigate through an I/A Series system to deter-
mine and fix the source of the problem and before it is allowed to escalate.
The name RemoteWatch Server supersedes the previous names “Sentinel
Server”, “Site Server”, and “Plant Sentinel”.

x
1. Overview
This chapter describes the contents of the RemoteWatch 3.1 release.
The RemoteWatch 3.1 GCS application contains:
 RemoteWatch DCS Monitoring (a.k.a. Device Relationship Management, or DRM)
software enhancements and defect corrections related to remotely monitoring DCS
resources (or assets).
 Station Access Manager (SAM) software related to accessing I/A Series workstations
(AWs and WPs) from the RemoteWatch Server. SAM is not updated in the RW 3.1
Release.
The RemoteWatch DCS Monitoring application package changes are:
 RemoteWatch 50 Series DAS (executes on 50 Series workstations with I/A Series
Version 6.3 and newer software)
 RemoteWatch 70 Series DAS (executes on 70 Series workstations with I/A Series
Version 6.3 and newer software)
 Invensys File Services (executes on RemoteWatch Server)
The Invensys Resource Web application is not updated by the RemoteWatch 3.1release.

Table 1-1. Release Media for RemoteWatch 3.1

Part Number Description

CG500BH I/A Series Remote Plus for 70 Series Workstations
CG500EH RW Version 3.1 Data Acquisition Software
CG500DN Station Access Manager (SAM)
CG500DM RemoteWatch Documentation
GC500EJ RW Version 3.1 RemoteWatch Server Applications

Table 1-2. Release Documentation for RemoteWatch 3.1

Part Number Description

B0860AS RemoteWatch Server Software Version 3.1 Installation Guide
B0860AQ RemoteWatch I/A Series Data Acquisition System (DAS) Version 3.1
Installation and Configuration
B0860AF Station Access Manager User's Guide
B0860AG RemoteWatch Server Day 0 Restoration Guide
B0860AR RemoteWatch DCS Monitoring Version 3.1 Upgrade
B0860AJ RemoteWatch User Guide

1
B0860RE – Rev A 1. Overview

2
2. Enhancements
This chapter describes the enhancements for RemoteWatch 3.1 software.
The following software packages have been enhanced:
 RemoteWatch 50 Series Data Acquisition (RW DAS)
 Remotewatch 70 Series Data Acquisition (RW DAS)
 RemoteWatch Server Software

2.1 RW 50 Series Data Acquisition Software

50 Series RW DQAS is enhanced to:
 Execute on an I/A Series V8.3 station (50 Series) (CAR 1013931, CAR 1013887)
 Use File Transfer Protocol (FTP) to transfer files to the RW Server. In previous
releases, the rcp (UNIX® remote copy) protocol was used. (CAR 1012884)

2.2 RW 70 Series Data Acquisition Software

70 Series RW DQAS is enhanced to:
 Use File Transfer Protocol (FTP) to transfer files to the RW Server. In previous
releases, the rcp (UNIX remote copy) protocol was used. (CAR 1012875)
 Support FCP270s and ZCP270s database data collection
 Collect AW processor and memory usage.

2.3 RemoteWatch Server Software

2.3.1 RemoteWatch DCS Monitoring Applications
The Invensys File Services is updated to process the data files transferred to the RW Server using
FTP.

3
B0860RE – Rev A 2. Enhancements

4
3. Operational Recommendations
This chapter describes the operational recommendations for RemoteWatch 3.1.

3.1 RW 50 Series Data Acquisition Software

Currently there are no 50 Series DAS operational recommendations.

3.2 RW 70 Series Data Acquisition Software

3.2.1 RW_WinExec_Service
The RW_WinExec_Service logs events to a flat text log file located in the
d:\opt\fox\bin\remote\tools\DAS\Logs directory and to the Windows® Event Log under
the Application section.
RW_WinExec_Service operational parameters such as its periodic execution rate for the probe
scripts, logging enable/disable, start delay can be adjusted via a flat text INI file that is located in
the d:\opt\fox\bin\remote\tools\DAS\cfg directory. It is strongly recommended that the
Execution_Interval be NO LESS than 60 minutes and the default Run_Interval be NO LESS
than 5 seconds.
RW_WinExec_Service executes probe scripts based on entries in the tasklist.csv file. The
tasklist.csv file is updated to contain an extra field for a time-out value. This time-out value is
used as a watchdog timer such that if the script takes too long (hangs for some reason), it can be
terminated automatically by the service instead of hanging the whole DAS application. If a certain
probe script is constantly timing out, the timer value can be lengthened up to a maximum of 15
minutes.

3.2.2 distribute_mbxCfg.vbs File Not Found Error

The distribute_mbxCfg.vbs program fails with a "File Not Found Error" error message. This fail-
ure occurs when the FistHost.txt file cannot be found in the
d:\opt\fox\bin\remote\tools\DAS\install\mbxCfg folder. If this error occurs, copy the
FistHost.txt file from the d:\opt\fox\bin\remote\tools\DAS\cfg folder to the
d:\opt\fox\bin\remote\tools\DAS\install\mbxCfg folder. This error does not occur on
the station used to install the 70 Series RW DAS software.

3.2.3 Operating System Resource Usage Data

On I/A versions 7.x, 8.0.B, 8.1 and 8.1.1, the operating system performance parameters captured
in the opsys.LETTERBUG.xml (where LETTERBUG is replaced with 70 Series station letter-
bug) may not be accurate. This is caused by defects in the MS WMI interface and in most cases is
solved by insuring that all the MS Patches specified at http://support.ips.invensys.com/content/Secu-
rity/mspatch/XP.ASP are installed. Even with the patches installed the free physical memory value
is not correct.

5
B0860RE – Rev A 3. Operational Recommendations

3.3 RemoteWatch DCS Monitoring Applications

Currently there are no operational recommendations for the DCS Monitoring applications, i.e.
Invensys File Services, Invensys Resource Web, and NextNine Virtual Service Engineer (VSE).

3.4 Station Access Manager

Windows XP stations only allow one user to be logged in at a time. When connecting using
Remote Desktop to a Windows XP station, if another user is currently logged in then they will be
logged off and you will resume their session. If this functionality is not desired, Remote Desktop
can be disabled for Windows XP stations in the Configuration Tool found in the Start menu.
When connecting to a Windows XP station with Remote Desktop, the NetOp host application
will stop functioning properly. Any subsequent attempts to connect with NetOp will fail until the
NetOp Host software is restarted on the Windows XP station. This applies to NetOp versions 9.0
and earlier.

3.4.1 Discovery Files

The Discovery script for Windows stations does not collect information for stations running
Windows Server® 2000/2003. These stations have to be entered manually.
If you get no network information from running the Discovery script on Solaris™ stations, verify
that the script is being run from the C shell. To switch to the C shell, type csh.

6
4. Installation Notes
This chapter describes the installation notes for RemoteWatch 3.0.

4.1 RW 50 Series Data Acquisition Software

The 50 Series DAS version 3.0 software is installed without having to uninstall the previous ver-
sion.

4.2 RW 70 Series Data Acquisition Software

The user should pay close attention to the installation prerequisites in Chapter 2 of the Remote-
Watch DAS Version 3.1 Installation and Configuration document (B0860AQ).
If DAS version 2.0 is already installed on the I/A Series AW70 Workstations - it must be un-
installed prior to installing DAS version 3.1. Refer to “70 Series DAS Version 2.0 Uninstallation”
on page 8 for the instructions to uninstall DAS version 2.0.
If DAS version 3.0 is already installed on the I/A Series AW70 workstations, it must be unin-
stalled prior to installing DAS version 3.1. Refer to “70 Series RW DAS 3.0 for Pre-I/A Series Ver-
sion 8.5 Uninstall Notes” on page 10 or “70 Series RW DAS 3.0 for I/A Series Version 8.5
Uninstall Notes” on page 12 for the instructions to uninstall DAS version 3.0.
DAS version 3.1 should be installed from a command window with the screen buffer properties
set for 200 characters across and at least 300 lines down. The progress of the installation process
can be followed on the command window. Refer to the B0860AQ document under the Chapter
titled “70_Series_RW_DAS Software Installation”. Step 3 of the installation process details the
instructions for setting the screen buffer properties.
The installation process automatically propagates to Version 6.x workstations (from Version 7.x
workstations) without using a separate installation process for Windows NT-based workstations.
It is vital that the Windows Simple File Sharing property be disabled on each 70 Series work-
station that is to have DAS installed. This is described in Chapter 2 of B0860AQ as well. If Sim-
ple File Sharing is enabled, the installation process cannot remotely install DAS to other
workstations on the network. The installation script may terminate with a Permission Denied or
Access Denied error.

4.2.1 Set the Default Scripting Interface to CScript

The default scripting engine for the Windows® Operating System is WScript. This must be
changed to CScript for proper scripting operation. For the purposes of the RW_DAS installation,
this procedure only needs to be performed on the workstation where the installation will be initi-
ated.
1. In a command window (Start->Run cmd), enter wscript//H:cscript and press
<Enter>.
2. A dialog box specifying CScript will be displayed, as shown in Figure 4-1.

7
B0860RE – Rev A 4. Installation Notes

Figure 4-1. CScript Confirmation

3. Click OK.

4.2.2 70 Series DAS Version 1.0 Uninstallation

DAS Version 1.0 must be uninstalled from all I/A Series workstations that have it installed. This
must be performed manually. For each workstation on which DAS Version 1.0 is installed, pro-
ceed as follows:
1. Delete the scheduled task “drmDasTask.” On Windows XP workstations, “Scheduled
Tasks” is located in the Control Panel. On Windows NT workstations, “Scheduled
Tasks” is located in Windows Explorer towards the bottom of the My Computer tree.
In either case, select the Scheduled Tasks folder. Then select drmDasTask and
delete it.
2. If there are any log files or XML result files that you want to save, save them now. Sav-
ing these files is not required.
3. Using Windows Explorer, navigate to d:\opt\fox\bin\remote\tools and delete
the \Das folder and everything under it including all folders and files.

4.2.3 70 Series DAS Version 2.0 Uninstallation

If DAS Version 2.0 exists on a 70 Series workstation on which you want to install DAS
Version 3.0, DAS Version 2.0 must be removed first. A script (70_DAS_20_Uninstall.vbs) is pro-
vided on the RW Version 3.0 Data Acquisition Software CD-ROM (CG500EH) to aid in the
uninstallation process.
Up to two separate DAS 2.0 packages can be installed on any workstation: “70_Series_DAS” and
“70_Dist_Install”. To uninstall both these packages, the 70_DAS_20_Uninstall.vbs script makes
two passes during its execution.
The first pass uninstalls the 70_Series_DAS package from every workstation on a list created by
the 70_DAS_20_Uninstall.vbs script and removes the d:\opt\fox\bin\remote\tools\das
directory structure. By removing the 70_Series_DAS packages first, more control is provided over
the uninstallation session.

8
4. Installation Notes B0860RE – Rev A

The second pass uninstalls the 70_Dist_Install package and the directory
d:\opt\fox\bin\remote\DAS_Dist_Install.
While not every workstation will have the 70_Dist_Install package, all have the 70_Series_DAS
package.
Perform the steps below:
1. If there are any logs or XML results files that should be saved on any of the worksta-
tions, save them now. Saving these files is NOT required.
2. Set the default script interface as described in “Set the Default Scripting Interface to
CScript” on page 7.
3. Insert the RW Version 3.0 Data Acquisition Software CD-ROM (CG500EH) into
the CD-ROM drive.
4. Open a command window to E:\70_Series_DAS and adjust the command window
screen buffer properties as follows:
a. Open a command window.
b. Select the title-bar, right-click it and select Properties.
c. In the Properties dialog box, select the Layout tab. Under Screen Buffer size, set
the width to 200 and the height to 300. Click OK twice to save the settings for
this command window session.
5. Execute the script 70_DAS_20_UnInstall.vbs.
6. A dialog box appears with a message indicating that a list of all workstations which
can be remotely uninstalled from this station will be presented in Notepad for editing.
Any stations removed from the list will NOT have the Version 2.0 70_Series_Das
package removed by this script. Click OK.
7. Notepad appears with the list of the workstations that can be reached by this worksta-
tion. Edit the file as desired. Then save and close Notepad.
8. A second dialog box appears prompting for the fox account password for each work-
station. This is followed by another dialog box asking (yes / no) if you want to use the
same password for all of the workstations. This yes/no prompt occurs only once.
Click either as desired.
9. The script proceeds and uninstalls the packages from the workstations in the list. A
log file dist_uninstall.log is saved in the d:\Temp\das_dist_install direc-
tory.
10. On each AW70, manually check for the existence of the
d:\opt\fox\bin\remote\tools\Das directory. If it is still present, delete it.
It is possible that some scheduled DAS task may have been running at the time the
DAS Version 2.0 uninstallation procedure occurred. If this happened, the \Das direc-
tory will not have been removed. For I/A Series version 8.x workstations, this typically
occurs as files that are created after the DAS Version 2.0 installation (such as logs and
XML files, etc.) are not removed as noted in “Miscellaneous DAS 2.0 Uninstall
Notes” on page 10.

9
B0860RE – Rev A 4. Installation Notes

4.2.4 Miscellaneous DAS 2.0 Uninstall Notes

There is an operational difference between I/A Series version 7.x and 8.x workstations when using
the 70_DAS_20_Uninstall script. When the 70_DAS_20_Uninstall script runs the uninstallation
of 70_Series_DAS on I/A Series version 8.x workstations, not all of the files are removed from the
\DAS directory. The files not removed include the various logs and XML output files that exist
after the original DAS Version 2.0 installation. The entire \DAS directory is removed on
I/A Series 7.x workstations including the logs and XML output files.
If the 70_DAS_20_UnInstall script is NOT used, it is important that the packages be removed
via the Add/Remove Programs feature FIRST before manually deleting any files via Windows
Explorer. Otherwise, the package entries cannot be removed from the Add/Remove Programs
list.
If the 70_Dist_Install package is removed manually via the Add/Remove programs, it will use the
local StationsToInstall.txt file located in d:\opt\fox\bin\remote\Das_Dist_Install
to remove the 70_Series_Das packages from all of the workstations in this list.

NOTE
Be aware that this does not appear to work for workstations with I/A Series version
8.x. On these I/A Series workstations, if the 70_DAS_20_Uninstall script is not
used, the packages must be uninstalled via the Add/Remove Programs feature on
each workstation. Additionally the Das_Dist_Install directory must be removed and
the …tools\Das directory tree as well.

If a workstation is removed from the local stationsToInstall.txt file and then the
70_Dist_Install package is run manually from the Add/Remove Programs feature, the
70_Series_Das package will not be uninstalled from the workstation that has been removed from
the list. However, if subsequently 70_Series_Das is removed manually from a workstation that
was NOT in StationsToInstall.txt, the Das_Dist_Install directory is NOT cleaned up on
that workstation. This directory must be removed manually via Window Explorer or a command
window.

4.2.5 70 Series RW DAS 3.0 for Pre-I/A Series Version 8.5

Uninstall Notes
If the 70_Series_RW_DAS software must be uninstalled for any reason, use the following proce-
dure:
1. Insert the CD-ROM (part number CG500EH) into the CD-ROM drive.
2. Open a command window to E:\70_Series_DAS.
3. Execute the script SetScriptMode.vbs
4. Execute the script 70_RW_Uninstall.vbs. This script may take some time to exe-
cute especially if the RW_Winexec_Service is pending on completion of a data acqui-
sition task before it can be stopped and removed.
5. On some 70 Series stations, after the password is entered two additional dialog boxes
are displayed. See Figure 4-2 and Figure 4-3.

10
4. Installation Notes B0860RE – Rev A

Figure 4-2. After Installation Dialog

If Figure 4-2 is displayed, wait 30 seconds and click Next. When Figure 4-3 is dis-
played, ignore the text contained in the dialog box and click Finish.

Figure 4-3. Finish Admin Install Dialog

6. To verify that the un-install operation executed properly, check the Add/Remove
Software applet on the workstations and verify the package
70_Series_RW_DAS_x.x is not present.
This completes the removal of the 70 Series DAS software (Version 3.0) on 70 Series workstations
with I/A Series software versions 6.x, 7.x and 8.0 through 8.4.
For operational details of the 70_Series_RW_DAS, refer to the RemoteWatch User's Guide
(B0860AJ).

11
B0860RE – Rev A 4. Installation Notes

4.2.6 70 Series RW DAS 3.0 for I/A Series Version 8.5 Uninstall
Notes
If the RW_WinExec DAS software must be uninstalled for any reason, use the following proce-
dure:
1. Login to the proper account for installation:
a. For a secure system, use the IA Installer account. Typically, the name is IAIn-
staller.
b. For a standard system, use the fox account.
2. Open a command window to d:\opt\fox\bin\remote\tools\DAS\install.
3. Execute the script uninstall_70.cmd. This script may take some time to execute
especially if the RW_Winexec service is pending on completion of a data acquisition
task before it can be stopped and removed.
4. On secure I/A Series systems, if the IA Installer account is not named IAInstaller, the
following occurs:
a. A dialog box asks if the I/A Installer account has been renamed.
b. If Yes is selected, another dialog box prompting for the IA Installer account name
appears. Enter the new account name, and click OK.
5. When prompted, select the station(s) to uninstall.
6. If a remote workstation is contained in the list of stations to uninstall, then proceed as
follows:
 On a standard I/A Series system, enter the fox account password at the prompt.
 On a secure I/A Series system, perform the following:
 In the dialog box, indicate whether or not the I/A Services account has been
renamed.
 If the IA Services account has been renamed, another dialog box appears.
Enter the new name and click OK.
 Enter the IA Services account password and click OK.
7. To verify that the un-install operation executed properly, check the Add/Remove
Software applet on the workstations and verify the package RW_WinExec_Pkg is
not present.
This completes the removal of the 70 Series DAS software (Version 3.0) on 70 Series workstations
with I/A Series V8.5 software.
For operational details of the RW_WinExec DAS, refer to the RemoteWatch User's Guide
(B0860AJ).

4.3 RemoteWatch DCS Monitoring Applications

The RemoteWatch DCS Monitoring applications are preinstalled on the RemoteWatch Server
before shipment to the customer's location.
RemoteWatch Servers that exist at a customer's location (either commissioned or not yet commis-
sioned) require the Invensys File Services application be updated to IFS version 3.1. The proce-

12
4. Installation Notes B0860RE – Rev A

dure for this update is contained in the RemoteWatch DCS Monitoring Version 3.1 Upgrade
document (B0860AR).
The Invensys Resource Web and NextNine VSE software is unchanged in the RemoteWatch 3.0
release.

4.4 Station Access Manager

The Station Access Manager (SAM) application utilizes several third-party applications to initiate
remote sessions to other stations. These applications include NetOp Remote Control Guest,
FileZilla FTP Client, and Hummingbird Exceed. It is recommended that these applications are
installed prior to installing the SAM application, although this is not necessary. If any of these
applications are not installed, that functionality will not work in SAM application. They can be
installed at a later time and configured using the Configuration Tool.
During installation, the configuration tool will allow you to specify the location of the third-party
applications as well as some other options. If any of these settings need to be changed at a later
point, this configuration tool can be accessed from the Station Access Manager in the Start Menu.
NetOp and Exceed require valid licenses to run properly. FileZilla is open software and an instal-
lation package can be found on the SAM installation CD.

13
B0860RE – Rev A 4. Installation Notes

14
5. Problems Resolved
This chapter describes the problems resolved for the RemoteWatch 3.1 release.

5.1 50 Series RW Data Acquisition Software

5.1.1 50 Series RW DAS on I/A Series V8.3 Stations (CAR
1013931, CAR 1013887)
Description: The 50 Series RW DAS does not function on V8.3 50 Series stations.

Solution: The 3.1 50 Series RW DAS is updated to execute on V8.3 50 Series sta-
tions.

5.1.2 Use of FTP in Place of RCP for File Transfer (CAR 1012884)
Description: Field Support request to use FTP in place of RCP for file transfer from I/A
50 Series stations to the Remote Watch Server. Using FTP in both Solaris
and Windows environment would give a single system-wide solution for
data transfer and allow less complex firewall rules.

Solution: The 50 Series RW DAS Version 3.1 is updated to use the FTP protocol to
transfer files to the RW Server. The unix remote copy (rcp) is no longer
supported.

5.1.3 50 Series AWs Hosting Multiple LAN Modules

(CAR1011264)
Description: On 50 Series AWs that host multiple CarrierBand LAN modules, LAN
data is only collected for one LAN module.

Solution: The RW DAS data probe, g_landata, has been updated to collect data
from multiple LAN modules

5.1.4 Success or Failure Message for 50 Series Installation (CR

FM#29785)
Description: The 50 Series RW DAS installation software does not output a success or
failure message.

Solution: The installation software is updated to provide a success or failure message

when the installation is completed.

15
B0860RE – Rev A 5. Problems Resolved

5.1.5 Error Messages When Installing on 50 Series Solaris Station

(CR FM# 29709)
Description: While installing 50 Series RW DAS on a Solaris station with I/A version
7.2.1 I received several error messages during install:
 Installation appeared to be successful... but no indication.
 When I ran validateEngine I received the following:
Comm: ... /cfg/DasSumsList: No such file or directory
DAS software successful validation

Solution: The installation software and the validateEngine utility have been updated
to correct these issues.

5.1.6 Mailbox and Manual Entry of Two Configuration Files (CR

FM#30031)
Description: The 50 Series mailbox and fist configuration data files are built and dis-
tributed dynamically, during installation. When the mailbox station or fist
station is changed this required that two configuration files on each 50
Series station has to be manually entered.

Solution: The configuration of the mailbox and fist configuration files is divided
into two separate functions:
 Discovery of FistHost station for the system and the DAS Mailbox
stations for each node
 Distribution of the discovered information to the DasMailBox.txt
and FistHost.txt files on each 50 Series station on the system.
The discovery of the FistHost and DAS MailBox stations is performed
during installation by the $DAS/install/cfgDasMbox.sh program,
which results in a mbxcfg.csv file and a FistHost.txt file both located in the
$DAS/cfg directory.
Distribution of the discovered information to the DasMailBox.txt and Fis-
tHost.txt files on each 50 Series station on the system is done by the
$DAS/install/distMboxfiles.sh program
This allows the user to update the DasMailBox.txt and FistHost.txt files
on all 50 Series station from a single location (i.e., computer) and then
distribute the files to all the 50 Series stations on the I/A system.

5.1.7 Linking Multiple I/A Series Systems with Non-Unique

Station Names to a Single RWS (CR FM#30032)
Description: The ability to link multiple I/A Series systems to the RWS has yielded the
problem of multiple stations with the same name needing to be processed.
Usually, the way the current system handles multiple systems with same
name is by placing the system name in front of the second station’s letter-

16
5. Problems Resolved B0860RE – Rev A

bug (for example, unit2_AW0001); however, this functionality is not sup-

ported on 50 Series stations.

Solution: A prefix for a 50 Series station is specified in the $DAS/cfg/setvars file,

using the rtTARPREFIX variable. If the variable is specified as rtTAR-
PREFIX = “”, then no prefix is used. The prefix is added to the tar files
send to the RW Server. The RW Server's Invensys File Services application
builds the XML data files based on the prefix of the tar files.

5.1.8 Removal of Old Data Files on Each RW DAS Execution (CR

FM#30037)
Description: The RawOut and XMLOut data folders used by the RW DAS application
on I/A workstations are never cleaned up. When system configuration is
modified old files continue to be copied to the VSE causing stale data
alarms. On Solaris this appears to only be station counter files but in Win-
dows, it is all files. Output folders should be cleaned after the files are suc-
cessfully sent to the VSE. This is causing a big problem with customers
since they are being notified about alarms on stations that no longer exist.
Our engineers also feel required to log onto the VSE and validate alarms
before they report them to the customer.

Solution: At the start of each execution cycle, the 50 Series RW DAS deletes all the
files contained in the $DAS/RawOut, $DAS/ferret_out, and
$DAS/files_out directories.

5.2 70 Series RW Data Acquisition Software

5.2.1 RW DAS File Transfer Mechanism To Use FTP To Replace
Microsoft® Mapped Drive (CAR 1012875)
Description: The 70 Series RW DAS for I/A V6.3 through 8.4.x uses the Windows
Operating System mapped drive mechanism to transfer data to FTP root
on the Remote Watch Server. Customer requesting we use Internet File
Transfer protocol (FTP) instead of mapped drives to comply with corpo-
rate security policy. Most security installation will not allow mapping
drives across firewalls. This has also been requested by other customer
security groups.

Solution: The 70 Series RW DAS is updated to use FTP to transfer files to the RW
Server. The transfer of DAS data files to the RW Server using the Win-
dows Operating Systems mapped drive mechanism is no longer sup-
ported.

5.2.2 I/A Quick Fix 1009256 (CR FM#29907)

Description: I/A QF 1009256 causes diag_dbvu.vbs to "hang".

17
B0860RE – Rev A 5. Problems Resolved

Solution: The diag_dbvu.vbs data probe is updated to work correctly with I/A
QF 1009256 by specifying the control station type, e.g., CP60, CP30.

5.2.3 70 Series RW DAS Collection of FCP270 and ZCP270

Database Resource Information (CR FM#30000)
Description: The 70 Series RW DAS does not collect FCP270 and ZCP270 database
resource information.

Solution: The diag_dbvu.vbs data probe is updated to process FCP270s and

ZCP270s provided that Quick Fix 1012997 installed. If Quick Fix
1012997 is not installed a error will be reported in the
$DAS\log\probes.log file.

5.2.4 70 Series RW DAS Installation D: Drive Access (CAR

1013288)
Description: The installation of the 70 Series RW DAS software on the local computer
uses the "IA" share to access the D: drive.

Solution: The installation of the 70 Series RW DAS software on the local computer
is changed to access the D: drive by the path D:\.

5.2.5 frev.exe Not Correctly Releasing OM Objects

(CAR1013351)
Description: Each time the frev.exe utility is executed by the 70 Series RW DAS soft-
ware, an OM object is used and not released.

Solution: The 70 Series RW DAS software has replaced the frev.exe utility with a
new utility, smon_get.exe. This new utility correctly manages OM
objects, i.e. creates, uses, and then releases the object.

5.2.6 P92 Style J (Dell T3400) and 70 Series RW

DAS File Transfer to RW Server Failure (CR FM#29957)
Description: The FTP utility on P92 style J (Dell T3400) is named ftp.exe.dis-
abled. This prevents the 70 Series RW DAS from transferring data to the
RW Server.

Solution: The ftp_send.vbs utility used to transfer data to the RW server is

updated to check and see if ftp.exe exists. If ftp.exe does not exist,
then ftp.exe.disabled is used, otherwise ftp.exe is used.

18
5. Problems Resolved B0860RE – Rev A

5.2.7 The diag_dbvu.vbs Data Probe Reports Incorrect Number

of Local and Remote Linkages (CR FM#29999)
Description: The diag_dbvu.vbs data probe reports the incorrect number of local
and remote linkages.

Solution: The diag_dbvu.vbs data probe is updated to correctly parse dbuv's output
and report the correct number of local and remote linkages.

5.2.8 RW DAS Installation Failure on Standard I/A Series V8.5

Terminal Server (CAR 1018223)
Description: The RW DAS software cannot be installed on a standard version 8.5 I/A
Series Terminal Server (P91/P90). The installation keeps prompting for
the installation account.

Solution: The installation software is updated to resolve this defect.

5.2.9 RW_WinExec Service Startup Failure on a Standard

I/A Series V8.5 Terminal Server (P91/P90) after a Reboot (CR
FM#30167)
Description: The RW_WinExec service does not start on a standard I/A Series V8.5
Terminal Server (P91/P90) after a reboot. If the RW_WinExec service is
started manually using the Service Control Panel the service starts without
a problem.

Solution: A defect in the RW_WinExec service's reading of the process list has been
corrected and now the RW_WinExec service starts up after a reboot.

5.2.10 Windows Operating System Resources Collected by

70 Series RW DAS (PER3346)
Description: Request to add Windows Operating system resources to the 70 Series RW
DAS.

Solution: The das_opsys.vbs data probe responsible for gathering operating sys-
tem related data is updated to collection the following kernel wide infor-
mation:
 Logical Disk Free Megabytes
 Percent of Committed Bytes in use
 Available Mbytes
 Pages/sec
 Memory pool non-paged bytes
 Memory pool paged bytes

19
B0860RE – Rev A 5. Problems Resolved

 Page file percent usage

 Percent interrupt time
 Percent processor time
 Context switches per second
 Processor queue length
In addition the das_opsys.vbs data probe collects the following data for
each process:
 Percent processor time
 Handle count
 Private bytes
 Thread count
 Virtual bytes
 Working set size

5.2.11 RW DAS Re-install Failure on I/A Series V8.5 AWs (CRs

FM#29982, FM#29992)
Description: When uninstalling RW DAS on both secure and unsecure stations, either
locally or remotely, there are read-only files left in
D:\opt\fox\bin\remote\tools\DAS\install.
Trying to reinstall DAS will result in an error because the read-only files
cannot be overwritten. They have to be removed manually before installa-
tion can occur.

Solution: In the RW DAS 3.1 release all files in the

D:\opt\fox\bin\remote\tools\DAS\install folder have a read-
write (not read-only) permission. This permits a reinstall to refresh (over-
write) files in the D:\opt\fox\bin\remote\tools\DAS\install
folder.

5.2.12 das_frevinfo.vbs Data Probe Failure on I/A Series V8.1

and V8.1.1 P92 Stations (CAR 1013746)
Description: DAS V3.0 + QF1013174 Installation on the AW70/ V8.1.1, a Windows
message box is displayed every day on the AW70 screens. This Message
box displays the following error information: frev.exe- Entry Point Not
Found. The procedure entry point fdr_SM_CHG_DST_RQ could not
be located in the dynamic link library foxfdr.dll. This problem occurs only
on the V8.1.1 I/A stations. (The V8.2 and later IA stations don't exhibit
this problem.) The cause of the problem is the DRM FREV probe sched-
uled every 24h on the AW70. The entry point ''fdr_SM_CHG_DST_RQ
'' exists in the foxfdr.dll library located in the NUTCRACKER2 (I/A
XP SP2) directory but doesn't exist in the foxfdr.dll library located in the
NUTCRACKER2 (XP SP1) directory. Temporarily, the probe FREV has
been disabled (commented in the tasklist.csv file) to avoid the problem.

20
5. Problems Resolved B0860RE – Rev A

Solution: The das_frevinfo.vbs data probe is updated to use the correct

foxfdr.dll for I/A Series workstation V8.1 and V8.1.1 (the
foxfdr.dll installed by I/A on the workstation).

5.2.13 70 Series Mailbox and Fist Configuration Data Files

Manually Updated on Each 70 Series Station (CR FM#30031)
Description: The 70 Series mailbox and fist configuration data files are built and dis-
tributed dynamically during installation. When the mailbox station or fist
station is changed, two configuration files on each 70 Series station have
to be manually entered.

Solution: The configuration of the mailbox and fist configuration files is divided
into two separate functions:
 Discovery of FistHost station for the system and the DAS Mailbox
stations for each node
 Distribution of the discovered information to the DasMailBox.txt
and FistHost.txt files on each 70 Series station on the system.
The discovery of the FistHost and DAS MailBox stations is performed
during installation by the $DAS\install\bld_mbxCfg.vbs program,
which results in a mbx_cfg.csv file and a FistHost.txt file both
located in the $DAS\install\mbxCfg folder.
Distribution of the discovered information to the DasMailBox.txt and
FistHost.txt files on each 70 Series station on the system is done by the
$DAS\install\distribute_mbxCfg.vbs program
This allows the user to update the DasMailBox.txt and FistHost.txt files
on all 70 Series station from a single location (i.e. computer) and then dis-
tribute the files to all the 70 Series stations on the I/A system.

5.2.14 Linking Multiple I/A Series Systems with Non-Unique

Station Names to a Single RWS (CR FM#30032)
Description: The ability to link multiple I/A Series systems to the RWS has yielded the
problem of multiple stations with the same name needing to be processed.
Usually, the way the current system handles multiple systems with the
same name is by placing the system name in front of the second station’s
letterbug (example, unit2_AW0001); however other programs are unable
to handle this.

Solution: All the 70 Series RW DAS programs properly generate XML data files
based on the StationPrefix specified in the $DAS\cfg\dasFiles.cfg file.
If the entry "StationPrefix =" exists then no prefix is specified.

21
B0860RE – Rev A 5. Problems Resolved

5.2.15 Removal of Old Data Files on Each RW DAS Execution

(CR FM#30037)
Description: The RawOut and XmlOut data folders used by the RW DAS application
on I/A workstations are never cleaned up. When system configuration is
modified old files continue to be copied to the VSE causing stale data
alarms. On Solaris this appears to only be station counter files but in Win-
dows, it is all files. Output folders should be cleaned after the files are suc-
cessfully sent to the VSE. This is causing a big problem with customers
since they are being notified about alarms on stations that no longer exist.
Our engineers also feel required to log onto the VSE and validate alarms
before they report them to the customer.

Solution: At the start of each execution cycle, the 70 Series RW DAS deletes all the
files contained in the $DAS\XmlOut, $DAS\ferret_out, and
$DAS\files_out directories.

5.2.16 Archive File Transfer to RW Server Failure (CR

FM#30067, FM#30129)
Description: When 70 Series RW DAS attempts to transfer the archive to the Remote-
Watch Server via FTP, it places the archive in the D:\ftp-
root\resource_das\data\7z_input directory. If the 7z_input
folder is missing, DAS places the archive file in D:\ftproot of the
RemoteWatch Server where it does not get processed by the File Services.

Solution: The ftp_data.vbs program is updated to verify the 7z_input folder

exists before starting a data transfer; if the folder does not exist, it is cre-
ated.

5.3 RemoteWatch Monitoring

5.3.1 Linking Multiple I/A Series Systems with Non-Unique
Station Names to a Single RWS (CR FM#30032)
Description: The ability to link multiple I/A Series systems to the RWS has yielded the
problem of multiple stations with the same name needing to be processed.
Usually, the way the current system handles multiple systems with same
name is by placing the system name in front of the second station’s letter-
bug (example, unit2_AW0001); however this functionality is not sup-
ported on 50 Series stations.

Solution: The RW Server's Invensys File Services 50 Series data file processing
scripts are updated to create XML data files based on the prefix of the tar
files. The prefix is added at the beginning of the "station name" section of
the XML file name, i.e. opsys.Unit1_AW0001, to all references to the
"station name" and System Monitor name within the XML data file.

22
5. Problems Resolved B0860RE – Rev A

5.3.2 ISFService Improper Processing of Multiple diagfist Files

(CR FM#29885)
Description: Multiple diagfist files will not create the single Fist file on RW Server.
Diagfist from 9 nodes present, but only two are processed. No errors given
in IS log or anywhere else. Problem duplicated in TAC lab.

Solution: The ISFService processing of the multiple diagfist files is corrected, so that
multiple diagfist files results is all stations being contained in the
d:\resource_das\data\ fist.IASystem.xml file.

5.3.3 XML Data Files for 50 Series Station Contain Incorrect

Timestamp Values (CAR 1013402)
Description: 22 Jan 2010 (PB) - The timestamp attribute contained in the xml data
files for 50 Series stations is not properly formatted. The ISFService data
processing scripts responsible for the converting the 50 Series raw data
files to the xml data file does not correctly convert the date/time attribute.

Solution: The ISFService data processing scripts responsible for the converting the
50 Series raw data files to the xml data file are updated to correctly convert
the date/time attribute.

5.3.4 Improve Efficiency of 70 Series Data File Processing by

Extracting Archive to RW Server DAS Center Repository Folder
(CAR 1013760)
Description: Each 70 Series data file is transfer individually to the RW Server. This
requires the ISFService to process each XML data file; at times, this
induces a heavy load on the ISFService and the Microsoft file watcher
mechanism.

Solution: The 70 Series XML and other data files are now sent as a file archive to the
RW server. The structure of the archive is such that data files can be
extracted by the ISTARService directly to the D:\resource_das\data
folder. This change to the file processing on the RemoteWatch Server
reduces the number of times a 70 Series data file has to be processed on
the RemoteWatch Server, thereby reducing the load on the ISFService and
the MS file watcher mechanism.

23
B0860RE – Rev A 5. Problems Resolved

5.3.5 IFS Error Handling and Reporting (CR FM#29979)

Description: Enhance IFS error handling and reporting.

Solution: The IFS software is updated to remove a possible cause of ISFService and
ISTARService failures. In addition, the event messages sent to the ISLog
eventlog are enhanced to report on intra-service queue usage in order to
provide diagnostic information about IFS service failures.

5.3.6 IFS Services Logging Level for Each Service (CR FM#30091)
Description: The IFS services do not access the event logging sections of the iscon-
fig.xml unique to the service, instead the event logging attributes are all
derived based on the first event logging attributes defined in the iscon-
fig.xml file.

Solution: The IFS Service software allows the logging level for each service, i.e. ISF-
Service, ISTARService, and ISDBService, to be specified uniquely in each
services section of the isconfig.xml configuration file.

5.3.7 svc_cpy.cmd Cannot Copy Folders

Description: svc_cpy.cmd used to process the XML input data files and the swi_out,
files_out, and ferret_out input data files located on the PS generates an
error because the program attempts to copy the folders, swi_out, files_out,
and ferret_out. The folders do not need to be copied (only the contents).

Solution: The svc_cpy.cmd is replaced with VBScript svc_cpy.vbs that does not
attempt to copy the folders. In addition the processing of files in the
d:\ftproot\resource_das\{Letterbug}\swi_out folder is elimi-
nated. This files in the swi_out folder are not used by RemoteWatch DCS
monitoring or NextNine.

24
5. Problems Resolved B0860RE – Rev A

25
Invensys Operations Management
5601 Granite Parkway Suite 1000
Plano, TX 75024
United States of America
http://www.iom.invensys.com

Global Customer Support

Inside U.S.: 1-866-746-6477
Outside U.S.: 1-508-549-2424 or contact your
local Invensys representative.
Email: iom.support@invensys.com
Website: http://support.ips.invensys.com