Ig 51796

PDMS Installation Guide
AVEVA Solutions Ltd
Disclaimer
Information of a technical nature, and particulars of the product and its use, is given by AVEVA Solutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaim any and all warranties and conditions, expressed or implied, to the fullest extent permitted by law. Neither the author nor AVEVA Solutions Ltd, or any of its subsidiaries, shall be liable to any person or entity for any actions, claims, loss or damage arising from the use or possession of any information, particulars, or errors in this publication, or any incorrect use of the product, whatsoever.
Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every part of it (including source code, object code, any data contained in it, the manual and any other documentation supplied with it) belongs to AVEVA Solutions Ltd or its subsidiaries. All other rights are reserved to AVEVA Solutions Ltd and its subsidiaries. The information contained in this document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without the prior written permission of AVEVA Solutions Ltd Where such permission is granted, it expressly requires that this Disclaimer and Copyright notice is prominently displayed at the beginning of every copy that is made. The manual and associated documentation may not be adapted, reproduced, or copied, in any material or electronic form, without the prior written permission of AVEVA Solutions Ltd. The user may also not reverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of the product described in this publication may be incorporated into any third-party software, product, machine, or system without the prior written permission of AVEVA Solutions Ltd, save as permitted by law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal prosecution. The AVEVA products described in this guide are to be installed and operated strictly in accordance with the terms and conditions of the respective licence agreements, and in accordance with the relevant User Documentation. Unauthorised or unlicensed use of the product is strictly prohibited. First published September 2007 AVEVA Solutions Ltd, and its subsidiaries 2007 AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom
Trademarks
AVEVA and Tribon are registered trademarks of AVEVA Solutions Ltd or its subsidiaries. Unauthorised use of the AVEVA or Tribon trademarks is strictly forbidden. AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd or its subsidiaries, registered in the UK, Europe and other countries (worldwide). The copyright, trade mark rights, or other intellectual property rights in any other product, its name or logo belongs to its respective owner.
Contents
Page
PDMS
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Contents of this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1 Associated Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . 2:1

AVEVA PDMS 12.0 Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Licence File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Installing the Software Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1

Basic Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1
NET Framework Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1
Uninstalling and Reinstalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2 Flexman License Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2 Remote Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2 Silent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2
Deployment across a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployment using SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployment using logon script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployment using GPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example of deploy.bat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4 3:4 3:5 3:6 3:6
Setting Up the Windows Environment . . . . . . . . . . . . . . . . . . . . . . . 4:1

Windows Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1
2007 AVEVA Solutions Ltd
12.0
Graphics Card Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1 Setting the License File Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2 PDMS Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2 Running PDMS from a Command Prompt Window . . . . . . . . . . . . . . . . . . . . . . 4:4 Customising PDMS Start-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4
Creating Your Own Batch File to Run PDMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5
Running PDMS in batch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5 Plotting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6
Language Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1

Preparing Windows to use Supported Languages . . . . . . . . . . . . . . . . . . . . . . . 5:1
Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1 Windows XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2
Preparing PDMS to use Latin Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2 Preparing PDMS to use Far Eastern Languages. . . . . . . . . . . . . . . . . . . . . . . . . 5:3
Running PDMS Under Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1

Spaces in Windows pathnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1 Linking to Microsoft Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1 Windows Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1
PDMS Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1

Sample Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1
Copying Project SAM to Your User Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Users and Teams in the Sample Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MDBs in the Sample Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sample Project and your own Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1 7:1 7:2 7:3
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1 License Manager Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1 Entering PDMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:2 Problems with Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:3
Structure of PDMS on .NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1 PDMSEXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1
ii
12.0
GUI Module Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1

Wrappers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2 .NET Loading Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2 Win32 DLLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2
Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:3
PDMSEXE Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDMSEXE/DESIGN subdirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDMSEXE/DRAFT subdirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDMSEXE/MONITOR subdirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDMSEXE/ISODRAFT subdirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDMSEXE/ADMIN subdirectory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add-ins .............................................................. 9:3 9:4 9:4 9:4 9:4 9:4 9:4
Forms and Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:4
Troubleshooting the .NET Installation . . . . . . . . . . . . . . . . . . . . . . 10:1

Version Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:1 Wrappers or a Dependency Missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:1 Interface Incompatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2 No Add-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2 Window Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:3 Serialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:3
iii
12.0
iv
12.0

Introduction
Introduction
This guide explains how to install and set up PDMS 12 on a workstation running the Microsoft Windows 2000 or Windows XP operating system (hereafter referred to jointly as 'Windows'). Local Administrator rights are required to perform the installation. This guide assumes you are familiar with the concepts of folder/file hierarchies for storing data on disks and with basic Windows terminology and commands. If you are not, you may also need to refer to your operating system documentation while you carry out the installation. The guide also assumes that you have already gained access to the PDMS installation files via a CD/DVD, from the AVEVA Web site, or by some other route.
1.1
Contents of this Guide

Hardware and software requirements are described in: Hardware and Software Requirements. For completely up-to-date information, please see the AVEVA Website at http://www.aveva.com/products/support/support.html and refer to the Customer Support Hardware pages. The Web pages also give hints on ways of setting up and running PDMS on different computers in order to achieve the most efficient performance. Installing the Software Suite, describes how to install and license the software. Setting Up the Windows Environment, explains how to configure the Windows operating system before you run PDMS. Language Support, describes how to set up the Windows Environment to use PDMS with different Language options. Running PDMS Under Windows, gives some advice on using PDMS in a Windows environment. PDMS Projects, describes the sample project that is supplied as part of PDMS, and how to set up your own projects. Troubleshooting, describes solutions for some of the errors that you could encounter when running PDMS. Structure of PDMS on .NET, outlines the way in which PDMS in installed and configured in a Microsoft .NET environment. Troubleshooting the .NET Installation, describes solutions to some of the .NET related issues you might encounter.
1:1
12.0

Introduction
1.2
Associated Products
There are various AVEVA products that may be used in conjunction with PDMS. You may wish to consider installing these at the same time. Those closely associated with PDMS include the following DESIGN products: Global - for synchronisation of PDMS projects between world-wide sites Model Management - for change & status control of engineering objects (e.g. pipes, welds, ) from system DESIGN through detailing and into deliverable production
For details of the installation of these add-on products, please refer to the relevant installation guide. If they are required, it may be advisable to read these before installing PDMS.
1:2
12.0

Hardware and Software Requirements

Please refer to the Minimum Systems Requirements guide and ensure that your system and network meets all of the minimum requirements before attempting to install the software.
2.1
AVEVA PDMS 12.0 Software Installation

AVEVA PDMS 12.0 software is only supplied on DVD. The DVD contains Release Notes the User documentation in PDF format the Microsoft InstallShield wizard (which allows you to choose the software you want to install) an installable version of Microsofts .NET 2.0
First insert the disk in your Workstation DVD drive, and then follow the InstallShield instructions. If the disk does not start, click Start>Run, and then browse for the Setup.exe or Install.exe file.
2.1.1
Licence File
To operate, AVEVA software must be able to access the correct Flexman 3.1 licence file, which should be installed on either the Server, on your workstation, or on a networked workstation. Note: Although the disk contains several AVEVA products, you will only be able to use the items that are licensed to you. You will get an on-screen notification to warn you when the licence is due renewal.
2:1
12.0

2:2
12.0

Installing the Software Suite
3
3.1

Basic Installation
AVEVA PDMS 12.0 is supplied on DVD. The disk contains the Microsoft InstallShield wizard, and an installable version of Microsofts .NET 2.0. Also on the disk is a folder containing the Installation instructions and user documentation, and it is recommended that you carefully read all of the Installation instructions before installing the software. To install AVEVA PDMS 12.0, first insert the disk in your Workstations DVD drive, click for Contents, then select a product, and then follow the InstallShield instructions. If the disk does not start, click Start>Run, and then browse for the Start.htm file. During the installation sequence, follow the on-screen instructions as they appear. You will be given a choice between two levels of installation: Full installation Installs all available product components (recommended for a new installation unless there are good reasons for restricting the options available to end users). Custom installation Presents you with a list of all available product components from which you can select those to be installed.
It is recommended that you use the default settings for folder paths etc. unless you have good reasons for doing otherwise. Important: You must not use embedded spaces in folder path names. The process needs at least 3GB of free disk space for a full installation of all options. InstallShield checks that there is enough space available before it starts, and warns you if there is not. When the process is complete, select Start>Programs/AVEVA 12 to reach the Make Project, PDMS Documentation, Project Creation Wizard, Run Background Process Manager and Run PDMS options.
3.1.1
NET Framework Installation

The new graphical user interface requires that Microsofts .NET Framework 2.0 be installed. The .NET Framework is supplied on the installation CD, and is installed automatically if it is not already installed.
3:1
12.0

3.2
Uninstalling and Reinstalling

If InstallShield detects an existing installation, it will display the options for modifying/ repairing/removing the files rather than simply offering the standard installation options. To remove installed components from your hard disk, or to add additional components to an existing installation, select Start>Settings>Control Panel and use the Add/Remove Programs tool. As an alternative procedure, repeat Steps 1 to 4 of the installation sequence detailed above. The InstallShield Wizard will detect your existing installation and will give you the following options: Modify Displays the same list of options as the Custom installation. Select new components to be added and/or deselect any currently installed components to be removed. Repair Reinstalls all currently installed components (to correct any corrupted files etc.). Remove Removes all currently installed components.
Note: Uninstalling PDMS will not uninstall Microsofts .NET Framework, which must be removed separately if required.
3.3
Flexman License Manager

You must install and set up the Flexman license system before launching the installed software. This will usually be done only on the server. Please see the Flexman Installation Guide. News and update information is also available for Flexman on the AVEVA support web-site.
3.4
Remote Installation
If you wish to have one server installation of PDMS accessed from remote workstations, you must ensure that the Windows system DLLs on each remote workstation are upgraded to a suitable version for running the AVEVA PDMS application programs. You can achieve this by installing AVEVA PDMS itself in minimal form; that is, select the Custom Installation type and then deselect everything except 'PDMS Core Components'. In addition, this release includes a stand-alone 'Thin Client' installer which can be used on individual workstations to update the necessary Windows system DLLs, and which also provides start menu shortcuts to the main PDMS installation.
3.5
Silent Installation
This section will instruct the user on how to perform a silent installation of PDMS. The following assumptions are made: User defined path names do not contain spaces. The network share that is being used is shared and that the users performing the installations have access rights to the necessary folder. You can access these
3:2
12.0

commands either from a UNC path or a network drive. A network drive is used in this manual. 1. The folder names in this manual are variable and the user can specify their personal choices. The number of files demonstrated may vary depending on what version is being implemented. Copy the content from the PDMS 12 DVD to a network share. The following screen shot will demonstrate this:
2.
On a workstation create an InstallShield Response File. Please see the following screen shot to create the setup.iss file:
Follow the instructions in the PDMS installation wizard to complete the creation of the InstallShield Response File. 3. To deploy the software silently on other computers use the /s /w switches in conjunction with setup.exe. It is also optional to create a log file of the installation using the f2
3:3
12.0

switch (an example being setup.exe /s /w /f2"%TMP%\setup.log") illustrated as follows:
This can be
3.5.1
Deployment across a network

There are numerous methods for such a deployment. However here are three commonly used methods of deploying the software across a network. These can be depicted in the following section of the manual. This is not a step-by-step approach as the installation will depend on the environment the user has installed.
3.5.2
Deployment using SMS

Please use the standard procedures for deploying with SMS and use the setup.exe /w /s at the command line.
3:4
12.0

Below is an example of such a dialog box:
3.5.3
Deployment using logon script

In your logonscript check if PDMS is installed. If not then install it.
3:5
12.0

Logonscript example:
3.5.4
Deployment using GPO

Create a Software Installation Settings file (Zap) Example zap file:
Reference here: http://technet2.microsoft.com/ windowsserver/en/library/3512b600-5bb4-4dae-8b2c7b71ef9951a01033.mspx?pf=true [Application] FriendlyName = "AVEVA PDMS 12" SetupCommand = "\\Server\Install\PDMS12\int\t51677\PDMS\Installation4\De ploy.bat" DisplayVersion = 12.0 Publisher = AVEVA
3.5.5
Example of deploy.bat
:InstallPDMS12 :: Install AVEVA PDMS 12.0 Silently echo Installing AVEVA PDMS 12.0 if exist "%TEMP%\PDMS12Inst.log" "%TEMP%\PDMS12Inst.log" del /Q /F
call "%~dp0setup.exe" /w /s /f2"%TEMP%\PDMS12Inst.log" :: Check if installation is okay
3:6
12.0

findstr /I 1>nul 2>&1
/C:"resultcode=0"
"%temp%\PDMS12inst.log"
IF "%ERRORLEVEL%" EQU "0" ( echo Installation succeeded exit /b 0 ) ELSE ( echo Installation failed exit /b 1 )
3:7
12.0

3:8
12.0

Setting Up the Windows Environment

This chapter describes how to configure the Windows operating system before you run PDMS. Following installation of PDMS, you should perform the following steps: Check the settings for your graphics board: See Graphics Card Settings. Ensure the Flexman License Manager daemon is running, and set environment variables relating to Flexman: See Setting the License File Location. Configure Windows parameters for PDMS: see PDMS Environment Variables. You can then run PDMS by clicking on the PDMS shortcut or icon, which will set up the remaining environment variables required.
Note: In the following instructions it is assumed that AVEVA PDMS has been installed in folder C:\AVEVA. If it has been installed elsewhere, substitute C:\AVEVA with the name of the installation folder.
4.1
Windows Control Panel

The Windows Control Panel contains tools that are used to change the way Windows looks and behaves. This Install Guide describes how to use Control Panel tools to configure Windows to run PDMS. Open the Control Panel as follows: Windows 2000 Click Start, point to Settings, and then click Control Panel Windows XP If your computer is set up with the Classic Start menu, click Start, point to Settings, and then click Control Panel. If your computer is set up with the standard Start menu, click Start and then click Control Panel.
4.2
Graphics Card Settings

You should set your display to a resolution of at least 1024 x 768 and the colour depth to True colour or 16.7 million colours. This can be set by opening the Control Panel. Select Display and select the Settings tab. Make the appropriate selections on the form for your graphics card. Due to the rapidly changing list of hardware accelerated OpenGL graphics cards commercially available, an up-to-date list of supported graphics cards, graphics device drivers and recommended device driver configuration cannot be included in this document. However, the AVEVA Support Web pages (http://www.aveva.com/support) contain a current
4:1
12.0

list of both tested and supported graphics cards, along with advice on configuration of graphics device drivers.
4.3
Setting the License File Location

Before you can use PDMS, you must set up the Flexman license system and connect to the Flexman License Manager daemon (see the Flexman Installation Guide). A licence file should be requested from AVEVA Customer Services.
4.4
PDMS Environment Variables

PDMS uses Windows Environment variables to locate folders containing PDMS system files and users project data. This allows you to locate these folders anywhere on the file system. The default location for PDMS system files is C:\AVEVA\plant\PDMS12.0\, unless the default location was changed during the installation. PDMS is supplied with a file evars.bat in the PDMS executables folder which sets default values for the environment variables so that they point to the folder structure as installed. It also sets the PATH variable to include the PDMSEXE folder containing PDMS executables. You may need to modify this file to reflect the folder structure of your own installation. The following is a list of the variables you may need to reset, with a brief description of each one and the default setting. Note: all environment variables must be entered in UPPERCASE.
Search Paths of Folders Containing Spaces

Search paths of folders can contain spaces, by using a semicolon as the separator between folders, for example: set PDMSUI=C:\Local PDMS\Appware;M:\Project PDMS\Appware; a:\Company PDMS\Appware Note: that in order to define an environment variable that contains just one item including spaces, it must explicitly include a final semicolon. For example: set PDMSUI=C:\Local PDMS\Appware;
Length of Search Path Environment Variable

The lengths of PDMS search path environment variables can be up to a maximum of 5120 characters.
Recursive Expansion of Environment Variables

An environment variable defining a search path can itself contain references to other environment variables. For example: set MPATH=%ROOT%\Standard Version;%ROOT%\Update Version set ROOT=C:\Program Files\AVEVA; (note final semicolon) Then on PDMS: *$m%MYPATH%\mac
4:2
12.0

Will check in turn for:
C:\Program Files\AVEVA\Standard Version\mac C:\Program Files\AVEVA\Update Version\mac

PDMS System Environment Variables The following environment variables refer to the location of PDMS system files. PDMSEXE Executable folder C:\AVEVA\Plant\PDMS12.0 PDMSEXEMAIN PDMSUI PMLLIB PDMSDFLTS PDMSPLOTS Copy of PDMSEXE, but can be a search path C:\AVEVA\Plant\PDMS12.0 Application User Interface folder (PML 1) C:\AVEVA\Plant\PDMS12.0\pdmsui Application User Interface folder (PML 2) C:\AVEVA\Plant\PDMS12.0\pmllib Applications defaults folder C:\AVEVA\Plant\PDMS12.0\pdmsui\dflts Applications PLOTS folder C:\AVEVA\Plant\PDMS12.0\pdmsui\plots Pointer to the PLOT executable. C:\AVEVA\Plant\PDMS12.0\plot\plot.exe Online help data files. C:\AVEVA\Plant\PDMS12.0\onlinehelp Online help data files. C:\AVEVA\Plant\PDMS12.0\onlinehelp
PLOTCADC PDMSHELPDIR PDMSHELPDIR
PDMS User Environment Variables The following environment variables refer to the location of users PDMS folders. Users must have write permission to these folders. PDMSWK PDMSUSER Temporary PDMS work file folder C:\temp Application Users save/restore setup area (or the users 'home' folder) C:\AVEVA\Plant\PDMS12.0\pdmsuser
4:3
12.0

PDMSREPDIR PDMSDFLTS
PDMS Applicationware Report Input and Output folder. C:\AVEVA\Plant\PDMS12.0\pdmsui\reports Applications defaults folder. Note that individual users may not have permission to change PDMS System defaults in C:\AVEVA\Plant\PDMS12.0\pdmsui\dflts, but they should have their own local defaults area. This is achieved by setting a PDMSDFLTS search path, e.g. C:\USERDFLTS C:\AVEVA\Plant\PDMS12.0\pdmsui\dflts.
Project Environment Variables For each PDMS project, four more environment variables must be set. For example, for a project ABC: ABC000 ABCISO ABCMAC ABCPIC Project database folder Project ISODRAFT options folder Project Inter-DB connection macro folder Project DRAFT picture file folder
PDMS is installed with sample project data (See PDMS Projects). PDMS Project Environment variables for these projects are set in evars.bat.
4.5
Running PDMS from a Command Prompt Window

You can run PDMS from a Command Prompt window rather than using the Start/Programs menu. To do this you must set your PATH variable to include the folder where PDMS is installed. Windows 2000 and Windows XP Open the Control Panel. Select System, and pick the Advanced tab. Click on the Environment Variables button. Edit the system variable Path to add the PDMS folder C:\AVEVA\Plant\PDMS12.0\) to the list of folders in the Path variable. (for example,
Once the Path variable includes the AVEVA PDMS folder, you can run PDMS by typing pdms at a command prompt.
4.6
Customising PDMS Start-Up

There is a batch (.bat) file supplied in C:\AVEVA\plant\PDMS12.0\ called pdms.bat which allows entry into PDMS. You can run PDMS using this batch file in any of the following ways: Use the shortcut in the Windows Start menu, Start>Programs>AVEVA>PDMS 12.0>Run PDMS You can create a shortcut on your desktop to run your batch file. With the cursor in the desktop area, click with the right-hand button and select New>Shortcut. This shows a
4:4
12.0

sequence of dialogs to help you create the shortcut. Type in the location of pdms.bat, for example: C:\AVEVA\plant\PDMS12.0\pdms.bat then press Next and give the shortcut a name. Press Finish. You should now be able to double-click on the shortcut icon to enter PDMS. If you have C:\AVEVA\plant\PDMS12.0\ (the path name for the pdms.bat file) in your PATH environment variable, just type pdms in a command window to execute the batch file. Otherwise, navigate to the folder where the batch file is stored and type pdms or pdms.bat.
4.6.1
Creating Your Own Batch File to Run PDMS

You can set up your own batch files to run PDMS. For example, you may wish to run DESIGN checking utilities every night, or update batches of drawings overnight. Begin by creating a batch file, for example, runpdmsmacro.bat. Type the following line into this file: C:\AVEVA\plant\PDMS12.0\pdms.bat TTY SAM SYSTEM/XXXXXX /STRUC $M/ mymacrofile Where: TTY tells PDMS not to start the PDMS GUI. This gives command line only operation. SAM is the project name. SYSTEM/XXXXXX is the PDMS username/password to be used when running the command macro /STRUC selects the required MDB mymacrofile is the pathname of a PDMS command macro, containing the commands that you want to execute in PDMS.
In this example, running runpdmsmacro.bat will enter PDMS in project SAM, as user SYSTEM/XXXXXX, in MDB /STRUC, and run the PDMS command macro mymacrofile.
4.7
Running PDMS in batch

PDMS creates a separate PDMSConsole process to manage the command-line input/ output for all modules. When PDMS is invoked from a .bat file, processing of this file resumes as soon as you leave MONITOR - even though you are still using PDMS. To help manage this situation, PDMSWait.exe is distributed as part of PDMS and can be used to make a PDMS script wait for PDMS to complete before continuing. PDMSWait uses Windows facilities to wait for an event triggered by PDMSConsole when PDMS finishes. Because you can be running more than one PDMS session on any one computer, both PDMSWait and PDMSConsole look for an environment variable PDMS_CONSOLE_IDENTIFIER before doing this. You can set PDMS_CONSOLE_IDENTIFIER to any unique string. In a .bat file you can use the %RANDOM% or %TIME% values provided by Windows; in a Perl script, you can use the process number, accessible as $$.
4:5
12.0

Example:
set PDMS_CONSOLE_IDENTIFIER=%RANDOM% call %PDMSEXE%\pdms call %PDMSEXE%\pdmswait echo Returned to .bat at %TIME%
This will start PDMS, then wait until it has finished before resuming the script. The MONITOR Reference Manual provides more details on running PDMS batch programs.
4.8
Plotting
To plot in a Windows environment, we recommend that you use the plotcadc.bat file supplied in the AVEVA PDMS folder. Note that you may have to modify the plotcadc.bat file to suit your local printer installation. The Network Plotter must be mapped using the NET USE command. See your network documentation for more information. To run the plotcadc.bat file, give a command in the format: C:\AVEVA\Plant\PDMS12.0\plotcadc.bat plotfile format printer options Where options are the AVEVA PLOT utility options, and may be omitted. See the PLOT User Guide for more information. Note that the options must be enclosed in quotes. Example:
plotcadc.bat c:\pdms\plot1 ps \\ntserver\NTPostScript plotcadc.bat c:\pdms\plot1 hpgl \\ntserver\NThpgl 'CE=Y'
4:6
12.0

Language Support
Language Support
By default, your PDMS project can use any language whose characters are contained within the Latin-1 character set. The Languages covered by the Latin-1 character set a listed in the table below. If you want to use any of the other, non-Latin-1 languages supported by PDMS, it is necessary to configure your PDMS project and the Windows operating system. This chapter describes how to use PDMS on Windows 2000 and Windows XP Professional in each of the supported language groups: Latin-1 Latin-2 Latin-Cyrillic Far Eastern
Supported Languages Name Latin 1 Description ISO 8859-1 Latin alphabet 1 Languages covered Danish, Dutch, English, Faroese, Finnish, French, German, Icelandic, Irish, Italian, Norwegian, Portuguese, Spanish, Swedish, Albanian, Czech, English, German, Hungarian, Polish, Rumanian, SerboCroat, Slovak, Slovene Bulgarian, Byelorussian, English, Macedonian, Serbo-Croatian, Ukrainian, Russian Japanese, Korean, Simplified Chinese, Traditional Chinese
Latin 2
ISO 8859-2 Latin alphabet 2
Latin Cyrillic
ISO 8859-5 Latin/Cyrillic alphabet
Far Eastern
PDMS does not support any other language character set, nor does it support the mixing of any of the above, except for mixing one Far Eastern language with English.
5.1
5.1.1
Preparing Windows to use Supported Languages

Windows 2000
To add an additional language in Windows 2000, follow these steps: 1. Open the Control Panel.
5:1
12.0

Language Support
2. Double-click Regional Options to show the Regional Options dialog. 3. Click the Input Locales tab. 4. In the Input Locales box, click the required language, and then click Properties. 5. In the Keyboard Layout box, click the required keyboard layout, click OK, and then click OK. 6. Click the General tab. Click to select the check box next to the language group you wish to install, and then click Apply. The system will either prompt for a Windows 2000 CD-ROM or access the system files across the network. Once the language is installed, Windows 2000 will prompt you to restart the computer.
5.1.2
Windows XP
To add an additional language in Windows XP, follow these steps: 1. Open the Control Panel. 2. Double-click Regional and Language Options. 3. On the Regional options tab, under Standards and formats, select the required language from the list. 4. Click the Languages tab, and then click Details under "Text services and input languages". 5. Under Default input language, select the required language. If the required language appears in the list, click OK. If it does not appear in the list, then click Add under "Installed Services", and then click the language you want to add and the keyboard layout you want to use for that language. To configure the settings for the Language bar, click Language Bar under "Preferences". The Language bar is used to switch between languages while you are using PDMS. Click OK to close the Language Bar Settings dialog. Click OK to close the Text Services and Input Languages dialog. 6. Click the Advanced tab. Under Languages for non-Unicode programs, select the required language. Click Apply. It may be necessary to install new code page conversion tables. Only member of the Administrators group can install code page conversion tables. The system will either prompt for a Windows XP CD-ROM or access the system files across the network. Once the language is installed, Windows XP will prompt you to restart the computer. Note: For Far Eastern language support, it is necessary have the East Asian support option installed.
5.2
Preparing PDMS to use Latin Languages

In PDMS ADMIN, you must specify a character set for each project by using one of the following commands on the PDMS ADMIN command line: Command PROJECT CHARSET LATIN 1 (default) Languages covered Danish, Dutch, English, Faroese, Finnish, French, German, Icelandic, Irish, Italian, Norwegian, Portuguese, Spanish, Swedish,
5:2
12.0

Language Support
Command PROJECT CHARSET LATIN 2 PROJECT CHARSET LATIN CYRILLIC
Languages covered Albanian, Czech, English, German, Hungarian, Polish, Rumanian, Serbo-Croat, Slovak, Slovene Bulgarian, Byelorussian, English, Macedonian, SerboCroatian, Ukrainian, Russian
The corresponding font family must be selected for DRAFT and ISODRAFT drawings. Use Project>Font Families and select the Font Type appropriate for you chosen language. For details, see the Adminstrator User Guide and Adminstrator Command Reference Manual.
5.3
Preparing PDMS to use Far Eastern Languages

You must ensure that your licence file is for the language version you require. Before you use PDMS, you must set the environment variable CADC_LANG as follows: CADC_LANG=Japanese CADC_LANG=Korean CADC_LANG=Chinese CADC_LANG= TChinese Kanji Korean Simplified Chinese Traditional Chinese
In PDMS ADMIN, you must specify the multibyte character set for each project by using the command corresponding to your required language: PROJECT MBCHARSET JAP PROJECT MBCHARSET KOR FILE /<font filename> PROJECT MBCHARSET CHI PROJECT MBCHARSET TCHIN FILE /<font filename> Simplified Chinese Traditional Chinese
For details, see the Adminstrator User Guide and Adminstrator Command Reference Manual.
5:3
12.0

Language Support
5:4
12.0

Running PDMS Under Windows
6
6.1

Spaces in Windows pathnames
To run macros with spaces in the filenames, you must enclose the filename in quotes, without a leading slash. For example:
$m'c:\Program Files\Macros\space.mac' arg1 arg2

Due to the way in which PDMS parses its command lines, this format is also recommended for use with filenames containing Asian characters.
6.2
Linking to Microsoft Excel

You can make your reports load directly into a Microsoft Excel spreadsheet, as commaseparated files: Select Utilities>Reports>Modify from the PDMS main menu bar. Pick a report template. Click on OK: the Modify Template form is displayed. Select Options>Other Formats... from the Modify Template form menu bar. This displays the Report Format form. From this form: Choose the CSV option from the Format drop-down list. Click on OK: this returns you to the Modify Template form.
Select the Overwrite radio button. For the filename enter %PDMSUSER%/fname.csv (the .csv extension is important). In the System command text box enter. 'cmd/c C:\<excel folder>\excel.exe %PDMSUSER%\fname.csv'. where C:\<excel folder> is the location of Excel on your system. Note that it is necessary to enclose Windows command arguments in double quotation marks if the argument contains embedded spaces. :\<excel folder>\.
6.3
Windows Parameters
The following setting can be used to improve performance when repositioning forms in PDMS. These are optional Windows Parameter settings. Windows 2000 Open the Control Panel. Select Display and select the Effects tab. On the form, uncheck Show Window Contents While Dragging.
6:1
12.0

Windows XP Open the Control Panel. Select Display, then select the Appearance tab and click on the Effects button. On the form, uncheck Show Window Contents While Dragging and Show shadows under menus.
6:2
12.0

PDMS Projects
7
7.1
PDMS Projects
Sample Project
PDMS is supplied with a sample project, which can be used in several ways: It provides you with examples of the use of PDMS. It provides you with sample libraries, catalogues and specifications which enable you to use PDMS before you set up your own, and can be used as starting points when you do start to create your own. It provides you with starting points for the tutorials in the following manuals: Pipework Support Design User Guide Pipework Design User Guide Structural Design User Guide HVAC User Guide Reporting Reference Manual Drawing Production User Guide It provides an example of how to set up your own projects. MAS (Master) provides data in read-only databases. This data should not be deleted or changed in any way, or the rest of the sample project will become unusable. SAM (Sample) contains several MDBs which can be modified, and so they can be used for training,
The sample project is actually two projects in PDMS terms:
7.1.1
Copying Project SAM to Your User Area

The sample project is loaded automatically when you install PDMS. You should copy the sample project to your user area and run it as supplied. The project files are held in two directories: sam000 holds all DESIGN data and catalogue data; sampic holds the DRAFT picture libraries.
7.1.2
Users and Teams in the Sample Project

Free User The Free user has username/password SYSTEM/XXXXXX. General Users Team ADMIN Username/password ADMIN/ADMIN
7:1
12.0

PDMS Projects
CATS DEMO EQUI HANGER HVAC PIPE SAMPLE STRUC TEAMA TEAMB TEAMC TEAMD TEAME TEAMF TEAMG
CATS/CATS DEMO/DEMO EQUI/EQUI HANGER/HANGER HVAC/HVAC PIPE/PIPE SAMPLE/SAMPLE STRUC/STRUC USERA/A USERB/B USERCC USERD/D USERE/E USERF/F USERG/G
General User with Administration Rights There is a user named ADMIN who is a member of all teams except MASTER. In particular, ADMIN is a member of the following teams: CATADMIN DRAFTADMIN HSADMIN ISOADMIN
Membership of these teams gives special administration rights within the corresponding constructor module. Each MDB contains databases with appropriate access rights. There are also teams and users associated with each MDB with appropriate access rights.
7.1.3
MDBs in the Sample Project

This section assumes that you are already familiar with PDMS databases. The sample project contains the following MDBs which can be used for demonstration or training purposes: CATS DEMO EQUI HANGER An MDB for practising using Catalogues and Specifications. A demonstration MDB. An MDB for the Equipment tutorials. An MDB for the Support Design tutorial. This MDB contains suitable pipework, steelwork and civils as a starting point.
7:2
12.0

PDMS Projects
HVAC MASTER MASTERCAT PIPE SAMPLE
An MDB for the HVAC Design tutorial. This MDB contains suitable steelwork and civils as a starting point. An MDB containing the master Catalogues and Specifications, LEXICON, Dictionaries etc. An MDB used for practising the use of Catalogues and Specifications. An MDB for the Pipework Design and Pipework Spooling tutorials. An MDB for the Reporting from PDMS and Drawing Production tutorials. This MDB contains DESIGN data from which reports and drawings can be produced. You can also produce isometrics. An MDB for the Structural Design tutorial. Additional MDBs available for training purposes.
STRUC TRAINA to TRAING
7.1.4
Sample Project and your own Projects

You can add databases from the sample projects SAM and MAS to your own projects from within PDMS ADMIN, using the Install options on the main menu bar. Note that these options are only available if you have the project environment variables for SAM and MAS set. Note: On DRAFT Libraries: You must have DRAFT libraries available in your current project before you can enter the module. You may find it convenient to install the libraries supplied by AVEVA in the MAS project (using the Install options), even if you wish to create your own libraries for the project.
7:3
12.0

PDMS Projects
7:4
12.0

Troubleshooting
Troubleshooting
Here are some suggestions about solving some problems you may encounter when using PDMS under Windows.
8.1
General
Error: Explanation: Error: Explanation: The dynamic link library DFORMD.dll could not be found in the specified path. This is supplied with PDMS. Perhaps you have not set your PATH variable. The PATH setting must include C:\AVEVA\plant\PDMS12.0 STOP. The application failed to initialise properly (0xc0000135). Click on OK to terminate the application. This occurs after a number of other errors. The most likely reason is a problem with the PATH variable.
8.2
License Manager Errors

Error: Solution: When you start up lmgrd it says <time> (lmgrd) Can't make folder C:\FLEXlm, errno: 2 No such file or folder, etc. There is no C: drive for the license manager to write to. As the System Administrator or a Power User, you need to make a shared disk called C:. This can be done on a networked or non-networked computer. Within the Windows Explorers File menu, create a new folder (e.g. D:\C_drive) and make it current. Select File>Properties and select the Share tab. Click on the Shared As: option button and then click OK. Then from the Tools menu select Map Network Drive. Select C: from the Drive: drop-down list in the displayed form and type: \\hostname\C_drive in the Path box. Then click on OK. (C:) should now appear in the list of available drives in Explorer Error: <time> (lmgrd) "<host>": Not a valid server hostname, exiting.
8:1
12.0

Troubleshooting
Explanation:
The hostname used by AVEVA to create the license file does not correspond with the computer on which you are running PDMS. The hostname comes from the variable COMPUTERNAME, which you can obtain by typing 'env|findstr COMPUTERNAME' in a Command Prompt window. Compare this with the license file contents, and resubmit if necessary. FLEXlm: checkout failed: Cannot connect to license server (-15, 10:10061) WinSock error code. lmgrd has not been started up - see above for details. FlexLM: checkout failed: Cannot find license file (-1,73:2) No such file or folder. lmgrd has not been started up - see above for details. FlexLM: checkout failed: Licensed number of users already reached (4,132). You have exceeded the permitted number of users specified in your license file.
Pop-up Mess.: Explanation: Pop-up Mess.: Explanation: Pop-up Mess.: Explanation:
8.3
Entering PDMS
Error: Explanation: Error: (43,9) Environment Variable not defined for project name. You have not set the environment variable for the project, e.g. XYZ000. (43,1) Project <xxx> not available! Error 7 allocating system database. Explanation: Error: The environment variable for the project does not point to the correct location. Either the disk and/or folder do not exist or are not readable. <username> not found. Invalid username or password. or Bad Password Explanation: Error: Solution: Error: You are trying to enter PDMS without a valid PDMS username and/or password. PDMSWK environment variable not set. Set PDMSWK to c:\temp or some other folder where PDMS can create temporary files. Error 34 opening variables file.
8:2
12.0

Troubleshooting
Explanation: Error: Explanation:
You cannot create a file in the location pointed to by environment variable PDMSWK. Project <xxx> is pre version 8. This can happen if you have transferred the project from UNIX using FTP in ASCII rather than Binary format.
8.4
Problems with Graphics

Error: Solution: Cannot pick certain items in DESIGN 3D shaded views. There is probably a problem with the display driver for the graphics board that you are using. Make sure you have the version of the display driver recommended on our supported display drivers Web page. Incorrect colours. Check the setting of your Display. The colour resolution should be set to True Colour or 16.7 million colours. Graphics speed (for example in 3D views) is poor. Check the setting of your Display.
Error: Solution: Error: Solution:
8:3
12.0

Troubleshooting
8:4
12.0

Structure of PDMS on .NET

From AVEVA PDMS 12, the GUI uses the Microsoft .NET environment including the latest WinForms based user interface components. Using this state-of-the-art technology enables docking forms and toolbars in PDMS and provides a robust foundation for the future provision of standard application programming interfaces. This does affect the way PDMS is installed: this section gives a brief overview and the following one outlines how to troubleshoot the installation.
9.1
Overview
This section describes the overall structure and components of the PDMS .NET installation, and the environment necessary to run it. Each PDMS GUI module now consists of a thin .NET exe, a .NET Wrapper DLL and a Win32 DLL plus some other shared components including 3rd party controls from Infragistics. The .NET components are private assemblies installed under the root directory %PDMSEXE%.
9.2
PDMSEXE
The environment variable %PDMSEXE% is used to locate the executable on module switch. It is also used to locate attlib.dat (attribute and noun definitions), message.dat (message definitions), desvir.dat (schema definition) etc. Normally PDMS is started from pdms.bat which is located in your %PATH%. Both %PDMSEXE% and %PATH% should include the install directory.
9.3
GUI Module Structure

Each GUI module is structured in the same way. For DESIGN the structure looks like this
9:1
12.0

where des.exe and des.dll live in the directory %PDMSEXE% and Wrappers.dll lives in the DESIGN subdirectory below %PDMSEXE%. So, when running a PDMS GUI module %PDMSEXE% is used to locate the executable, .NET loading rules are used to load Wrappers.dll and Win32 DLL loading rules are used to load des.dll (and other Win32 DLLs on which des.dll depends).
9.3.1
Wrappers
For each GUI module (DESIGN, DRAFT, ADMIN, ISODRAFT and MONITOR) there is a Wrappers.dll in a subdirectory with the same name as the module. Each Wrapper.dll has a dynamic link to the appropriate Win32 DLL for that module. .NET loading rules are used to load the appropriate Wrappers.dll for a given module. So, when running des.exe, the version of Wrappers.dll linked with des.dll will be loaded. DESIGN and DRAFT subdirectories also contain a drawlistWrapper dll which is used by the Drawlist add-in.
9.3.2
.NET Loading Rules

All the .NET assemblies are Private assemblies and are installed under %PDMSEXE% (Assembly Base directory) or a subdirectory below. .NET loads private assemblies from the base directory of the application. If it cant find the private assembly here it uses the applications configuration file called <module>.exe.config to see whether it contains any path hints. Path hints are stored in the <probing> element. So, for example, des.exe.config has the following probing path <probing privatePath="Design" />. This means that Wrappers.dll is loaded from the subdirectory DESIGN below the application directory.
9.3.3
Win32 DLLs
Each Wrappers.dll depends on the given modules Win32 DLL, e.g. DESIGNs Wrappers.dll found in the DESIGN subdirectory depends on des.dll. Win32 DLL loading rules apply here. These are: The directory from which the importing component loaded. (e.g. the DESIGN subdirectory where Wrappers.dll is loaded) The (application's) current directory (where its run from) The Windows directory (default: C:\Windows) (we dont install anything here) The directories that are listed in the PATH environment variable
Since the module DLL does not live in the same directory as the Wrappers.dll then unless you are running from %PDMSEXE%, your %PATH% will be used to locate the module DLL.
9:2
12.0

(The Wrappers.dll subdirectory is the directory which is first searched for all the Win32 DLLs on which Wrappers depends i.e. <module>.dll, sglNet.dll, udDNet.dll, )
9.4
Components
The following components will be installed under %PDMSEXE% or one of its subdirectories. This is not a complete list but a list of all .NET related files for GUI modules (DESIGN, DRAFT, ISODRAFT, ADMIN and MONITOR). Each module has an .exe and corresponding dll e.g. des.exe and des.dll, a config file, a manifest file and an Addins file. The config file is used to specify the location of the Wrappers dlls for each application, the manifest file is used to set the visual style of the application and the Addins file defines which add-ins the application will load (e.g. Explorer, Drawlist, ).
9.4.1
PDMSEXE Directory
DESIGN/SPOOLER des.exe, des.dll, des.exe.config, des.exe.manifest, DesignAddins.xml, SpoolerAddins.xml
DRAFT dra.exe, dra.dll, dra.exe.config, dra.exe.manifest, DraftAddins.xml
MONITOR mon.exe, mon.dll, mon.exe.config, mon.exe.manifest
ISODRAFT iss.exe, iss.dll, iss.exe.config, iss.exe.manifest, IsodraftAddins.xml
ADMIN adm.exe, adm.dll, adm.exe.config, adm.exe.manifest
Shared Depends.dll, DrawList.dll, DrawListAddin.dll, ExplorerAddin.dll, ExplorerControl.dll, ForeignLanguage.dll, HistoryAddIn.dll, MyDataAddIn.dll, ReferenceListAddin.dll, PDMSCommands.dll, PDMSFilters.dll, PDMSResources.dll, PDMSResources.resources, StartUp.dll, ApplicationFramework.dll, udNet.dll, DruidNet.dll
Infragistics
This is a third-party GUI tool-kit:
Infragistics.Shared.v3.dll, Infragistics.Win.UltraWinDock.v3.dll, Infragistics.Win.UltraWinExplorerBar.v3.dll, Infragistics.Win.UltraWinGrid.v3.dll, Infragistics.Win.UltraWinStatusBar.v3.dll, Infragistics.Win.UltraWinTabbedMdi.v3.dll,
9:3
12.0

Infragistics.Win.UltraWinTabControl.v3.dll, Infragistics.Win.UltraWinToolbars.v3.dll, Infragistics.Win.UltraWinTree.v3.dll, Infragistics.Win.v3.dll, Infragistics.Win.Misc.v3.dll System msvcp71.dll, msvcr71.dll Other DLLs required by DRAFT
These DLLs are loaded as required by specific DRAFT commands:
Draft_DXF_LI.dll, Draft_DGN_LI.dll, Draft_Test_LI.dll, Draft_SVG_LI.dll Other DLLs required by DESIGN sgl5NET.dll
9.4.2
PDMSEXE/DESIGN subdirectory
drawlistWrappers.dll, Wrappers.dll
9.4.3
PDMSEXE/DRAFT subdirectory
9.4.4
PDMSEXE/MONITOR subdirectory
Wrappers.dll
9.4.5
PDMSEXE/ISODRAFT subdirectory
9.4.6
PDMSEXE/ADMIN subdirectory
Wrappers.dll
9.4.7
Add-ins
These new user interface .NET components are loaded by the Application Framework. Each module has an addin file which defines the set of add-ins it will load, e.g. for DESIGN this file is DesignAddins.xml. The toolbar entries to show and hide each add-in are defined in PML.
9.5
Forms and Menus

Most of the User Interface is still defined in PML located in %PMLLIB% and %PDMSUI%.
9:4
12.0
Software Installation Guide

Troubleshooting the .NET Installation
10
10.1

Version Error
Error: Solution: System.IO.FileLoadException: The located assembly's manifest definition with name 'PDMSResources' does not match the assembly reference. All .Net assemblies must be the same version. Open File>Properties>Version>Assembly Version, and check that all version numbers are the same.
10.2
Wrappers or a Dependency Missing

Error: An exception System.IO.FileNotFoundException has occurred in mon.exe. Additional information: File or assembly name Wrappers, or one of its dependencies, was not found. Solution: All the .NET assemblies are Private assemblies and are installed under %PDMSEXE% (Assembly Base directory) or a subdirectory below. .NET loads private assemblies from the base directory of the application. If it cant find the private assembly here, it uses the applications configuration file called <module>.exe.config to see whether it contains any path hints. Path hints are stored in the <probing> element. So, for example, des.exe.config has the following probing path <probing privatePath="Design" />. This means that Wrappers.dll is loaded from the subdirectory DESIGN below the application directory. Each Wrappers.dll depends on the given modules Win32 DLL e.g. DESIGNs Wrappers.dll found in the Design subdirectory depends on des.dll. Win32 DLL loading rules apply here. These are: The directory from which the importing component loaded. (i.e. the DESIGN subdirectory where Wrappers.dll is loaded in the case of DESIGN) The (application's) current directory (where its run from) The Windows directory (default: C:\Windows) (we dont install anything here) The directories that are listed in the PATH environment variable
10:1
12.0

Since the module DLL does not live in the same directory as the Wrappers.dll then unless PDMS is running from %PDMSEXE% the %PATH% will be used to locate the module DLL. (The Wrappers.dll subdirectory is effectively is the directory which is first looked in for all the Win32 DLLs which Wrappers depends on i.e. <module>.dll, sglNet.dll, udDNet.dll, ) Make sure that both %PDMSEXE% and %PATH% point to the root directory in which PDMS is installed.
10.3
Interface Incompatibility
Error: An exception mon.exe, or System.MissingMethodException has occurred in
An exception System.IO.FileNotFoundException has occurred in mon.exe Additional information: A procedure imported by 'Wrappers' could not be loaded Solution: The interfaces between components are not compatible. Check that File>Properties>Version Assembly Version on all assemblies is 12, or whatever the current version is.
10.4
No Add-ins
Problem: Solution: Add-ins missing from module Add-ins loaded by each module are defined in the following xml files: DesignAddins.xml DraftAddins.xml IsodraftAddins.xml SpoolerAddins.xml
If Add-ins are missing, check that these files exist in %PDMSEXE%
10:2
12.0

10.5
Window Layout
Problem: Solution: Window layout is not restored e.g. Add-ins position and/or docked state, The file <module><version>WindowLayout.xml in the %PDMSUSER% directory stores this information for the each GUI module. If this file is deleted then the window layout will return to its default.
10.6
Serialization
Serialization is the process used to store the data - e.g. history stacks, toolbar state - for the GUI in a .NET environment. Problem: Information is stored per project and per module in the following files in the %PDMSUSER% directory: <project><version>Settings.bin <module><version>Settings.bin. CAF (Common Application Framework) window layout information is stored in: c:\documents and settings\<username>\local settings\application data\AVEVA\PDMS Solution: These files may be deleted or transferred between users working on the same project. Users can delete or transfer the root directory.
10:3
12.0

10:4
12.0

Ig 51796

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ig 51796

Uploaded by

Copyright:

Available Formats

PDMS Installation Guide

AVEVA Solutions Ltd

PDMS Installation Guide

PDMS Installation Guide

Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . 2:1

Installing the Software Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1

Setting Up the Windows Environment . . . . . . . . . . . . . . . . . . . . . . . 4:1

2007 AVEVA Solutions Ltd

PDMS Installation Guide

Running PDMS in batch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5 Plotting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6

Language Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1

Running PDMS Under Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1

PDMS Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1

Structure of PDMS on .NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1

2007 AVEVA Solutions Ltd

PDMS Installation Guide

GUI Module Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1

Forms and Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:4

Troubleshooting the .NET Installation . . . . . . . . . . . . . . . . . . . . . . 10:1

2007 AVEVA Solutions Ltd

PDMS Installation Guide

2007 AVEVA Solutions Ltd

PDMS Installation Guide

Contents of this Guide

2007 AVEVA Solutions Ltd

PDMS Installation Guide

2007 AVEVA Solutions Ltd

PDMS Installation Guide

Hardware and Software Requirements

AVEVA PDMS 12.0 Software Installation

2007 AVEVA Solutions Ltd

PDMS Installation Guide

2007 AVEVA Solutions Ltd

PDMS Installation Guide

Installing the Software Suite

NET Framework Installation

2007 AVEVA Solutions Ltd

PDMS Installation Guide

Uninstalling and Reinstalling

Flexman License Manager

2007 AVEVA Solutions Ltd

PDMS Installation Guide

2007 AVEVA Solutions Ltd

PDMS Installation Guide

switch (an example being setup.exe /s /w /f2"%TMP%\setup.log") illustrated as follows:

Deployment across a network

Deployment using SMS

2007 AVEVA Solutions Ltd

PDMS Installation Guide

Below is an example of such a dialog box:

Deployment using logon script

2007 AVEVA Solutions Ltd

PDMS Installation Guide

Deployment using GPO

call "%~dp0setup.exe" /w /s /f2"%TEMP%\PDMS12Inst.log" :: Check if installation is okay

2007 AVEVA Solutions Ltd

PDMS Installation Guide

findstr /I 1>nul 2>&1

2007 AVEVA Solutions Ltd

PDMS Installation Guide

2007 AVEVA Solutions Ltd

PDMS Installation Guide