Go to Programs - Pervasive and keep drilling until you get to Documentation. There's a list of "status codes". Look up your error number. It should give you a starting point. This one's on me.
"3103: Server name not found by Pervasive Network Services Layer
The search for a target server name was unable to resolve an address after searching NDS, bindery, named pipes, and DNS. Some possible causes include:
No common communication protocol is available between the server and the client. Check the Supported protocols setting within the Communication protocols option for both the client and server. Make sure there is a common protocol (either SPX or TCP/IP) between the server and the requester.
For Windows NT/2000:
The MicroKernel engine not running.
Server only: Named pipes are used in these two operating systems to resolve server names. The networking at the operating system level was unable to find the target named pipe.
For NetWare:
The Server Addressing Protocol (SAP) filtered out the server name. SAP is used in NetWare 3.x and can be used in version 4.x. This type of filtering is common in WAN environments.
NWCALLS.DLL and/or NWIPXSPX.DLL is missing when using the Win16 client. This is especially likely if the Win32 clients are functioning but the Win16 clients do not. These are NetWare system files that can be obtained from Novell web site (
http://www.novell.com).
For NetWare using TCP/IP: The server name is not in DNS.
For Novell NetWare 4.11 and Microsoft Windows 98 installs of Pervasive.SQL 2000 Client:
When the Pervasive System Analyzer tries to perform the first communication/functionality test, a status 3103 is returned. This status code may be caused by having no supported protocols set in the Pervasive.SQL 2000 client configuration utility. If Microsoft SPX is added as a supported protocol, the installation should complete without error. "
Pages: 1
Betrieve error 3103 (Read 2802 times)
