Article ID: 030516100959 - Last Review: 04 April 2007 by jasonl - Revision: 2 - Views: 4374
Symptom
When starting Service Accent, you receive a status 116
Cause
Status 116 is generated when the workstation is unable to communicate with the PC that has been designated as the database gateway (by using the Pervasive.SQL Gateway Locator to achieve this). The workstation is attempting to route its network requests to the server but is not receiving a reply.
Solution
Perform one or more of the following to attempt to rectify the problem:
On a server running Pervasive.SQL Workgroup, ensure it is logged in as the Pervasive.SQL components in this instance are not running as a service but as an application
Run the Pervasive.SQL gateway locator, locate your AccentDB folder and check the machine name assigned to that folder. This is the PC assigned as the gateway
Ensure that the PC acting as the gateway is running the Pervasive.SQL components correctly
Map your AccentDB folder as a drive letter and then run DBRouter rather than a UNC path name
Ensure each user is logged in to his or her workstation using a unique logon name; Pervasive.SQL uses the logon names to track connections and multiple connections using the same logon name can cause Pervasive.SQL to invalidate connection attempts
Re-install Pervasive.SQL on the workstation to ensure the correct Pervasive.SQL components are installed
Starting a Pervasive.SQL client application on the server has been reported as fixing a status 116. If you have installed Service Accent on the server try starting it to see if the error resolves.
For additional resources and information, you can go to the Service Accent Support Centre
