Miscellaneous Installation Notes

Network Service Account #

One Windows Server 2003 and higher, ASP.NET apps run by default using the Network Service account. When Process Director needs to access applications like mail (e.g. \InetPub\mailroot\Pickup), the Network Service account needs to be given permission to those resources. The account can be changed in the Application Pool configuration.

Port 80 #

Process Director uses the HTTP port 80 for all client-to-server communications. If Process Director is behind a firewall, ensure your firewall is configured to allow incoming TCP requests to port 80 to Process Director. You may also use Network Address Translation (NAT) on Process Director connections, if desired. To configure Process Director to use another port, first configure the new port number in the Microsoft Internet Service Manager. Process Director must also be configured to communicate using this new port number. This is configured in the Interface URL field in the online Administration section. For example to use port 8000 for Process Director, configure the online Administration Interface URL field in the installation tab to a value such as this (where your.external-host.com is your valid Internet domain name or IP address):

http://your.external-host.com:8000/

WebDAV #

WebDAV isn't enabled by default in Process Director. For some functions, such as making Process Director compatible with Acrobat PDF annotations, WebDAV Authoring must be enabled in IIS. The WebDAV Redirector must be installed for Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012. (The WebDAV Redirector is already installed on Windows Vista, Windows 7, and higher.) To install the WebDAV Redirector, refer to Microsoft's WebDAV Installation documentation.

When using SQL Server Express 2008 and the SQL Server Management Studio you have to connect to the server name: servername\SQLEXPRESS.

For Process Director v6.1.0 and higher, BP Logix recommends that, if WebDAV is installed in IIS, to ensure it uses only the default installation settings, and to have it enabled. If WebDAV is installed in IIS but is not used, BP Logix recommends uninstalling the WebDAV module completely, to avoid conflicts with some UI features. If WebDAV is installed but disabled, it will cause a 405 Method Not Allowed on PUT HTTP Requests error. Disabling it and removing it from the Handler Mappings section won't be enough either. Thus, if the WebDAV module is not being used, it should be removed entirely, not disabled.

IIS and .NET #

During the product install, if a user installs .NET before installing IIS this will cause IIS not to use .NET. Commonly, this failure to register will result in a HTTP Error 500.19 – Internal Server Error page being displayed when trying to access a Process Director URL. Resolving the issue will require the use of the Microsoft ASP.NET IIS Registration Tool.

The HTTP Error 500.19 will also occur if "ASP.NET 4.5" isn't installed as a Server Role, in which case the registration command has no effect and won't resolve the issue. Ensure that the ASP.NET 4.5 Server Role is installed via the server manager prior to attempting the registration command. For Windows 2012 Server, this server role is disabled by default. See the Windows 2012 Server section of this document for instructions on how to configure the server roles properly.

The following Registration tool commands are the most commonly used to register .NET with IIS:

aspnet_regiis –u: Run in the v2.0.50727 folder if this is the current version of the Framework that you're running.

aspnet_regiis –i: Run in the v4.0.30319 folder if this is the current version of the Framework that you're running.

You can find more information on these commands from the registration tool link above.

You'll have to run the commands in the following dotnet folders:

ASP.NET v3.5: %windir%\Microsoft.NET\Framework\v2.0.50727

ASP.NET v4.5: %windir%\Microsoft.NET\Framework\v4.0.30319

Advanced Reporting and Windows 10 #

When running Windows 10 Professional, the Advanced Reporting Component doesn't run properly when the IIS Application Pool is running with the Identity is set as ApplicationPoolIdentity. For the Reporting Component to work, the IIS Application pool must be running under the Network Service identity. The Identity can be changed in the Advanced Settings for the Application Pool.

SQL Server Transparent Data Encryption (TDE) #

Process Director is compatible with TDE on SQL Server Enterprise editions of Microsoft SQL Server 2008 R2 and higher. For more information on TDE, please see Microsoft's TDE documentation in MSDN.