Installing Plant Applications

You should install or upgrade to .NET Framework 4.7.

1. Stop all SOA services, Plant Applications services, and SQL server services to prevent the .NET Framework 4.7 installation from rolling back.
2. Download and install the .NET Framework 4.7 from the Microsoft product website.
3. Use the Control Panel to verify Microsoft .NET Framework 4.7 is listed as an installed program.
4. Restart the services.

1. Open Server Manager.
2. Expand Roles, then select Web Server (IIS).
3. Scroll down in the information listed for the Web Server (IIS) to view installed Role Services, and verify that the correct services have been installed.
4. If needed, click Add Roles in the Roles Services section to start the Add Role Services wizard to add a role.
5. Click the Web Server (Installed) box to enable service selection. Restart the machine if role services have been added.
6. Expand Features, and run the Add Features wizard.

   

7. Select HTTP Activation under .NET Framework 3.5.1 Features, then run the wizard to install the feature.

WebDAV Publishing causes an error when deleting or updating comments or events. When installing IIS, do not include WebDAV.

If IIS is already installed with WebDAV, uninstall it from the Role Services screen of the Server Manager.

1. Open Internet Information Services (IIS) Manager from the Server Manager, then right-click the icon to open the ISAPI Filters pane from the ISS section of the ISS Manager.

   

2. Expand the Executable column and look for any executable path containing two backslashes instead of one. Right-click the executable and select Edit.

   

3. Change the ISAPI Filter path to use a single slash, such as \aspnet_filter.dll as shown in the following example.

   

4. Navigate to ISAPI and CGI Restrictions under IIS for the Report Server, then right-click to open the pane.

   

5. Verify that the Framework and Framework64 extensions for ASP.NET, version 4.0.30919, are set to Allowed. Right-click an entry to make a change if necessary.

   

The Remote Data Service (RDS) allows Plant Applications Client components, including the Administrator, to access historians without installing the API components on the local server.

1. Use the Plant Applications client installation to install the RDS service on the remote historian server.
2. Edit the historian in the Plant Applications Administrator, then select the Remote Data Source option to facilitate communications.
3. Install Historian Client API tools.
   1. Install the Historian on the computer where you will install the Plant Applications server.
   2. Select the following components on the Select Components page:
      • Historian Excel Add-in
      • Historian Administrator
      • Historian Client Tools
      • Historian Documentation & Help
      • OLE DB
   3. Click Next, then click Finish to restart the computer with your changes.

The Proficy Application Server installs Workflow components as prerequisites for Plant Applications.

1. Copy software and extract files to the machine where you want to install the Proficy Application Server components, then run InstallFrontEnd.exe as an administrator.
2. From the Installation Menu, select Proficy Application Server from the Prerequisites group.
3. Select the Proficy Application Server from the options in the Application Server Setup Wizard screen.
4. Select Core as the type of Proficy Application Server, then click Next.
5. Accept the End User License Agreement (EULA) for Proficy Workflow by clicking I Agree.
6. From the Installation Folders and Architecture screen, select the destination folders for the installation location, then select 32-bit architecture. Click Next to continue.

   

   Note: Plant Applications does not support 64-bit architecture.
7. Specify Active Directory Lightweight Directory Services (AD LDS) settings if using AD LDS, or use a standalone local directory. Click Next to continue.

   

   Note: If AD LDS is not installed, the wizard defines a standalone local directory.
8. Verify that the SQL Server Browser service is running. At the Database Configuration screen, specify SQL Server settings for the installation. The example screen specifies a database named SOADB, which is typical when installing a UMDB from a SOA database. If upgrading from an existing Plant Applications database, specify its name. Or enter a new name for the UMDB. Click Next to continue.

   

   The SQL User account used for the database when installing Plant Applications requires, at minimum, system administraor priviliges. To review login permissions and connection properties set up in SQL Server:
   1. Select Properties by right-clicking a server name in Object Explorer in SQL Server Management Studio.
   2. Review the Security and Permissions pages in the Server Properties window.
   3. Click View connection properties in the Connections pane.
9. If needed, start the SQL Server Agent (MSSQLSERVER) service.
10. At the Security screen, enter administrator credentials for Workflow.

    

11. From the Service Certificates screen, generate new certificates or import existing certificates. For more information, see, SSL Security Certificates. Click Next to continue.
    The installation program places a certificate into the trusted root store on the server where the Application Server is installed.
12. At the Web Service screen, enter credentials for the KSPUser account created to connect the Proficy web service to the database.

    

    1. Enter the domain name for the website where the Proficy application web server is hosted.
    2. Enter a password for the Internal SQL Database User (KSPUser).
    3. Click Next to continue.
    Note: You must install the Plant Applications Server before installing web components on a separate machine.
13. If the installation wizard displays a Firewall Detected message, disable your firewalls or configure your computer to communicate with the server. Click Next to continue.
14. From the Installation Confirmation screen, click Install to install Proficy components. Follow any additional screen prompts.
    Note: The installation program times out after 10 minutes if the Proficy Server service does not start, and a message prompts you to manually start the service. Once the service starts, the installation automatically continues.
    The installation script performs the following actions:

    • Installs MS Visual C++ redistributables.
      Note: In order to install Workflow 2.6, you may be required to uninstall version VC++ 2017 and then reinstall it.
    • Installs Proficy Application Server.
    • Sets up the SOA database.
    • Sets up security.
    • Sets up IIS.
    • Sets up SQL.
15. Upon successful installation, the wizard displays a confirmation message. Click Exit to close the installation wizard.
16. You can verify that the SQL Server installed successfully by checking the SQL server setup failed status in the SetupDataPlantAppsTemplateFile.xml file under Program Data/Proficy.

After IIS is installed and basic setup completed, you may need to bind an SSL certificate to HTTPS on the machine where the web server is installed.

1. Start the Internet Information Services (IIS) Manager.
2. Navigate to and select Default Web Site. Select Bindings.

   

   The Site Bindings dialog box is displayed.

   

3. Bind the certificate to HTTPS.
   1. Click Add to display the Add Site Binding dialog box.
      If you are re-binding the HTTPS certificate, select https from the Site Bindings dialog box, then click Edit.
   2. Select https in the Type field.

      

   3. In the SSL certificate field, enter the fully-qualified domain name of the server that received the certificate.

      For the Proficy Application Server, the server is typically the host that the Web Server uses to connect to the server.

      If you are re-binding the HTTPS certificate, the port remains 443. Select your SSL certificate from the drop-down menu. Click View to verify that you have a private key that corresponds to the certificate.

   4. Click OK to add HTTPS binding to the list of bindings in the Site Bindings dialog box.
4. Close the Site Bindings dialog box.
5. Close the Internet Information Services (IIS) Manager.

1. Select Plant Applications Server from the Installation menu to start the Setup Wizard. If the installation does not automatically start, locate and double-click the ProficyServer.exe file.
2. Accept the End User License Agreement (EULA), then click I Agree to continue.
3. Enter the administrator credentials for the Proficy (Workflow) SOA Server or Proficy (Workflow) Client at the Configure Security screen, then click Next to continue.

   In the following example, Admin is the Administrator Name that was entered when installing Workflow.

   

4. If needed, select Install Plant Applications Service Provider (PASP) at the Install PASP screen, and click Next.
   Note: The PASP supports Plant Applications versions 4.4.1 and 5.0 for customers using interface methods published with the old version of the service provider. A standalone installation program is available if you install the PASP at a later time. The new MESCore Service Provider, which supports the UMDB, is installed with Plant Applications 6.0 or higher. Methods for the PASP remain documented in the Proficy Workflow help. You must install the PASP to run any workflow applications developed to run against Plant Applications 6.0 and earlier, as they will not run with the new MESCore SP.
5. From the Ready to Install screen, click Install to start the installation.

   The installation script times out after 10 minutes if the Proficy Server service does not start, and prompts you to manually start the service. Once the service is started, the installation automatically continues.

   The installation script performs the following actions:

   • Maps user accounts to the installed database.
   • Installs Plant Applications Server.
   • Sets COM DLLs and ActiveX controls by registering the following files:
     • C:\Program Files\Common Files\Proficy\Plant Applications\PRMsgs.dll
     • C:\Program Files\Common Files\Proficy\Plant Applications\ProfSVR.dll
   • Creates the Plant Applications database and tables, and populates the database (database size affects length of time).
   • Installs the MESCore Service Provider module.
   • Stops the Proficy Server, Proficy Publisher, and Proficy STS services.
   • Installs product options, including displays, and sets up the Proficy site, Plant Applications services, and MESCore service views and triggers.
   • Creates a BAT file with uninstall settings.
   • Calls a data model loader to create aspect tables for the database.
   • Starts the PRLicenseMgr, PRProficyMgr, and Plant Applications services, and restarts Proficy services.
6. From the Configure Site screen, enable any essential product items.

   

   Click Save to save your changes, then click Exit to complete the wizard.

7. Click Exit to close the wizard.
8. Confirm that the Proficy Server and Proficy Server Manager services are started. If services fail to start, check the applicable log files.
9. Verify your installation by checking the installation log files.

   Directory	Action
   <Drive>:\<Program Files>\Proficy\Proficy Database\SetupLogs	Verify that Verifies.log and StoredProcedures.log files for the UMDB contain no errors.
   <Drive>:\<Program Files>\Proficy\Proficy Server\SetupLogs	Verify that its StoredProcedures.log file contains no errors.
   <Drive>:\<Program Files>\Proficy\Proficy Server\LogFiles	Verify that the Plant Applications Service log files, CalculationMgr-xx.log files, and Gateway-xx.log files contain a Connected to Router notification. This notification indicates that the TCP/IP communications are functioning successfully on the Plant Applications Server.
   <Drive>:\<Program Files>\Proficy\Proficy Server\LogFiles	Verify that the Router-xx.log file initialized successfully and does not contain any errors.

If you are using Web Server reports, install the Plant Applications Report (Web) Server after installing the Plant Applications Server, but before installing a Plant Applications Client.

1. Select Plant Applications Client from the Installation Menu, then click Next at the Welcome screen.
2. When prompted, click OK to review the Important Product Information page.
3. From the Custom Setup screen, select Plant Applications Client and Plant Applications Excel Add-in from the list of options.

   You can also select Plant Applications Administrator, OPC Server, and Remote Data Services to install.

   No prerequisite software is required to install the Proficy OPC Server. However, you can use an OPC test client such as Matrikon OPC Explorer to test connections to the OPC Server. See Plant Applications Help to set up a user account.

   Click Space to display the available and required space for features.

4. Click Next to continue.
   You are prompted to install desktop shortcuts and, if needed, Microsoft Excel.
5. Enter the name of the SQL database server, or click Browse button to select one. Click Next to continue.
6. On the next screen, accept or change the destination folder.
7. Click Yes to allow Plant Applications to bypass firewall and port settings, or to make appropriate setup changes.
8. From the Ready to Install screen, click Install.
   The Installing Plant Applications Client screen is displayed as the wizard installs the software and completes post-installation tasks.
9. When the wizard displays the InstallShield Wizard Completed screen, click Finish. Ignore an error message related to a file unzip action not responding.

The Plant Applications SDK is a DLL that exposes methods to read and write Plant Applications data to use with VB.NET applications, Excel reports, and so forth.

1. Select Plant Applications .NET SDK from the Installation Menu.
2. Click Next at the Welcome screen.
3. From the Setup Type screen, select Typical to install DLLs or Custom to provide options to install help or the SDK test application.
4. Click Next. If you selected the Custom installation options, make the applicable selections.
5. Click Finish.

You must install the Plant Applications Message Bridge on the Plant Applications server node to access the real-time updates on the applications in the Plant Applications Universal Client.

About This Task

The Plant Applications Message Bridge installer installs the following prerequisites:

• Erlang OTP
• RabbitMQ Server

Note: If the Plant Applications Message Bridge is currently installed, do not reinstall the Message Bridge. You can verify whether the Message Bridge is installed in the Programs and Features list on your computer as shown in the following image.

1. Select the Plant Applications Message Bridge wizard, and, on the welcome screen, select Next to install the Message Bridge.

   

   The Missing Prerequisites screen appears, listing any prerequisites that must be installed.

   

2. In the Missing Prerequisites screen, select Continue to install any missing prerequisites.
   The Read and accept the license agreement to continue screen appears.
3. Read the license agreement, select Accept, and then select Next to continue the installation.
   The Microsoft SQL Server Credentials screen appears.

   

4. In the Microsoft SQL Server Credentials screen, enter the credentials to access the Microsoft SQL server as described in the following table.

   Credential	Description
   Hostname	Enter the host name where the Microsoft SQL server is installed in the format HOST_NAME\INSTANCE, where HOST_NAME is the host name (either a fully qualified domain name or IP address, of the server), and INSTANCE is the instance of the server.
   Database	Enter the name of the Plant Applications database that you want to connect with the Plant Applications Universal Client.
   User	Enter the user name that has permissions to access the database you entered in the Database box. By default, the user name appears as sa.
   Password	Enter the password for the user you entered in the User box.
   Instance	Enter the name of the instance of the SQL server. Entering an instance is optional.
   Port	Enter the number of the port that the instance uses to listen for client connections.

5. Select Validate Connection to validate the database connection.
   If the database connection is successfully validated, the Next button is enabled.
6. Select Next.
   The RabbitMQ Administrator Account Credentials screen appears.
7. In the RabbitMQ Administrator Account Credentials section, enter the user name and password for an existing RabbitMQ Administrator, if RabbitMQ is already installed. Else, provide the user name and password you intend to use as an administrator.
8. In the Plant Applications Administrator Account Credentials section, enter the user name and password for an administrator account in Plant Applications, and then select Validate Connection to validate the credentials.
   If the credentials are successfully validated, the Next button is enabled.
9. Select Next.
   The You are ready to install screen appears.

   

10. Select Install to install all the prerequisites and the Message Bridge.
    Depending on the options selected, the installation process may take some time. The installer displays the status updates.
    On successful installation, the Installation Successful screen appears.

    

11. Optional: Select View Logs to see the installation details.
12. In the Installation Successful screen, select Exit to close the wizard.

1. Open the RabbitMQ management console, http://localhost:15672.
2. Login as a guest. Enter guest as the Username and Password.
   Note: The default user ???guest??? is an administrative user and its login credentials are published on the official RabbitMQ web site. It is recommended that you update this user or delete it as per your local security policies.

   

3. On the Admin tab, select Add a User. Enter the username and password provided for the RabbitMQ account during the setup and for Tags, select Set > Admin.
4. Click Add user.

   

5. In the All users list, click on the user you just added under the Name column.
6. Set the required permissions for the user and click Set permission.
   
7. The page refreshes and the user is added with the selected permissions.

If you are upgrading an existing SOA database to a UMDB, prepare the database for migration by running the CreateAspect command from the command line with any required aspect options.

1. From a command prompt, enter the Plant Applications installation path. For example: .
   C:\<Program Files location>\Proficy\Proficy Workflow\Program
2. Run the Proficy.MESCore.Utils.CreateAspect.exe program to create Equipment and Material aspects, or add the following options to create aspects:

   Option	Description
   /addEquipProp	Creates the Equipment Property aspect.
   /addEquipProp /addMatProp	Creates Equipment and Material aspects as well as the Equipment Property and Material Property aspects.
   /addEquipProp /addMatProp	Creates Equipment and Material aspects as well as the Equipment Property and Material Property aspects.

   For example: Proficy.MESCore.Utils.CreateAspect.exe /addEquipProp /addMatProp

1. From Internet Explorer, select Tools > Internet Options.
2. Select Local Intranet on the Security tab, then click Custom Level to display the Security Settings dialog.
3. Scroll down to User Authentication, then select Automatic logon with current username and password. Click OK.
4. Select Trusted sites on the Security tab, then click Custom Level to display the Security Settings dialog.
5. Scroll down to User Authentication, then select Automatic logon with current username and password. Click OK
6. Select Trusted sites on the Security tab, then click Sites to modify the Trusted sites dialog.
   1. Verify that the web server name and localhost are included in the list of trusted sites in the format http://servername.
   2. tTo add the web server or local host to the list of trusted sites, enter the server in the Add this website to the zone field in the format http://servername, then click Add.
   3. Click Close.
7. On the Privacy tab, click Advanced to display the Advanced Privacy Settings dialog.
8. Select Override automatic cookie handling, then click OK.
9. Scroll down to Security on the Advanced tab, and verify that Enable Integrated Windows Authentication (requires restart) is selected. Click OK.

After installing IIS roles, you can install the Plant Applications Report Server.

1. Run InstallFrontEnd.exe to display the Plant Applications Installation Menu.
2. Select Plant Applications Report Server to start the installation program. If the installation does not start, run the PlantApplicationsWebServer.exe file.
3. Click Next at the Welcome screen, click OK at the next screen to proceed, and then click Yes to override firewall settings.
4. At the Custom Setup screen, select the components to install on this server. Click Next to continue.

   

5. If a dialog opens to to acknowledge installation of a distiller to produce PDF documents, click OK
6. Accept default port numbers for the HTTPS port, or enter different ports as needed. Click Next.

   

7. Enter the name of the SQL Database server if prompted, and select the authentication method. If using Server authentication, enter the server credentials, then click Next.

   

   The Web Server installation program checks a specific registry key for an existing SQL Server name.
8. Click Next to continue. Record any listed tasks that you may need to complete.
9. Click Next to continue, and complete the dialog when prompted:
   1. Confirm whether you want to install the Plant Applications Web Reporting engines on the same computer as the Plant Applications Server.
   2. If the Plant Applications Web Server already exists, confirm that you want to overwrite its configuration.
   3. Click Next.
10. Enter the Windows Account (username) and Password of the local Windows user account for the machine where the Plant Applications Report engines and Plant Applications services will be running. Click Next.
    Note: Although the Plant Applications services run under the Local System account, you should use a local Windows user account.
11. At the Destination Folder screen, accept the default location for the web server destination folder, or click Browse to select another location. Click Next.
12. Click OK to acknowledge that SharePoint Portal Services are required to access Sharepoint dashboards.
    Note: See Changing the SharePoint Port Number for steps to use a port other than port 80.
13. Click Install at the Ready to Install the Program screen to begin copying files.
    The installation program sets up the web server. The program installs the Microsoft SOAP if needed, imports the Web Part templates, and populates the database.

    Note: If a portal is not found, a prompt notifies you that Web parts will be available only through the Plant Applications Web Server or Proficy Real-time Information Portal (RTIP).
14. Click Finish.
    Report Server instances are displayed under the Sites folder in the IIS Manager.
15. Restart your computer to complete the installation.

1. Start Excel under the same login account used by the Plant Applications Report Engine services.
2. Under the Internet Information Services (IIS) Manager, verify that Anonymous access has been enabled for the three virtual FTP directories (Templates, Reports, and PAReporting) by enabling Anonymous Authentication for the PAReportingFTP site.

   

   Note: By default, this action occurs when installing the Web Server for Plant Applications.
3. Verify that the anonymous users (IUSR_*) have full control.
4. Verify that you can use FTP, and log in as anonymous.
5. Right-click the ..\inetpub\wwwroot folder in Windows Explorer, select Properties, and then open the Security tab. Grant full control under Permissions to all users including Users <computer name>, IIS_IUSR_<computer name> (Internet Guest Account) and IIS_WPG (Launch IIS Process Account).
6. In Local Users and Groups (access from Computer Management, or search for ???Local Users??? from the Windows Start menu), add the following users to the Administrators group:
   • IUSR_<computer name> (Internet Guest Account)
   • IWAM_<computer name> (Launch IIS Process Account)

When the Plant Applications Report Server has been installed on a different machine from the Plant Applications Web Client, you must configure Plant Applications Report Server applications (PAReporting, Apps, and ProficyDashBoard) to use different X-Frame-Options.

1. Start the Internet Information Services (IIS) Manager.
2. In the IIS Manger, drill down in the Connections tree to Sites > Default Web Site > Apps, and then select HTTP Response Headers.

   

1. Start Excel from the command line.
   1. Click Start > Run.
   2. Type excel.exe in the Open field, then click OK.
2. Click Microsoft Office, then click Excel Options.
3. Click the Add-Ins category
4. In the Manage box, click Excel Add-ins, then click Go to display the Add-Ins dialog box.
5. Select the Plant Applications Excel Add-In check box, then click OK.
   A message verifies the Plant Applications Add-in has been installed.
6. Click Plant Applications on the Add-ins ribbon, then click Options to display the Plant Applications Add In Options dialog box.
7. Under Server Access, verify the following three items in the display
   • Correct default server.
   • Correct user.
   • Connected status.

   If not:

   1. Click Edit to display the Connect Server dialog to edit the user details. If necessary, log in with Plant Applications Administrator credentials.
   2. Right-click the server, then click Edit to update the Add-in connection details.
   3. In the Server dialog, click Advanced, and verify that the Default Server is selected. Click OK.
   4. If the Add-In is not connected to the server, right-click the server. Select Connect, then click Close.
   5. Click Save to update the registry settings.
8. Click the Microsoft Office button, then select Excel Options to display the Excel Options screen.
9. Click Trust Center, then click Trust Center Settings to display the Trust Center screen.
10. Click Add-ins, and verify that all options are not selected.
11. Click Macro Settings, then select Enable all macros.
12. Click OK, then click Save.
13. Clear the Save AutoRecover information every option, then select the Disable AutoRecover for this workbook only option.
14. Click OK and close Excel.

You must manually upgrade your system to use UTC on an existing Plant Applications installation.

• Create a gap in your data, based on your server time.
  1. Change the UTC.

     Server time	Do this	Example
     GMT	Switch to UTC. The gap is created automatically when you switch to UTC time.	If you are at GMT -5:00 and your last data was recorded at 14:22, when you switch to UTC (GMT) the data is stored at 19:22, creating a gap in your data of five hours.
     +GMT	Wait until the UTC time is newer than the last time stamp in the database. This prevents data from being overwritten.	If you are at GMT +3:00 and your last data was recorded at 11:00:00, you can shut down the server, wait for four hours and switch to UTC. The system stores your data i at 12:00:00, providing a one-hour gap.

  2. Move the server as described in the Knowledgebase article KB5427 at the Support web site: https://digitalsupport.ge.com.
• To eliminate the runtime data from the copy of your database, move the server as specified in KB5427 and truncate your runtime data. See the the support web site https://digitalsupport.ge.com for the additional truncation procedure.

After installing Plant Applications, you can implement support for additional languages using its Native Language Support (NLS) features.

1. Select All Programs from the Windows Start menu.
2. In the Proficy folder, open the Proficy Plant Applications folder.
3. In the Configuration folder, select Configure Plant Applications Language Support. You can also run ConfigurePALanguages.exe to set up language support.
4. At the Configure Plant Applications Database screen, modify any server settings as needed.
5. Select one or more languages to include, then click Save.
   Tip: Use these options to set up language support after any subsequent Service pack or SIM upgrade.

Communication conflicts can arise when some third-party applications use port 12280, also used by Plant Applications, which can cause the application to disconnect from the router.

You can edit the values in the Plant Applications configuration file to customize your installation.

After installing the Plant Applications Server, the Plant Applications Server services should start automatically.

1. Open the Windows Control Panel, and double-click Administrative Tools.
2. Double-click Services.
3. Scroll through the list of services and verify that the Plant Applications Server services have all started. If they have not started, start them manually.
   Another method for verifying that the Plant Applications Server services have started is to view the server log files. These text files are created during the Plant Applications Server installation. Each service has its own log file. By default, the log files are located on the Plant Applications Server in the following directory:

   C:\<Program Files>\Proficy\Proficy Server\LogFiles

When using Plant Applications, the connection to the server can be lost for a number of reasons.

1. Start Plant Applications Administrator and log in with username comxclient and password comx.
2. Start Plant Applications client and log in with username comxclient and password comx.
3. Start Microsoft Excel.
4. Load the Plant Applications Add-in for Excel, click Tools > Add-ins > Plant Applications Excel Add-in.
5. Connect to the Plant Applications Server. For more information, see Connecting to a Server topic in the online help for the Add-in.

SharePoint Services 3.0 uses port 80 by default, which is the port used by the Plant Applications Web server.

1. On the Plant Applications Web server, select Start > Administrative Tools > Internet Information Services (IIS) Manager to open Internet Information Services (IIS) Manager.
2. Expand the server and expand Web Sites.
3. Right-click SharePoint - 80, then select Properties.
   The SharePoint ??? 80 Properties dialog box appears.
4. Under web site identification on the Web Site tab, enter an unused port number in the TCP Port field. Click OK.
5. Right-click SharePoint Central Administration v3, then select Browse to display the SharePoint Central Administration page.
6. Select the Operations tab and select Alternate access mappings under Global Configurations.
7. Under Internal URL, select the URL for the server (for example: http://<myservername>/).
8. In the URL protocol, host and port field, append the port number used in step 5 to the end of the computer name. For example: http://<myservername>:85/.
9. Click OK and, if necessary, start the Default Web Site.
   Note: Add the port number to the SharePoint URL. For example, if you used port 81, the URL would be: http://<myservername>:81.

You can use an SQL Server database as the Plant Applications database or Unified Manufacturing Database (UMDB).

1. Back up the database on the SQL Server instance.
   See How to create a database backup (Enterprise Manager) in the SQL Server Books Online.
2. Make a copy of the backup file.
   Because SQL Server Management Studio does not allow restoration from a network location, the backup file must be copied to the local disk of the SQL Server instance.
3. Restore the database to the SQL Server instance.
   See How to: Create a New Database from an Existing Database Backup (SQL Server Management Studio in the SQL Server Books Online.
4. After the database has been restored, ensure that permissions are set up correctly in the Plant Applications database. From SQL Server Management Studio, run the following script to rebuild the SQL permissions

   exec sp_Revokedbaccess 'ProficyDBO' 
            go 
            exec sp_Revokedbaccess 'ComXClient' 
            go  
            exec sp_Revokedbaccess 'ProficyConnect'
            go 
            exec SpSupport_ChangeDBOAccount 'Proficydbo','ProficyDBO'

After installing the Plant Applications Server, you can move the Plant Applications or Unified Manufacturing Database (UMDB) database file and log file to a separate physical disk to optimize performance.

1. Locate the MDF and LDF files.
   1. Start SQL Server Management Studio from the Windows Start menu.
   2. Navigate to the database, right-click it, then select Properties to display the Database Properties dialog box.
   3. Under Select a page, right-click Files to view the location of the MDF and LDF files.
2. Stop the following Plant Applications Server services:
   • Proficy Server Manager
   • Proficy Server Router
   • Proficy Server License Manager
3. Stop the Proficy Server, Proficy Publisher, and Proficy STS Services used for SOA.
4. In SQL Server Management Studio, take the database offline.
   1. Select Plant Applications SQL Server, then select Databases.
   2. Right-click the Plant Applications database, select Tasks, and then select Take Offline.
5. Detach the database (refer to SQL Server documentation).
6. Copy the MDF and LDF files to the SQL Server instance.
7. Attach the database to the SQL Server instance.
8. Bring the database online, then verify the location of the MDF and LDF files.
9. Restart the Plant Applications Server and SOA services.
10. After the database has been restored, verify that permissions are set up correctly in the Plant Applications database. From SQL Server Management Studio, run the following script to rebuild the SQL permissions:

    exec sp_Revokedbaccess 'ProficyDBO'Plant Applications
    go
    exec sp_Revokedbaccess 'ComXClient'
    go
    exec sp_Revokedbaccess 'ProficyConnect'
    go
    exec SpSupport_ChangeDBOAccount 'Proficydbo','ProficyDBO'

By default, Plant Applications uses port 12280, which is occasionally used by other software. This can cause communication conflicts causing the Plant Applications Server to disconnect from the Proficy Router.

1. On the Plant Applications Server, navigate to <drive>:\Program Files\Proficy\Proficy Server\Messaging. By default, this directory is on the C: drive.
2. Using a text editor, open each of the INI files.
3. Locate the following line: Protocol0_Item0 = 12280.
4. Change 12280 to an unused port number. You must use the same port number in each of the four files.
5. Save the file.
6. After you update all the files, restart the Plant Applications Server.

When installing the Plant Applications Server, if the SQL user information cannot be validated, the installation program generates an error message.

Database Install Fatal Error encountered: Invalid SQL Username and Password Install aborted. 

Plant Applications Server or Common Licensing installation fails upon encountering a pre-existing installation.

• Rename the single executable file to setup.exe, and run the installation again.
• Disable Terminal Services on the machine, and re-run the installation.
• Replace the compressed, single executable with a full DVD release.
• Run the installation from Add/Remove Programs rather than launching the installation directly. Create the Fonts folder in the location where the setup is checking under the current user at Documents and Settings\\Windows\Fonts.

The Plant Applications SQL Server can fail when running at the same time as an Online-Transaction Processing (OLTP) application and a reporting database.

1. In SQL Server Management Studio, right-click the server, then click Properties to display the Server Properties dialog box.
2. Under Select a page, click Advanced to display the Advanced page.
3. Under Parallelism, edit the Max Degree of Parallelism value. The default is 0 (zero), which uses the actual number of available processors.

   Option	Description
   Edit	Recommended value: half the number of processors on the server.
   1	Disables the option.

4. Click OK.

The Plant Applications Server License Manager service may not start due an incorrect database password stored in the registry.

1. Set the proficydbo password to the default password, proficydbo, in SQL Server.
2. Set the comxclient password to the default password, comxclient, in SQL Server.
3. Delete the encrypted passwords from the registry:
   • HKEY_LOCAL_MACHINE\SOFTWARE\Proficy\Plant Applications\Proficy Server\DBParam1
   • HKEY_LOCAL_MACHINE\SOFTWARE\Proficy\Plant Applications\Proficy Server\DBParam2
4. Start Proficy Server License Manager to initialize the registry to the default.
5. Reset the password using the Administrator.

If you are having difficulty viewing the web content tree or you are receiving errors when you try to view the tree in a web client, you may need to enable parent paths for the PAReporting virtual directory.

1. Open Internet Information Services (IIS) Manager and expand the server.
2. Right-click the PAReportingvirtual directory, then click Properties.
   The PAReporting dialog box appears.
3. On the Virtual Directory tab, click Configuration.
   The Application Configuration dialog box appears.
4. On the Options tab, select Enable parent paths.

   

5. Click OK twice to return to the Internet Information Services window.
6. Close the Internet Information Services window.

If the Plant Applications Web Reports are not working correctly, you may need to enable HTTP Keep-Alives.

1. In the Internet Information Services (IIS) Manager, locate the local computer.
2. Expand Web Sites, right-click the website, and then select Properties. The Properties dialog box for the web site is displayed.
3. On the Web Site tab, click Connections and ensure Enable HTTP Keep-Alives is selected.
4. Click OK.

When stopping the Proficy Server, the system can generate a 1067 error message indicating that the process terminated unexpectedly. This error can be ignored.

Proficy Server installation can fail when the scripts utility cannot log in with authentication for the previously installed version.

Script Execution- Login Failed

After installation, the system displays a failed to connect to database server message when starting the Plant Applications Administrator or client.

About This Task

Note: If the server appears in the list of Plant Applications Servers in the Plant Applications Administrator, double-click the server name to display the list of nodes.

1. Verify that the Proficy Licensing and Proficy Server License Manager services are running. If not, start the services. Restart the Plant Applications Administrator or Client to see if it connects to the database.
2. If you are still unable to connect to the database, register the following controls using the command line:
   • Regsvr32 ???C:\<Program Files location>\Common Files\Proficy\Plant Applications\PRMsgs.dll???
   • Regsvr32 ???C:\<Program Files location>\Common Files\Proficy\Plant Applications\ProfCDG.ocx???
   • Regsvr32 ???C:\<Program Files location>\Common Files\Proficy\Plant Applications\ProfSVR.dll???
   • Regsvr32 ???C:\<Program Files location>\Common Files\Proficy\Plant Applications\PRUtils.dll???

   Note: The Program Files location varies depending on whether the operating system is 32- or 64-bit. For a 64-bit operating system, the path is Program Files (x86). For a 32-bit operating system, the path is Program Files.

The License Manager depends on the ProficyConnect database user.

1. Stop the following services:
   • Proficy Server Manager
   • Proficy Server Router
   • Proficy License Manager
2. Connect to the SQL server as sa, under the main Security\Logins branch, then delete the ComXClient, ProficyConnect, and Proficydbo users.
3. Run the following command as a database query:
   exec spSupport_ChangeDBOAccount
4. Restart the Proficy License Manager and Proficy Server Manager services.

• Verify that all related services, including the licensing and Proficy Server services, are running.
• Stop and restart the services if necessary.

1. Verify whether the Historian is uninstalled.
2. Reinstall the Historian on the same node as Plant Applications.