Service Accent knowledge base

Pervasive.SQL error 2 using Windows Server 2003 and Pervasive.SQL Server Edition

Article ID: 0501051317553 - Last Review: 17 May 2006 by jasonl - Revision: 1 - Views: 4795

Symptom

When you start Service Accent, you receive a Pervasive.SQL error 2.

Cause

This can be caused if your AccentDB folder is mapped to a shared folder on a Windows Server 2003 server via a drive letter. The security features in Windows Server 2003 appear to prevent the Pervasive.SQL client components from communicating with the Pervasive.SQL server components properly.

Solution

Rather than use a drive letter to map your database folder, use the UNC path instead. For example, run:

\\server\share\AccentDB\dbrouter.exe

to map your database.

Related articles

•	Running the Pervasive.SQL server engine under Windows Server 2003

•	3103, 3012 or 3014 error when trying to access a Pervasive database

•	Can not link to the WORK table using Pervasive.SQL ODBC

•	Can't start Pervasive Server Engine, Error 1069, login failure

•	Configuring Pervasive.SQL ODBC

•	Connecting to your Service Accent database via ODBC with Pervasive.V8 and later

•	Error message "1607:Unable to install InstallShield Scripting runtime" when trying to install Pervasive.SQL

•	Error message "DBU - Access Denied" when entering Pervasive.SQL license key

•	How to close Pervasive.SQL tables manually

•	How to configure Pervasive Backup Agent

•	How to disable the Local MicroKernel Engine under Pervasive.SQL V9

Additional articles from the white papers

•	Pervasive Backup Agent v3

•	Service Accent - Installing Pervasive. SQL

•	Installing and configuring Pervasive. SQL 2000

For additional resources and information, you can go to the Service Accent Support Centre

Click here to go to the Service Accent Support Centre