4000 to 4099

---

Database Utilities Status Codes

This section lists the status codes you can receive when using the Database Utilities (DBU).

4083: Component not loaded

If you receive this status code while attempting to start the Pervasive.SQL Transactional or Relational Services, you are missing a key file. To resolve this problem, uninstall Pervasive.SQL V8 and reinstall it.

---

Note
You may get more information about the situation that caused this error by setting the environment variable, PVSW_DISP_LOAD_ERRS=AIF, and running the application again. This enables the Services DLL to display on-screen module load errors. However, this environment variable should only be set to diagnose module load errors. In all other cases, it should not be set.

---

4086: An internal error occurred. Utilities Requester receive size too small. Verify that the correct components are loaded

This status code may appear when all three communication protocols (TCP/IP, SPX and NetBios) are present. By default, all three of these protocols are enabled. To resolve this error message, disable one of the protocols in the server configuration.

In Pervasive.SQL 8 and later, NetBIOS is not supported by the Server engine.

To Adjust Server Protocols:

1. Click Start4Programs4Pervasive.SQL V84Control Center.
2. Expand Pervasive.SQL V8 Engines and expand the desired database.
3. Expand Configuration, then expand Server, and click on Communication Protocols.
4. In the right hand frame, double-click on Supported protocols.
5. The Supported protocols dialog box opens.
6. At this point, you can deselect an option as appropriate to your network environment. In most cases, only the first two protocols are needed. Highlight a protocol in the list, then click on the "<" button to remove it from the list.
7. Click OK.
8. Close the Pervasive Control Center and stop and restart the engine.
9. Ensure that each client workstation that access the database server has at least one Supported Protocol in common with the server, or else the clients cannot communicate with the server. At each workstation, check the Configuration setting Client4Communication Protocols4Supported Protocols.