Registry Entries (Windows 2012) - PDS - Installation

Plant Design System (PDS) Project Setup Technical Reference

PPMProductFamily
3D Design and Visualization
PPMProduct
PDS
PPMCategory
Installation

This section covers PDS installation prerequisites for Windows 2012.

During the PDS installation, do not install any of the products into a folder with a space in the path. For example, by default, Iplot will load into the "c:\Program Files" folder. You must change the path to a folder without spaces, for example: "d:\win32app\ingr\iplot".

No Intergraph Products Loaded

  1. Start the registry editor (regedt32.exe).

  2. Open the HKEY_LOCAL_MACHINE > SOFTWARE > Wow6432Node folder.

  3. Create the INTERGRAPH folder by selecting EDIT > NEW > KEY from the Registry Editor menu bar.

    If the Intergraph network adapter has been loaded, this folder will already exist.

  4. Enter Intergraph for the KEY NAME. Note that it is case-sensitive.

    An Intergraph key now displays under the Wow6432Node folder.

  5. Highlight the new Intergraph key and select EDIT > NEW STRING VALUE from the Registry Editor menu bar.

  6. Enter COMMON for the VALUE NAME. Note that it is case-sensitive.

  7. Double-click COMMON, and then enter C:\win32app\ingr\share in the String Editor form. The information that appears in the right-hand side of the registry editor when you open the Intergraph folder should look like this:

    COMMON: REG_SZ: c:\win32app\ingr\share

Intergraph Products Already Loaded

  1. Start the registry editor (regedt32.exe).

  2. Open the HKEY_LOCAL_MACHINE > SOFTWARE > Wow6432Node folder.

  3. Open the Intergraph key, and verify that the COMMON value is as shown:

    COMMON: REG_SZ: C:\Program Files \Common Files\Intergraph

  4. Edit the COMMON value as shown:

    C:\win32app\ingr\share

  5. Go to the C:\Program Files\Common Files\Intergraph directory and note which Intergraph products have files loaded in this location. Remove these products and reload them.

Creation of "DisableUNCCheck"

This change should be made on all Windows workstations and Servers, where the Command Processor key does not already exist. The time at which you do this is not critical (for example, if you have already loaded products, you can still make this change).

  1. Start the registry editor (regedt32.exe).

  2. On the Local Machine window, open the HKEY_LOCAL_MACHINE > SOFTWARE > MICROSOFT folder.

  3. Select EDIT > NEW > KEY from the registry editor menu bar.

  4. Enter Command Processor for the Key Name. Note that it is a case-sensitive. Make sure you leave a blank space between the two words.

  5. Leave the Default String field empty.

    The Command Processor folder displays under the MICROSOFT folder.

  6. Highlight the new Command Processor key from the Registry Editor menu bar and select EDIT > NEW DWORD (32-bit) VALUE.

  7. Enter DisableUNCCheck for the Value Name. Note that this is a single word and it is case-sensitive.

  8. Double-click DisableUNCCheck to open the DWORD (32-bit) VALUE editor dialog box.

  9. Select the Hex radio button, and enter 1 (numeric one) in the Data field.

    When you open the Command Processor folder, the following information now displays in the Registry Editor :

    DisableUNCCheck: REG_DWORD:0x00000001 (1)

Winreg Key

All paths defined within the PDS project are defined with a NODENAME and the actual PATH to the file or directory on the node. There is a registry entry named HKEY_LOCAL_MACHINE > System > CurrentControlSet > Services > LanManServer > Shares that contains a listing of the Shares available on the server, and the local path to those shares. The mount code used by PDS takes the NODENAME and PATH from the PDS project, accesses the registry key, HKEY_LOCAL_MACHINE > System > CurrentControlSet > Services > LanManServer > Shares, and attempts to resolve the NODENAME and PATH into a UNC path. Once successful, this UNC path is passed back to PDS to access the needed files. This explains why in a new installation of PDS, when the WINREG key of the server has not been modified, only users who are administrators on the server can successfully use PDS.

In the past, it was recommended that you delete the WINREG key to resolve this problem. But, by adding the path to the HKEY_LOCAL_MACHINE > System > CurrentControlSet > Services > LanManServer > Shares key to the AllowedPaths sub-key of the WINREG key, all users will have access to the information needed to resolve the NODENAME and PATH into a UNC path for use by PDS.

This modification is needed on all server nodes and should be done prior to project creation. This modification is also needed on any client nodes that will use remote batch queues to pipe PDS batch jobs to another machine for processing.

  1. Include Path.

    1. Open the registry on the server using regedt32.exe.

    2. Find the key HKEY_LOCAL_MACHINE > System > CurrentControlSet > Control > SecurePipeServers > WINREG > AllowedPaths.

    3. Double-click the AllowedPaths registry key.

      This is a multi-line value.

      The Multi-String Editor displays.

    4. Enter System\CurrentControlSet\Services\LanManServer\Shares and then click OK.

      All users should now be able to use PDS without requiring Administrative rights on the server.

    5. Reboot the server.

  2. Delete the Winreg key.

    1. Open the registry on the server using regedt32.exe.

    2. Find the key HKEY_LOCAL_MACHINE > System > CurrentControlSet > Control > SecurePipeServers > WINREG.

    3. Delete the WINREG key by selecting it and pressing DELETE.

    4. Reboot the server.

The common errors associated with the WINREG key are listed below.

  • 'Maximum Number of Shares Exceeded'

  • 'Error 67, Error Mounting Remotename'

  • 'Net address and directory could not be mounted verify the specified control files'

  • 'Error in Number of Columns' when trying to create Equipment Models'

  • 'No Matching Sharename for drive letter:\path'

  • Empty log files when routing PDS batch queues to a remote machine for processing.