If I try to use the "Create Associated Terminal" to create a terminal for an existing device, it only works when the terminal type selected is "Generic." Also, if I view a previously-created terminal in Blueprint Administrator, I only see the "Settings" tab; the "Configuration" tab is missing.

This can happen if the Analyst or Collector has been reinstalled for whatever reason, but the existing database remained intact and is being used by the new installation.

To correct this behavior, do the following:

  1. On the Collector or Analyst (whichever is hosting the EDI service), locate the terminal's ".terminal.config" file. In Windows 2003, this would be in C:\Documents and Settings\All Users\Application Data\PharosSystems\Blueprint\TerminalPlugins. In Windows 2008, this would be in C:\Program Data\PharosSystems\Blueprint\TerminalPlugins. For this example, the Omega PS200.1.0.1.terminal.config file will be used.
  2. Move this file to the Blueprint \Bin directory (C:\Program Files\PharosSystems\Blueprint\Bin; on 64-bit systems, start in C:\Program Files (x86)).
  3. In a Command Prompt window that is running as an Administrator, navigate to the \Bin directory.
  4. Execute the following command:

    C:\Windows\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe /TerminalConfigFile="Omega PS200.1.0.1.terminal.config" PharosSystems.Blueprint.TerminalPlugins.Ini.dll

    Note that this example assumes that Microsoft Windows is installed to the Windows directory. Also, replace the file name (shown in blue) with the .terminal.config file that has been moved.
  5. Back in Blueprint Administrator, go to Devices > Terminals and select the terminal. The terminal definition should now include the "Configuration" tab.

At this point, you may also use the "Create Associated Terminal" button and reference that terminal type in the resulting dialog box. You will need to repeat these steps for every terminal type that exists within the solution.