This occurs when all defined connection definitions do not connect to an active Workgroup Server (WGS). This might indicate that they are down for maintenance.
If this occurs when installing a new environment and you know that the WGS is running, then it is possible that the default connection definition is not setup correctly. You can update the connection information using the database utility, nsqjdbcmk.
Run nsqjdbcmk.bat (or .sh) by changing the directory to [AUTOPILOT_HOME]/sql-scripts/nsqjdbcmk then running nsqjdbcmk on a command prompt. You will see the nsqjdbcmk options listed below.
Update connection information with database utility, nsqjdbcmk (10.2 and higher)
Enter option 9. You will be presented with a list of existing connections (each associated with a number option), or an option to add a new connection. To update an existing connection, simply enter the connection’s number and update the connection name, host IP and/or port.
Update connection information within the nsqjdbcmk.properties file (prior to 10.2)
Enter option 3. You will recreate the permits database to add the connection information. In the nsqjdbcmk.properties file. Review the settings in this file to ensure they are correct. The sample configuration has the below commented out, showing the default values:
This sample works when running the web applications and WGS on the same host at the default port.