5 1 2007 - 210SCN PDF

Uniformance PHD
Release 210
Software Change Notice
May 2007
UNMEDX-SCN
Version 2.0
Copyright, Notices, and Trademarks
© Honeywell Inc. 1998 – 2007. All Rights Reserved.
While this information is presented in good faith and believed to be accurate, Honeywell disclaims
the implied warranties of merchantability and fitness for a particular purpose and makes no
express warranties except as may be stated in its written agreement with and for its customers.
In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The
information and specifications in this document are subject to change without notice.
Honeywell, TotalPlant, Uniformance PHD, Experion, PlantScape and Business.FLEX are U.S.
registered trademarks of Honeywell Inc.
Other brand or product names are trademarks of their respective owners.
Release Information
Uniformance PHD
Document Revision: 2.0
Document Revision Date: May 2007
Document Number: SCN-210
Model Number: UNMEDX-SCN
Honeywell Process Solutions

2500 W. Union Hills Drive
Phoenix, Arizona 85027 USA
ii • Uniformance PHD 210 Software Change Notice

Table of Contents
1. Read Me First ....................................................................................................... 9

1.1 Introduction ............................................................................................... 9
Uniformance 210 General Release ....................................................... 9
Document scope .................................................................................... 9
Uniformance PHD components ........................................................... 10
Prerequisite skills to install/upgrade and configure system................. 10
Tested/validated software .................................................................... 10
Installation/upgrade instructions .......................................................... 11
1.2 Important Notes ...................................................................................... 11
210 Release Notes .............................................................................. 11
1.3 Constraints.............................................................................................. 13
1.4 Support for Migration from Oracle 8i ...................................................... 13
1.5 Customer-Performed Installation and Upgrade Guidance ..................... 14
2. Uniformance PHD Release 210 Users and Supported Platforms................. 19

2.1 Intended Users of this Release .............................................................. 19
2.2 Main Uniformance Nodes ....................................................................... 19
2.3 Server Node Requirements .................................................................... 20
2.4 Desktop Node Requirements ................................................................. 22
2.5 PHD Configuration Tool Node Requirements ........................................ 25
Operating system................................................................................. 25
2.6 Database Node Requirements ............................................................... 26
Operating system................................................................................. 26
RDBMS ................................................................................................ 26
2.7 Other System Requirements .................................................................. 26
PHDManager ....................................................................................... 26
Remote PHDManager.......................................................................... 26
PHD OPC DA/HDA server ................................................................... 27
PHD applications (Application Server installation) .............................. 27
TPS compatibility matrix ...................................................................... 27
Uniformance PHD 210 Software Change Notice • iii

1 Read Me First
1.1 Introduction
3. Uniformance PHD Release 210 Functionality Changes ................................. 29

3.1 New Features in Release 210................................................................. 29
Experion integration.............................................................................. 29
OPC standard adherence..................................................................... 29
License keys......................................................................................... 29
.NET support ........................................................................................ 29
DCHECK utility ..................................................................................... 30
Experion RDM and System Management installation and licensing ... 30
Desktop Support for Data Enumeration ............................................... 30
Remote API .......................................................................................... 31
3.2 Uniformance PHD 210 Enhancements................................................... 32
3.3 Database Separation .............................................................................. 33
3.4 Functionality Removed or Not Supported............................................... 35
4. Uniformance PHD Release 210 Media.............................................................. 37
5. General Special Considerations....................................................................... 39

5.1 Installation Sequence for New Installs .................................................... 39
5.2 Installer Does Not Show Administrators Group in the "Select Group
Membership" List .................................................................................... 39
5.3 Experion Tag Synchronization Installation Sequence ............................ 39
5.4 APP Node Security Policies Restrict PHD User Rights.......................... 39
5.5 Upgrading from Uniformance 200/201/202............................................. 40
5.6 Incorrect Default Username for App Server Install ................................. 42
5.7 Incorrect Default Username for Namespace Server Install .................... 43
5.8 New Hardware Requirements for Oracle Upgrade................................. 44
5.9 Support for User Developed Legacy Applications .................................. 44
5.10 Legacy API Server Does Not Support Multi-threading ........................... 44
5.11 Support for Uniformance 150 PHD Server ............................................. 45
5.12 MS Loop-Back Adapter Must Be Installed on Windows 2000 and
Windows 2003......................................................................................... 45
5.13 Do NOT Delete "127.0.0.1 localhost" from the HOSTS File ................... 46
5.14 Specifying an Invalid Host Will Cause RDC Problems ........................... 46
iv • Uniformance PHD 210 Software Change Notice
1 Read Me First
1.1 Introduction
5.15 Legacy Code Needs to be Updated if Port Number is Appended to

Hostname ............................................................................................... 46
5.16 HCI installs a version of kill.exe.............................................................. 47
5.17 Silent Install of Desktop Not Supported.................................................. 47
5.18 Bug in Windows XP/2003 Telnet Client.................................................. 48
5.19 Using OPC on Windows XP SP2 or Windows 2003 SP1 ...................... 48
5.20 Queue Overwrite not Reported .............................................................. 49
5.21 Incorrect Create_sequence.sql File Generated ..................................... 49
5.22 Duplicate entries in the Add/Remove Programs Applet ......................... 50
5.23 PHD2REL PHDTagsets are lost during upgrade. .................................. 50
5.24 upgrdUnf2.cmd script could take a long time to complete. .................... 50
5.25 Possible to run out of disk space during an upgrade to Uniformance 210
when Generic Auditing enabled ............................................................. 51
6. Special Considerations for PHD Server .......................................................... 53

6.1 Large Systems Will Require Tuning ....................................................... 53
6.2 Use of PHD Server 150 Within PHD 210 Configuration......................... 53
6.3 Windows OS May Select a Port Assigned to a PHD Service................. 53
6.4 CUR Section Size to Increase Significantly............................................ 54
6.5 Mixed 150 and 200 Archives .................................................................. 54
6.6 PHDMAN INIT SYSTEM Systematically Fails with an Oracle Error ...... 54
6.7 Shutting Down a Uniformance 150 PHD Server When Using
RemotePeer150 RDI .............................................................................. 55
6.8 Archive Files Not Created by CONSTORE ............................................ 55
6.9 Data Integrity Issues if Changing Tag Type or Data Type ..................... 56
6.10 History Recovery for RDC Scheme Without a Standby Collector.......... 56
6.11 RDI Host Table Size ............................................................................... 57
6.12 Tag Synchronization............................................................................... 57
6.13 Tag Collection Rates .............................................................................. 57
6.14 PHD/Experion Link Performs Duplicate History Recovery..................... 58
Uniformance PHD 210 Software Change Notice • v

1 Read Me First
1.1 Introduction
7. Special Considerations for RDIs ...................................................................... 59

7.1 Included RDIs.......................................................................................... 59
7.2 RDISetup Fails if INTS configured for PHD Server ................................ 59
7.3 Netclient RDIs Need to be Replaced ...................................................... 59
7.4 "Unable to locate DLLs" error for PlantScape RDI ................................. 59
7.5 Using the PlantScape RDI to Access an Experion System .................... 60
7.6 Virtual Tag RDI........................................................................................60
7.7 PHD Experion Link goes to ACTIVE INACTIVE when adding or
removing tags.......................................................................................... 61
8. Special Considerations for Uniformance PHD Desktop ................................ 63

8.1 Upgrading from Uniformance 200 or Earlier ........................................... 63
8.2 Using 210 Desktop with 150 Server Can Cause Serious Issues on 150
Server...................................................................................................... 63
8.3 Visual PHD and Visual Basic .................................................................. 63
8.4 Visual PHD Login/Connection Mechanism Has Changed...................... 64
8.5 Memory and Handle Leak....................................................................... 64
8.6 EXCEL Companion ................................................................................. 64
8.7 Process Trend.........................................................................................65
8.8 Desktop Application Support for Remote API......................................... 65
8.9 User Security........................................................................................... 66
9. Special Considerations for PHD Configuration Tool (Previously Named TPI)69

9.1 Upgrading from Uniformance 200/201/202............................................. 69
9.2 PHD Configuration Tool Uses PHD_HOST Registry Entry .................... 69
9.3 Proper Shutdown of PHD Configuration Tool ......................................... 69
9.4 Data Execution Prevention (DEP) and the PHD Configuration Tools .... 70
9.5 Uniformance Password Can Not be Changed Under INTS.................... 71
9.6 Unable to Replace Text in Virtual Tag Calculation ................................. 71
9.7 Tagloader Builds Points Incorrectly ........................................................ 71
vi • Uniformance PHD 210 Software Change Notice

1 Read Me First
1.1 Introduction
9.8 Incorrect Data During TagLoad .............................................................. 72

9.9 Errors using the Microsoft ODBC Driver for Oracle ............................... 72
10. Special Considerations for Uniformance PHD Database .............................. 73

10.1 Authentication Across Mixed Domains Does Not Work ......................... 73
10.2 Watch for Duplicate Engineering Units................................................... 73
11. Special Considerations for Application Server .............................................. 75

11.1 EJC unable to collect data...................................................................... 75
11.2 EJC may crash on APP Node 211 ......................................................... 75
11.3 Installation – Recovery of Registry Settings for the Application Server . 75
11.4 EJC Needs to be Restarted if the LCN is Reset .................................... 76
12. Special Considerations for Tools .................................................................... 77
13. Special Considerations for Documentation.................................................... 79

13.1 Documentation Added to Media ............................................................. 79
13.2 Documents Renamed............................................................................. 79
14. Problems Fixed in Uniformance PHD 210....................................................... 81

14.1 PHD Problems Fixed .............................................................................. 81
PHD Server .......................................................................................... 81
PHD Calculations................................................................................. 83
PHD Data Storage / Extraction ............................................................ 84
PHD Administration.............................................................................. 87
PHD Manager ...................................................................................... 87
OPC Server.......................................................................................... 88
Tag / User Security .............................................................................. 89
Tagloader / Import / Export .................................................................. 89
14.2 RDI.......................................................................................................... 89
RDI Server ........................................................................................... 89
TypeA – Honeywell .............................................................................. 90
14.3 Desktop................................................................................................... 91
Companions ......................................................................................... 91
Uniformance PHD 210 Software Change Notice • vii

1 Read Me First
1.1 Introduction
General and Installation ....................................................................... 92

Process Trend ......................................................................................93
OLE DB Provider ..................................................................................94
Visual PHD ........................................................................................... 94
14.4 Database................................................................................................. 95
14.5 PHD Configuration Tool (previously named TPI).................................... 97
14.6 Application Server ................................................................................... 97
14.7 Documentation ........................................................................................ 98
15. Recommendations for System Administrators ............................................ 105

15.1 Disaster Recovery.................................................................................105
15.2 Anti-Virus Recommendations ...............................................................105
Overview.............................................................................................105
Recommendations..............................................................................105
16. Problem Reporting...........................................................................................107
viii • Uniformance PHD 210 Software Change Notice

1. Read Me First
MANDATORY PATCH 210.1.1 FOR PHD GENERAL RELEASE
All customers are advised that the 210.1.1 patch or later must be
downloaded and applied at all PHD release 210 sites. This
patch provides critical updates that correct installation and
migration issues, as well as improving system stability.
Customers already running the PHD 210 Controlled Release
are encouraged to apply the patch as soon as practical.
The 210.1.1 patch may be obtained on Solution Support On-
Line, or from Honeywell Support (see Section 16).
1.1 Introduction
Uniformance 210 General Release
The Uniformance 210 General Release consists of the Uniformance R210 Base/Limited
Release augmented by the Uniformance 210.1.1 Patch. Therefore, customers are strongly
encouraged to review both the R210 Software Change Notification (this document) and the
210.1.1 Patch Release Letter prior to proceeding.
The Uniformance 210.1.1 Patch is available for electronic download from SSOL or may be
obtained on request from Honeywell Support (see Section 16).
Only individuals who have received Honeywell training in PHD installation and upgrade
should attempt PHD installation. Such individuals must also be familiar with the PHD
system, Windows system management, and network management.
Document scope
This document contains information a customer needs for this Uniformance release,
including last minute changes not included in the product documentation. The document
includes information the customer must read before installing the software. The Special
Considerations section may include information on known defects and related information
such as risks, workarounds, and how to avoid the defect.
Because the Uniformance 210.1.1 Patch is an integral part of this release, this document
must be read in conjunction with the 210.1.1 Patch Release Letter to get a complete
overview of the Uniformance 210 product.
Uniformance PHD 210 Software Change Notice • 9

1 Read Me First
1.1 Introduction
Uniformance PHD components

Uniformance PHD 210 contains the following major components:
• Process History Database (PHD) Server
• OLE For Process Control (OPC) Server - Data Access (DA) 3.0 compliant/
Historical Data Access (HDA) 1.2 compliant
• Experion tools including an integrated data interface and a tag synchronization

capability
• Type A Real-Time Data Interfaces (RDIs)
• Uniformance PHD Desktop
• PHD Configuration Tool - previously named Total Plant Information (TPI)
• Uniformance Database on Oracle 9.2
• Uniformance PHD applications
Prerequisite skills to install/upgrade and configure system

Honeywell made every attempt to simplify the installation and configuration tasks for
Uniformance; however, the Uniformance product is a complex system requiring technical
expertise. See Section 1.5 Customer Upgrade Guidance for the prerequisite skills to install
or upgrade and configure the system.
Existing system upgrades require careful planning and staging. Honeywell has qualified
engineers that would be pleased to assist in this activity in order to facilitate a smooth
upgrade and minimize the impact to plant operations.
Tested/validated software
Uniformance PHD 210 has been validated on the basic North American English language
versions of the following:
• Windows 2000 Server (SP4)

• Windows 2003 Standard (SP1)
• Windows 2003 Enterprise (SP1)
• Windows 2003 R2 – Requires PHD release 210.1.1 or later
Uniformance PHD 210 has not been tested or validated with non-English language
versions or the various specialized versions of Windows Server including, but not limited
to the following:
10 • Uniformance PHD 210 Software Change Notice

1 Read Me First
1.2 Important Notes
• Internet Information Server

• SQL Server
• Small Business Server
Installation of the non-tested/validated products on a PHD server is not supported and may
result in PHD errors.
If unsure whether Uniformance PHD 210 is compatible with any specific Windows
configuration, customers are advised to consult Honeywell Solution Support Online
(SSOL) or TAC to obtain the latest information regarding the operation of Uniformance
PHD 210 in the proposed Windows environment.
Installation/upgrade instructions
Please see the following Special Considerations sections in this document:
• Section 5, General Special Considerations
• Section 6, Special Considerations for PHD Server
• Section 7, Special Considerations for RDIs
• Section 8, Special Considerations for Uniformance PHD Desktop
• Section 9, Special Considerations for PHD Configuration Tool (Previously Named TPI)
• Section 10, Special Considerations for Uniformance PHD Database
• Section 11, Special Considerations for Application Server
1.2 Important Notes

210 Release Notes
1. Please read the Special Considerations sections prior to installation and use.
2. It is strongly recommended that Uniformance PHD customers using PHD Server
releases prior to 150, upgrade to the 150 PHD Server before upgrading to the 210
PHD Server.
3. Uniformance PHD customers on releases prior to 150 who want to upgrade directly
to the 210 PHD Server should contact Honeywell for advice before proceeding.
4. Note that the 210 desktop cannot be used with the 150 Server. The 210 desktop can
be used with the 201 and 202 servers.
1 Read Me First
1.2 Important Notes
5. The 160, 200, 201 and 202 desktops can be used with the 210 server. Compatibility
with these desktops is provided for migration purposes only. There are no plans to
enhance these desktops in the future. Customers are encouraged to upgrade their
desktops to the current version.
6. This release provides support for the Business.FLEX 200 release.
7. Upgrading the database to 210 requires upgrading Uniformance TPI (now named
PHD Configuration Tool).
8. If a site is upgrading from a Uniformance/Business.FLEX base, then a dual upgrade
is required for Uniformance and Business.FLEX, each with respective database and
TPI upgrade requirements.
9. Although every effort has been made to enable PHD to compensate for differences in
the clock settings on the various systems and servers in plant operation, it is highly
recommended that the plant utilize a “time synchronization” procedure to ensure that
the time is consistent across the network.
10. This release is referred to as Uniformance PHD 210.1. It can be used for brand new
installations, or to support a migration upgrade from 150/200/201/202.
11. Any site or user specific custom objects in the Uniformance database will require
special handling. Refer to the Windows Database Installation Guide (in100) for
instructions.
12. Please refer to your shipping list for a list of products contained in your order.
13. Documentation is subject to on-going modification and clarification. The latest
product documents will be posted on SSOL. Customers are urged to review the
documents on SSOL on a regular basis.
14. Customers are urged to check SSOL on a regular basis for program updates and
patches and to review the Patch Release Letters for fixes applicable to their site.

1 Read Me First
1.3 Constraints
210 Upgrade advisories
ATTENTION
The upgrade process may overwrite the Registry settings for the log and
archive files created for Uniformance 200/201/202.
This is only of concern if custom settings have been made for the location of
archives and log files. The keys to check are as follows:
HKLM\Software\Honeywell\Uniformance\PHDServer\PHD_ARCHIVE
HKLM\Software\Honeywell\Uniformance\LogFiles
HKLM\Software\Honeywell\Uniformance\Apps
Server\Evt_Jrnl\DBConnect
ATTENTION
It is good practice to back-up the system prior to upgrading.
Good practice includes opening and saving any .dat file in the NtSite
directory. This updates the file date to avoid files being overwritten by an
installation repair.
At minimum, the NtSite directory should be copied/backed-up prior to

commencing installation, because the new PHD Server files may overwrite
the customer-modified files in this directory.
1.3 Constraints
The current implementation of Uniformance PHD is limited to supporting the following:
• Up to 256 RDIs
• Up to 8192 Users in non-INTS mode.
Note: When in Windows integrated security (INTS) mode, then the appropriate
operating system limit is applicable (substantially more then 8192).
• Up to 148 Roles (default 60)
• Up to 1024 open Archive files, depending on physical memory (recommended 768)
1.4 Support for Migration from Oracle 8i

Uniformance 210 has been developed for Oracle 9i and the Uniformance 210 database uses
structures and features specific to this version of Oracle. To facilitate a phased migration
from Uniformance 201, and Oracle 8i, to Uniformance 210, Honeywell R&D recommends
1 Read Me First
1.5 Customer-Performed Installation and Upgrade Guidance
installing Oracle 9i and the Uniformance 210 database on a machine separate from the
existing Oracle 8i / Uniformance 201 database.
Once the Oracle 9i / Uniformance 210 database has been loaded, the Applications Server
and the PHD Configuration Tools (TPI) may be upgraded to 210. The 201 version of the
Applications Server and the 201 version of TPI will not be able to connect to the 210
database. During the migration, it is expected that configuration is frozen until the full
migration has been completed.
The above implementation will allow collectors, still at Uniformance 201 and Oracle 8i, to
load configuration data from the Uniformance 201 / Oracle 8i database while the Oracle 91
/ Uniformance 210 database may be used to provide configuration data for servers that
have been upgraded to Uniformance 210.
Further guidance may be found in the “Uniformance Windows Database Installation
Guide” (IN-100).

Starting with Release 210, some customers may be able to do their own installs and upgrades
for small or medium PHD systems. This section outlines minimum required skills and
experience and offers guidelines to help assess technical complexity.
The information presented applies to the following releases and upgrade scenarios only:
- Customer performed installs of PHD Release R210 and later
- Customer performed upgrades from:
PHD R200, R201 or R202 going to PHD R210 or later
PHD R210 or later upgrades to any post R210 PHD release
Exclusions:
No other releases or upgrade scenarios are supported for customer performed
installation or upgrade.
Upgrades from PHD R150 (or prior release) to PHD R200 series releases should
under no circumstances be attempted without the use of Honeywell Services.
The installation or upgrade of BusinessFlex or other advanced applications is not
covered by this document.

1 Read Me First
Honeywell provides services to perform PHD installation, upgrade and the migration
planning. Even if all other criteria specified here are met, Honeywell highly recommends
that customers with large, customized or complex PHD installations utilize these Honeywell
services to minimize the potential for project delays and plant disruption. Customers should
direct any questions on this subject to Honeywell Support. A Honeywell Support Engineer
can provide a recommendation on the feasibility of a specific proposed customer performed
install or upgrade.
Honeywell will provide standard product support to customers performing their own
installations and upgrades conditional on the person performing the work having the
following training and skills:
1. PHD administration training or equivalent experience managing PHD systems. Specific

skills required include, but are not limited to:
Back up and restoration of PHD systems
Familiar with PHDMAN commands
Able to start, stop, and configure RDIs
2. Oracle database administration training or equivalent experience. Specific skills required

include, but are not limited to:
Back up and restoration of ORACLE databases
Comprehension of Oracle database concepts, objects, and structures
Note that it is recommended that the customer have a fully trained Oracle Database
Administrator available to assist in the installation and configuration of the Oracle
database.
3. MS Windows Administrator training or equivalent knowledge (including an

understanding of domain models, and security). Specific skills required include, but are
not limited to:
Back up and modification of registry values
Ability to create Windows users and assign to groups
Comprehension of Windows and networking concepts.
Additional considerations in determining the installation complexity and feasibility of a

customer performed installation or upgrade are as follows:

1 Read Me First
Backup and Recovery:

The customer must be confident that steps can be taken to completely restore PHD and
Oracle back to the original state prior to launching an upgrade or install. If there are any
reservations about the ability to backup and restore the system, the customer should not
attempt to proceed. The customer needs to carefully consider any unique system
configuration complexities and be confident that needed skills are available for this critical
step.
Oracle Database Requirements:

If the following conditions for the Oracle install are not met, Honeywell Services should be
engaged:
The Oracle database instance install is implemented on Windows only and contains only
tablespaces that are part of the default Uniformance PHD installation
For upgrades, the database may contain no additional (either customer added or added by
other applications) custom tables, indexes, scripts, or other items to the Honeywell-
provided database
If the installation of the Oracle database instance is planned for a UNIX platform, please
review the policy for limited support for Uniformance Oracle database installs on UNIX
platforms before proceeding. A copy of this policy is available on the on-line support web
site.
PHD Server Requirements

If the following conditions for the PHD Server install are not met, Honeywell Services should
be engaged:
RDI Installation guidelines:
- All RDIs will be installed on the Windows platform only
- No R150 RDIs will be configured to communicate with a R202 or later system
- Only one RDI Server is required to be configured
No staged migration is required as part of the upgrade process. (A staged migration
involves PHD servers and Application servers running together at different version
levels against the same database.)
Attention: For a complete assessment of feasibility, please contact a Honeywell Support

Engineer. Honeywell Support will not be in a position to provide training or tutorials

1 Read Me First
needed to assist customers that do not have the minimum skills outlined in this policy.
Assuming customers do have the minimum skill levels and assuming the complexity
guidelines presented here are adhered to, Honeywell will provide standard product
support should issues be encountered.
WARNING
When Honeywell advanced applications, such as Business.FLEX, are to be
installed in addition to PHD applications, the customer should check for
additional training requirements to ensure the successful upgrade of both the
PHD and advanced applications.
The PHD customer upgrade training course addresses the steps required to
upgrade PHD systems, and does not address additional advanced
applications.
It is the responsibility of the customer to backup the system prior to starting

an upgrade.
Honeywell will not be responsible for the unsuccessful upgrade of custom

database changes, or the impact they may have on the overall database
upgrade.

2. Uniformance PHD Release 210 Users and
Supported Platforms
2.1 Intended Users of this Release
This release is intended for all users of the Uniformance products including:
• Uniformance Desktop users – those who need to access and/or view PHD data with
the various Uniformance Desktop tools: Process Trend, Excel Companion,
PowerPoint Companion, Visual PHD, Tag Explorer, ModTag, Graphics Library, and
the tool for accessing PHD registry data
• Uniformance custom application developers – those who need to use the interfaces
for accessing PHD data (provided through the Uniformance Desktop) including two
OLE DB Providers (PHD and OPC) and a new interface for developing PHD
applications natively using .NET (referred to as the PHD .NET wrapper).
• System administrators and configuration personnel – those who need to use the
PHD Configuration Tool for tag configuration, virtual tag definition, application
configuration, or security administration.
• Application users – those who wish to apply the Business.FLEX 200 applications,
other Honeywell products, or other 3rd party products that are compatible with PHD.
2.2 Main Uniformance Nodes

The Uniformance PHD environment provides several Windows services. At a broad
level, these services may run on the same or different platforms. Typically, there are
four main platforms or nodes on which these services run - they are as follows:
• Server Node – supports PHD Server and RDIs.
• Desktop Node – supports the Desktop and OLE DB Provider.
• Configuration Tool Node - supports the PHD Configuration Tool (previously
named TPI).
• Database Node – supports the Oracle9i Release2 database.

2 Uniformance PHD Release 210 Users and Supported Platforms
2.3 Server Node Requirements

Operating system
The supported platforms for the Server Node include the North American English
language versions of the following:
• Windows 2000 Professional (SP4)
• Windows 2000 Advanced Server (SP4) – No support for advanced functions such as
clustering.
• Windows 2003 Standard (SP 1)
• Windows 2003 Enterprise (SP 1) – No support for advanced functions such as
clustering.
• Windows 2003 R2 – Requires PHD release 210.1.1 or later
The supported APP platforms for the Server Node include:
APP Type/Version Windows 2000 Server Windows 2000

Professional
APP 211 Yes (SP3) Yes (SP3)
APP 230/231 Yes (SP4) Yes (SP4)
Note: Honeywell does not support PHD Server on a GUS node
Experion support
Uniformance 210 introduces enhanced integration and optimized data collection from the
Experion 300 platform
Note: With the release of the 210.1.1 update, Honeywell supports PHD data collection
from the LCN-connected Experion ESVT node running Experion 300.1 or later. Some
conditions do apply:
• Data collection must be using the new Experion Link. Collection from an ESVT is
not supported using RDIs.

• Experion servers, including the ESVT, perform multiple tasks, and the capacity and
features of data collection are different from an APP. Customers are advised to
contact Honeywell to assist in determining whether an APP or ESVT should be used
to provide data to PHD at a particular site.
Hardware requirements
Use the following general hardware requirements for the Server Node as guidelines. The
requirements vary depending on the software configuration. For a detailed set of sizing
guidelines for a specific configuration, please contact your Honeywell account
representative or Honeywell Support – they will be pleased to assist in defining your
system configuration and then recommending the appropriate hardware requirements for
that system configuration.
System Class PHD Server Configuration Minimum Hardware Configuration
Collector Node
*
Small Up to 10,000 tags Pentium 4 - 866 MHz or equivalent
<7 RDIs 512 MB RAM
<10 client connections
Medium 10,000 – 25,000 tags Dual Pentium 4 - 866 MHz, or
8-10 RDIs Single Pentium 4 – 1.4 GHz, or

See NOTE
equivalent
10-15 client connections
1 GB RAM
Large Over 25,000 tags Contact your Honeywell account

representative
>10 RDIs
Up to 40 client connections

2.4 Desktop Node Requirements
System Class PHD Server Configuration Minimum Hardware Configuration
Robust Data Collection (RDC) Shadow Configuration
Any RDC Shadow Dual Pentium 4 - 866 MHz or

equivalent See NOTE
1 GB RAM
NOTE:
Some computers that ran Uniformance 150 under Windows NT 4.0 may not be adequate with
Uniformance 210 and Windows 2000/2003. Use of an underpowered system may result in
system failure due to differences in the management of kernel memory and processor utilization
and the additional load imposed by Windows 2000/2003, Oracle 9, and Uniformance 210.

Operating system
The supported platforms for the desktop node include the North American English
language versions of the following:
• Windows 2000 Advanced Server (SP4)
• Windows XP Professional (SP2)
• Windows 2003 Standard (SP1)
• Windows 2003 Enterprise – No support for advanced function, such as clustering.
The supported GUS and APP platforms on which the desktop node can reside are as
follows:
LCN Node Type/Version Windows 2000 Server Windows 2000

Professional
APP 211 / GUS 320 Yes (SP3) Yes (SP3)

Microsoft Office
The supported Microsoft Office versions for the desktop include the American English
editions of the following:
• Office 2000 SR1A, SP3
• Office 2003
• Office XP SP2
Note: Visual PHD may be used with the following Microsoft Office applications:
• Microsoft Excel - to create spreadsheets to retrieve and display data, and to
calculate retrieved data using the VisualPHD OLE Server.
• Microsoft PowerPoint - to create presentations that retrieve and display PHD data if
the PowerPoint Companion is use to add the Visual PHD controls.
Note: The PHD Configuration Tool (previously named TPI) is based on Access 97
and requires the Access 97 run-time library – Access 97 runtime is installed
automatically when you install the PHD Configuration Tool.
Oracle client
At minimum, the Oracle 9.2.0.6 client is required with the Uniformance 210 Desktop to
access an Oracle9i Release 2 Server. The Oracle 9.2.0.8 client is also supported.
Honeywell recommends that the Oracle 9.2.0.6 or 9.2.0.8 client be used by the
Uniformance 160, 200 and 201 desktops to access the Oracle9i Release2 Server
(although the Oracle 8.1.7 client may also be used). Uniformance 210 does not support
any other Oracle clients.
Microsoft DAO and .NET

Microsoft Data Access Objects (DAO 3.6) and .NET Framework 1.1 are included and
installed by the Desktop installation as required.

Hardware requirements
If the Desktop is run by itself, then the minimum hardware configuration requirements
are driven by the Operating System requirements. The following state the Microsoft
recommendations.
- The recommended system configuration to use Microsoft Office XP is Microsoft
Windows XP Professional on a personal computer with a Pentium III processor and
128 megabytes (MB) of RAM.
- The recommended system configuration to use Windows 2000 Professional on a
personal computer with a Pentium II processor and a minimum of 64 Megabytes of
RAM.
If the Desktop runs on a GUS node or APP node then the minimum system requirements
for those systems are applicable.

2.5 PHD Configuration Tool Node Requirements
2.5 PHD Configuration Tool Node Requirements

Operating system
The supported platforms for the PHD Configuration Tool Node include the North
American English language versions of the following operating systems:
• Windows 2000 Advanced Server (SP4) – No support for "server clustering"
• Windows 2003 Standard (SP1 or R2)
• Windows 2003 Enterprise (SP1 or R2) – No support for advanced function, such as
clustering.
The following states the Microsoft recommendation:
The recommended system configuration is to use Windows 2000 Professional on a
personal computer with a Pentium II processor and a minimum of 64 Megabytes of
RAM.
Note: Honeywell does not support the PHD Configuration Tool on a GUS node. The
PHD Configuration Tool may run on an APP node; however, Honeywell recommends
that the node not belong to the TPS domain.
Note: When considering installing the PHD Configuration Tool on a multi processor
system, users should be aware of Microsoft Knowledge Base article Q178650.
Microsoft Office
The supported Microsoft Office versions for the Configuration Tool node include the
North American English editions of: the following:
• Office 2000 SR1A, SP3
• Office 2003
• Office XP SP2
Oracle Client
The PHD Configuration Tool requires the Oracle 9.2 Client with patch 9.2.0.6 applied.

2.6 Database Node Requirements
2.6 Database Node Requirements

Operating system
The supported platforms for the Database Node include the North American English
language versions of the following operating systems:
• Windows 2003 Enterprise (SP1 or R2) – No support for advanced functions, such
as clustering
RDBMS
The Database Node requires Oracle 9.2 server with patch 9.2.0.6 applied.
2.7 Other System Requirements

PHDManager
The PHDManager utility is a management interface that can be run from any of the main
nodes or from another Windows-based platform connected to the network.
Remote PHDManager
Remote PHDManager can run on the North American English language versions of: the
following operating systems:
as clustering.

2.7 Other System Requirements
PHD OPC DA/HDA server

The PHD OPC DA/HDA Server can be installed on the Server Node, the Desktop node,
or a separate platform.
The OPC Server (when not installed on the Server Node or Desktop Node) can run on
the North American English language versions of the following operating systems:
as clustering
PHD applications (Application Server installation)

The PHD applications REL2PHD, PHD2REL and Legacy Tag Synchronization can be
run on a Server Node; however, Event Journal Collection must run on an APP node.
TPS compatibility matrix

The following table identifies the APP and GUS node support matrix against each of the
major Uniformance 210 nodes.
TPS Node PHD PHD PHD OPC PHD Database
Type/Version Server Desktop Server Configuration
Tool
APP 211 Yes Yes Yes Yes Yes
APP 230/231 Yes Yes Yes Yes Yes
GUS 320 Yes
GUS 330 Yes
GUS 340/341 Yes
GUS 350 Yes

3. Uniformance PHD Release 210 Functionality
Changes
3.1 New Features in Release 210
Experion integration
This release provides tighter integration with the Experion PKS System R300 General
Release (R300 Limited Release by request). Specifically this release provides the following
capabilities:
• Tag Synchronization with Experion PKS - Details are available in the PHD User
Guide (pim030). Users should be aware that this is specific to the Experion system;
however, in future releases, it is anticipated that this tool will be expanded and
eventually will replace the “legacy’ Tag Synchronization tool provided in earlier
releases. The ability to view the Tag Synchronization status is also available
through the Uniformance System Monitor (USM).
• Integrated Data Collection Subsystem – Details are available in the PHD/Experion
Link Configuration Guide (rdi410).
• Ability to trend PHD data on Experion Operator trends
OPC standard adherence

Honeywell recognizes the benefits realized by Industry accepted standards in connectivity
and interoperability for Industrial Automation. Honeywell is a strong advocate and founding
member of the OPC foundation and is pleased to introduce compliance with the Data Access
(DA) 3.0 standard as well as the History Data Access (HDA) 1.2 standard defined by the
OPC foundation in this release. Users may notice an update in aggregate behavior from the
HDA 1.1 aggregates available in Release 201 and 202. The OPC foundation web site
(http://www.opcfoundation.org) provides descriptions of HDA 1.2 aggregates.
License keys
In accordance with other Honeywell products, Uniformance PHD now utilizes a license key
to install/activate components of the PHD system.
.NET support
A new interface, referred to as the PHD .NET wrapper, is available for users developing
custom applications using .NET technology to provide access to PHD data. It is included in
the release in the desktop installation. The PHDAPINET help file contains information on
using the PHD .NET wrapper.

3 Uniformance PHD Release 210 Functionality Changes
User software developers may also be interested in the client application sample programs,
written in C#, that have been included as examples of custom applications. Executables and
the corresponding source files have been included in the Visual PHD\Examples directory. If
users wish to open the source files, they will require Visual Studio 2003.
There are two examples included: PHDTagFilterDemo.exe and PhdMonikerSampleApp.exe.
PHDTagFilterDemo demonstrates how to use some of the new PHD features provided in
release 210. Specifically, it uses the new filtering capabilities, which are accessible through
the .NET wrapper. Some of the other PHDTagFilterDemo functionality is consistent with the
Tag Explorer tool; however, rather then using the Oracle DB, it accesses PHD directly.
PhdMonikerSampleApp demonstrates the ability to retrieve tag data in an HTML or XML

format. PhdMonikerSampleApp is similar to ModTag without the ability to perform write
backs to PHD. This sample also demonstrates how to create an URL which can be used to
retrieve tag data inside a Microsoft Internet Explorer window.
These examples are provided ‘as is’ without any official support and are intended for
demonstration purposes. While the example programs should be intuitive to a knowledgeable
developer, additional information is available through an embedded Help system.
DCHECK utility
A utility, referred to as DCHECK, is now included on the distribution media and available in
the PHDServer directory. The DCHECK utility is used to correct corrupted archive files.
Information on how to use the tool is included in the embedded help feature.
WARNING: Please note that this tool should be used under the advisement of the
appropriate Honeywell Support Organization, as this tool has the potential to corrupt archive
files if used improperly. Archive backups should be taken prior to using the tool.
Experion RDM and System Management installation and licensing

For the PHD 210 interface to redundant Experion Servers, customers will need to install the
Redirection Manager (RDM) from the Experion Applications DVD on to the PHD Server.
Currently, RDM requires a license to be entered during installation, so Honeywell will
provide a default license for PHD. Note: Installing RDM also installs System Management
runtime.
Desktop Support for Data Enumeration

Modtag and the PHD OLE Server now support data enumeration.

Remote API
A new service is provided to enable client access to a PHD Server located either behind a
firewall or in a domain that does not have a trust relationship with the domain where the
client is located.
The following desktop applications have been upgraded to use the Remote API if required:
• Visual PHD
• Process Trend
• Modtag
• Excel Companion
• PowerPoint Companion

3.2 Uniformance PHD 210 Enhancements
3.2 Uniformance PHD 210 Enhancements

Honeywell made several enhancements as well as PAR corrections (see section 14, Problems
Fixed in Uniformance PHD 210). The primary enhancements are as follows:
• Support for Windows 2003 domains.

• Qualified to run on Fault Tolerant Ethernet (FTE).
• Qualified to run with Windows Terminal Services. This is only applicable for
PHD-only nodes and not the TPS nodes. The use of Windows Terminal Services on
APP nodes may negatively impact system performance and cause data disruption.
• PHD applications (Legacy Tag Synchronization tool, Event Journal Collector,
PHD2REL, and REL2PHD) are updated to run as services. Refer to the Applications
Server User Guide (pim275)
• Name Space Server (Existing sites may be required to perform some configuration
updates in order to maintain current functionality. Refer to the Process History
Database System Manual (pim030)
• Enhanced handling of digital values. Refer to the Process History Database User
Guide (pim020)
• As security remains a key interest of Honeywell and the Uniformance customer
base, various security enhancements have been incorporated. For detailed
information on these enhancements and how to utilize them, refer to the
Uniformance PHD Security and Network Planning Guide (am065).
• Improved performance when searching for data with tags that have no data or
missing values
• Two new aggregates (Last Time and Raw Average) are available from the OLE DB
providers, Visual PHD, and the new PHD.NET Wrapper. Refer to the Process
History Database User Guide (pim020)
• Improved routing definition. Refer to the Process History Database User Guide
(pim020).
• OPC and LxS RDI log files no longer log the repetitive “NaN” messages.
• RDI Services has been superseded by RDISetup as documented in the respective
RDI Installation Guides.

3.3 Database Separation
• Configuration of Robust Data Collection has been improved. Refer to the Robust
Data Collection User Guide (pim350) and the Process History Database User
Guide (pim020)
• Documentation improvements.

• Starting with Uniformance 210, tables and business logic relating to PHD
configuration and operation have been migrated out of the existing TOTALPLANT
schema in the PRD database and into a new UNIFORMANCE schema in a new
UNF database.
• The existing TOTALPLANT schema in the PRD database will now be managed
and upgraded by the Business.FLEX product group.
• Components of the Plant Reference Model subsystem (including Equipment and
Product configuration and their associated attribute definitions), which have been
traditionally included with the Uniformance Product have been removed from
Uniformance and will now be distributed with Business.FLEX 200. The forms and
reports in the 210 PHD Configuration Tool and the tables and business logic in the
DB have been removed to reflect this change.
• Components of the Infrastructure Management subsystem, including Applications
Server Configuration, have been removed from Uniformance and will be distributed
with Business.FLEX 200. The forms and reports in 210 Uniformance PHD
Configuration Tool and the tables and business logic in the Uniformance Database
have been removed to reflect this change. Note: The Uniformance applications
(Event Journal Collection, PHD2REL, REL2PHD, and Legacy Tag
Synchronization), previously scheduled through the Applications Server
Configuration forms, are now entirely configured through forms under the
Uniformance Process History subsystem.
• The Uniformance/Business.FLEX shared users and roles functionality has been
broken in order to facilitate the application segregation. In this release, PHD users
and their associated roles will now be stored exclusively in the UNIFORMANCE
schema in the UNF database. Business users and roles will continue to be stored in
the TOTALPLANT schema in the PRD database.
For this release only, the upgrade will reset Uniformance passwords. The
default password will be the user name. In those instances where the user
name is longer than 14 characters, the default password will be the first 14
characters of the user name.

• The upgrade from Uniformance 20X to Uniformance 210 should be transparent and
should not require any special operator intervention if the upgrade steps are followed
in the Database Installation Guide.
• The design approach for the database upgrade is to leave the existing PRD database
in place after the UNF database is up and running. It is up to the site to determine
what to do with the TOTALPLANT PRD database.
• Database links between the UNF database and the PRD database will be
established during the Business.FLEX 200 installation as a mechanism for keeping
the PRD database up-to-date with process tags and engineering units.
The following options should be considered and analyzed:
1. If the site does not have any Business.FLEX or custom applications installed,
then the PRD database can be decommissioned after the UNF database is up
and has been validated.
2. If the site has Business.FLEX applications installed and the site wishes to
continue using those applications, then an upgrade should not occur until
Business.FLEX 200 is available. Uniformance will need to be upgraded first,
followed by the Business.FLEX upgrade.
Refer to the Uniformance (Database Installation Guide and PHD Configuration
Tool Installation Guide) and Business.FLEX product documentation for
specifics.
3. If the site has other products or custom applications that have placed tables or
objects in the TOTALPLANT schema of the PRD database, then the
Uniformance 210 upgrade may impact these products or applications. These
other product tables and objects will not be migrated to the new UNF database
but will remain in the PRD database.
It is expected that these applications will continue to operate; however, if they
are referencing PHD-specific tables in the PRD database, then it must be noted
that these tables will no longer be receiving current data. The Business.FLEX
200 release will provide the links for getting the latest IP_TAG and
IP_ENG_UNIT data.
4. If the site has other products or custom applications that have placed tables or
objects in their own schema in the PRD database, then the Uniformance 210
upgrade is not expected to impact these products or applications. It is expected
that these applications will continue to operate if they are not referencing any
PHD-specific tables.

3.4 Functionality Removed or Not Supported
If the applications are referencing PHD-specific tables in the PRD database,

then it must be noted that these tables will no longer be receiving current data.
The Business.FLEX 200 release will provide the links for getting the latest
IP_TAG and IP_ENG_UNIT data.
ATTENTION
It is up to each site to determine if the database separation may impact their
operations and determine an appropriate strategy prior to performing the 210
upgrade.
Users should be aware that the PHD 210 UNF database does not support the
creation of custom database objects. The PRD database, that portion of the
database supported by BusinessFLEX, will continue to be the preferred
location for custom objects.

The Application Scheduler (IP_Schedule.exe) is no longer included in the Uniformance
PHD release - this is now included in the Business.FLEX 200 release, available under a
separate order. The Uniformance applications (Event Journal Collection, PHD2REL,
REL2PHD, and Legacy Tag Synchronization) have been updated as Windows services,
thus eliminating the requirement for the Application Scheduler. If the Application
Scheduler has been used for other custom applications, then the site can do the
following:
• Order the Business. FLEX release,
• Utilize the Windows Scheduler for scheduling of applications, or
• Consider evaluating other scheduler packages for suitability to the site's needs.
While Honeywell cannot endorse any of the products for a custom usage, there are a
substantial number of commercially available offerings that should satisfy site needs. A
general review of one such tool at the following web site was favorable:
http://www.visualcron.com/
The following items are NOT supported:
• PHD Configuration Tool support for regionalization.
• Support for non-English editions of Microsoft operating systems or Microsoft
Office (any version).
• Support for migration from releases prior to 150.


4. Uniformance PHD Release 210 Media
The following table lists the media for Uniformance PHD Release 210.1. The label on
the media shows the release version and the date Honeywell reproduced the software.
Label Media Product
Uniformance PHD CD-ROM PHD Server

Software Windows 2000 Professional/Server (SP4)
Windows 2003 Standard/Enterprise (SP1 or R2)
Release 210.1
Uniformance PHD Desktop
51157623 Windows 2000 Professional/Server (SP4)
Decemberr 2005 Windows XP(SP2)
RDIs
1 of 1
• Exception Condition RDI
• File Access/FTP RDI
• Gateway RDI
• LxS Remote RDI
• LxS Standard RDI
• Manual Input RDI
• OPC Remote RDI
• OPC Standard RDI
• PlantScape 3XX/400/500 Remote RDI
• PlantScape 3XX/400/500 Standard RDI
• Remote Peer 150 RDI Windows/AIX/HPUX/VMS
• Remote Peer 200 RDI
• Shadow RDI
• Virtual RDI
• Test RDI
• PHD/Experion Link

4 Uniformance PHD Release 210 Media
Label Media Product
Uniformance PHD Database

Windows 2000 Professional/Server (SP4)
PHD Configuration Tool (previously named TPI)
Windows XP
Uniformance Applications
Uniformance PHD Documentation
PDF documents as listed in document US03200

5. General Special Considerations
5.1 Installation Sequence for New Installs

Description If installing the Uniformance 210 PHD Server and the
Uniformance 210 Desktop on the same system, then PHD
Server must be installed before the Desktop.
5.2 Installer Does Not Show Administrators Group in the

"Select Group Membership" List
Description Due to a bug in the Wise Installer, the Administrator Group
does not show up for selection when installing any
component where a service logon user name and password is
assigned.
Discussion User may be added to the group by typing the Administators

group name directly.
5.3 Experion Tag Synchronization Installation Sequence

Description While not mandatory, it is recommended that the newly
released Experion Tag Synchronization utility be installed on
the same node that the PHD Server is installed on.
5.4 APP Node Security Policies Restrict PHD User Rights

Description Security policies implemented for an APP node that has been
joined to the TPS Domain restrict user rights.
Discussion These policies can prevent PHD-software from starting up

properly as the software application requires the user to be an
administrator on the local computer. The security policies
will require modifications to enable the users assigned to start
PHD the correct access rights.

5 General Special Considerations
5.5 Upgrading from Uniformance 200/201/202

Description If upgrading from Uniformance 200/201, it is necessary to do
the following:
1. Completely shut-down all PHD components installed on
the system being upgraded
2. Backup any .DAT files to retain any modifications made.
3. Install the software from the distribution CD by selecting
the appropriate section under the software install option.
4. Restore the .DAT files saved in Step 2 above to retain
any customization.
Refer to the following Notes for each subsystem:
PHD Server:
• Needs to be Cold started after an upgrade
• The user will be prompted for service account details
PHD OPC Server
• Shut-down OPC Server
• Install the software from the distribution CD
• Restart the OPC Server
Desktop
• Completely shutdown all components (Visual PHD,
Process Trend, ModTag, Companions, Tag Explorer).
It is necessary to remove the 200 or other prior release.
The 202 or earlier Desktop does not have to be removed
prior to installing the 210 Desktop.
• Install the software from the distribution CD
• Reboot
• Requires that the database be upgraded concurrently.

• Close all forms

• Install the software from the distribution CD. The install
will overwrite existing versions.
• Attach Tables and Commit Permissions, as the
SYSTEM.MDW and UNFAPP.MDE files have been
overwritten/replaced.
Application Server
• Completely shut-down all services (such as REL2PHD,
PHD2REL, MSGLOGSERVER, Event Journal,
IP_SCHEDULE).
• Install the software from the distribution CD.
• Reboot the server.
• The logon details for the service need to be supplied.
Tools
• Manually delete the UnfConfig MDB file prior to
installing the tools
Remote RDIs
• To update the remote RDIs (RemotePeer200.exe,
RemotePeer150.exe, RemoteLxS.exe, RemoteOPC.exe,
or RemotePlantScape.exe) on another machine, it is
necessary to do the following
− Stop the service on that machine.
− Copy the remote RDI executable to the appropriate
directory on the machine.
− Restart the service on the machine.

5.6 Incorrect Default Username for App Server Install
5.6 Incorrect Default Username for App Server Install

Description The installation process (setup.exe) for R210 AppServer
displays an authentication screen, the Oracle Server
Connection screen, showing a default username of
UNISERVER which will not work.
Discussion To get by the Oracle Server Connection screen, enter a valid

Oracle user to test the connection to the database:
1. Enter the Oracle Instance Name, ie: UNIFORMANCE
(Customers will need to subtitute the word ‘Uniformance’
with their own instance name at their site).
2. For the Database Authentication, select the Oracle
Authentication.
3. Enter a valid Oracle user, with username and password,
ie: UNIFORMANCE/UNIFORMANCE
4. Click “Next” to continue.
The authentication will fail unless the following prerequisites
are met:
1. A running R210 Uniformance Oracle database (does not
have to be on the same node).
2. Oracle client software installed on the node where the
Application Server is being installed (if Oracle Server is
not present on the node).
3. Oracle ODBC data source name (DSN) set up for
Uniformance on the node where the Application Server is
being installed.
If the authentication fails or can not be completed, the user
remains on this screen until the installation is cancelled.

5.7 Incorrect Default Username for Namespace Server Install
5.7 Incorrect Default Username for Namespace Server Install

Description The installation process (setup.exe) for R210 Namespace
Server displays an authentication screen, the Oracle Server
Connection screen, showing a default username of
PHD_READONLY which will not work. The Namespace
Server requires an Oracle username which is configured to
have insert, update and delete privileges on the “PHD
NAMESPACE SERVER BACKGROUND PROCESS”
function.
Discussion To get by the Oracle Server Connection screen, enter a valid

Oracle user to test the connection to the database:
1. Enter the Oracle Instance Name, ie: UNIFORMANCE
(Customers will need to substitute the word
‘Uniformance’ with their own instance name at their site).
2. For the Database Authentication, select the Oracle
Authentication.
3. Enter a valid Oracle user which has the appropriate
privileges, with username and password, ie:
UNIFORMANCE/UNIFORMANCE
4. Click “Next” to continue.
The authentication will fail unless the following prerequisites
are met:
1. A running R210 Uniformance Oracle database (does not
have to be on the same node).
2. Oracle client software installed on the node where the
Application Server is being installed (if Oracle Server is
not present on the node).
3. Oracle ODBC data source name (DSN) set up for
Uniformance on the node where the Application Server is
being installed.
If the authentication fails or can not be completed, the user
remains on this screen until the installation is cancelled.

5.8 New Hardware Requirements for Oracle Upgrade
5.8 New Hardware Requirements for Oracle Upgrade

Description Honeywell recommends that you provide a separate machine
for the 210 Uniformance ORACLE9i database.
Discussion The general approach for Uniformance 210 database upgrades

is to leave the existing TOTALPLANT PRD database in
place. Once you have completed and verified the
Uniformance upgrade, you may decommission the old
database TOTALPLANT PRD database if you are not using
any Business.FLEX applications. If you are using
Business.FLEX applications, then leave the TOTALPLANT
PRD database in place.
If you are upgrading from 200 or 201, Honeywell can provide
services to enable you to run ORACLE8i and ORACLE9i on
the same machine, if needed.
5.9 Support for User Developed Legacy Applications

Description Users who have developed applications using the published
R150 run-time APIs can continue to use the header and library
files found on the Uniformance 150 CD.
Discussion The Legacy API Server provides an API consistent with

Uniformance R150 run-time API thus permitting user
developed applications to continue to function unchanged.
The Legacy API does not support new functionality or new
technologies such as multi-threading.
5.10 Legacy API Server Does Not Support Multi-threading

Description The LegacyAPI Server provides support for legacy
applications.
Discussion The Legacy API Server provides compatibility with for

applications written for Uniformance 150, and thus, does not
fully support new functionality such as multi-threading or new
technologies such as .NET.

5.11 Support for Uniformance 150 PHD Server
5.11 Support for Uniformance 150 PHD Server

Description The Uniformance 150 PHD Server requires updated
components in order to communicate with a Uniformance
R210 PHD Server.
Discussion The updated components that need to be installed on a

Uniformance 150 PHD Server are included on the
Uniformance 20x distribution CD in the \Misc\RDI directory.
The included components are as follows:
rdi_gateway.exe
rditcpip.dll
rdiutils.dll
rdi3501.pdf
5.12 MS Loop-Back Adapter Must Be Installed on Windows

2000 and Windows 2003
Description Loop-back adapter must be installed on Windows 2000 and
Windows 2003 to prevent unloading of the TCP/IP stack on a
link state failure.
Discussion Microsoft Article: Q239924 details the registry key to disable

the media sensing feature in Windows 2000 which causes the
TCP/IP protocol stack to be unloaded on a link state failure
(such as disconnection of the network cable). Disabling the
media sensing feature does not always prevent unloading of
the TCP/IP stack thus it is necessary to install the loop-back
adapter software to simulate a connection in the event the
network link fails.

5.13 Do NOT Delete "127.0.0.1 localhost" from the HOSTS File
5.13 Do NOT Delete "127.0.0.1 localhost" from the HOSTS File

Description Do NOT delete "127.0.0.1 localhost" from the HOSTS file.
Discussion This entry, which is created when Windows is installed, is

used by certain PHD functions. If the entry is deleted, those
PHD functions will not operate correctly.
5.14 Specifying an Invalid Host Will Cause RDC Problems

Description When the host name cannot be resolved and IP name address
resolution takes longer than the scan rate, the Shadow server
may fall behind. This may occur when the STANDBY node
has been defined, but is not yet present.
This is an IP layer issue beyond the control of PHD.
Discussion Use a method that reduces or eliminates name resolution - for

example, make sure valid hosts file entries exist or use an IP
address instead of a hostname.
5.15 Legacy Code Needs to be Updated if Port Number is

Appended to Hostname
Description The R150/R201 OLE Server allowed connections to be made
with the port number appended to the hostname (for
example,"localhost/3000"), and some customers used non-
standard ports on PHD Buffers.
Any (Honeywell or customer-written) legacy applications
using the OLE server which have the port number appended
to the hostname will fail to connect to a 210 PHD Server.
Discussion The OLE server in 210 connects to the APIServer at default

port 3100. It is unable to connect to LegacyAPI or 150 servers
any more. Any (Honeywell or customer written) application
using the OLE server and having the port number hard-coded
need to be modified to use port 3100.

5.16 HCI installs a version of kill.exe
5.16 HCI installs a version of kill.exe

Description HCI components installs a version of kill.exe in c:\Program
Files\Honeywell\TPS\Base\kill.exe.
Discussion Because this directory appears in the PATH before the

PHDServer path, this version of kill.exe is used, rather than
the Uniformance version.
Check if c:\Program Files\Honeywell\TPS\Base\kill.exe
exists and, if it does, rename it so that it will not be invoked
when users run the kill command. The Uniformance version of
kill.exe is an enhanced version that will suffice for HCI’s
purposes as well.
5.17 Silent Install of Desktop Not Supported

Description A silent install of the Desktop will cause problems. Issuing the
following command will break VisualPHD, ModTag and
Process Trend: msiexec /p Unf_R210.1_Desktop.msp /qn
/l*v c:\temp\setup2.log
Discussion The PHD ListenPort value of 3100 is read from the following
registry key:
HKLM\SOFTWARE\Honeywell\Uniformance\PHDServer\
PHD_PORT
The value is a REG_SZ and MSI prefixes it with a #. The #
has to be removed prior to writing it back to the registry;
otherwise, it gets written as a STRING. The # is removed if the
User Interface is invoked during setup; however, when doing a
silent install, the User Interface is not invoked and the # is not
removed – thus, #3100 is written as a string back to the
registry.
Workaround - Create a .REG file that writes the value back as
a DWORD after running the .MSP without invoking the User
Interface.

5.18 Bug in Windows XP/2003 Telnet Client
5.18 Bug in Windows XP/2003 Telnet Client

Description The Windows XP/2003 Telnet Client always performs local
echo and it can not be turned off.
Discussion After having established a connection to APIServer,

RAPIServer or RDIServer, characters are doubled (echoed) on
the screen so it becomes impossible to enter the username and
password. This is not seen using the Windows 2000 Telnet
Client.
5.19 Using OPC on Windows XP SP2 or Windows 2003 SP1

Description Windows XP SP2 and Windows 2003 SP1 introduce
improvements which directly impact OPC via DCOM and
which may prevent proper functioning of OPC clients or
servers.
Discussion Windows XP SP2 and Windows 2003 SP1 add new DCOM
limit settings and turn the Windows Firewall on by default
thereby causing OPC communication via DCOM to fail. In
order to re-enable OPC communication, it is necessary to:
• Configure the Firewall appropriately or disable the

Firewall (not recommended unless the machine is all ready
behind a corporate firewall).
• Reconfigure DCOM.
Full details of the actions required are described in the OPC
White Paper “Using OPC via DCOM with Microsoft Windows
XP Service Pack 2” available at
http://www.igearonline.com/print/OPCXPSP2.pdf

5.20 Queue Overwrite not Reported
5.20 Queue Overwrite not Reported

Description No queue overwrite is logged when constore processing is
disabled and the modification of values results in a non-
archived data value rolling off of the queue.
5.21 Incorrect Create_sequence.sql File Generated

Description The Create_sequence.sql file generated when upgrading from
Uniformance PHD 150 to Uniformance PHD 210 creates
IP_TAG_TAGNO with an incorrect start value. (BeAware
Advisory 2006-06)
During the upgrade to Uniformance 210, the database
sequences need to be recreated and stored in the new
UNIFORMANCE database. This is done by retrieving the last
value of the sequence in the TOTALPLANT database and then
generating a script to be run against the new UNIFORMANCE
database.
In a 150 database, the sequence for the IP_TAG TAGNO
column exists but is not used. Instead, TPI generates the value
for TAGNO. Because of this, the sequence for the IP_TAG
TAGNO column is generated incorrectly in the new
UNIFORMANCE database.
Discussion The Uniformance 210.1.1 patch contains two scripts to address

this problem:
1. For customers who have all ready migrated, a script is
provided to correct the database.
2. For customers still planning to migrated, a script to
generate the correct version of the Create_sequence.sql file
is provided to migrate the database properly.

5.22 Duplicate entries in the Add/Remove Programs Applet
5.22 Duplicate entries in the Add/Remove Programs Applet

Description Due to a difference in naming in Uniformance R200.1, the
existing icons are not replaced when installing Uniformance
PHD R210. (BeAware Advisory 2006-05)
Customers will see 2 icons for Uniformance in the
Windows>Control Panel>Add/Remove Programs applet.
Discussion De-install Uniformance PHD R200.1 prior to installing

Uniformance PHD R210.
5.23 PHD2REL PHDTagsets are lost during upgrade.

Description When upgrading database from Pre-210 to R210 the tagsets for
PHDTagset , used by PHD2REL, are lost.
During the database upgrade to Uniformance 210, there is a

step that migrates data from the Tagset table (IP_TAGSET) to a
new Tag Collection Table (IP_TAG_COLLECTION).
This step fails to migrate the data during the upgrade.
Discussion In 210.1.1, an updated script will be provided which should be

used rather then the one on the CD. If a site has already
upgraded using the CD script, then 210.1.1 also contains
another script to correct their setup provided that the old
Totalplant database is still available.
5.24 upgrdUnf2.cmd script could take a long time to complete.

Description Due to the possible large number of deletes occurring, it may
look as if the upgrdUnf2.cmd script is not running.
Discussion If this occurs, the user should monitor the free disk space to
ensure that space is available and should allow the script to
complete. If it appears that there is insufficient disk space (see
also 5.25 below), terminate the script by pressing CNTL+C (it
may take a while to stop) and contact Honeywell Support (see
Section 16) before proceeding.

5.25 Possible to run out of disk space during an upgrade to Uniformance 210 when Generic Auditing
enabled
5.25 Possible to run out of disk space during an upgrade to

Uniformance 210 when Generic Auditing enabled
It is possible to run out of disk space when doing an upgrade if:
Description
1. You are upgrading from a Uniformance 200, 201, or 202
database, and
2. You are upgrading from a system that uses

BusinessFlex and which also uses Generic Auditing to
capture BusinessFlex data changes.
This is not an issue if you are upgrading from a Uniformance only

database. This is only an issue if there are a very large number
of captured BusinessFlex data change records in the audit
tables.
In general, if a site has been running with Generic Auditing

enabled for more than 6 months, then it is recommended that the
site contact Honeywell Support for assistance in determining if
this is a potential issue.
During execution of the upgrdUnf2.cmd scrip, there is a step that
Discussion
removes the BusinessFlex generic auditing data from the
IP_AUDIT_DETAIL, IP_AUDIT_KEYS, IP_AUDIT_CPTR, and
the IP_AUDIT_HDR tables. A commit is performed only after all
the data has been deleted. If there is a large amount of data to
be deleted from these tables, this may cause the undo
tablespace to grow in size in order to accommodate a possible
rollback and, thereby, cause the undo file to consume the
available disk space.
If an out of disk space condition as described above occurs,
please contact Honeywell Support (see Section 16) before
proceeding.

6. Special Considerations for PHD Server
6.1 Large Systems Will Require Tuning
Description Systems encompassing large numbers of tags, clients and
RDIs will need to be tuned.
Discussion Depending on available memory and the number of clients,

tags, and RDIs, PHD Server may Dr Watson on Cold start if
DBM_FILTER is set to 0 or when a large number of tag
changes are send to PHD. Due to the complexity of tuning,
Honeywell assistance/advice should be obtained.
6.2 Use of PHD Server 150 Within PHD 210 Configuration

Description Uniformance PHD Server 150 is supported within a
Uniformance PHD 210 configuration. One or more 150 PHD
Servers may co-exist with Uniformance PHD 210 servers;
however, certain Uniformance PHD 210 features will not be
available to the 150 servers.
6.3 Windows OS May Select a Port Assigned to a PHD

Service
Description It is possible that the Windows OS may select a port that has
been assigned to a PHD service (most likely an RDI in RDC
state) when the Windows OS is automatically assigning ports
to services that use port communication. This prevents the
service from receiving any proper communication link.
Discussion The workaround is to identify in the services file (located

under WINNT\System32\Drivers\etc) all the ports that can be
used by PHD services. A reboot of the computer will be
required but this will then prevent the Windows OS from
assigning one of these ports out to another communication
link. See discussion under Section 2.5.1 Server Node and
2.5.1.2 Robust Data Collection (RDC) Shadow Configuration.

6 Special Considerations for PHD Server
6.4 CUR Section Size to Increase Significantly
6.4 CUR Section Size to Increase Significantly

Description Setting the download flag for tags causes the CUR section
size to increase significantly.
Discussion When a tag is designated as a download tag, an allocation is

made in the CUR shared memory section for this tag. This
allocation is much larger than the data size specified for the
tag. As a result the size of the CUR section increases rapidly
as the number of tags with the download flag set increases.
To minimize the size of the CUR section, keep the number of
tags with the download flag set to a minimum.
6.5 Mixed 150 and 200 Archives

Description While it may be possible to mix R150 and R200 archives, the
practice of interspersing R150 amongst R200 archives is not
recommended.
6.6 PHDMAN INIT SYSTEM Systematically Fails with an

Oracle Error
Description A generic problem that may be encountered at a customer site
is that PHDMAN INIT SYSTEM systematically fails with an
Oracle error.
Discussion The failure results from the DAO for Oracle having different
settings depending on what version of Oracle is used (7.x, 8.x
or 9.x). The most relevant discussion may be found at
<http://www.intranetjournal.com/ix/msg/39831.html>, with a
pointer to the actual solution
http://support.microsoft.com/default.aspx?scid=kb;EN-
US;q264012. The fixes to the registry have been left as a
manual exercise.

6.7 Shutting Down a Uniformance 150 PHD Server When Using RemotePeer150 RDI
6.7 Shutting Down a Uniformance 150 PHD Server When

Using RemotePeer150 RDI
Description All RemotePeer150 Services need to be shutdown on the
system hosting the Uniformance 150 PHD Server prior to
shutting down the Uniformance 150 PHD Server.
Discussion If the RemotePeer150 Services are not properly terminated, it

will not be possible to Cold Start the Uniformance 150 PHD
Server as the files will be flagged as “In Use.” The issue is
that the RemotePeer RDIs have an attachment to the global
memory sections. The fact that the RemotePeer RDIs are
active and attached to the global sections prevents PHD from
performing a deletion of the global sections which normally
occurs on a COLD start.
6.8 Archive Files Not Created by CONSTORE

Description If there are no archive files and no current data to be stored, it
seems likely that the archive files may not have been created
by CONSTORE.
Discussion If no archive files exist, they are created by the CONSTORE

thread when it attempts to store tag data. However, if there
are no tag values to store (nothing in the raw data queue), then
it is likely that CONSTORE does not perform the store
process and may, in turn, not detect the absence of the archive
files. In 150, a blank SCAN archive file is distributed for this
reason.
The scenario described is only likely to happen on Shadow
servers that have never collected any real-time data, and go
into history recovery immediately the first time they are
started. The simple workaround is that blank archive files
should be created for the SCAN, MANV and CHAR logical
archives.

6.9 Data Integrity Issues if Changing Tag Type or Data Type
6.9 Data Integrity Issues if Changing Tag Type or Data

Type
Description Tag types and data types should not be changed after data
collection for the tag commences.
Discussion If you change the data type (for example, float to integer),
PHD cannot properly decode the archive file records and may,
therefore, display the wrong timestamp, date, data, or
confidence.
If you change the tag type (for example, manual input to
collected), data access issues may result.
6.10 History Recovery for RDC Scheme Without a Standby

Collector
Description History recovery may now occur from the source system
through the Buffer to the Shadow server, even if a secondary
(Standby) collector has NOT been configured in RDC.
Discussion A user may choose, in RDC, to implement a Shadow server

and a single collector as a "PHD to PHD" type of interface - a
shadow RDI runs on the Shadow RDC node and a "history
recoverable" RDI runs on the buffer node.
On previous releases under RDC, the expectation was that
History Recovery occurred from only the secondary collector
- if a secondary collector was not configured, then History
Recovery would not occur. When RDC history recovery was
required on previous releases, and a single collector was in
place, a Gateway RDI on the shadow had to be used in
conjunction with the RemotePeer RDI on the collector.

6.11 RDI Host Table Size
6.11 RDI Host Table Size

Description A Registry key that allows a user to specify the size of the
host/rdi cross-reference table has been added.
Discussion The location of the key is:

HKLM\Software\Honeywell\Uniformance\PHDServer\Rdi
HostTableSize
By default, the key is not present and the system uses a size of
256 for this table. If the user wishes to add it, it should be
configured as a DWORD with valid values ranging from 256
to 65535. This key should only be defined when the number
of RDI entries in the IP_RDI_SPEC table exceeds 256. Most
sites will not exceed the 256 records limit, and thus this key
will not be applicable.
6.12 Tag Synchronization

Description Tag synchronization is only available for tags assigned to
Experion history.
6.13 Tag Collection Rates

Description If PHD tags are collected through the PHD/Experion LINK
and the tag is also in Experion history, data collection rates
will be at the rate the tag is assigned to on Experion.
Discussion Changes to the PHD tag definition will not result in a change
to the actual data collection rate. If the PHD tag rate is set
slower than the Experion rate, some data loading issues may
occur. Customers are advised to leave the PHD rate equal to
the Experion rate.

6.14 PHD/Experion Link Performs Duplicate History Recovery
6.14 PHD/Experion Link Performs Duplicate History

Recovery
Description The Experion Link performs history recovery based on the
oldest of the current timestamps for all associated tags. If the
following sequence of events occurs:
• link shut down (either manually, or for some other
reason)
• new PHD tags configured on the link (either via
TagSync, or manually)
• link is restarted
• link starts history recovery max_histrecmn minutes ago,
thus doing duplicate history recovery for all existing tags
then PHD will over-write the current data it has for affected
tags. Any changes which may have been made to collected
data will be lost. .
Discussion The Experion Links uses the OPC HDA interface ReadRaw
for History Recovery which accepts 1 timestamp for all the
items requested. Since only one timestamp can be specified
to the ReadRaw call, the oldest time across all the tags is
passed.

7. Special Considerations for RDIs
7.1 Included RDIs
Description Only Type A RDIs are included in this release.
See section 4, Uniformance PHD Release 210 Media.
Discussion If you are currently using Type B or Type C RDIs, contact

Honeywell to arrange assistance in upgrading these.
7.2 RDISetup Fails if INTS configured for PHD Server

Description The RDI Configuration tool (RDISetup.exe) may fail if PHD
is configured to use an external Oracle account (i.e.
UNISERVER, UNISERVICE).
Discussion RDISetup may fail to get the appropriate Oracle connection

information from the database. It informs the user that it failed
to get information from the PHDPARAMS file and exits. The
workaround is to configure PHD to use the UNISERVICE
account and re-run RDISetup.
7.3 Netclient RDIs Need to be Replaced

Description All netclient RDIs (Shadow, Peer and Remote) in Release 150
will have to be replaced with the RemotePeer and Gateway
RDIs included with Release 210.1.
Discussion A full discussion may be found in Remote Peer Real-Time

Data Interface Installation Guide (rdi100).
7.4 "Unable to locate DLLs" error for PlantScape RDI

Description When starting-up the PlantScape RDI, an "RDI Server -
Unable to locate DLLs" error is noticed.
Discussion It is necessary to copy the MSVCP71.DLL &

MSVCR71.DLL files to the PHDServer directory
dformd.dll

7 Special Considerations for RDIs
7.5 Using the PlantScape RDI to Access an Experion System
7.5 Using the PlantScape RDI to Access an Experion System

Description When using the PlantScape RDI to access an Experion
system, it is necessary to copy the following files from the
Experion system to the PHDServer directory:
• gdadetach.dll
• hscnetapi.dll
• hscsrvapi.dll
• msvcp71.dll
• msvcr71.dll
• dformd.dll
• shheap.dll
7.6 Virtual Tag RDI

Description When operating in Exception collection mode, the Virtual Tag
RDI will not return data for a tag if the result of the tag
calculation is an End of Data.
Discussion Previous releases of the Virtual Tag RDI have returned a 0, -1

confidence value for calculations that did not produce a result.
If the calculation returns an error code other than an end of
data error code, the exception function will only return a 0, -1
result for the first occurrence of an error for each tag, rather
than generating 0, -1 value at the requested poll frequency.
The exception functionality must be manually enabled, as the
required RDI seed data is not present to allow RDISetup (the
replacement for rdi_services) to automatically generate the
GO file with the exception collection parameter enabled for
this RDI. The GO file for the Virtual Tag RDI must be
manually edited and the parameter /x added to the end of the
command line parameters for the RDI.
The /x parameter enables exception collection of tags
associated with this interface.
Future releases of the Virtual Tag RDI documentation will
include instructions regarding use of this parameter.

7 Special Considerations for RDIs
7.7 PHD Experion Link goes to ACTIVE INACTIVE when adding or removing tags
7.7 PHD Experion Link goes to ACTIVE INACTIVE when

adding or removing tags
Description When a tag is added to the PHD Experion Link, the link will
go to ACTIVE INACTIVE.
Discussion Although the link returns to ACTIVE ACTIVE the next time
the RDI tries to reconnect, this is not normal behavior for the
dynamic adding/removing of tags from the OPC Group on the
Interface and this behavior results from a bug in RDM.

8. Special Considerations for Uniformance PHD
Desktop
8.1 Upgrading from Uniformance 200 or Earlier
Description If upgrading from Uniformance 200 or earlier, it is necessary
to do the following:
• Completely shutdown all components (Visual PHD,
Process Trend, ModTag, Companions, Tag Explorer).
• Uninstall the Uniformance PHD Desktop 200 or other
prior release.
• Install the software from the Uniformance distribution
CD.
• Reboot.
8.2 Using 210 Desktop with 150 Server Can Cause

Serious Issues on 150 Server
Description Using the OLE client 210 to connect to an 150 server (using
"hostname/3000") causes two instances of apisrv.exe to start on
the 150 server and use all the CPU.
Discussion Any attempt to use the 210 desktop to retrieve data from an 150
server will result in "network client request failed" errors, as the
210 desktop attempts to connect on port 3100. However, explicitly
setting the port to 3000 (that is, specifying the hostname as
"hostname/3000") results in the symptoms described above.
8.3 Visual PHD and Visual Basic

Description Visual PHD 210 may be used with Visual Basic 5, Visual Basic 6,
or Visual Studio .NET provided that only the COM objects are
used. There is no support for the .NET extensions.

8 Special Considerations for Uniformance PHD Desktop
8.4 Visual PHD Login/Connection Mechanism Has Changed
8.4 Visual PHD Login/Connection Mechanism Has

Changed
Description The Uniformance 150 version would assign a default user on the
first connection to PHD and then allow you to change the User by
passing in a Username and Password which PHD would check.
Discussion With Uniformance 202 and later, Visual PHD will pass the User's
token to PHD where it is checked to be from a valid user. If the
User token is not from a valid user then no connection is created
and an exception will be thrown. The Login command will only
work if there is an open connection to PHD.
8.5 Memory and Handle Leak

Description An invalid HOSTS name can cause a memory and handle leak
on the client side.
Discussion Ensure that all HOST names are resolvable.
8.6 EXCEL Companion

Description When using the Excel Companion, a user may receive the
following error while trying to fetch raw data:
An error occurred while building the output. [10001] -E-
BADPARVAL - Bad parameter value specified. [-2147220991]
Or the following error while trying to fetch resampled data
(snapshot, average, etc.):
An error occurred while determining the size of the output.
[10001] -E- BADPARVAL - Bad parameter value specified. [-
2147220991]
Discussion This could also occur in other Microsoft Visual Basic

applications when using the variants to retrieve data.

8.7 Process Trend
8.7 Process Trend

Description The Cpk Process Capability Index has been added to the
Statistical Analysis trend in Process Trend.
Discussion The Process Capability index is defined as the Cp for a

centered process producing a similar level of defects - the
ratio between permissible deviation (measured from the mean
value to the nearest specific limit of acceptability) and the
actual one-sided 3 x sigma spread of the process. As a
formula, Cpk = either (USL-Mean)/(3 x sigma) or (Mean-
LSL)/(3 x sigma), whichever is smaller (that is, depending on
whether the shift is up or down).
8.8 Desktop Application Support for Remote API

Description To use the Remote API, it is necessary to configure the
Desktop applications.
Discussion Configuration of the Desktop applications consists of

selecting Remote Access and supplying a valid username and
password. Each application features a means for providing
this information.
• Visual PHD provides a new ‘UseRemoteAPI’ property

for custom coding and a new ‘Remote Access’ tab on the
data control property page.
• Process Trend has a new ‘PHD Access’ tab on the Plot

Defaults dialog box..
• ModTag has a new ‘Remote PHD Access’ tab on the

Options dialog box.
• Excel Companion lists a new ‘PHD Remote API Access’

section on the Configuration tab of Default dialog box.
• PowerPoint Companion provides a new ‘Remote Access’

tab on data control property page.

8.9 User Security
8.9 User Security

Description By default, the PHD users will have to be valid Windows accounts
on the PHD Server or they will be unable to connect to PHD using
the 200 API.
User must be able to be validated on the current domain. This
means that
• There must be a trust between the domains (Can be a one

way trust), or
• The user must be identical between the domains (same

username and password).
Discussion Any cross domain PHD access will require the establishment of a
trust relationship between the domains.
With the Uniformance PHD 200 release, user validation was
modified to use Windows NT User validation. The Windows
operating system provides a user security infrastructure that
allows processes to run as specific users and thereby be granted
that user’s rights.
This permits administrators to tailor user rights to specific user
responsibilities and ensures that applications, including PHD,
honor these rights. Therefore, users are not allowed perform
actions through PHD applications that they would not be allowed
to perform by other means.
When a user makes a request to PHD, the PHD processes
impersonate that user to gain their specific access rights. This
ensures that the access rights to PHD data, granted by the system
administrator, are honored. If the user cannot be validated by
Windows, no access to tag data through PHD is allowed.
This changes the default behavior of PHD which in R150 allowed
connections regardless of whether the user was a valid Windows
user or not. Each connected user was allowed public permissions
to tag data.
In this release, if a user cannot be validated as a valid Windows
user, the connection to PHD is not allowed. This strengthens the
security to tag data by ensuring that only valid users are able to

8.9 User Security
access the PHD system.

The 210 Desktop applications now connect to the PHD Server
through the 210 API rather than through the LegacyAPI service.
When the user connects through the 210 API, the API validates
the user through the standard Windows NT User validation
techniques. If the user is not a valid Windows user, the
connection is immediately dropped, preventing unauthorized users
from connecting to PHD and possibly accessing PHD data they
are not authorized to see. Valid Windows users are users that are
known in the current domain, or are users who are defined in a
trusted domain, or are identical to a user in this domain (including
password). In the case that the user is a valid Windows user, a
connection is established, and the user is impersonated to establish
their access rights to PHD tag data.
The Remote API provides a way to configure the system so that
users can connect “anonymously” to hold the connection. They
can then perform a PHD user login to gain access rights to tag
data.

9. Special Considerations for PHD Configuration
Tool (Previously Named TPI)
Description If upgrading from Uniformance 200/201, it is necessary to do the
following:
• Review the PHD Configuration Tool Installation Guide
(in080).
• Close all forms.
• Install the software from the distribution CD. The install will
overwrite existing versions.
9.2 PHD Configuration Tool Uses PHD_HOST Registry

Entry
Description The PHD Configuration Tool uses the PHD_HOST registry entry
to determine where to send updates. In PHD 201 and earlier, TPI
used the PHD_HOST environment variable to determine where to
update the tag.
Discussion If the PHD_HOST registry entry on the Buffer points to

"localhost", the PHD Configuration Tool updates the local Buffer
and does NOT propagate the changes to the Shadow Server.
9.3 Proper Shutdown of PHD Configuration Tool

Description The system.mdw file will get corrupted if the PHD Configuration
Tool is not shutdown in an orderly fashion.
Discussion If the application is terminated unexpectedly (such as a power

outage or network drop), the system.mdw file may get corrupted.

9 Special Considerations for PHD Configuration Tool (Previously Named TPI)
9.4 Data Execution Prevention (DEP) and the PHD Configuration Tools
9.4 Data Execution Prevention (DEP) and the PHD

Configuration Tools
Description Data Execution Prevention (DEP) is a set of hardware and
software technologies that perform additional checks on memory
to help prevent malicious code from running on a system.
The primary benefit of DEP is to help prevent code execution
from data pages. Typically, code is not executed from the default
heap and the stack. Hardware-enforced DEP detects code that is
running from these locations and raises an exception when
execution occurs. Software-enforced DEP can help prevent
malicious code from taking advantage of exception-handling
mechanisms in Windows.
Data Execution Prevention (DEP) may prevent the PHD
Configuration Tools from functioning correctly.
See Knowledge Base Article 1-1DBO9B for more details.
Discussion You can manually create a list of specific programs that do not
have DEP applied by using the System dialog box in Control
Panel.
Do the following to exempt the PHD Configuration Tools on a PC
utilizing DEP:
• Go into DEP through the System dialog box in Control Panel.
• Select the Advanced tab.
• Click Performance Settings.
• Select the Data Execution Prevention tab.
• Click Add.
• Browse to the C:\Program Files\Common Files\Access 97
Runtime folder.
• Select Msaccess.exe.
For a detailed description of the Data Execution Prevention
feature and workarounds, please see the following Microsoft
knowledge based article:
http://support.microsoft.com/kb/875352

9.5 Uniformance Password Can Not be Changed Under INTS
9.5 Uniformance Password Can Not be Changed Under

INTS
Description User is unable to change the password in TPI Admin when
Windows integrated (INTS) security is on.
Discussion The Uniformance password should be set prior to activating

Windows integrated security (INTS).
9.6 Unable to Replace Text in Virtual Tag Calculation

Description When attempting to use the search and replace functionality in the
PHD Configuration Tool (previously named TPI) to replace some
text in a virtual calculation, the PHD Configuration Tool may
crash.
Discussion To replace the text, copy the tag definition to Notepad or

WordPad and make the changes there; and then copy the modified
definition back to the PHD Configuration Tool.
9.7 Tagloader Builds Points Incorrectly

Description In a tagload file, If the field that specifies the range of a tag
has a certain number of rows where integer ranges are
provided, the remaining records are also tagloaded as integers,
even if they are specified with a decimal.
Discussion The workaround is to ensure that the majority of records in

the first 25 records of a tagload file have decimal numbers for
the range.

9.8 Incorrect Data During TagLoad
9.8 Incorrect Data During TagLoad

Description When doing a TagLoad from the PHD Configuration Tool,
the resulting tags might end up with wrong data in the Tag
Source field (SRC_TAGNAME).
Discussion This problem is related to the actual tagnames provided in the

CSV file and to the number of rows in the file. The tagload
might put the correct data into the database if fewer rows are
included in the CSV file.
Enclosing each source tagname in the CSV file in double
quotes solves the problem. Excel does not put these in double
quotes, even if the column is formatted as text, so you should
manually edit the CSV file and add the double quotes to the
source tagname.
9.9 Errors using the Microsoft ODBC Driver for Oracle

Description Customers who use the Microsoft ODBC driver instead of the
Oracle ODBC driver will encounter several ODBC errors.
Discussion Honeywell has only qualified the Oracle ODBC Driver. Use of
the Microsoft ODBC Driver for Oracle is not supported.

10. Special Considerations for Uniformance PHD
Database
10.1 Authentication Across Mixed Domains Does Not Work
Description Because of an Oracle 9 bug in the NTS adapter, OS
authentication across mixed domains does not work.
Discussion If an OS account is on a Windows NT 4.0 domain and the

database server is in an ADS domain, OS authentication
(login with a '/' without using password) does not work. This
is also true if the OS account is on an ADS domain and the
database server is in a a Windows NT 4.0 domain.
It works if both the OS accounts and the database servers are
on the same type of domain.
Oracle does not have a date on when this will be fixed;
however, mixed domain OS authentication continues to work
in Oracle 8i.
10.2 Watch for Duplicate Engineering Units

Description When upgrdprep is run during the database upgrade, watch
for any messages displayed on the screen that indicate
duplicate engineering units were found.
Discussion If a message is displayed indicating this, DO NOT continue

with the Uniformance database upgrade. Refer to the
Business.FLEX database upgrade manual to find and apply
the patch that will fix this problem.
After the Business.FLEX patch has been applied, you may
continue with the Uniformance database upgrade by re-
running upgrdprep to insure no further issues exist, and then
continue with the upgrade.

11. Special Considerations for Application Server
11.1 EJC unable to collect data
Description EJC unable to collect data after the node name is changed.
Discussion On initial set-up of EJC, the current name of the node from
which data is to be collected is stored in the registry. EJC
uses this registry entry as the key to access the configuration
data stored in Oracle. If, subsequently, the node name is
changed (including from lower case to upper case) and EJC is
re-installed, EJC will not be able to access its configuration
information until the database entry is corrected to match the
current node name.
11.2 EJC may crash on APP Node 211

Description EJC has been observed to crash on APP node 211 unless the
latest Window updates, including MDAC 2.7, have been
installed.
11.3 Installation – Recovery of Registry Settings for the

Application Server
Description Users should record the current settings of the Registry entries
for the Uniformance applications prior to upgrading and
should review these after completing the upgrade.
Discussion The installation process may over write the Registry settings
for the Uniformance applications. The key to check is
HKLM\Software\Honeywell\Uniformance\Apps Server\
Evt_Jrnl\DBConnect

11 Special Considerations for Application Server
11.4 EJC Needs to be Restarted if the LCN is Reset
11.4 EJC Needs to be Restarted if the LCN is Reset

Description If the LCN is reset, either through the Native Window, or
from the App node, the user will need to restart the EJC
service.
Discussion If EJC is running on the AppNode with a connection to to the

LCN and the LCN is reset, then EJC will lose the connection
to LCN and will not be able to regain it. Therefore, it will be
necessary to restart the EJC service.

12. Special Considerations for Tools
Page intentionally left blank.

13. Special Considerations for Documentation
13.1 Documentation Added to Media
Description The following documents have been added:
• IN-060 PHD Server Installation Guide
• IN-100 Windows Database Installation Guide
• PIM-410 Database Administrator's Guide
• RDI-410 PHD/Experion Server Configuration Guide
13.2 Documents Renamed

Description The following documents have been renamed:
• IN-080 TPI Installation Guide to PHD

Configuration Tool Installation Guide
• AM-010 TotalPlant Information Application User

Guide to PHD Configuration Tool User Guide
• AM-080 TPI Administration User Guide to PHD

Configuration Tool Administration User Guide

14. Problems Fixed in Uniformance PHD 210
The following customer defects have been resolved in Uniformance PHD R210:
14.1 PHD Problems Fixed

PHD Server
Defect Number First Released Description
Installation of R201 PHD server was running but after cold

1-11U0K5 201.1.6 / 202.1.2
start nothing works
?Queue overwrites? on PHDMAN Mon Que screen shows

1-12LB1I 210.1
wrong number when Data Storage is disabled
1-13XSG6 210.1 PHD Server Crash
Degradation in PHD performance, followed by phdserver

1-1418QL 201.1.6 / 202.1.2
crash
A call to phdapi_getlist causes Visual PHD OLE Server

1-14AHSN 201.1.6 / 202.1.2
crash
1-14JO0D 201.1.6 / 202.1.2 Robustness Improvement
1-14VVNY 201.1.6 / 202.1.2 Crash on PHD shadow server while testing
1-14ZVJS 201.1.6 / 202.1.2 WPKS incompatibility
1-1548GR 201.1.6 / 202.1.2 RDIServer leaking handles and memory
problem with an OPC client accessing tags via transparent

1-1548IS 201.1.6 / 202.1.2
data access
1-15J50Q 201.1.6 / 202.1.2 Memory Leak in APIServer and LegacyAPI
1-15O4DN 201.1.6 / 202.1.2 Memory leak in PHD server
A memory leak occurs in PHD when performing Get Data

1-160Z6N 201.1.6 / 202.1.2
Requests using Transparent Data access.
1-1640EV 201.1.6 / 202.1.2 201.1.5 APIServer and LegacyAPI memory leaks
1-178QMR 210.1 Archive utilities require further kernel functions exposed.
1-17MJRF 202.1.3 Tag Audit logging enhancement
1-194R9C 201/202 Patch Client problems after server upgrade to

14 Problems Fixed in Uniformance PHD 210

PHD201.1.6/202.1.2.
The command "phdstart /install" or "phdstart /remove" does

1-1985N6 210.1
not exit properly.
PUT from PHD Desktop tools no longer returns error when

1-19W3ST 202.1.3
RDI down
1-1CGC5X 210.1 Uniformance PHD 201 Legacy API Problem
1-1CJ7ST 201.1.7 / 202.1.3 PHD - prob - it's crashing unknown cause, slow to reboot
PHD- exceeding user limit, cant get access to data during

1-1CK2E0 210.1
recovery, SCN Also needed
PHDMSWB32.DLL forces server connection to perform

1-1D6SF7 210.1
date conversions
Security hole! When connecting to various PHD servers the

1-1DYMM9 210.1
access token does not get updated.
Needs to disable logging feature in PHD for tags w/ bad

1-1EIHAU 210.1
values.
RemotePeer200 does not collect data if source tag

1-1GSFH1 210.1
specifies an expression rather than a tagname
1-1F42AX 210.1 USM malfunction
Can not upgrade PHDSERVER component to 201.1.7 from

1-1JEVFW 201.1.7
201.1.6 on a W2KServer
Wrong user identity when issuing PHDMAN commands and

1-1MIUM5 210.1
even tag updates
1-1O5MAJ 210.1 PHDServer problems
PHD Server termination may be a result of a locking logic

1-1SLEZS 210.1
error on deleting the last client entry
1-1VV74X 210.1 PHD rejects all of client connections
1-1VYCML 210.1 apiserver stopped
1-1W7ZO7 210.1 arc_open and arc_fetch errors
1-20EHRZ 210.1 PHDServer Service Termination
1-OHFY1 210.1 Performing Tag update full does not pick up when a tag is


made inactive. TPI send does work.
1-RY5RX 210.1 PHD Server loops forever at about 80% CPU
1-S1LCJ 210.1 PHD problem, can't modify tags
PHDServer CRASH on COLLECTOR with VIRTUAL TAG

1-U5ATX 210.1
having too many input tags
Installation of R201 PHD server was running but after cold

1-Z2M2M 201.1.6 / 202.1.2
start nothing works
PHD Calculations
1-169BRS 201.1.7 / 202.1.2 Daily tags collecting at 6:00 instead of midnight.
1-1A0YGG 210.1 PHD Server getting stuck in coldstart on INIT PROCEDURE
1-1DWRS5 210.1 EP1A & phred.toler [PHR_Delta]
1-1E8YLX 210.1 Invalid Excel calculation
PHDGETDATA error when formula is used in name range

1-1EE305 210.1
that contains tag list
1-1FYOQL 210.1 using excel companion getting error invalid time enter
1-1H6K0L 210.1 $substr() fails with corrupted CHAR values
1-1JJ51T 210.1 Failure in Uniformance add in for Excel
PHD function definition does not work for function

1-MIGBK 210.1
$SUBSTR
problem with virtual tag calculation involving another virtual

1-RVSPP 210.1
tag with time delta tag
1-UJRRN 201.1.7 / 202.1.3 REGSLOPE calculation returns erroneous results
When Archive Resample is selected for Virtual Tags,

1-VFJ65 201.1.6 / 202.1.2
retrieval of data returns EOD.

PHD Data Storage / Extraction
1-11LD9W 202.1.2 PHD RDI stuck in TAGLIST on my Shadow Server.
1-13ZXWO 201.1.6 / 202.1.2 Add exception mode to Virtual RDI
1-1422X2 201.1.6 / 202.1.2 Legacy API PHD server crashing
1-14C9OL 210.1 PHDExport is so slow, it's unusable
1-14FN8F 202.1.2 PHDExport only writes first char of tagname to log file
1-14KKSD 201.1.6 / 202.1.2 Data retrieval issues for CHAR tag from R150 archives
PHDExport file contains data outside of specified time

1-14KW9G 202.1.3
period
1-1579JP 201.1.6 / 202.1.2 Incomplete error handling in getdata
PHD201.1.5 hangs when querying for manual input data

1-15QG7F 210.1
and MANV is empty
Transparent data access does not work with manual input

1-161I69 210.1
tags
CUR GBL Sizes incorrectly calculated. Exorbitant CUR

1-173UUZ 210.1
section sizes.
Only local manual input tag updated. Deficiency in

1-177055 210.1
Transparent Data Access
If MANV is empty, a query for a manual tag with data in

1-17GYIS 210.1
SCAN (from 150 system) returns EOD
Put download fails using REL_TO_PHD to write to LCN but

1-17MR3X 202.1.2
OK into PHD shadow archive.
1-191B8V 202.1.3 PHDImport fails to import to remote PHD server
Pulling data from PHD, virtual tags, manual or character

1-191W79 210.1
tags, PHD CPU goes to 100%
Need to retrieve manual data distributed over multiple PHD

1-197JWN 210.1
hosts using Transparent
1-19F0X1 201.1.7 / 202.1.3 MISEED does not seed MI tag values to the queue
1-1ALJ5P 202.1.3 PHDExport creates unreadable binary files

1-1ASV23 201.1.7 / 202.1.3 Legacy API Server Crash
1-1BCK0G 201.1.7 / 202.1.3 Gross Error Detection does not work correctly
1-1BERMC 210.1 HIGH - 1-79623710 - PHD Server service is crashing
1-1BI8N5 201.1.7 / 202.1.2 1-77673514 - APIServer issue
1-1CAAQF 201.1.7 / 202.1.3 PHD201.1.6 data queue shows duplicate values.
1-1CYQVR 202.1.3 "NOSUCHTAG - Specified tag does not exist"
1-1DOSOM 201.1.7 / 202.1.3 Data integrity problem with Enumeration data
1-1E3P5A 210.1 Queue overrides caused by gross error detection
When fetching snapshot data, it is supposed to extrapolate

1-1EE18X 201.1.7 / 202.1.3
from the last good stored value.
MANV archives are not rolling over when MAX_ARCFILEKB

1-1EUJ0K 210.1
is reached
PHDMAN fails to find data in archives if start date is in the

1-1EUZ01 210.1
future
PHD storing duplicate bad values and causing archive

1-1F9JMD 202.1.3
overlaps
1-1FD5VB 201.1.7 / 202.1.3 getdata returning incorrect error code
PHD Stored Virtual Tags - forced recalculation by

1-1FGADM 210.1
referencing tags. Over-write stored value.
1-1G0J5W 201.1.7 / 202.1.3 '"Gross Error Elimination" algorithm does not work properly
1-1GS30O 210.1 phdserver.exe crash when modifying historical CHAR data
1-1HFZ78 210.1 phdserver.exe crash caused by MISEED
1-1I12S1 210.1 archives do not automatically rolled over
PHDMAN SHOW DATA does not display archive records

1-1N6MRB 210.1
with future start dates
1-1N6MST 210.1 MISEED does not seed future values
Unusually long response times for large data request

1-1OJUNJ 210.1
against a single archive

Timestamps for puts from PHD Desktop are stored one hour
1-1RGH5U 210.1
ahead of actual time.
Issue with rel PHD service not restarting when api service
1-1Y9H2L 210.1
restarts
1-20MPWP 201.1.7 Legacyapi crash
1-2FS7QB 210.1 APIServer stopped during testing of new 202 patch
1-358UTN 201.1.7 PHD is displaying wrong values for datatype enumaration
Ability to define all routings in Oracle and use table to

1-7CBUN 210.1
populate routings on server
1-I1C6V 210.1 Enhance error message to include the tag number.
1-MS0DD 210.1 Archive had data for tags that were outside the end date.
Data incorrectly timestamped in Shadow Server when

1-NOKJY 210.1
DELTACLOCK exceeded.
Prevent data being written to a PHD archive when

1-O4ED2 210.1
CONSTORE is disabled.
1-OUB7N 210.1 UPDATE TAG FULL error
1-QVKT9 210.1 PI RDI & Date in Archive Files
1-S9V4J 210.1 Long data extraction times for character tags
1-SWZX0 210.1 Backup of the archives that are kept open for write
1-V1LGZ 210.1 Namespace Server does not pick up tagname updates.
1-V3MNH 210.1 Archives erroneous start date
PHD crashing when working with ProTrend and

1-W59TE 201.1.6 / 202.1.2
PRISM/WPKS
PHd rel date header archive has date time stamp that
1-WJYQ9 210.1
appears to be wrong
PHD201 Doesn't Enforce Hi/Lo Extremes For Manual Input

1-ZED27 210.1
Tags

PHD Administration
1-14KW8V 201.1.6 / 202.1.2 Typo in APIServer telnet session
1-1537WW 210.1 PHDMAN fails to connect to FQDN
1-1CBUR5 210.1 Uniformance certified for 2003 Native Domain
1-1FJ1MN 210.1 Display state of INTS on PHDMAN display
1-1JEBPG 210.1 PHD connection confusion
1-1JZ6TB 210.1 PHDMAN corruption
1-1SHYEM 210.1 R201.1.6:when in PHD Mgr to mon que tag#-access denied
1-1Y0BPF / If tag names don't exist, what happens to PHD import &
210.1
1-1YMQZR Exports
1-1Y47DR 210.1 Kernel functions need to be exposed
1-24NR05 210.1 Error: [10007]-W-FAILED-Specified Operation Failed
Tag security takes precedence over PHD_MANAGER

1-JMAP5 210.1
group
1-UAJ6L 210.1 Transparent data access does not support Manual tags.
Tag Configuration versus Tag Query case sensitivity

7N-6U2O 210.1
asymmetry in TPI.
PHD Manager
PHD R202 problem in PHDMAN- command sho route gets

1-16OCX3 210.1
error 10010
RDIServer crashes when connection cannot be

1-1W6B7G 210.1
authenticated through SSPI
PHDMAN freezes when connection is attempted by an

1-1ZKB3V 210.1
account that is member of sufficiently many groups
1-I0G2H 210.1 Remote Connections to RDIServer don't work with WTS

OPC Server
OPC Client connected to PHD OPC Server doesn't "see"

1-16CR84 210.1
changes made to PHD tag units.
OPC Client takes too long to disconnect from PHD OPC

1-16CRBX 210.1
Server with more than 2500 items per OPC group
PHD OPC Server does not implement aggregate

1-173WDU 210.1
OPCHDA_COUNT (required by AFM: FXTAGCOUNT)
When using a list of tags to request PHD Value, the errors

1-18TB93 210.1
are Hidden.
1-18TBAC 210.1 PHD Uses wrong connection
1-1AGLNV 210.1 OPC Server is leaking memory in 4K chunks
1-1BCJQ7 202.1.3 OPC Server leaks memory
1-1C2138 210.1 OPC Server crashes when PHD is stopped.
1-1C6PKG 210.1 OPC to PHD problem with the connection
Problem with PHD OPC server - if you request invalid tag it

1-1CNGYI 201.1.6
comes back with bad status
1-1CRN0N 202.1.3 incorrect data from OPCHDA server
1-1FVMLL 210.1 OPCServer crash when CreateLogFile is set to 1
bug in the PHD HDA OPC server (relates to SetLocaleId

1-1VSS7L 210.1
function in the IOPC Common Interface)
1-1XC965 210.1 OPC Server memory leak
OPCHDA_COUNT function does not work after applying

1-MOIGP 210.1
200.1.2
1-O00T8 201.1.4 'incorrect data from OPCHDA server
1-QE626 210.1 AFM designer - parsing the source file improperly
1-Z0E07 201.1.6 / 202.1.2 UA is not fetching PHD Data and hanging continuously.
5V-10YZ7 210.1 HDA Server does not implement MAXIMUM correctly
PHD200 HDA Server returns incorrect timestamp for

5V-10YZI 210.1
MINIMUMACTUALTIME and MAXIMUMACTUALTIME

14.2 RDI
5V-10ZY1 210.1 OPC HDA Wrapper does not handle TIMESTEP correctly
Tag / User Security
Defect Number First Released

Description
User profile table should not be loaded when the

1-1G8K9G 202.1.4
customer is running in INTS mode
1-1SV2K0 210.1 Some client cannot connect to API Server
1-1VM1L4 210.1 Tag security not observed without DBSecurityServer
Tagloader / Import / Export

Description
5024507 210.1 PHD doesn't like long tagnames
1-1A564T 202.1.3 Add switch to PHDImport to ignore non-existing tags.
PHD R201 & PHDImport - when tag not found, import

1-1DGEAN 210.1
aborts
1-1HNQCY 202.1.3 PHDimport not working
14.2 RDI
RDI Server

Description
1-13PTIG 210.1 RDIServer loses connection to PHDServer
1-141X3M 201.1.6 / 202.1.2 Download fails on First Tag in List on Collector Node
PHD RDI peer to peer communication problem, not

1-1422BY 210.1
connecting
Logging bad value messages to event log masks

1-17705M 210.1
serious errors
1-17708L 210.1 Terminal Services prevents communication with

14.2 RDI

Description
RDIServer
PHD RDI server.exe on buffer node has memory leak

1-17FXV6 201.1.6 / 202.1.2
R202.1
1-17HFKV 202.1.2 / 201.1.7 Occasional RDI Server Interruption on 201.1.5.
1-18XHUI 210.1 Reading QNAN and display 100% confidence
1-19WR7Q 201.1.6 RDI Server is crashing once a day
GatewayRDI's .out file needs to show more meaningful

1-19Z0GP 210.1
messages.
1-1ABD3D 210.1 RDI does not support out of sequence data
1-1FQU9C 201.1.7 RDI Server Crash
PHD OPC RDI talking to Experion OPC Server reports a

1-1GJXO2 210.1
Bad Value as 0.0 with 100% confidence
1-1QDT6R 210.1 Problems setting up new PHD R201.1.7 node for testing
1-MXSBV 210.1 RDI on Shadow server is stuck in Taglist
1-WXYAG 201.1.6 / 202.1.2 rel 201.1.3 giving errors on RDIs, invalid handle
1-X2BE3 201.1.6 / 202.1.2 Having problem with OPC RDI
TypeA – Honeywell

Description
After upgrading from PHD 200 to Uniformance 201.1.5.1

1-166K3E 210.1
the OPC RDI does work anymore.
Unable to alter RemotePeer to use other than port 2000

1-1BF1LW 210.1
for PHDServer
Performance improvements required for OPC RDI

1-1CI7JT 201.1.7 / 202.1.3
integration with Experion.
When using gateway/remotepeer150 and setting

1-1RC2PJ 210.1
prefetch causes rdi to remain inactive/inactive
1-1Y7WE7 210.1 RemotePeer150 crashes

14.3 Desktop

Description
Remote Foxboro RDI dies after pinging the Standby

1-NE3QY 210.1
server with no communication between them
Duplicate error_messages inserted by OPC RDI in

1-UDRCT 210.1
PHD_EVENT.log
MAX_STOREDELTA system parameter not behaving as

1-V8Q23 210.1
expected .
1-VX9O6 210.1 RDI Convert From Units fails.
With a redundant PS system the RDI generates

5V-10CNI 210.1
unnecessary messages
RUNRDI command times out when run from Terminal

5V-NQVI 210.1
Server client.
When configured for RDC PS RDI doesn't do History

7N-30SP 210.1
Recovery
14.3 Desktop
Companions
Description
Excel Companion R202.1.1 generates error -E-

1-13QQ9G 201.1.6 / 202.1.2
NOMEM-Unable to allocate memory
1-15101U 202.1.2 Uniformance Excel Addin Failing
1-159QTJ 202.1.2 Excel Companion indicating "Invalid Time"
Excel Companion continues to use the previous value (it

1-15KN75 202.1.2
doesn't reset the option back to 0 until Exc
Excel Companion fails to retrieve most attributes in non-

1-15P2F3 202.1.2
Matrix mode
Date format problem with Uniformance 202.1.1 Desktop

1-16AXLW 202.1.2
running on Office 2003.
1-16GUQ7 202.1.2 MEDIUM - 1-70189761 - 202.1 Desktop
1-16J00X 202.1.2 Uniformance XLA Error

14.3 Desktop

Description
1-1D2YGI 202.1.3 Excel Companion Overall Reduction
1-1D2YHP 202.1.3 Excel Companion Overall Reduction
PHD does not handle DST correctly from Summer to

1-1DA6NI 210.1
Wintertime. Causes loss of data in Excel Companion.
Problem with Uniformance Desktop R202.1.2 Excel

1-1DX1XD 210.1
Companion
Problem with Uniformance Desktop R202.1.2 Excel

1-1DX3U9 210.1
Companion when results are saved in Text format
Desktop v202.1.2.5/v202.1.2.6 -Excel cells value gets

1-1F8ITQ 202.1.3
erased under certain conditions
Excel Companion 202.1 errors when calling the same

1-1FCOGG 210.1
tag more than once in the PHDGetData window
PHD_GETDATA does not return expected data when

1-1FGSFL 202.1.3
request is YEAR to YEAR+1D
Excel Companion does not support mixed case

1-1HNQR3 210.1
engineering units in ad-hoc calculations
1-1IPKZZ 210.1 Infinite loop in Excel Companion quickchart
1-1SHQ3B 210.1 Excel Companion handle leak
1-1VPSXH 210.1 Problem with Snapshot query
Small issue in ModTag's Tag Definition Dialog -

1-Y3ZAZ 202.1.2
Interpolation Method, case manual input tag
General and Installation

Description
WPKSActLIb Active X control does not correctly handle

1-13PVZ7 202.1.2
absolute times
Garbage characters in string tag with VB application -

1-169LAC 202.1.2
OLE Automation Server
Uninstalling the Uniformance System Monitoring

1-17E0LN 210.1
application, also uninstalled the PHDstart service

14.3 Desktop

Description
1-17H349 202.1.2 PHD DB Security Server does not install PHDknl.dll
1-1AREET 210.1 PHD202 desktop installation ?
After 202 Upgrade user profile still points to USERS_TS

1-1BC5IZ 210.1
and TEMP_TS
1-1CJ7OX 210.1 Uniformance Config Tool Installation Error
PowerPoint Companion 202.1 visual PHD tool bar does

1-1ISKBD 210.1
not install on Windows XP with Office 2003
1-1O6TPB 210.1 UNF202 upgrade step 15 creates unexpected error
PowerPoint Companion does not install on Windows XP

1-244AKB 210.1
system running Office 2003
1-JNJB3 210.1 R200 Script Issue
1-NORMT 210.1 Problem in guspro trend
1-VORIB 210.1 PHD - Shadow server config
1-YEY07 210.1 Desktop installation problem
Process Trend

Description
Crashes with Serious Error message & run time error

1-12LEM3 202.1.2
message
Process Trend: 'PlotTagDefinition Error: Error 6:

1-13PNKM 202.1.3
Overflow'
Process Trend is corrupt when using the feature “save

1-18W5IX 210.1
username and password”
Uniformance Process Trends Auto Scale Value Axis

1-18Z824 210.1
sets values to low 0 and high 4
Process Trend - R202 Customer would like Favorites

1-195HDB 210.1
behavior restored to its R160 style
1-1BIE0T 210.1 Bad object handle error on invoking process trend from

14.3 Desktop

Description
Workcenter trend for regression
Process Trend cannot be invoked from a Workcenter

1-1BJYG4 202.1.3
Client Login
1-1CN8GT 202.1.3 Trend interaction requires administrative access
Process Trend crashes with an Runtime error 10000

1-1RUKWQ 210.1
Access Violation.
1-5PALN 210.1 Process Trend issue
1-NGZGL 202.1.2 Process Trend does not return correct average values.
Process Trend Time axis Snapshot frequency is

1-VBG0E 210.1
displayed incorrectly when hairline cursor is active.
Process Trend - "PHD Login" feature does not save

1-VBRT8 202.1.3
password
1-YQW7Q 202.1.2 Process Trend crashes on clicking on Copy button.
OLE DB Provider

Description
Wrong Engineering Data IP_PHD_REDUCTION

1-18FSDF 202.1.3
averages
1-1G5RVO 210.1 System upgr after that prob is manual input tags.
Require changes to OLE DB provider to get string,

1-J6CVC 210.1
integer, float values into Crystal Reports
1-X4ZIB 202.1.1 Excel Companion Error when Fetching Data
PHD R201 OLE DB Provider can write to virtual tag

7N-C0WN 210.1
without getting an error message
Visual PHD

Description
1-144Q1Z 202.1.2 Tank Calculator stops working with Desktop 202

14.4 Database

Description
Requirement to have the clients (OCX control) better

1-1537LH 210.1
manage no timely response of PHDServer
1-178LTF 210.1 PHD Tag Name Problem
Visual PHD object - maximum rows property - doesn't

1-1AFRQM 210.1
accept failures R201
Visual PHD DownLoadStatus not correctly handled in

1-1B2QZG 210.1
R202
1-1BTC56 210.1 Visual PHD 202 can't handle large data requests
Garbage char data retrieved from VisualPHD when

1-1DNCQB 210.1
using record navigation
After upgrade of PHD server, virtual tags don't work

1-1FWU8Y 210.1
w/VB calls
Custom data request using Visual PHD is returning

1-2XH2O3 210.1
values different than what is seen using Modtag
When trying to use the ZoomOut function in VisualPHD

1-YP1NK 202.1.2
with the PHDGraph object the method fails.
When using visual PHD graph control PRINT method it

5V-Y999 202.1.3
returns an error.
14.4 Database
Description
1-160ZE2 210.1 DELPRLD.SQL incorrectly references IP_APPL_ERR
Add New Record command button was disabled in User

1-1DWQ0A 210.1
Profile Configuration
Commit permission failed after db upgrade from 150 to

1-1H7SPI 210.1
202
Possibility of running out of disk space during an
1-39EXGU 210.1
upgrade to uniformance 210.
1-R508L 210.1 Insufficient range in engineering unit scaling factors

0

Description
1-U6Z4U 202.1.2 Menu items get deleted when upgrading

14.5 PHD Configuration Tool (previously named TPI)
14.5 PHD Configuration Tool (previously named TPI)

Description
1-171HA2 210.1 PHD 202, unable to use TPI on buffer node
1-1HF8GK 210.1 Can't change TPI totalplant password
The Scan Frequency Units is not inherited from the

1-1HG1ZK 210.1
parent tag in TPI
Uniformance TP! R202 External Data Cross Reference

1-1XCYX0 210.1
does not know table IP_PRPRTY.
TPI in R200 if you remove the assigned parent tag the

1-JE9EF 210.1
effective inheritance is not reset
When cold-started, PHD reports errors for old,

1-OUCEV 210.1
nonexistent virtual tags
14.6 Application Server

Description
PHD to REL is returning 0,0 for all tags for all

1-11LRSD 202.1.2
configurations
1-13XE8R 202.1.2 Event Journal Collection terminates prematurely
1-1409KH 210.1 R201.1 EJC event collection is 1 hour behind
Memory leak found in pipetophd in R202 Application

1-142AWV 202.1.2
server
1-14JZZ2 202.1.2 problem w/ collecting event journals PHD 202
Previous day's data in EJC tables gets deleted with

1-14QO1F 202.1.2
default EJCMAXDATADAYS value.
1-164M6H 202.1.2 A small memory leak exists in EJC.
1-168FTR 202.1.2 R202 PHD2REL does not work properly.
1-17MJSD 202.1.2 The pipetophd process leaks memory

14.7 Documentation

Description
PHD2REL stops function when Oracle is shutdown and

1-18L4T5 210.1
restarted
1-GZVUT 210.1 EJC Reports
14.7 Documentation
Description
How to start PowerPoint Companion with 201 Desktop

1-10OEGK 210.1
installed
PowerPoint Companion's ppcomp.dll is not referenced

1-11TXKK 210.1
in the PowerPoint Companion User Guide
1-121Y6Z 210.1 New User Role assignments did not take effect
Incorrect titles in two PHD Configuration Tool

1-12IVT5 210.1
(previously named TPI) Help Files
1-12IWOK 210.1 Database System Spec and Tech Data Corrections
1-12IXAP 210.1 Visual PHD User Guide Errors
1-12IY0Q 210.1 Tag Explorer User Guide Errors
Document Summary for Uniformance 202 Reference

1-12IZ1E 210.1
Guide
1-12J034 210.1 Infrastructure Management User Guide
1-12J1TW 210.1 PHD System Manual Documentation Errors
1-12J3B6 210.1 Manual Input RDI installation guide
1-12J3OF 210.1 OPC Server Installation Guide
1-12JB0P 210.1 Uniformance logo

1-12JBL6 210.1
Installation Documentation
1-12L5DZ 210.1 Application Server Installation Guide
1-12L74F 210.1 Desktop - Inconsistency in About information, logo,

14.7 Documentation

Description
copyright info.
Experion/PlantScape RDI Installation Guide info re

1-12L7WA 210.1
redundancy
1-12L9WY 210.1 Scan frequency in milliseconds.
Automatic error checking in log files (Part of

1-12QFYN 210.1
Requirement 3.3)
1-12QG01 210.1 Release OPC Automation Wrappers (Requirement 7.4)
Improved RDI Services (RDISetup) when Multiple RDI

1-12QG1X 210.1
Servers are installed (Requirement 3.3.6)
1-12QG4N 210.1 PHD Functions calling PHD Functions
Discrepancies in PHD Configuration Tool (previously

1-12QG6J 210.1 named TPI), PHDServer, Database Installation Guide,
and PHD user guide.
1-12QGAL 210.1 Engineering Unit Conversion Issues
Uniformance database migration will fail if custom

1-12SLD1 210.1
tablespaces exist
1-13PBO0 210.1 Uniformance PHD Server Installation Guide
1-13PNGY 210.1 ModTag User Guide
Manual input tag accepts values beyond the high - low

1-13PNSH 210.1
extreme range defined in TPI.
1-13PQGM 210.1 Security Overview
1-13PQO0 210.1 PHDMAN User Guide
1-13PR1H 210.1 Database Administrators Guide - suggest clarification
Database Administrators Guide - invalid document

1-13PR3X 210.1
reference
1-13PTH5 210.1 Process History Database User Guide
1-13PTJU 210.1 App. Server Help : Query form shown is not readable
ScanRate value displayed in MON QUE screen is

1-13PTM1 210.1
incorrect.

14.7 Documentation

Description
1-13PTNE 210.1 Documentation for Archive Resampling
Behavior of INTEGER types is not correctly described in

1-14GAZ7 210.1
PHD System Manual
R20x documentation does not address the limitations of

1-14GT4V 210.1
Transparent Data Access
1-14NG0D 210.1 ICE testing Oracle removal
1-14NGGJ 210.1 ICE testing System Path
1-14NGOE 210.1 ICE testing - Oracle patches
Improvements to Uniformance Database installation

1-14ODJ5 210.1
guide
Commit all Permissions in TPI fails /w ODBC Error on

1-14PKEG 210.1
UNISECURITY.SETOBJECTSECURITYFORROLES
1-158JW7 210.1 [[OM]PlantScape RDI is not becoming active.
1-15M61V 210.1 Document registry setting for BypassXHistRecovery
Low - 1-70398621 - Confidence of extrapolated data -

1-15WVYZ 210.1
documentation conflicts (QUAS00001722)
SCN is not clear on the impact of the PHD_HOST

1-160ZM4 210.1
registry key.
1-1617SD 210.1 PHD Server R202 compatibility with Oracle 8i Client.
Oracle 8i Server/Client uninstall requires PHD and/or

1-1617SY 210.1
MSDTC to be down
1-1617TH 210.1 Oracle Client uninstall does not mention %PATH%
1-1617U2 210.1 Oracle 9i Client installation requirements are not clear
1-1617UN 210.1 Upgrading is not covered in sufficient detail
1-1699FT 210.1 Value of PHD noise gating must be set above zero
PHD Server Installation Guide - PHDMAN MON SYS

1-17AQUI 210.1
screen given is incorrect.
1-17AQWP 210.1 Desktop - Excel Companion; LIMS gives ODBC Error.

14.7 Documentation

Description
Scale Low Extreme and Scale High Extreme do not

1-17AR0R 210.1
work against Manual Input tags.

1-17AR44 210.1
Installation guide
1-17AR5K 210.1 PHD System Manual Documentation Errors
1-17IZAQ 210.1 Documentation for AM060 - Security Administration
1-17WIAE 210.1 annotations in process trend - cannot move around
EJC Reports - Cannot Query Point Name using =

1-188ZN1 210.1
operator
1-18JMMO 210.1 Legacy API problem causes OPC problem
Data item will not be updated when status changes from

1-18V4MM 210.1
not_OK to OK.
1-19SW00 210.1 registry change during patch 202.1.2 install
1-19VCGH 210.1 Installation of PlantScape/Experion RDI documentation
wants to understand maximum store delta parameter,

1-1A39BH 210.1
PHD 2.1.6
1-1AENG9 210.1 Parameters from Remote Peer RDI Installation Guide
Improvement request for RDI initialization(related to

1-1AR4ID 210.1 SR# 1-72241981)
Improvement request for RDI initialization(related to

1-1AR4JW 210.1 SR# 1-72241981)
1-1B547P 210.1 PHD Documentation does not describe MISEED
1-1BDFJC 201.1.7 / 202.1.2 Question on RDC History Recovery
1-1BTG7C 210.1 Incorrect definition of $time() function
Problems with connection R202 Desktop to Server

1-1CN7GH 210.1
across Firewall
PHD documentation does not specify default

1-1CUOSV 210.1
compression for tags
1-1DG39G 210.1 OPC Server installed on PHDServer and pointing to

14.7 Documentation

Description
another PHD Server will not function.
1-1DIC3Q 210.1 help setting up OPC RDI
1-1DNZUP 210.1 Problems with hostnames longer than 15 characters
Uniformance 202 Security Administration Guide

1-1DWPVJ 210.1
references an invalid parameter
Uniformance 202 Security Administration Guide and

1-1DWPW6 210.1
Domain users

1-1DWPXC 210.1
UNISERVER domain user

1-1DWPXY 210.1
Update Users command in TPI Admin

1-1DWPZE 210.1
ODBC configuration
PHD Documenation neads clarifaction on disabling

1-1F6QQ7 210.1
Constore for MANV archies.
Windows 2003 DEP feature is terminating TPI and

1-1GFSEU 210.1
ip_schedule.exe
PHDMAN uses require 445 and 137to be open to

1-1GFSHU 210.1
connect to PHD Server
RemotePeer200 does not collect data if source tag

1-1GSFH1 210.1
specifies an expression rather than a tagname
1-1GUGIQ 210.1 EPKS RDIs in RDC mode switching all the time.
1-1HBEXE 210.1 RDIs Not Working
1-1HH80S 210.1 How to turn on MISEED.
1-1HPLRF 210.1 Data transparency is not working
Documentation is unclear on functionality of

1-1HUD7Y 210.1
PCT_STATEQSIZE PHD system parameter
1-1HZ94L 210.1 OPC RDI configuration of long source tagnames
1-1ISKDI 210.1 PP Addin not used anymore on companion 202.1

14.7 Documentation

Description
PHD does not support unit conversion for INTEGER

1-1JMTXD 210.1
tags
1-1N1AF9 210.1 Question re exception condition interface
1-63824 210.1 Comma in property causes error in EXCEL/LIMS
1-7XALN 210.1 Customer thinks he found a bug in the TAG Loader
Virtual tag expression does not support all reduction

1-D2UPV 210.1
functions
1-F4L6Q 210.1 ASCII format for PHDimport
1-I607Z 210.1 PHD- RDC command not working with 2nd RDI server
Installation process does not check for multiple copies

1-KLU9F 210.1
of MultLang32.dll and system.mdw
Updating the Release 200 Collector cause the

1-LG4C5 210.1
PHDSRVC.EXE program to crash
Namespace Server TPI configuration is wrong. Value

1-LSG4H 210.1
should be RDIName and desc should be Gateway ID.
Improve explanation of the IDB option in the LxS RDI

1-M4DOI 210.1
documentation.
Mapping between OLEDB and VisualPHD retrieval

1-MLLZK 210.1
types
1-MZ913 210.1 Has ? about how to do report query in PHD
Lxs RDIs able to download data to TPS system even if

1-NE304 210.1
"CONTROL" keyword is not set up in GO RDI file
The precision of $TIME() within Getdata function in

1-Q0MYT 210.1
Excel Comapnion.
RDI-service crashes when OPC-RDI (Exception mode)

1-QRI9M 210.1
against DaVinci OPC-server is started.
The settings of the MIN_HISTRECMN and

1-SVUQ8 210.1 MAX_HISTRECMN in the PHD system Manual is
incorrect
1-U6CK9 210.1 PHD Failure if more than 682 archives connected

14.7 Documentation

Description
Parameter UnusedFileCache=5 should be documented

1-UIY5F 210.1
in user documentation
Documentation does not mention parameter "/l" to run

1-X18QD 210.1
RDI in local PHD mode
Visual PHD documentation refers to incorrect versions

1-YAB91 210.1
of Visual Basic
1-YRC89 210.1 PowerPoint Companion contains outdated material.

15. Recommendations for System Administrators
15.1 Disaster Recovery
For PHD Uniformance Oracle Database backup guidelines, see the Database
Administrators Guide (pim410).
For PHD Archive backup guidelines, see the PHD System Manual (pim030).
15.2 Anti-Virus Recommendations

Overview
Anti-Virus software is one element of a comprehensive process control security strategy.
Anti-Virus software will prevent some virus attacks. For the remainder, Anti-Virus
software will help alert that a virus has infected the system and my help in virus removal.
Recommendations
System Administrators should regularly check the Honeywell web-site for up-dated
information and recommendations.
PHD Server
Anti-Virus software should be configured to do a full scan at system start up
"On-demand" full system scans should only be performed when "safe" to do so as data
collection from the DCS may be impacted resulting in a possible loss of data.
PHD Archives in the SCAN, MANUAL, or CHARACTER classes should be excluded
from virus scanning.
System scans of the Oracle database are highly impactive and should only be performed
in accordance with the sites DBA / Oracle guidelines. In general, the Oracle database
should be excluded from virus scanning.
PHD Qualified Software

McAfee Anti-Virus
Norton Anti-Virus

15 Recommendations for System Administrators
15.2 Anti-Virus Recommendations

16. Problem Reporting
ATTENTION
If you have questions regarding this release, please call:
TAC at 1-800-822-7673
OR
Calgary Help Desk at support@honeywell.com or at 1-403-216-2870.

Honeywell International
Process Solutions
2500 West Union Hills Drive
Phoenix, AZ 85027
USA

5 1 2007 - 210SCN PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

5 1 2007 - 210SCN PDF

Загружено:

Авторское право:

Доступные форматы

Uniformance PHD

Other brand or product names are trademarks of their respective owners.

Model Number: UNMEDX-SCN

Honeywell Process Solutions

ii • Uniformance PHD 210 Software Change Notice

1. Read Me First ....................................................................................................... 9

2. Uniformance PHD Release 210 Users and Supported Platforms................. 19

Uniformance PHD 210 Software Change Notice • iii

3. Uniformance PHD Release 210 Functionality Changes ................................. 29

4. Uniformance PHD Release 210 Media.............................................................. 37

5. General Special Considerations....................................................................... 39

5.15 Legacy Code Needs to be Updated if Port Number is Appended to

6. Special Considerations for PHD Server .......................................................... 53

Uniformance PHD 210 Software Change Notice • v

7. Special Considerations for RDIs ...................................................................... 59

8. Special Considerations for Uniformance PHD Desktop ................................ 63

9. Special Considerations for PHD Configuration Tool (Previously Named TPI)69

vi • Uniformance PHD 210 Software Change Notice

9.8 Incorrect Data During TagLoad .............................................................. 72

10. Special Considerations for Uniformance PHD Database .............................. 73

11. Special Considerations for Application Server .............................................. 75

12. Special Considerations for Tools .................................................................... 77

13. Special Considerations for Documentation.................................................... 79

14. Problems Fixed in Uniformance PHD 210....................................................... 81

Uniformance PHD 210 Software Change Notice • vii

General and Installation ....................................................................... 92

15. Recommendations for System Administrators ............................................ 105

16. Problem Reporting...........................................................................................107

viii • Uniformance PHD 210 Software Change Notice

Uniformance PHD 210 Software Change Notice • 9

Uniformance PHD components

• Process History Database (PHD) Server

• Experion tools including an integrated data interface and a tag synchronization

• Type A Real-Time Data Interfaces (RDIs)

• Uniformance PHD Desktop

• PHD Configuration Tool - previously named Total Plant Information (TPI)

• Uniformance Database on Oracle 9.2

• Uniformance PHD applications

Prerequisite skills to install/upgrade and configure system

• Windows 2000 Server (SP4)

10 • Uniformance PHD 210 Software Change Notice

• Internet Information Server

1.2 Important Notes

12 • Uniformance PHD 210 Software Change Notice

210 Upgrade advisories

At minimum, the NtSite directory should be copied/backed-up prior to

1.4 Support for Migration from Oracle 8i

1.5 Customer-Performed Installation and Upgrade Guidance

14 • Uniformance PHD 210 Software Change Notice

1. PHD administration training or equivalent experience managing PHD systems. Specific

2. Oracle database administration training or equivalent experience. Specific skills required

3. MS Windows Administrator training or equivalent knowledge (including an

Additional considerations in determining the installation complexity and feasibility of a

Uniformance PHD 210 Software Change Notice • 15

Backup and Recovery:

Oracle Database Requirements:

PHD Server Requirements

Attention: For a complete assessment of feasibility, please contact a Honeywell Support

16 • Uniformance PHD 210 Software Change Notice

It is the responsibility of the customer to backup the system prior to starting

Honeywell will not be responsible for the unsuccessful upgrade of custom

Uniformance PHD 210 Software Change Notice • 17

2.2 Main Uniformance Nodes