ProjectWise Administrator Help

Before You Install or Upgrade ProjectWise Design Integration Server

  1. See the ProjectWise readme for a list of supported operating systems and other system requirements.
  2. If a previous version of ProjectWise Design Integration Server and ProjectWise Orchestration Framework Service is installed, uninstall them now (uninstall Integration Server first, then uninstall Orchestration Framework Service).
  3. ProjectWise Design Integration Server cannot be installed on a computer on which either ProjectWise Caching Server or ProjectWise Gateway Service is already installed.
  4. Make sure the computer you are installing on is on the domain.
  5. Make sure the latest Windows updates have been installed.
    In particular, make sure you have the update for Universal C Runtime (CRT) in Windows installed:


  6. Make sure that the computers on which you install ProjectWise Design Integration Server and all ProjectWise Caching Servers have their clocks synchronized with the time of an authoritative computer. If the clocks are not properly synchronized, then any tokens issued by ProjectWise Design Integration Server may expire prematurely when a user attempts to check out a document, causing the operation to fail. See the following Microsoft article for details:

  7. Installing the automated file processing features of the ProjectWise Design Integration Server (full text indexing, thumbnail image and file property extractors) automatically installs ProjectWise Orchestration Framework Service which has its own requirements, therefore if you plan to implement these features, the following must be done before you install:
    1. Part of the ProjectWise Orchestration Framework Service installation involves connecting to a SQL Server database to use, therefore, on this or another computer, install Microsoft SQL Server or SQL Server Express.

      (For convenience, ProjectWise delivers Microsoft SQL Server 2016 Express SP2, which you can select to install from the ProjectWise Server installer when you are installing ProjectWise Design Integration Server.)

    2. If you plan to connect to the Orchestration Framework database using an ODBC connection, then you must first create an empty database in SQL Server to be used as the Orchestration Framework database, and then create a 64-bit ODBC data source on this computer that connects to the empty database in SQL Server.

      If you plan to use a direct database connection, you can skip this step and let the Orchestration Framework Database Setup dialog (opens during Integration Server / Orchestration Framework installation) create the Orchestration Framework database in SQL Server for you.

    3. Set up the user account under which ProjectWise Orchestration Framework Service will run. You will enter the credentials of this account on the Orchestration Framework Configuration page of the ProjectWise Server installer.

      This account:

      • can either be a local account or a Windows account
      • is recommended to have a password that is set to never expire
      • must be a member of the Administrators group on this computer (Control Panel > Administrative Tools > Computer Management > System Tools > Local Users and Groups > Groups)
      • must have the Log on as a service right on this computer (Control Panel > Administrative Tools > Local Security Policy > Security Settings > Local Policies > User Rights Assignments)
      • must also already exist in SQL Server (under Security > Logins)
      Tip: ProjectWise Orchestration Framework Service will stop running if and when this user account's password expires. Because Windows accounts typically have passwords that periodically expire, one solution is to use a local account with a non-expiring password. Another solution is to use a Windows domain account and set its password to never expire, or simply manually reset the password for ProjectWise Orchestration Framework Service in the Services window, ideally before the password expires.
    4. Make sure the user account you use to launch the ProjectWise Server installer is a Windows account that is a member of the local Administrators group.
    5. Make sure these Windows features are installed and running:
      • .NET Framework 4.6
      • .NET Framework 3.5
      • Message Queuing
      • Windows Search (if using Windows Search with full text indexing)

      Make sure the Message Queuing and Windows Search services are running in the Services window.

    6. If you plan to perform text extractions on this computer, you can either use the default index storage location as set by the ProjectWise Design Integration Server installer, or you can preset the index storage location before installing ProjectWise Design Integration Server (see Presetting the Full Text Index Storage Location).
    7. Install the software required (if any) for the file types you plan to process:
      • Full text indexing

        Depending on the file types you want to index text from, you may need to install additional software on the ProjectWise Design Integration Server computer where the extraction is being performed. The additional software required is an iFilter for the required file type, but in some cases you may have to install the full application to get the required iFilter. The following table lists some of the common file types that you will need to install additional software for:

        To index text from Install
        DGN and DWG documents Any supported version of MicroStation CONNECT Edition or V8i
        PDF documents Adobe PDF iFilter (9.0 or 11.0, 64-bit)
        MSG (Microsoft Outlook message) documents MSG iFilter (64-bit)
        Note: Currently, ProjectWise cannot index text from a DGN document that is attached to an MSG document.
      • Thumbnail image extractions:

        No additional software is required to extract thumbnail images from V8 DGN, AutoCAD DWG (AutoCAD 2010 and later formats), and Revit documents.

        Note: Thumbnails cannot be generated from pre-V8 DGN documents.
      • File property extractions:
        Note: The MSG iFilter is no longer required to extract file properties from MSG documents.
        Note: Due to an AutoCAD limitation, you cannot extract file properties from DWG documents.