Troubleshooting Sage BusinessVision access issues

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:

  • You're unable to log in
    No one can log in to the company on the server
  • You're receiving the error, "Invalid Control File. The BusinessVision control file for this company (BVCON.FIL) is no longer accessible, the company selected cannot be accessed by BusinessVision. Do you wish to remove the company from the list?" when attempting to log in to a Business Vision company.
  • You're receiving an error with a "status code 94 or 116" when attempting to open the control file with the Pervasive Function Executor

Disclaimer

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.

Causes

The following will cause a status code 94 error:

  • An Incorrect SAT entry has been written to the registry. With Pervasive, an entry is added to the registry called SAT entries. These entries are used as a persistent cache that maintains information about the server, server type, and connection type.
  • Runtime Server Support configured incorrectly
  • Lack of proper rights at the operating system level
  • Server firewall
  • Corrupted Pervasive files on the workstation
  • Corrupted Pervasive files on the serverca
  • Pervasive on the server does not recognize listen IP address
  • Old Pervasive licenses on the workstation
  • Bad drive mapping
  • Corrupted Windows folder
  • No Gateway or Gateway pointing to old server

Resolution

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.

Rights

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.

  1. Create a user with Domain administrative rights and ensure that the user has full control rights to the BusinessVision data directory.
  2. Modify the Pervasive.SQL database engine to login as the user created in Step 1. To modify the Pervasive.SQL database engine to login as another user: 
    1. Choose Start, Settings, Control Panel, Administrative Tools, Services.
    2. Select the service Pervasive.SQL (Transactional), right click and choose Properties.
    3. Select the Log On tab and select This Account.
    4. Input the user with Domain administrative rights.
    5. Choose Apply and choose OK.
    6. Change the Pervasive.SQL (Relational) service to logon as a user with Domain administrative rights.
  3. Stop and Restart both the Pervasive.SQL (Transactional) and the Pervasive.SQL (Relational) services:
    1. Right click and choose Properties, Stop, Start.

Server Firewall

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.

Corrupted Pervasive Files on Workstation

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.

Corrupted Pervasive Files on Server

Uninstall an reinstall Pervasive on the server.

Ping from workstation to the server does not match server IP address

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.

No Gateway or Gateway pointing to old server

Use the Gateway Locator to set a permanent gateway to the server.

Incorrect SAT Entry and Runtime Server Support

  1. In Windows click Start, All Programs, Pervasive, Pervasive.SQL, Pervasive.SQL 9 Control Center.
  2. Click Configure Microkernel Router.
  3. Click Security.
  4. In the Runtime Server Support box, enter No.
  5. Click OK.

Pervasive V10

A.

  1. In Windows click Start, Run.
  2. In the Open: box, enter regedit.
  3. Go to HKEY_LOCAL_MACHINE\Software\Pervasive Software\Communications Requester\Version 10\Settings.
  4. Delete SAT entries (SatEntry0, SatEntry1, etc) and set value for NumSatEntries to 0.


B.

  1. In Windows click Start, All Programs, Pervasive, Pervasive.SQL, Pervasive.SQL 10 Control Center.
  2. Click Configure Microkernel Router.
  3. Click Security.
  4. In the Runtime Server Support box, enter No.
  5. Click OK.

Pervasive Listen IP Address

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:

  1. Click Windows Start, Pervasive, Pervasive Control Center.
  2. Click Configure Local Engine.
  3. Click Communication Protocols.
  4. Unselect the TCP/IP Multihomed checkbox.
  5. In the Listen IP Address box type server IP address.
  6. Click OK.
  7. Stop and restart Pervasive 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.

Old Pervasive Licenses

Using the Pervasive License Administrator on the Windows Start menu, remove any licenses for previous versions on the workstation.

Bad Drive Mapping

Disconnect the drive mapping and remap. For assistance contact your network administrator.

Corrupted Windows Folder

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.

Anonymous