Don't let access issues with Sage BusinessVision derail you. The steps further down in this blog post will help with the following issues related to accessing Sage BusinessVision:
Operating System Warning
This solution requires advanced knowledge of your computer's operating system. Contact your system administrator for assistance.
Modifying your Windows Registry incorrectly can severely affect system operations. Sage is not responsible for operation issues caused by incorrectly modifying your Windows Registry.
Always create a backup of your data before proceeding with advanced solutions.
The following will cause a status code 94 error:
The first thing to try is stopping and restarting the Pervasive service (or application) on the server, even if only one workstation is receiving the status code 94 error. This procedure resolves many 94 errors.
Lack of proper rights at the Operating System level cause Status 94: "the application encountered a permissions error."
The Pervasive.SQL (Transactional) and the Pervasive.SQL (Relational) services logon to the network as a network user. This user must have full access to and control of the BusinessVision data directory.
The server firewall may also result in a status code 94. As a test disable the firewall to see if it resolves the error. See KB 28331 for a possible resolution. This refers to port 3351 which should be allowed in the firewall.
In some cases, Pervasive may be corrupted on the workstation. You may be able to log into local data, but when trying to log into data on a server you will receive an error. When opening the Bvcon.fil with the Function Executor you receive a status code 94 permissions error. Reinstall Pervasive on the workstation.
Uninstall an reinstall Pervasive on the server.
Edit the HOSTS file on the workstation under C:\Windows\System32\drivers\etc to include the correct IP Address of the server and the server name.
Use the Gateway Locator to set a permanent gateway to the server.
In some cases, the Pervasive engine on the server may not be listening to the correct IP address.
To force the Pervasive on server to listen to a specific IP address follow this procedure on the server:
This setting is normally used when there are two network cards installed in the server and static IP addresses are used.
Use the Pervasive System Analyzer to test the active installation, using the Test Network Communication option. Confirm that the communication connection passes with the correct server IP address.
Using the Pervasive License Administrator on the Windows Start menu, remove any licenses for previous versions on the workstation.
Disconnect the drive mapping and remap. For assistance contact your network administrator.
Create a new Windows folder and copy the contents of the corrupted folder.
The information above can be located in our Error: "Invalid Control File" or "Btrieve Status Code 94 or 116" Sage Knowledgebase article.
Please note that this Support Group is for Sage BusinessVision only. If you have a question about Sage Timeslips, I would recommend posting your question with full details, in one of the Forums in that Support Group.
Here is the direct link to the Sage Timeslips Support Group on Sage City:
We are unable to log in to our Time Slips. We have version 2017.