PSIsafe Troubleshooting: Network Environment: Legacy CRS / OpenAPI configuration in open and closed network environments

Advanced / Custom CRS / OpenAPI configuration in a closed network environment

For specific errors, see “Error Messages” below

This solution relays some specific details about PSIsafe's legacy CRS, renamed OpenAPI, that must be acknowledged when working in a closed network environment.

Sometimes, client-side developers may which to execute custom HTML or other calls to our OpenAPI and PSIsafe 64 bit server. These calls will fail if the database is not registered to match the current server environment.

Your first steps are to ensure that the most recent OpenAPI version is installed. Check AutoTask here: https://us.awp.autotask.net/15/filelink/4730d-5167213-9f01ac23b9-2

Also, for redundancy's sake, ensure you have the most recent version of the 64 bit server for their version.

Check the status of all the services.

IIS and Permissions

Once you've verified the version that is installed by default, the installer for OpenAPI will create a default IIS instance as well. This instance will likely not match any custom legacy CRS instance or other instance already configured. Note the following:

1.     The Application Pool may need to be built from scratch.

2.     Application pools need authentication, either through pass-through of the application, in which case the Application Pool itself needs to be added by typing in the following into a search field under Sites [SiteName] Edit Permissions Edit Add, as in this screenshot:

Syntax: IIS AppPool\[AppPoolName]

3.     In some rare cases, the AppPool may also need these same permissions on the C:\Windows\Temp folder, more details in this solution:

Registration in a closed Environment

Once all of these steps are complete, take a look at your registration:

Standard Registration

(Attached to network, dynamic or static IP, IPv4/IPv6): 192.168.x.x\[SQL Server Name] e.g. 192.169.1.210\PSIsafe or [PC NAME]\[SQL Server Name] e.g. TECH-JFERNANDEZ\PSIsafe

Registration for a non-internet, LAN/WAN (local only) connection via RDP from standard connection (Closed network environment 1):

(Attached to network, dynamic or static IP, IPv4/IPv6): [SQL Server Name] e.g. PSIsafe NOT 192.168.x.x \[SQL Server Name] or  [PC NAME]\[SQL Server Name]

Registration for standard network connection via VM hosted on standard connection:

(Note: in this example, the user hosts the SQL server on the VM, if the SQL Server is hosted on a different machine or VM, ensure that PC/VM is on the same domain and use that IPv4/PC Name/VM Name instead.)

(Attached to network, dynamic or static IP, IPv4/IPv6): 192.168.x.x\[SQL Server Name] e.g. 192.169.1.210\PSIsafe or [VM PC NAME]\[SQL Server Name] e.g. TECH-JFERNANDEZ\PSIsafe

Registration for a non-internet, LAN/WAN (local only) connection via VM hosted on standard connection (Closed network environment 2):

(Note: You must configure your VM client to connect and register on the network within the same domain as the server)

(Attached to network, dynamic or static IP, IPv4/IPv6): 192.168.x.x\[SQL Server Name] e.g. 192.169.1.210\PSIsafe or \[SQL Server Name] e.g. TECH-JFERNANDEZ\PSIsafe

DO NOT USE:

127.0.0.1/[SQLSERVERNAME]

::1/[SQLSERVERNAME]

1:1/[SQLSERVERNAME]

NOTE: IPv4 (x.x.x.x) format works best for most configurations pre-11.1

Error Messages

In many cases, incorrectly configured databases will result in no database shown in the launcher, like so:

Most common error code:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – could not open a connection to SQL Server)

In a similar solution to 411, here: https://na53.salesforce.com/501f2000000avNN?srPos=14&srKp=501

Unable to connect to server. Reason: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

Conclusion:

Match your connection type and configuration to the above options and you should be able to avoid these issues and error codes.