Pervasive Error Code 116
Posted: January 14th, 2012, 4:28 amThis message is the translation of Pervasive error code 116. There can be a number of different reasons for that so it is not easy to jump to a single solution. In theory, this message could occur in a Pervasive Client/Server installation, but that is unlikely. It generally will be in a 3-user Workgroup environment and I would suggest the following approach:
- Make sure the Pervasive Database - Pre-load engine starts automatically on each computer. That is, immediately after doing a Windows Restart you should be able to see the engine icon in the System Tray/Notification Area on Taskbar.
1. You should be able to right-click and select About. If this is not the case, then the Pervasive install was incomplete to some degree.
2. Make sure that you can “ping” between the computers by name. If they have a computer designated as the C21 “server”, then it should be necessary only to be able to ping from each workstation to that computer. But it would be good to try pinging in all directions. Inability to ping could indicate that the TCP/IP network protocol properties are not configured correctly on a computer.
How to Ping
1. On each computer right-click on My Computer and select Properties.
2. From the Computer Name tab note the “computer name” (not description).
3. Start a (DOS) Command Prompt window.
4. From any given computer, “ping” the other computers. For example, from Station3, enter the follow type commands:
ping station1
ping station2
You will see messages indicating the success of the ping.
Getting rid of Pervasive Overhead
If problems were found/corrected in the first 2 steps, this may not be necessary to solve this particular issue. But it is generally good to do anyway. If nothing else, it could do away with some unnecessary overhead the Pervasive engine could be going through.
On each computer run the Pervasive Control Center.
In the left pane, open the tree until you get to the <local computer> Configuration node.
Under “Server” check/set the following properties:
Access (highlight Access in left pane, double-click “Name” in right pane to check/set value).
Accept Remote Request > set to “On”.
Communication protocols
Supported protocols > make sure only “Selected” item is Microsoft TCP/IP.
Under “Client” check/set the following properties:
Access
Gateway Durability > set to: “Off”
Target Engine > set to “Try Server, then Workstation”
Use Local MicroKernel Engine > set to “On”
Use Remote MicroKernel Engine > set to “On”
Communication protocols
Supported protocols > make sure only “Selected” item is Microsoft TCP/IP
Exit out of the Pervasive Control Center, responding “Yes” when asked if you want to save configuration changes. Then Stop/Restart the Pervasive Pre-load engine (you can just restart the computer to accomplish this).
- Make sure the Pervasive Database - Pre-load engine starts automatically on each computer. That is, immediately after doing a Windows Restart you should be able to see the engine icon in the System Tray/Notification Area on Taskbar.
1. You should be able to right-click and select About. If this is not the case, then the Pervasive install was incomplete to some degree.
2. Make sure that you can “ping” between the computers by name. If they have a computer designated as the C21 “server”, then it should be necessary only to be able to ping from each workstation to that computer. But it would be good to try pinging in all directions. Inability to ping could indicate that the TCP/IP network protocol properties are not configured correctly on a computer.
How to Ping
1. On each computer right-click on My Computer and select Properties.
2. From the Computer Name tab note the “computer name” (not description).
3. Start a (DOS) Command Prompt window.
4. From any given computer, “ping” the other computers. For example, from Station3, enter the follow type commands:
ping station1
ping station2
You will see messages indicating the success of the ping.
Getting rid of Pervasive Overhead
If problems were found/corrected in the first 2 steps, this may not be necessary to solve this particular issue. But it is generally good to do anyway. If nothing else, it could do away with some unnecessary overhead the Pervasive engine could be going through.
On each computer run the Pervasive Control Center.
In the left pane, open the tree until you get to the <local computer> Configuration node.
Under “Server” check/set the following properties:
Access (highlight Access in left pane, double-click “Name” in right pane to check/set value).
Accept Remote Request > set to “On”.
Communication protocols
Supported protocols > make sure only “Selected” item is Microsoft TCP/IP.
Under “Client” check/set the following properties:
Access
Gateway Durability > set to: “Off”
Target Engine > set to “Try Server, then Workstation”
Use Local MicroKernel Engine > set to “On”
Use Remote MicroKernel Engine > set to “On”
Communication protocols
Supported protocols > make sure only “Selected” item is Microsoft TCP/IP
Exit out of the Pervasive Control Center, responding “Yes” when asked if you want to save configuration changes. Then Stop/Restart the Pervasive Pre-load engine (you can just restart the computer to accomplish this).