Configuring ProjectWise On A Windows 2003 Server [TN]


	Applies To

	Product(s):	ProjectWise
	Version(s):	All
	Environment:	N/A
	Area:	N/A
	Subarea:	N/A
	Original Author:	Bentley Technical Support Group

Bentley Orchestration Framework Setup

Things to know before installing:

MicroStation V8 2004 Edition or higher must be installed before installing the Orchestration Framework on a computer.
To ensure thumbnail creation for ProjectWise it is recommended that you install Microsoft Office on your Orchestration Framework server and test that the Operating System can create thumbnails of the desired files in question. If you can not create thumbnails in Windows Explorer for Office documents then be sure to enable the "Save Preview Picture" option, which can be found at File/Properties/Summary Tab.
Set up a Windows user account with administrative privileges and be sure to give this user to the "log on as a service" right.
Set up Microsoft Message Queuing on your Windows 2003 Server.
ProjectWise Application Server, Distribution System Server, and Automation Services all support the same Bentley Orchestration Framework. If any combination of these servers is to be installed on a computer, you only need to install Bentley Orchestration Framework once on that computer. If those servers are to be installed on their own computers, you will need to first install Bentley Orchestration Framework on each computer.
The Bentley Orchestration Framework installer checks your computer for the existence of certain prerequisite software. If the installer detects that a prerequisite is missing, it prompts you to either set up or install the prerequisite, whichever the case may be. Once all prerequisite software is installed, installation of Bentley Orchestration Framework begins.
Your Windows 2000/2003 computer already has a version of Microsoft Data Access Components (MDAC) installed as part of the operating system. When installing the Orchestration Framework, the installer checks to see if your operating system has MDAC 2.8; if the installer does not detect this version you are presented with the option to either install or not install the upgrade to MDAC 2.8. If you choose to install the upgrade, you will not be prompted to upgrade MDAC again on this computer if you happen to reinstall Bentley Orchestration Framework. If you choose not to upgrade to MDAC 2.8, you will not be able to continue with installation of the Orchestration Framework.
If the password changes for the user account used to install Bentley Orchestration Framework or SQL Server, the new password will have to be manually updated for each of these from the Services window. If MSDE is used instead of SQL Server as the database for Bentley Orchestration Framework, and if it was installed through the Bentley Orchestration Framework installer, you will not have to update the password for that, since MSDE's default user account ("sa") is not connected to the user account used to install Bentley Orchestration Framework.

Installing Orchestration Framework:

From the ProjectWise Server Setups, select Orchestration Framework and click Install. If Microsoft .NET Framework is not installed, a dialog box opens, prompting you to accept the license agreement for .NET Framework. You must accept this agreement to continue. Once accepted, .NET Framework begins installing. This piece of the installation may take a while.
When the .NET Framework installation is complete and the Bentley Orchestration Framework installer opens, click Next.
When the License Agreement page opens, click Yes.
If MDAC 2.8 is already installed, skip to step 6 or If MDAC 2.8 is not already installed, when the Setup Type page opens, select Upgrade to MDAC 2.8 and click Next. You can choose not to upgrade to MDAC 2.8, however, you will not be able to continue with Orchestration Framework installation. After you accept the MDAC license agreement, installation of MDAC 2.8 begins. This piece of the installation may take a while.
When MDAC 2.8 update is finished, restart your computer when prompted. When your computer restarts, continue with step 6.
If either Microsoft SQL Server or MSDE is already installed on this computer, skip to step 9.If neither Microsoft SQL Server nor MSDE is already installed on this computer, the Setup Type page opens, prompting you to select a data repository. This data repository is where you will create a database instance for the Orchestration Framework later in this procedure.
To install and use the MSDE delivered with Bentley Orchestration Framework, select Install MSDE and click Next, then continue with step 8 or to use a database (either SQL Server or MSDE) that is located on another computer, select Do not Install MSDE, click Next, then skip to step 9. If you choose to install MSDE, please be patient as this piece of the installation may take a while.
When MSDE installation is finished, restart your computer when prompted. When your computer restarts, continue with Step 9.
When the Choose Destination Location page opens, accept the default or click Browse to change the installation location, then click Next.
When the Setup Type page opens, select Typical and click Next.
When the Start Copying Files page opens, click Next. When the Orchestration Framework files have been installed, the Configure Shepherd Credentials dialog box opens. In this dialog box you are to specify the existing user account (Windows domain or local) that will have credentials to run the Orchestration Framework Shepherd. If the user you specify has a network account, in the Domain field, type the domain name that user is in. If the user has a local account, type the computer name in the Domain field.
Enter the appropriate information in the Domain, Username, Password, and Confirm Password fields and click OK. After you configure shepherd credentials, the Orchestration Framework Datasource page opens, informing you that you are about to identify a database to be used by the Orchestration Framework.
Click Next
If you did not install MSDE through this installer, skip to step 15 or If you installed MSDE through this installer, when the SA Password dialog box opens, create a password for MSDE's "sa" account, then click OK. The Orchestration Framework Database Setup dialog box opens. Using this dialog box you can either select an existing Orchestration Framework database instance, or you can create a new one. You use an existing database instance if you know that MSDE or SQL Server contains an empty database instance not yet dedicated to any other purpose, or if MSDE or SQL Server contains a database instance already in use by the Orchestration Framework. You create a new database instance if you know that MSDE or SQL Server does not yet contain an Orchestration Framework database instance.
In the Server text field, type name of the computer on which MSDE or SQL Server resides.
Below the Server text field, select the option for logging in to the database server. If you select 'Use Windows NT integrated security', you will automatically be logged in using your current Windows NT username and password. If you have an account in the database that is not based on a Windows NT username and password, then select 'Use a specific name and password' and type the appropriate user name and password in the fields below the option.
To create a new database instance in MSDE or SQL Server, click New, type a name for the new database in the Create Database dialog box, then click OK or to use an existing database instance in MSDE or SQL Server, select one from the Database dropdown list box. If you created a new database instance, or selected an existing instance that used a previous version of the Orchestration Framework database schema, the Database Status field reads "The selected database is not currently configured for the Orchestration Framework. Continuing will install version 1.4 of the Orchestration Framework database schema." If you selected an existing instance that uses the current version of the Orchestration Framework database schema, the Database Status field reads "The selected database is configured to support the Orchestration Framework schema required by this install."
When finished, click OK in the Orchestration Framework Database Setup dialog box. At this point the Bentley Orchestration Framework installation completes. If this is the first time you are installing MDAC, MSDE, and/or .NET Framework on this computer, and if you have not done so yet, the installer may prompt you to restart your computer.
Select to restart the computer now if that option is available, and then click Finish. When the computer restarts, proceed with the next piece of your installation ProjectWise Application Server, Distribution System Server or Automation Services.

Troubleshooting Tips:
Problem: Dbsetup fails to start when installing Orchestration FrameWork - Exception has been thrown by the target of an invocation. Error setup failed could not load dbsetup.

Solution: There was a previous version of Orchestration framework installed on the computer. Either it was not uninstalled properly or the uninstaller did not remove the entries in the windows\assembly directory. Go to the Windows\assembly directory and remove the old version of the .bentley.orchestration and the policy.bentley.orchestration then reinstall the Orchestration Framework.

ProjectWise Application Server Setup

Things to know before installing:

Create an empty database instance in your database (SQL Server, Oracle, or Sybase), then create an ODBC datasource that points to your new empty database instance.
Install MicroStation V8 2004 Edition and Bentley Orchestration Framework.

Installing ProjectWise Application Server

From the ProjectWise Server Setups, select ProjectWise Application Server and click Install.
When the installer opens, click Next.
When the License Agreement page opens, accept the agreement and click Next. The Custom Setup page opens, showing you the server features that will be installed, and the default installation location. If ProjectWise Application Server is the first ProjectWise 2004 Edition module (not including Bentley Orchestration Framework) that you are installing on this computer, the default installation location is "C:\Program Files\Bentley\ProjectWise\", which you can either accept or click Change to change. If another ProjectWise 2004 Edition module is already installed on this computer, you cannot change the installation location (the Change button will not display).
(Optional) - To change whether or not a feature gets installed, click the feature's icon and select the appropriate option from the menu. Items with an X to the left of them will not be installed.
Accept the default installation location, or if necessary click the Change button (if available) to change it, then click Next.
When the Ready to Install the Program page opens, click Install.
If you selected to install the Adobe PDF IFilter, when prompted, step through the IFilter's own setup program to completion.
When ProjectWise Application Server installation is complete, click Finish.

Installing ProjectWise Administrator:

From the ProjectWise Admin Setups, select ProjectWise Administrator and click Install.
When the installer opens, click Next.
When the License Agreement page opens, accept the agreement and click Next.
When the Setup Type page opens, select Custom and click Next. The Custom Setup page opens, showing you the administrative features that will be installed.
(Optional) - To change whether or not a feature gets installed, click the feature's icon and select the appropriate option from the menu. Items with an X to the left of them will not be installed.
Accept the default installation location, or if necessary click the Change button (if available) to change it, then click Next.
When the Ready to Install the Program page opens, click Install.
When installation is complete, click Finish.

Troubleshooting Tips:
Problem:

Orchestration Frame work is installed but the ProjectWise Application Server failed with Error 1722 when trying to install ProjectWise App Server on Windows 2003 Server.
User getting error 1920 - PWAppSrv failed to start when installing Project Application Server on Windows 2003 machine.

Solution:

Be sure to uninstall everything, and run the windows installer cleanup utility. You may want to change the user account for the Orchestration Frame work to the local system account. If that does not resolve the issue create a Shepherd.xml file in the Program Files\Bentley\Orchestration Framework directory, with one line that reads <processes></processes>. Stop and restart the Orchestration Framework then run the install for ProjectWise Application Server.
Verify that you do not have the Virtual Network Connection Service started. If so, stop the service and install ProjectWise Application Server.

ProjectWise Web Server Setup

Things to know before installing:

ProjectWise Web Server can be, but does not need to be, installed on the same computer as Bentley Publisher or ProjectWise Application Server.
Before installing ProjectWise Web Server, you must install Sun Micro System's Java 2 Runtime Environment, Standard Edition (JRE), version 1.4.1_01. The JRE is available from the ProjectWise Server Setups.
Configure Windows 2003 Server to run IIS by adding a new role to the server using the Manage Your Server utility and select Application Server. It is recommended that you do not install FrontPage Server extensions. Failure to do so may result in publishing permission problems within IIS.
Use Windows Update to download and install ALL security patches for Windows 2003.
Verify that IIS is properly configured by opening a browser to http://servername/. On a newly installed machine you should see an "Under Construction" page.
If you create a directory for a Logical Path(s) in the Bentley Publisher Administrator, the owner is the only one with access. If you want other users to have read and write access, you must specifically set this in the Security tab. To set the permissions for a directory right-click the directory from Windows Explorer. Select Properties, and then click the Security tab. Add the user(s) needing access to the directory.
Allow Active Server Pages, All Unknown ISAPI Extensions and All Unknown CGI Extensions in Web Service Extensions.
In IIS right click on Default Website and go to Properties. Select Home Directory/Configuration/Options and enable parent paths.
To publish files from Web Explorer Lite with Bentley Publisher configured as an ISAPI extension, you must set the following registry entry. From the Registry, introduce a DWORD value (UrlSegmentMaxLength) under KEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters Set the value for UrlSegmentMaxLength to 0.

Installing Bentley Publisher:

Run setup.exe for Bentley Publisher and accept the default configuration or change its installation path. Be sure not to install it in a path that contains spaces.
Select the Bentley Publisher Administrator
From the options on the left of the Administration window, click General Settings.
In the Server Mode section, select Run as a Web Server Extension.
Scroll to the bottom of the page and click SUBMIT.
From the options on the left of the Administration window, click Server Control.
If not already set, turn on automatically configure Microsoft IIS when pressing START or RESTART.
Click START.
In Windows Explorer go to "..BentleyPublisher\Tools and run the msxml.msi.
Accept all of the defaults settings until installation complete.

Installing ProjectWise Web Server:

From the ProjectWise Server Setups, select ProjectWise Web Server and click Install.
When the installer opens, click Next.
When the License Agreement page opens, accept the agreement and click Next.
When the Setup Type page opens, select Custom and click Next. The Custom Setup page opens, showing you the ProjectWise Web Server features that will be installed. If ProjectWise Web Server is the first ProjectWise 2004 Edition module you are installing on this computer, the default installation location is "C:\Program Files\Bentley\ProjectWise\", which you can either accept or click Change to change. If another ProjectWise 2004 Edition module is already installed on this computer, you cannot change the installation location (the Change button will not display).
(Optional) - To change whether or not an item gets installed, click the feature's icon and select the appropriate option from the menu. Items with an X to the left of them will not be installed.
Accept the default installation location, or if necessary click the Change button (if available) to change it, then click Next. If you have selected to install the Document Publisher, you are prompted to specify a temporary storage area for Document Publisher files. Make sure you have plenty of disk space set aside for this temporary storage area, as all the files that Web Explorer Lite users view will get copied here.
Accept the default location of "C:\PW-WebSrv-WorkDir\" and click Next, or click Select, specify a different location and click OK, then click Next.
When the Ready to Install the Program page opens, click Install.
When installation is complete, click Finish.
Then restart the computer.
After installing ProjectWise Web Server (8.5.1.xx or higher)go to the "...\WebServer\Bin" folder and double-click the "setupISAPIwin2k3.exe" file.
Click Install; when installation is complete, click Finish.
In Windows Explorer, right-click My Computer and choose Properties.
On the Advanced tab, click Environment Variables.
In System Variables list box, select the variable called PATH and click Edit.
At the end of the Variable Value field, add a semicolon and then add the path to the "...ProjectWise\Bin" directory. For example: ;C:\Program Files\Bentley\ProjectWise\Bin.
If you have installed Document Publisher, you also need to add a semicolon and then the path to "...ProjectWise\WebServer\docpub" to the end of the Variable Value field. For example: ;C:\Program Files\Bentley\ProjectWise\WebServer\docpub
Click OK to close the Edit System Variable dialog box.
Click OK to close the Environment Variables dialog box.
Click OK to close the System Properties dialog box.
In Windows Explorer, navigate to "C:\Program Files\Bentley\ProjectWise\WebServer\common\classes".
Open the file "PWLiteServlet.properties" in a text editor. Scroll down to the Viewing and Publishing Configuration section.
In this section you will find a default list of applications.
If you have installed Bentley Publisher, change BentleyPublisher.installed=false to BentleyPublisher.installed=true. Repeat this step for other applications you have installed.
Edit the line bp.url=http// to read bp.url=http//<YourServerName>, for example, bp.url=http//ggg1579.
If you have set up Bentley Publisher to 'Run as Web Server Extension', you can leave the line # bp.port= commented out or if you have configured Bentley Publisher to use a web server port other than port 80, uncomment the line # bp.port= and set the appropriate port value.
Save and close the "PWLiteServlet.properties" file.
In Windows Explorer, navigate to "C:\ProgramFiles\Bentley\ProjectWise\WebServer\common\classes".
29. Open the file "global.viewers.properties" in a text editor. Edit file for desired viewer for specific file type.
Reboot the server so that the system path is picked up by the Services.

Installing ProjectWise Publishing Gateway

From the ProjectWise Server Setups, select ProjectWise Publishing Gateway and click Install.
When the installer opens, click Next.
When the License Agreement page opens, accept the agreement and click Next.
When the Ready to Install the Program page opens, click Install. The installer automatically stops the Bentley Publisher service during installation.
When installation is complete, click Finish.

Troubleshooting Tips

Problem:

Publishing Gateway will not install?
Bentley Publisher Imaging Engine will not start on port 8080?

Solution:

If the Bentley Publisher service is not running, the ProjectWise Publishing Gateway installation will not complete and the PubConfig.xml configuration file might be damaged. You would then have to re-instate the backup PubConfig.xml before continuing with this installation.
Oracle's HTTP Service causes conflicts on port 8080. Either set this service to manual or change the Bentley Publisher Imaging Engine port in the Bentley Publisher Administrator.

ProjectWise Distribution and Automation Server Setup

When creating folder shares for the Automation Server, Distribution Server, or Digital InterPlot it is highly recommended that you use the Manage Your Server utility and select File Server. Use the share a folder wizard until you have finished sharing all of your folders. Failure to do so may result in write permission problems with shared folders.
When installing the ProjectWise Graphical Difference Utility you must also edit the PWLiteServlet.properties with the name of the virtual directory that you have created. For example di.url=http://Webserver/pwdiff.
For either the Distribution Server or the Automation Server set up a Windows user account with administrative privileges and give it "log on as a service" rights. It is easier to use the same account as the Orchestration Framework.
Set up Microsoft Message Queuing (MSMQ)
Set up a printer and a Digital InterPlot archive specifically for the use of the Distribution System.
The following software must be loaded on the Automation Server: MicroStation V8 2004 Edition, Bentley Orchestration Framework, Bentley Schematics 2004 Edition, PlantSpace P&ID, Bentley Triforma, PlantSpace Design Series, Microsoft Message Queuing, ProjectWise Administrator, and the ProjectWise Class Editor.
To redline using Digital InterPlot you must select Execute on the VDA that you create for Archive Explorer.

For Plotting with Digital InterPlot

Before you install Digital InterPlot, you must edit the Group Policy to accept older (kernel) printer drivers. (During installation, Digital InterPlot creates the "Digital InterPlot" printer using the "InterPlot Organizer Printer Driver." The creation of this printer will fail if the Group Policy is not changed.)
To edit the Group Policy to accept older kernel printer drivers. From a command prompt, type: gpedit.msc. Select "Computer Configuration - Administrative Templates - Printers - Disallow installation of printers using kernel-mode drivers" Double click "Disallow installation of printers using kernel-mode drivers." Select "Disabled," and then click OK.
The "File Pooling" feature must be turned off before you can print from the plotting interfaces. To turn off "File Pooling" From a command prompt, type: regedit. Locate the registry key "HKEY_LOCAL_MACHINE \System \CurrentControlSet \Control \Print." Select Edit -> New -> DWORD Value. Set Value Name to "DisableServerFilePooling". Set Data to "1".

For Archiving with Digital InterPlot

Prior to creating Digital InterPlot archives, make sure that the web page and file storage folders have the proper security permissions set for the user accounts used for creating an archive. When using Windows Server 2003 on a Digital InterPlot Web Server, the following properties must be set. To set "Active Server Pages" to "Allowed" Invoke Internet Information Services (IIS) Manager. Click the Plus Sign (+) next to the local computer to expand it's options. Select "Web Server Extensions." On the right frame, select "Active Server Pages." Set "Active Server Pages" to "Allowed."
To "Enable parent paths" Invoke Internet Information Services (IIS) Manager. Click the Plus Sign (+) next to the local computer to expand to Web Sites - Default Web Site. Click the Plus Sign (+) to expand "Default Web Site." Right-click on the web site created for Digital InterPlot, and then click "Properties." On the "Virtual Directory" tab, click the "Configuration" button. On the "Options" tab, check "Enable parent paths." Click OK.
To allow "anonymous access" Invoke Internet Information Services (IIS) Manager. Click the Plus Sign (+) next to the local computer to expand to Web Sites - Default Web Site. Click the Plus Sign (+) to expand "Default Web Site." Right-click on the web site created for Digital InterPlot, and then click "Properties." On the "Directory Security" tab, click the "Edit" button next to "Authentication and access control." Check "Enable anonymous access," and then specify the user name and password for the account that has access to the web store created for Digital InterPlot archiving. Click OK.
To view InterPlot Organizer Plot Set (IPS) links from Digital InterPlot web pages Invoke Internet Information Services (IIS) Manager. Click the Plus Sign (+) next to the local computer to expand to Web Sites - Default Web Site. Click the Plus Sign (+) to expand "Default Web Site." Right-click on the file storage Virtual Directory Alias created for Digital InterPlot, and then click "Properties." On the "HTTP Headers" tab, click the "MIME types" button. Click New. Type .ips for the Extension and "InterPlot Organizer Document" for the MIME type, and then click OK. Click New. Type .dpr for the Extension and "image/Digital Print Room Rendition" for the MIME type, and then click OK. Click OK to dismiss the MIME Types dialog, and then click OK to dismiss the Properties dialog. Stop and start IIS.

Installing Digital InterPlot

Create the Virtual Directory Alias (VDA) for the web page directory and any file storage directories. For example DIWeb and DIFiles. These VDAs need to point to locations on the local hard drive and these folder must be shared using the Manage Your Server Utility.
When creating your VDAs make sure Read and Run scripts are selected, select Next. If you will be using redlining, you will need to select Execute.
Install the Digital InterPlot Software.
Modify the licbroker.lic file in Program Files\Common Files\Bentley Shared\LicenseBroker to point to the SELECTserver containing the Digital InterPlot license. Replace INSERT_SELECT_SERVER_NAME_HERE with the name of the SELECTserver.
Go to Start\Run and type dcomcnfg. Dcomcnfg is a Microsoft delivered utility which enables administrators to configure DCOM security on the computer for all applications which do not set security. Running the dcomcnfg utility is necessary for Archive Explorer to perform operations like viewing remote Enterprise archives, searching for remote plot sets and sheets, and populating an Enterprise archive from remote machines. To run the dcomcnfg utility, select Start > Run and key in dcomcnfg. The Distributed COM Configuration Properties dialog will display. Select DPRArchServ and select Properties.
The DPRArchServ Properties dialog will display. Select the Security tab.
Select Use custom access permissions and select Edit. Add Everyone Allow Access. Select OK.
Select Use custom launch permissions and select Edit. Add Everyone Allow Launch. Select OK.
Select Use custom configuration permissions and select Edit. Add Everyone. Select OK.
Select the Identity tab. Enter the Orchestration Framework user created earlier that has access to the file storage directories. Select This user and enter the appropriate username/password. DCOMCNFG does not validate the user and password information. It is important that you type the user and password correctly. The user account must also have read/write access to each file storage directory. Entering a domain user which is also a local user may cause conflicts when launching DPRArchServ. For best results, make sure the domain account you enter is unique.
Select InterPlot Organizer Document and select Properties.
Select the Identity tab and set this to the launching user. Click OK.
Create a System DSN for the database using ODBC.
Start ODBC Data Source Administrator. On Windows 2000, select Start > Settings > Control Panel. Select Administrative Tools. Select Data Sources (ODBC). The ODBC Data Source Administrator dialog will display. Select the System DSN tab.
Select Add to create a DSN. The Create New Data Source dialog will display.
Use the Microsoft driver for your database.
Once System DSN is created Select Test Data Source to test the connection.
Select OK to continue.
Make sure that the user account that you gave to the Orchestration Framework and DPRArchServ is granted user rights to "Log on as service".
Create the archive using Archive Explorer.
Select Start > Programs > InterPlot Utilities > Archive Explorer. The Archive Explorer dialog will display.
Select My Computer. Select Tools > Create Archive. The Create Archive Wizard will display. Select Enterprise.
Enter the name of the archive to be created and a description. Do not user special characters in the name. Select Next.
Enter the name of the web server, the VDA created for the web page directory and the UNC share name. For example file://machinename/DIWeb. Select Next.
Use the Select button to browse to the System DSN. Click Next.
The File Storage Setup dialog will display. Select Add to specify the file storage directory.
Enter the path to the file storage directory, the VDA for the file storage directory, and the Orchestration Framework username/password that has read/write access to the file storage directory. For examplefile://machinename/DIFiles.
Next, the File Formats dialog will display. Select the appropriate options.
Next, the Optional Formats dialog will display. This dialog will allow any additional formats to be stored with the archive. Optional formats can be added to the archive definition at a later time if desired. Optional formats are not required to populate and view an archive.
The Plot Set Attributes dialog will display. Set the desired plot set attributes for the archive.
The Sheet Attributes dialog will display. Set the desired sheet attributes for the archive.
The View Hierarchy dialog will display.
The Review dialog will display.
Select Finish to complete the archive creation. The new archive will display in Archive Explorer.

Installing ProjectWise Graphical Difference Utility

Go to the \Program Files\Digital InterPlot\pwdiffwu folder and run Setup.exe.
Install the ProjectWise Graphical Differencing Utility on a location with the Digital InterPlot Server.
Follow the prompts and give the VDA a name, for example designcompare.
Then Click Finish.
Open the PWLiteServlet.Properties file on the ProjectWise Web Server and edit the following lines Digital InterPlot=false to true and di.url=http://server/virtualdirectory to di.url=http://servernamehere/designcompare.
Save the changes and restart the ProjectWise Web Server.

Installing ProjectWise Distribution Server

Install Bentley Orchestration Framework
From the ProjectWise Server Setups, select ProjectWise Distribution System Server and click Install.
When the installer opens, click Next.
When the License Agreement page opens, click Yes.
When the Setup Type page opens, select Typical and click Next.
When the Start Copying Files page opens, click Next. The Distribution System Datasource page opens, providing status about the datasource that is about to be configured.
The installer automatically finds the Orchestration Framework database instance you created during the Orchestration Framework installation, so all you have to do here is click Next. The Distribution System Datasource Configuration page opens. This page requires you to select a Distribution System file share, which will serve as the working directory for Distribution System jobs. If you have not created and shared a folder yet, do so now before continuing.
If you know the name of the computer on which the shared working directory is located, you can type the location (file://computername/fileshare) or you can click the Browse button to locate and select the Distribution System working directory. When finished, click Next. The Distribution System Datasource Configuration page opens.
In the Archive Groups text field, type a name for the Digital InterPlot archive group that will be used for generating renditions.
In the Printer text field, type the name of the Digital InterPlot printer you intend to use, using the following format: file://DI_computername/DI_printername
In the Archive Name text field, type the name of a valid Digital InterPlot archive.
Click Add, then click Next or Click Add, repeat the steps to define additional archive groups, then click Next. The Distribution System Configuration Type page opens with two options, Standard and Custom. The Standard option installs all of the Distribution System Server processors and dispatchers; the Custom option is used when you only want to install specific processors and/or dispatchers. If you are setting up the Distribution System for the first time, the Standard option is recommended.
Select the Standard option and click Next.
When the Distribution System DMS Connectors page opens, select connectors that you expect to use and click Next to begin configuration of the Distribution System.
When the word "Done" appears over the progress bar on the Distribution System Configuration In Progress page, click Close.
Back on the main Distribution System Server Components installer, click Finish.

Installing ProjectWise Distribution Server Plugin for Digital InterPlot

This must be installed on the computer when Digital InterPlot Archives can be found. From the ProjectWise Server Setups, select ProjectWise Distribution System Plugin for Digital InterPlot and click Install.
When the installer opens, click Next.
When the License Agreement page opens, click Yes.
When the Start Copying Files page opens, click Next to install the plug-in. When the files have been installed, the Select Archives page opens.
From the Available Archives list box, select the Digital InterPlot archive to configure and click the Add (→) button. Repeat this step for all of the available archives you want to configure.
Click Next.
When installation is complete, click Finish.

Installing ProjectWise Distribution Admin

Before installing Distribution System Administrator, make sure ProjectWise Explorer is already installed on this computer.
From the ProjectWise Admin Setups, select ProjectWise Distribution System Administrator and click Install.
When the installer opens, click Next.
When the License Agreement page opens, click Yes.
When the Setup Type page opens, select Typical and click Next.
When the Start Copying Files page opens, click Next to begin installation.
When installation is complete, click Finish.

Installing ProjectWise Automation Server

Install Bentley Orchestration Framework
From the ProjectWise Server Setups, select ProjectWise Automation Services and click Install.
When the installer opens, click Next.
When the License Agreement page opens, click Yes.
When the Setup Type page opens, select Typical and click Next.
When the Start Copying Files page opens, click Next. The Automation Services Datasource page opens, providing status about the datasource that is about to be configured.
The installer automatically finds the Orchestration Framework database instance you created during the Orchestration Framework installation, so all you have to do here is click Next. The Automation Services Datasource Configuration page opens, prompting you to select a Automation Services working directory (file share), which will serve as the working directory for component indexing jobs. If you have not created and shared a folder yet, do so now before continuing.
If you know the name of the computer on which the shared working directory is located, you can type the location (file://computername/fileshare) or you can click the Browse button to locate and select the Automation Services working directory. When finished, click Next.
Select the extension(s) you plan to use and click Next. If you are setting up Automation Services for the first time, the Standard option is recommended.
Select the Standard option and click Next.
When the word "Done" appears over the progress bar on the Automation Services Configuration In Progress page, click Close.
Back in the main Automation Services installer, click Finish.

Installing ProjectWise Automation Admin

Before installing Automation Services Administrator, make sure ProjectWise Administrator is already installed on this computer.
From the ProjectWise Admin Setups, select ProjectWise Automation Services Administrator and click Install.
When the installer opens, click Next.
When the License Agreement page opens, click Yes.
When the Setup Type page opens, select Typical and click Next.
When the Start Copying Files page opens, click Next to begin installation.
When installation is complete, click Finish.

Troubleshooting Tips

Problem:

When submitting a Distribution job to an archive on Digital InterPlot I receive a error create plot, access denied.
Can the working directory (share) for Distribution Server and for Automation Server be the same physical directory (share)?
Failed Rendition Generation has timed out -Problems with Distribution Server. User is trying to generate only .PDF with ProjectWise Distribution Server.

Solution:

Be sure to that you use DCOMCNFG on the Digital InterPlot machine and set the Orchestration Framework user or a domain account in the DPRArchServ Identity tab and set the InterPlot Organizer Document to the launching user. Then be sure that this user account is used in the file storage area of the Archive in question.
While Distribution Server will allow you to use the same working directory as Automation Services, it is recommended that they remain separate locations.
If the Digital Archive is a new archive you created, you need to re-install Distribution System Plugin for Digital InterPlot.

ProjectWise File Transfer Server Setup

Things to know before installing: The ProjectWise File Transfer Server can NOT be installed on computers on which ProjectWise Application Server or ProjectWise Connection Server is already installed.

Installing ProjectWise File Transfer Server:

From the ProjectWise Server Setups, select ProjectWise File Transfer Server and click Install.
When the installer opens, click Next.
When the License Agreement page opens, accept the agreement and click Next. The Custom Setup page opens. If ProjectWise File Transfer Server is the first ProjectWise 2004 Edition module you are installing on this computer, the default installation location is "C:\Program Files\Bentley\ProjectWise\", which you can either accept or click Change to change. If another ProjectWise 2004 Edition module is already installed on this computer, you cannot change the installation location (the Change button will not display).
Accept the default installation location, or if necessary click the Change button (if available) to change it, then click Next.
When the Ready to Install the Program page opens, click Install.
When installation is complete, click Finish.

Troubleshooting Tips

Problem:

Trying to run a new installation of File Transfer Server (FTS, DFS) error 1075. Dependency is not installed (started) or is marked for deletion.
Unable to create storage area with ProjectWise Administrator. Storage Area is located on a remote server which is running File Transfer Server. Error number is 58060.
Caching is working only for clients on the same subnet as the application server. All other clients can work in ProjectWise without problems, but are not using their designated cache locations on other File Transfer Servers.

Solution:

Upon closer inspection you should see that the license broker service (LicBroker) is not installed. Uninstall FTS and re-install.
Check that the service is running and started successfully with Event Viewer. Although the services dialog will state the service is started, the event viewer will say whether it has successfully started or not.
Add the Server providing the [Gateway] information to the ProjectWise Network Configuration Utility under DNS Services.

ProjectWise Connection Server Setup

Things to know before installing: The ProjectWise Connection Server can NOT be installed on computers on which ProjectWise Application Server or ProjectWise File Transfer Server is already installed.

Installing ProjectWise Connection Server:

From the ProjectWise Server Setups, select ProjectWise Connection Server and click Install.
When the installer opens, click Next.
When the License Agreement page opens, accept the agreement and click Next. The Custom Setup page opens. If ProjectWise Connection Server is the first ProjectWise 2004 Edition module you are installing on this computer, the default installation location is "C:\Program Files\Bentley\ProjectWise\", which you can either accept or click Change to change. If another ProjectWise 2004 Edition module is already installed on this computer, you cannot change the installation location (the Change button will not display).
Accept the default installation location, or if necessary click the Change button (if available) to change it, then click Next.
When the Ready to Install the Program page opens, click Install.
When installation is complete, click the Finish button.

Troubleshooting Tips

Problem: Trying to configure a DMZ Connection Sever so that the only computer to talk to the connection server is the application server sitting internal with multiple storage locations in different subnets.

Solution: Edit the Dmskrnl.cfg for the application server and set the following: [Routing] IP address of storage computer = 5800. If an IP address is not found then you will need to add a [NameResolution] Storage Computer Name=IP address of Storage Computer. Then set the Dmskrnl.cfg for the Connection server to [NameResolution] Storage Computer Name=IP address of Storage Computer and [Gateway] Storage Computer IP address = Application server IP address.

ProjectWise Authentication Server Setup

Things to know before installing:

Authentication Server can be, but does not need to be, installed on the same computer as ProjectWise Application Server.
ProjectWise Authentication Server Administrator and ProjectWise Authentication Server Engine are automatically installed when you install ProjectWise Authentication Server.
Make sure ProjectWise Administrator is already installed on this computer

Installing ProjectWise Authentication Server:

From the ProjectWise Server Setups, select ProjectWise Authentication Server and click Install.
When the installer opens, click Next.
When the License Agreement page opens, accept the agreement and click Next. The Custom Setup page opens, listing the features of the Authentication Server you can install, and the location to which they will be installed.
Select the items to be installed, then click Next. The Service Options page opens.
Type a valid Windows NT/2000 Domain name, Account Name and Password. This account must have appropriate rights to connect to the Domain that you plan to synchronize with the ProjectWise datasources.
When the Ready to Install the Program page opens, click Install.
When installation is complete, click the Finish button.

Troubleshooting Tips

Problem:

Authentication Server -Error 1058: "The service cannot be started because either it is disabled or it has no enabled device associated to it."
Reinstalled authentication server, getting error "synchronization has failed for the data source. Error code 2, cannot find the file specified." when launching Authentication Server.

Solution:

This behavior can occur if the service is disabled or if the service is disabled for the hardware profile that you are currently using. Click Start > Programs > Administrative Tools > Services. Double-click the service that did not start. Click the Log On tab. Verify that the service has not been disabled for the hardware profile that you are using. If it has, click Enable. Click the General tab. Verify that the service has not been disabled in the Startup Type box. If it has, click Automatic to have it start when you start the computer.
Add admin password to the 'Server' tab in the properties under Windows Security System > Authentication Server.

ProjectWise Indexing Server Setup

Things to know before installing:

ProjectWise Index Server cannot be installed on a computer on which ProjectWise Application Server is already installed.
Microsoft .NET Framework must be installed.
Microsoft Indexing Service must be enabled.
MDAC, which gets installed automatically by the ProjectWise Index Server installer, if the required version is not already installed.

Installing ProjectWise Indexing Server

From the ProjectWise Server Setups, select ProjectWise Index Server and click Install.
When the installer opens, click Next.
When the License Agreement page opens, accept the agreement and click Next. The Custom Setup page opens, showing you the server features that will be installed. If ProjectWise Index Server is the first ProjectWise 2004 Edition module that you are installing on this computer, the default installation location is "C:\Program Files\Bentley\ProjectWise\", which you can either accept or click Change to change. If another ProjectWise 2004 Edition module is already installed on this computer, you cannot change the installation location (the Change button will not display).
Accept the default installation location, or if necessary click the Change button (if available) to change it, then click Next.
When the Ready to Install the Program page opens, click Install.
When installation is complete, click Finish. After installation, you need to register this index server in ProjectWise Administrator.

Troubleshooting Tips:

Problem: "The Bentley ProjectWise Index Server 2004 Edition service on Local Computer started and then stopped. Some Services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service."

Solution: Missing JRUN and the service would stop from time to time.

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!