ig51796

PDMS

Installation Guide

DisclaimerInformation of a technical nature, and particulars of the product and its use, is given by AVEVASolutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaimany 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 orentity 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.

CopyrightCopyright and all other intellectual property rights in this manual and the associated software, and everypart of it (including source code, object code, any data contained in it, the manual and any otherdocumentation 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 inthis document is commercially sensitive, and shall not be copied, reproduced, stored in a retrievalsystem, or transmitted without the prior written permission of AVEVA Solutions Ltd Where suchpermission is granted, it expressly requires that this Disclaimer and Copyright notice is prominentlydisplayed at the beginning of every copy that is made.

The manual and associated documentation may not be adapted, reproduced, or copied, in any materialor electronic form, without the prior written permission of AVEVA Solutions Ltd. The user may also notreverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of theproduct 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 bylaw. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminalprosecution.

The AVEVA products described in this guide are to be installed and operated strictly in accordance withthe terms and conditions of the respective licence agreements, and in accordance with the relevantUser 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

TrademarksAVEVA and Tribon are registered trademarks of AVEVA Solutions Ltd or its subsidiaries. Unauthoriseduse of the AVEVA or Tribon trademarks is strictly forbidden.

AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd or itssubsidiaries, 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 orlogo belongs to its respective owner.

AVEVA Solutions Ltd

PDMS Installation Guide

Contents Page


PDMSIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1Contents of this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1Associated Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2

Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . 2:1AVEVA PDMS 12.0 Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1Licence File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1

Installing the Software Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1Basic Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1NET Framework Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1

Uninstalling and Reinstalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2Flexman License Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2Remote Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2Silent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2Deployment across a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4Deployment using SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4Deployment using logon script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:5Deployment using GPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:6Example of deploy.bat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:6

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

12.0i© 2007 AVEVA Solutions Ltd


Graphics Card Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1Setting the License File Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2PDMS Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2Running PDMS from a Command Prompt Window . . . . . . . . . . . . . . . . . . . . . . 4:4Customising PDMS Start-Up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4Creating Your Own Batch File to Run PDMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5

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

Language Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1Preparing Windows to use Supported Languages . . . . . . . . . . . . . . . . . . . . . . . 5:1Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1Windows XP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2

Preparing PDMS to use Latin Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2Preparing PDMS to use Far Eastern Languages. . . . . . . . . . . . . . . . . . . . . . . . . 5:3

Running PDMS Under Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1Spaces in Windows pathnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1Linking to Microsoft Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1Windows Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1

PDMS Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1Sample Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1Copying Project SAM to Your User Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1Users and Teams in the Sample Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1MDBs in the Sample Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:2Sample Project and your own Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:3

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1License Manager Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1Entering PDMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:2Problems with Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:3

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

12.0ii© 2007 AVEVA Solutions Ltd


GUI Module Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1Wrappers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2 .NET Loading Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2Win32 DLLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2

Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:3PDMSEXE Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:3PDMSEXE/DESIGN subdirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:4PDMSEXE/DRAFT subdirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:4PDMSEXE/MONITOR subdirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:4PDMSEXE/ISODRAFT subdirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:4PDMSEXE/ADMIN subdirectory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:4Add-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:4

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

Troubleshooting the .NET Installation . . . . . . . . . . . . . . . . . . . . . . 10:1Version Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:1Wrappers or a Dependency Missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:1Interface Incompatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2No Add-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2Window Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:3Serialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:3

12.0iii© 2007 AVEVA Solutions Ltd

PDMS Installation GuideIntroduction

1 Introduction

This guide explains how to install and set up PDMS 12 on a workstation running theMicrosoft 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 storingdata on disks and with basic Windows terminology and commands. If you are not, you mayalso need to refer to your operating system documentation while you carry out theinstallation.

The guide also assumes that you have already gained access to the PDMS installation filesvia a CD/DVD, from the AVEVA Web site, or by some other route.

1.1 Contents of this GuideHardware and software requirements are described in: Hardware and SoftwareRequirements. For completely up-to-date information, please see the AVEVA Website athttp://www.aveva.com/products/support/support.html and refer to the Customer SupportHardware pages. The Web pages also give hints on ways of setting up and running PDMSon 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 operatingsystem before you run PDMS.

Language Support, describes how to set up the Windows Environment to use PDMS withdifferent Language options.

Running PDMS Under Windows, gives some advice on using PDMS in a Windowsenvironment.

PDMS Projects, describes the sample project that is supplied as part of PDMS, and how toset up your own projects.

Troubleshooting, describes solutions for some of the errors that you could encounter whenrunning PDMS.

Structure of PDMS on .NET, outlines the way in which PDMS in installed and configured ina Microsoft .NET environment.

Troubleshooting the .NET Installation, describes solutions to some of the .NET relatedissues you might encounter.

12.01:1© 2007 AVEVA Solutions Ltd

http://www.aveva.com/products/support/support.html

PDMS Installation GuideIntroduction

1.2 Associated ProductsThere are various AVEVA products that may be used in conjunction with PDMS. You maywish to consider installing these at the same time. Those closely associated with PDMSinclude 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 relevantinstallation guide. If they are required, it may be advisable to read these before installingPDMS.


PDMS Installation GuideHardware and Software Requirements

2 Hardware and Software Requirements

Please refer to the Minimum Systems Requirements guide and ensure that your system andnetwork meets all of the minimum requirements before attempting to install the software.

2.1 AVEVA PDMS 12.0 Software InstallationAVEVA 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 Microsoft’s .NET 2.0

First insert the disk in your Workstation DVD drive, and then follow the InstallShieldinstructions.

If the disk does not start, click Start>Run, and then browse for the Setup.exe orInstall.exe file.

2.1.1 Licence FileTo 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 networkedworkstation.

Note: Although the disk contains several AVEVA products, you will only be able to use theitems that are licensed to you. You will get an on-screen notification to warn you when thelicence is due renewal.


PDMS Installation GuideHardware and Software Requirements


PDMS Installation GuideInstalling the Software Suite

3 Installing the Software Suite

3.1 Basic InstallationAVEVA PDMS 12.0 is supplied on DVD. The disk contains the Microsoft InstallShield wizard,and an installable version of Microsoft’s .NET 2.0. Also on the disk is a folder containing theInstallation instructions and user documentation, and it is recommended that you carefullyread all of the Installation instructions before installing the software.

To install AVEVA PDMS 12.0, first insert the disk in your Workstation’s DVD drive, click forContents, 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 willbe given a choice between two levels of installation:

• Full installationInstalls all available product components (recommended for a new installation unlessthere are good reasons for restricting the options available to end users).

• Custom installationPresents you with a list of all available product components from which you can selectthose to be installed.

It is recommended that you use the default settings for folder paths etc. unless you havegood 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 ifthere is not.

When the process is complete, select Start>Programs/AVEVA 12 to reach the MakeProject, PDMS Documentation, Project Creation Wizard, Run Background ProcessManager and Run PDMS options.

3.1.1 NET Framework InstallationThe new graphical user interface requires that Microsoft’s .NET Framework 2.0 be installed.The .NET Framework is supplied on the installation CD, and is installed automatically if it isnot already installed.



3.2 Uninstalling and ReinstallingIf 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 anexisting installation, select Start>Settings>Control Panel and use the Add/RemovePrograms 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 followingoptions:

• ModifyDisplays the same list of options as the Custom installation. Select new components tobe added and/or deselect any currently installed components to be removed.

• RepairReinstalls all currently installed components (to correct any corrupted files etc.).

• RemoveRemoves all currently installed components.

Note: Uninstalling PDMS will not uninstall Microsoft’s .NET Framework, which must beremoved separately if required.

3.3 Flexman License ManagerYou must install and set up the Flexman license system before launching the installedsoftware. This will usually be done only on the server. Please see the Flexman InstallationGuide. News and update information is also available for Flexman on the AVEVA supportweb-site.

3.4 Remote InstallationIf you wish to have one server installation of PDMS accessed from remote workstations, youmust ensure that the Windows system DLLs on each remote workstation are upgraded to asuitable version for running the AVEVA PDMS application programs. You can achieve thisby installing AVEVA PDMS itself in minimal form; that is, select the Custom Installation typeand then deselect everything except 'PDMS Core Components'.

In addition, this release includes a stand-alone 'Thin Client' installer which can be used onindividual workstations to update the necessary Windows system DLLs, and which alsoprovides start menu shortcuts to the main PDMS installation.

3.5 Silent InstallationThis 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



commands either from a UNC path or a network drive. A network drive is used in thismanual.

• The folder names in this manual are variable and the user can specify their personalchoices.

• The number of files demonstrated may vary depending on what version is beingimplemented.

1. Copy the content from the PDMS 12 DVD to a network share. The following screenshot will demonstrate this:

2. On a workstation create an InstallShield Response File. Please see the followingscreen shot to create the setup.iss file:

Follow the instructions in the PDMS installation wizard to complete the creation of theInstallShield Response File.

3. To deploy the software silently on other computers use the /s /w switches in conjunctionwith setup.exe. It is also optional to create a log file of the installation using the f2



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

3.5.1 Deployment across a networkThere are numerous methods for such a deployment. However here are three commonlyused methods of deploying the software across a network. These can be depicted in thefollowing section of the manual. This is not a step-by-step approach as the installation willdepend on the environment the user has installed.

3.5.2 Deployment using SMSPlease use the standard procedures for deploying with SMS and use the setup.exe /w /s atthe command line.



Below is an example of such a dialog box:

3.5.3 Deployment using logon scriptIn your logonscript check if PDMS is installed. If not then install it.



Logonscript example:

3.5.4 Deployment using GPOCreate a Software Installation Settings file (Zap)

Example zap file:

Reference here: http://technet2.microsoft.com/windowsserver/en/library/3512b600-5bb4-4dae-8b2c-7b71ef9951a01033.mspx?pf=true

[Application]

FriendlyName = "AVEVA PDMS 12"

SetupCommand ="\\Server\Install\PDMS12\int\t51677\PDMS\Installation4\Deploy.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" del /Q /F"%TEMP%\PDMS12Inst.log"

call "%~dp0setup.exe" /w /s /f2"%TEMP%\PDMS12Inst.log"

:: Check if installation is okay



findstr /I /C:"resultcode=0" "%temp%\PDMS12inst.log"1>nul 2>&1

IF "%ERRORLEVEL%" EQU "0" (

echo Installation succeeded

exit /b 0

) ELSE (

echo Installation failed

exit /b 1

)


PDMS Installation GuideSetting Up the Windows Environment

4 Setting Up the Windows Environment

This chapter describes how to configure the Windows operating system before you runPDMS. 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 infolder C:\AVEVA. If it has been installed elsewhere, substitute C:\AVEVA with thename of the installation folder.

4.1 Windows Control PanelThe Windows Control Panel contains tools that are used to change the way Windows looksand behaves. This Install Guide describes how to use Control Panel tools to configureWindows 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 clickControl Panel.

4.2 Graphics Card SettingsYou should set your display to a resolution of at least 1024 x 768 and the colour depth toTrue 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 cardscommercially available, an up-to-date list of supported graphics cards, graphics devicedrivers 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


http://www.aveva.com/engineeringit


list of both tested and supported graphics cards, along with advice on configuration ofgraphics device drivers.

4.3 Setting the License File LocationBefore you can use PDMS, you must set up the Flexman license system and connect to theFlexman License Manager daemon (see the Flexman Installation Guide). A licence fileshould be requested from AVEVA Customer Services.

4.4 PDMS Environment VariablesPDMS uses Windows Environment variables to locate folders containing PDMS system filesand 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 thedefault location was changed during the installation.

PDMS is supplied with a file evars.bat in the PDMS executables folder which sets defaultvalues for the environment variables so that they point to the folder structure as installed. Italso 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. Thefollowing is a list of the variables you may need to reset, with a brief description of each oneand the default setting.

Note: all environment variables must be entered in UPPERCASE.

• Search Paths of Folders Containing SpacesSearch paths of folders can contain spaces, by using a semicolon as the separator betweenfolders, 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 includingspaces, it must explicitly include a final semicolon. For example:

set PDMSUI=C:\Local PDMS\Appware;

• Length of Search Path Environment VariableThe lengths of PDMS search path environment variables can be up to a maximum of 5120characters.

• Recursive Expansion of Environment VariablesAn environment variable defining a search path can itself contain references to otherenvironment 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



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.

PDMS User Environment Variables

The following environment variables refer to the location of users PDMS folders. Users musthave write permission to these folders.

PDMSEXE Executable folder

C:\AVEVA\Plant\PDMS12.0

PDMSEXEMAIN Copy of PDMSEXE, but can be a search pathC:\AVEVA\Plant\PDMS12.0

PDMSUI Application User Interface folder (PML 1)C:\AVEVA\Plant\PDMS12.0\pdmsui

PMLLIB Application User Interface folder (PML 2)C:\AVEVA\Plant\PDMS12.0\pmllib

PDMSDFLTS Applications defaults folderC:\AVEVA\Plant\PDMS12.0\pdmsui\dflts

PDMSPLOTS Applications PLOTS folderC:\AVEVA\Plant\PDMS12.0\pdmsui\plots

PLOTCADC Pointer to the PLOT executable.C:\AVEVA\Plant\PDMS12.0\plot\plot.exe

PDMSHELPDIR Online help data files.C:\AVEVA\Plant\PDMS12.0\onlinehelp

PDMSHELPDIR Online help data files.C:\AVEVA\Plant\PDMS12.0\onlinehelp

PDMSWK Temporary PDMS work file folderC:\temp

PDMSUSER Application Users save/restore setup area (or the users'home' folder)

C:\AVEVA\Plant\PDMS12.0\pdmsuser



Project Environment Variables

For each PDMS project, four more environment variables must be set. For example, for aproject ABC:

PDMS is installed with sample project data (See PDMS Projects). PDMS ProjectEnvironment variables for these projects are set in evars.bat.

4.5 Running PDMS from a Command Prompt WindowYou can run PDMS from a Command Prompt window rather than using the Start/Programsmenu. To do this you must set your PATH variable to include the folder where PDMS isinstalled.

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 (for example,

C:\AVEVA\Plant\PDMS12.0\) to the list of folders in the Path variable.

Once the Path variable includes the AVEVA PDMS folder, you can run PDMS by typingpdms at a command prompt.

4.6 Customising PDMS Start-UpThere is a batch (.bat) file supplied in C:\AVEVA\plant\PDMS12.0\ called pdms.bat whichallows 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

PDMSREPDIR PDMS Applicationware Report Input and Output folder.C:\AVEVA\Plant\PDMS12.0\pdmsui\reports

PDMSDFLTS Applications defaults folder. Note that individual users maynot have permission to change PDMS System defaults inC:\AVEVA\Plant\PDMS12.0\pdmsui\dflts, but they shouldhave their own local defaults area. This is achieved bysetting a PDMSDFLTS search path, e.g. ‘C:\USERDFLTSC:\AVEVA\Plant\PDMS12.0\pdmsui\dflts’.

ABC000 Project database folder

ABCISO Project ISODRAFT options folder

ABCMAC Project Inter-DB connection macro folder

ABCPIC Project DRAFT picture file folder



sequence of dialogs to help you create the shortcut. Type in the location of pdms.bat,for example: C:\AVEVA\plant\PDMS12.0\pdms.batthen 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 yourPATH environment variable, just type pdms in a command window to execute thebatch file.

• Otherwise, navigate to the folder where the batch file is stored and type pdms orpdms.bat.

4.6.1 Creating Your Own Batch File to Run PDMSYou can set up your own batch files to run PDMS. For example, you may wish to runDESIGN 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 userSYSTEM/XXXXXX, in MDB /STRUC, and run the PDMS command macro mymacrofile.

4.7 Running PDMS in batchPDMS 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 fileresumes 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 beused to make a PDMS script wait for PDMS to complete before continuing.

PDMSWait uses Windows facilities to wait for an event triggered by PDMSConsole whenPDMS finishes. Because you can be running more than one PDMS session on any onecomputer, both PDMSWait and PDMSConsole look for an environment variablePDMS_CONSOLE_IDENTIFIER before doing this. You can setPDMS_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 theprocess number, accessible as $$.



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 PlottingTo plot in a Windows environment, we recommend that you use the plotcadc.bat filesupplied in the AVEVA PDMS folder. Note that you may have to modify the plotcadc.bat fileto suit your local printer installation.

The Network Plotter must be mapped using the NET USE command. See your networkdocumentation 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 PLOTUser Guide for more information. Note that the options must be enclosed in quotes.

Example:

set PDMS_CONSOLE_IDENTIFIER=%RANDOM%call %PDMSEXE%\pdmscall %PDMSEXE%\pdmswaitecho Returned to .bat at %TIME%

Example:

plotcadc.bat c:\pdms\plot1 ps \\ntserver\NTPostScriptplotcadc.bat c:\pdms\plot1 hpgl \\ntserver\NThpgl 'CE=Y'


PDMS Installation GuideLanguage Support

5 Language Support

By default, your PDMS project can use any language whose characters are contained withinthe Latin-1 character set. The Languages covered by the Latin-1 character set a listed inthe table below. If you want to use any of the other, non-Latin-1 languages supported byPDMS, 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 Professionalin each of the supported language groups:

• Latin-1• Latin-2• Latin-Cyrillic• Far Eastern

Supported Languages

PDMS does not support any other language character set, nor does it support the mixing ofany of the above, except for mixing one Far Eastern language with English.

5.1 Preparing Windows to use Supported Languages

5.1.1 Windows 2000To add an additional language in Windows 2000, follow these steps:

1. Open the Control Panel.

Name Description Languages covered

Latin 1 ISO 8859-1 Latin alphabet 1 Danish, Dutch, English, Faroese, Finnish,French, German, Icelandic, Irish, Italian,Norwegian, Portuguese, Spanish,Swedish,

Latin 2 ISO 8859-2 Latin alphabet 2 Albanian, Czech, English, German,Hungarian, Polish, Rumanian, Serbo-Croat, Slovak, Slovene

Latin Cyrillic ISO 8859-5 Latin/Cyrillicalphabet

Bulgarian, Byelorussian, English,Macedonian, Serbo-Croatian, Ukrainian,Russian

Far Eastern Japanese, Korean, Simplified Chinese,Traditional Chinese



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 2000CD-ROM or access the system files across the network. Once the language isinstalled, Windows 2000 will prompt you to restart the computer.

5.1.2 Windows XPTo 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 clickthe language you want to add and the keyboard layout you want to use for thatlanguage.To configure the settings for the Language bar, click Language Bar under"Preferences". The Language bar is used to switch between languages while you areusing 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 therequired language. Click Apply. It may be necessary to install new code pageconversion tables. Only member of the Administrators group can install code pageconversion tables. The system will either prompt for a Windows XP CD-ROM or accessthe system files across the network. Once the language is installed, Windows XP willprompt you to restart the computer.

Note: For Far Eastern language support, it is necessary have the East Asian supportoption installed.

5.2 Preparing PDMS to use Latin LanguagesIn PDMS ADMIN, you must specify a character set for each project by using one of thefollowing commands on the PDMS ADMIN command line:

Command Languages covered

PROJECT CHARSET LATIN 1(default)

Danish, Dutch, English, Faroese, Finnish, French,German, Icelandic, Irish, Italian, Norwegian,Portuguese, Spanish, Swedish,



The corresponding font family must be selected for DRAFT and ISODRAFT drawings. UseProject>Font Families and select the Font Type appropriate for you chosen language.

For details, see the Adminstrator User Guide and Adminstrator Command ReferenceManual.

5.3 Preparing PDMS to use Far Eastern LanguagesYou 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:

In PDMS ADMIN, you must specify the multibyte character set for each project by using thecommand corresponding to your required language:

For details, see the Adminstrator User Guide and Adminstrator Command ReferenceManual.

PROJECT CHARSET LATIN 2 Albanian, Czech, English, German, Hungarian, Polish,Rumanian, Serbo-Croat, Slovak, Slovene

PROJECT CHARSET LATINCYRILLIC

Bulgarian, Byelorussian, English, Macedonian, Serbo-Croatian, Ukrainian, Russian

Command Languages covered

CADC_LANG=Japanese Kanji

CADC_LANG=Korean Korean

CADC_LANG=Chinese Simplified Chinese

CADC_LANG= TChinese Traditional Chinese

PROJECT MBCHARSET JAP

PROJECT MBCHARSET KOR FILE /<font filename>

PROJECT MBCHARSET CHI Simplified Chinese

PROJECT MBCHARSET TCHIN FILE /<font filename> Traditional Chinese


PDMS Installation GuideRunning PDMS Under Windows

6 Running PDMS Under Windows

6.1 Spaces in Windows pathnamesTo 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 recommendedfor use with filenames containing Asian characters.

6.2 Linking to Microsoft ExcelYou can make your reports load directly into a Microsoft Excel spreadsheet, as comma-separated 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 isnecessary to enclose Windows command arguments in double quotation marks if theargument contains embedded spaces. :\<excel folder>\.

6.3 Windows ParametersThe following setting can be used to improve performance when repositioning forms inPDMS. 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.


PDMS Installation GuideRunning PDMS Under Windows

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 Draggingand Show shadows under menus.


PDMS Installation GuidePDMS Projects

7 PDMS Projects

7.1 Sample ProjectPDMS 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 youdo start to create your own.

• It provides you with starting points for the tutorials in the following manuals:Pipework Support Design User GuidePipework Design User Guide Structural Design User GuideHVAC User GuideReporting Reference ManualDrawing Production User Guide

• It provides an example of how to set up your own projects.

The sample project is actually two projects in PDMS terms:• 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,

7.1.1 Copying Project SAM to Your User AreaThe sample project is loaded automatically when you install PDMS. You should copy thesample project to your user area and run it as supplied. The project files are held in twodirectories: sam000 holds all DESIGN data and catalogue data; sampic holds the DRAFTpicture libraries.

7.1.2 Users and Teams in the Sample ProjectFree User

The Free user has username/password SYSTEM/XXXXXX.

General Users

Team Username/password

ADMIN ADMIN/ADMIN



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 correspondingconstructor module.

Each MDB contains databases with appropriate access rights. There are also teams andusers associated with each MDB with appropriate access rights.

7.1.3 MDBs in the Sample ProjectThis section assumes that you are already familiar with PDMS databases.

The sample project contains the following MDBs which can be used for demonstration ortraining purposes:

CATS CATS/CATS

DEMO DEMO/DEMO

EQUI EQUI/EQUI

HANGER HANGER/HANGER

HVAC HVAC/HVAC

PIPE PIPE/PIPE

SAMPLE SAMPLE/SAMPLE

STRUC STRUC/STRUC

TEAMA USERA/A

TEAMB USERB/B

TEAMC USERCC

TEAMD USERD/D

TEAME USERE/E

TEAMF USERF/F

TEAMG USERG/G

CATS An MDB for practising using Catalogues and Specifications.

DEMO A demonstration MDB.

EQUI An MDB for the Equipment tutorials.

HANGER An MDB for the Support Design tutorial. This MDB containssuitable pipework, steelwork and civils as a starting point.



7.1.4 Sample Project and your own ProjectsYou can add databases from the sample projects SAM and MAS to your own projects fromwithin PDMS ADMIN, using the Install options on the main menu bar. Note that theseoptions are only available if you have the project environment variables for SAM and MASset.

Note: On DRAFT Libraries: You must have DRAFT libraries available in your currentproject before you can enter the module. You may find it convenient to install thelibraries supplied by AVEVA in the MAS project (using the Install options), even ifyou wish to create your own libraries for the project.

HVAC An MDB for the HVAC Design tutorial. This MDB contains suitablesteelwork and civils as a starting point.

MASTER An MDB containing the master Catalogues and Specifications,LEXICON, Dictionaries etc.

MASTERCAT An MDB used for practising the use of Catalogues andSpecifications.

PIPE An MDB for the Pipework Design and Pipework Spooling tutorials.

SAMPLE An MDB for the Reporting from PDMS and Drawing Productiontutorials. This MDB contains DESIGN data from which reportsand drawings can be produced. You can also produce isometrics.

STRUC An MDB for the Structural Design tutorial.

TRAINA to TRAING Additional MDBs available for training purposes.


PDMS Installation GuideTroubleshooting

8 Troubleshooting

Here are some suggestions about solving some problems you may encounter when usingPDMS under Windows.

8.1 General

8.2 License Manager Errors

Error: The dynamic link library DFORMD.dll could not be found in thespecified path.

Explanation: This is supplied with PDMS. Perhaps you have not set your PATHvariable. The PATH setting must include ‘C:\AVEVA\plant\PDMS12.0’

Error: STOP. The application failed to initialise properly (0xc0000135). Clickon OK to terminate the application.

Explanation: This occurs after a number of other errors. The most likely reason is aproblem with the PATH variable.

Error: When you start up lmgrd it says <time> (lmgrd) Can't make folderC:\FLEXlm, errno: 2 No such file or folder, etc.

Solution: There is no C: drive for the license manager to write to. As the SystemAdministrator or a Power User, you need to make a shared disk calledC:. This can be done on a networked or non-networked computer.

Within the Windows Explorer’s File menu, create a new folder (e.g.D:\C_drive) and make it current. Select File>Properties and selectthe Share tab. Click on the Shared As: option button and then clickOK.

Then from the Tools menu select Map Network Drive. Select C: fromthe 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.3 Entering PDMS

Explanation: The hostname used by AVEVA to create the license file does notcorrespond with the computer on which you are running PDMS. Thehostname comes from the variable COMPUTERNAME, which youcan obtain by typing 'env|findstr COMPUTERNAME' in a CommandPrompt window. Compare this with the license file contents, andresubmit if necessary.

Pop-up Mess.: FLEXlm: checkout failed: Cannot connect to license server (-15,10:10061) WinSock error code.

Explanation: lmgrd has not been started up - see above for details.

Pop-up Mess.: FlexLM: checkout failed: Cannot find license file (-1,73:2) No such fileor folder.

Explanation: lmgrd has not been started up - see above for details.

Pop-up Mess.: FlexLM: checkout failed: Licensed number of users already reached (-4,132).

Explanation: You have exceeded the permitted number of users specified in yourlicense file.

Error: (43,9) Environment Variable not defined for project name.

Explanation: You have not set the environment variable for the project, e.g. XYZ000.

Error: (43,1) Project <xxx> not available!

Error 7 allocating system database.

Explanation: The environment variable for the project does not point to the correctlocation. Either the disk and/or folder do not exist or are not readable.

Error: <username> not found. Invalid username or password.

or

Bad Password

Explanation: You are trying to enter PDMS without a valid PDMS username and/orpassword.

Error: PDMSWK environment variable not set.

Solution: Set PDMSWK to c:\temp or some other folder where PDMS cancreate temporary files.

Error: Error 34 opening variables file.



8.4 Problems with Graphics

Explanation: You cannot create a file in the location pointed to by environmentvariable PDMSWK.

Error: Project <xxx> is pre version 8.

Explanation: This can happen if you have transferred the project from UNIX usingFTP in ASCII rather than Binary format.

Error: Cannot pick certain items in DESIGN 3D shaded views.

Solution: There is probably a problem with the display driver for the graphicsboard that you are using. Make sure you have the version of thedisplay driver recommended on our supported display drivers Webpage.

Error: Incorrect colours.

Solution: Check the setting of your Display. The colour resolution should be setto ‘True Colour’ or 16.7 million colours.

Error: Graphics speed (for example in 3D views) is poor.

Solution: Check the setting of your Display.


PDMS Installation GuideStructure of PDMS on .NET

9 Structure of PDMS on .NET

From AVEVA PDMS 12, the GUI uses the Microsoft .NET environment including the latestWinForms based user interface components. Using this state-of-the-art technology enablesdocking forms and toolbars in PDMS and provides a robust foundation for the futureprovision of standard application programming interfaces.

This does affect the way PDMS is installed: this section gives a brief overview and thefollowing one outlines how to troubleshoot the installation.

9.1 OverviewThis 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 componentsincluding 3rd party controls from Infragistics. The .NET components are private assembliesinstalled under the root directory %PDMSEXE%.

9.2 PDMSEXEThe environment variable %PDMSEXE% is used to locate the executable on moduleswitch. 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 frompdms.bat which is located in your %PATH%. Both %PDMSEXE% and %PATH% shouldinclude the install directory.

9.3 GUI Module StructureEach GUI module is structured in the same way. For DESIGN the structure looks like this



where des.exe and des.dll live in the directory %PDMSEXE% and Wrappers.dll lives in theDESIGN subdirectory below %PDMSEXE%. So, when running a PDMS GUI module%PDMSEXE% is used to locate the executable, .NET loading rules are used to loadWrappers.dll and Win32 DLL loading rules are used to load des.dll (and other Win32 DLLson which des.dll depends).

9.3.1 WrappersFor each GUI module (DESIGN, DRAFT, ADMIN, ISODRAFT and MONITOR) there is aWrappers.dll in a subdirectory with the same name as the module. Each Wrapper.dll has adynamic link to the appropriate Win32 DLL for that module. .NET loading rules are used toload the appropriate Wrappers.dll for a given module. So, when running des.exe, theversion of Wrappers.dll linked with des.dll will be loaded. DESIGN and DRAFTsubdirectories also contain a drawlistWrapper dll which is used by the Drawlist add-in.

9.3.2 .NET Loading RulesAll the .NET assemblies are Private assemblies and are installed under %PDMSEXE%(Assembly Base directory) or a subdirectory below. .NET loads private assemblies from thebase directory of the application. If it can’t find the private assembly here it uses theapplications configuration file called <module>.exe.config to see whether it contains anypath hints. Path hints are stored in the <probing> element. So, for example, des.exe.confighas the following probing path <probing privatePath="Design" />. This means thatWrappers.dll is loaded from the subdirectory DESIGN below the application directory.

9.3.3 Win32 DLLsEach Wrappers.dll depends on the given module’s Win32 DLL, e.g. DESIGN’s Wrappers.dllfound 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 DESIGNsubdirectory where Wrappers.dll is loaded)

• The (application's) current directory (where it’s run from)• The Windows directory (default: C:\Windows) (we don’t 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 unlessyou are running from %PDMSEXE%, your %PATH% will be used to locate the module DLL.



(The Wrappers.dll subdirectory is the directory which is first searched for all the Win32DLL’s on which Wrappers depends i.e. <module>.dll, sglNet.dll, udDNet.dll, …)

9.4 ComponentsThe 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 correspondingdll e.g. des.exe and des.dll, a config file, a manifest file and an Addins file. The config file isused to specify the location of the Wrappers dll’s for each application, the manifest file isused to set the visual style of the application and the Addins file defines which add-ins theapplication will load (e.g. Explorer, Drawlist, …).

9.4.1 PDMSEXE Directory

• DESIGN/SPOOLERdes.exe, des.dll, des.exe.config, des.exe.manifest, DesignAddins.xml, SpoolerAddins.xml

• DRAFTdra.exe, dra.dll, dra.exe.config, dra.exe.manifest, DraftAddins.xml

• MONITORmon.exe, mon.dll, mon.exe.config, mon.exe.manifest

• ISODRAFTiss.exe, iss.dll, iss.exe.config, iss.exe.manifest, IsodraftAddins.xml

• ADMINadm.exe, adm.dll, adm.exe.config, adm.exe.manifest

• SharedDepends.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

• InfragisticsThis 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,



Infragistics.Win.UltraWinTabControl.v3.dll, Infragistics.Win.UltraWinToolbars.v3.dll, Infragistics.Win.UltraWinTree.v3.dll, Infragistics.Win.v3.dll, Infragistics.Win.Misc.v3.dll

• Systemmsvcp71.dll, msvcr71.dll

• Other DLLs required by DRAFTThese 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 DESIGNsgl5NET.dll

9.4.2 PDMSEXE/DESIGN subdirectorydrawlistWrappers.dll, Wrappers.dll

9.4.3 PDMSEXE/DRAFT subdirectorydrawlistWrappers.dll, Wrappers.dll

9.4.4 PDMSEXE/MONITOR subdirectoryWrappers.dll

9.4.5 PDMSEXE/ISODRAFT subdirectorydrawlistWrappers.dll, Wrappers.dll

9.4.6 PDMSEXE/ADMIN subdirectoryWrappers.dll

9.4.7 Add-insThese 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 DESIGNthis file is DesignAddins.xml. The toolbar entries to show and hide each add-in are definedin PML.

9.5 Forms and MenusMost of the User Interface is still defined in PML located in %PMLLIB% and %PDMSUI%.


Software Installation GuideTroubleshooting the .NET Installation

10 Troubleshooting the .NET Installation

10.1 Version Error

10.2 Wrappers or a Dependency Missing

Error: System.IO.FileLoadException: The located assembly's manifest definitionwith name 'PDMSResources' does not match the assembly reference.

Solution: All .Net assemblies must be the same version. OpenFile>Properties>Version>Assembly Version, and check that all versionnumbers are the same.

Error: An exception ‘System.IO.FileNotFoundException’ has occurred inmon.exe.

Additional information: File or assembly name Wrappers, or one of itsdependencies, was not found.

Solution: All the .NET assemblies are Private assemblies and are installed under%PDMSEXE% (Assembly Base directory) or a subdirectory below. .NETloads private assemblies from the base directory of the application. If itcan’t find the private assembly here, it uses the application’s configurationfile 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 <probingprivatePath="Design" />. This means that Wrappers.dll is loaded from thesubdirectory DESIGN below the application directory. Each Wrappers.dlldepends on the given modules Win32 DLL e.g. DESIGN’s Wrappers.dllfound in the Design subdirectory depends on des.dll. Win32 DLL loadingrules apply here. These are:

• The directory from which the importing component loaded. (i.e. theDESIGN subdirectory where Wrappers.dll is loaded in the case ofDESIGN)

• The (application's) current directory (where it’s run from)• The Windows directory (default: C:\Windows) (we don’t install

anything here)• The directories that are listed in the PATH environment variable


PDMS Installation GuideTroubleshooting the .NET Installation

10.3 Interface Incompatibility

10.4 No Add-ins

Since the module DLL does not live in the same directory as theWrappers.dll then unless PDMS is running from %PDMSEXE% the%PATH% will be used to locate the module DLL. (The Wrappers.dllsubdirectory is effectively is the directory which is first looked in for all theWin32 DLL’s which Wrappers depends on i.e. <module>.dll, sglNet.dll,udDNet.dll, º)

Make sure that both %PDMSEXE% and %PATH% point to the rootdirectory in which PDMS is installed.

Error: An exception ‘System.MissingMethodException’ has occurred inmon.exe,or

An exception ‘System.IO.FileNotFoundException’ has occurred inmon.exe

Additional information: A procedure imported by 'Wrappers' could not beloaded

Solution: The interfaces between components are not compatible. Check thatFile>Properties>Version Assembly Version on all assemblies is 12, orwhatever the current version is.

Problem: Add-ins missing from module

Solution: 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.5 Window Layout

10.6 SerializationSerialization is the process used to store the data - e.g. history stacks, toolbar state - for theGUI in a .NET environment.

Problem: Window layout is not restored e.g. Add-ins position and/or docked state,…

Solution: The file <module><version>WindowLayout.xml in the %PDMSUSER%directory stores this information for the each GUI module. If this file isdeleted then the window layout will return to its default.

Problem: Information is stored per project and per module in the following files inthe %PDMSUSER% directory:

<project><version>Settings.bin

<module><version>Settings.bin.

CAF (Common Application Framework) window layout information isstored in:

c:\documents and settings\<username>\local settings\applicationdata\AVEVA\PDMS

Solution: These files may be deleted or transferred between users working on thesame project. Users can delete or transfer the root directory.


ig51796

Documents

Transcript of ig51796