Results 1 to 7 of 7
  1. #1
    Join Date
    Jan 2006
    Posts
    4

    Unanswered: Fatal Error 3105 Windows 2003 SBS

    Hi,
    I have some little problems with my win2003SBS an pervasive sql 2000i ver.7.90.
    Btrieve v6 is running on a client and on a server.
    Now when I open betrieve I put in my password and username and press enter!

    The message fatal error 3105: fatal error in filemanager.
    Firewall I deactivated on both client (Winxp prof) an server win2003sbs.

    what can i do to kill this problem??

    thanx Hubert

  2. #2
    Join Date
    Dec 2001
    Posts
    1,109
    Provided Answers: 4
    Well, first off you need to get the client and the server running the same version of Btrieve/Pervasive.
    Second, the 3105 means:
    3105: No available transport protocol for the Pervasive Network Services Layer
    No transport protocol that is common to both the target server engine and clients is available. For example, this status code could be caused by a client using SPX when the server engine only has TCP/IP available. Check the Supported protocols setting within the Communication protocols option for both the client and server. For more information on Communication protocols, refer to Advanced Operations Guide.

    Make sure you can ping the server by name and that either TCP/IP or SPX is properly configured between the client and the server.
    Mirtheil Software
    Certified Pervasive Developer
    Certified Pervasive Technician
    Custom Btrieve/VB development
    http://www.mirtheil.com
    I do not answer questions by email. Please post on the forum.

  3. #3
    Join Date
    Jan 2006
    Posts
    4

    Unhappy FATAL ERROR 3105 Pervasive.SQL7.9 sp4

    Thanx for answering.

    I still have the pproblem with a new Server Win2003 SBS Standard.
    PVSW Folder is already installed. Pervasive.SQL works fine with betrieve if I run it on my Server. A already install Client (a the moment the clients runs´on our old server very good) can´t connect to server with system analyser.

    ??? Why ??? folder rights are set.
    Protocols are equal on both sides (client/server TCP/IP).

    Any ideas???

  4. #4
    Join Date
    Dec 2001
    Posts
    1,109
    Provided Answers: 4
    What version of Pervasive are you using on the server? Is it still 7.90? What about the client?
    What error does PSA return?
    Does Function EXecutor or your application work? If not, what error do you see?
    Mirtheil Software
    Certified Pervasive Developer
    Certified Pervasive Technician
    Custom Btrieve/VB development
    http://www.mirtheil.com
    I do not answer questions by email. Please post on the forum.

  5. #5
    Join Date
    Jan 2006
    Posts
    4
    Its version 7.90.230.036 on Server and on Client 7.90.230.036.

    Tuesday, May 23, 2006, 16:53 ---

    **************************
    [NETWORK TEST]
    **************************
    Information : -----
    Information : Test started on Tue May 23 16:53:19 2006
    Information : Engine to test : Btrieve
    Information : Transport : All Available
    Information : Test level : Communications Stress Test
    Information : Target name : \\Amdserver2\Pvsw
    Information : -----

    Tuesday, May 23, 2006, 16:53 ---Step 1 : Establish the workstation environment.Information : Winsock description : WinSock 2.0
    Warning : Winsock SPX is unavailable
    Warning : socket error = 2
    Information : Winsock TCP/IP is available
    Information : Microsoft Networking API is available
    Warning : Could not load CALWIN32.DLL
    Warning : NetWare API is not available

    Tuesday, May 23, 2006, 16:53 ---Step 2 : Determine full target name.Information : Input target name is \\AMDSERVER2\PVSW
    Information : IDSHOSTS file found as C:\PVSW\BIN\idshosts
    Information : IDSHOSTS entry : #
    Information : IDSHOSTS entry : # Example IDSHOSTS file.
    Information : IDSHOSTS entry : #
    Information : IDSHOSTS entry : # IDSHOSTS is a text file that resembles the standard Windows LMHOSTS
    Information : IDSHOSTS entry : # specifications. The file must reside the %SystemRoot%\system32
    Information : IDSHOSTS entry : # directory on Windows NT, or %SystemRoot%\system on Windows 95 and 98.
    Information : IDSHOSTS entry : #
    Information : IDSHOSTS entry : # IDSHOSTS is formated as the following:
    Information : IDSHOSTS entry : #
    Information : IDSHOSTS entry : # 1. All comments must be preceded by #
    Information : IDSHOSTS entry : # 2. The server or drive being mapped has to be the first entry on
    Information : IDSHOSTS entry : # a new line.
    Information : IDSHOSTS entry : # 3. One or more spaces must separate the drive or server being
    Information : IDSHOSTS entry : # mapped from the IDS server name.
    Information : IDSHOSTS entry : # 4. If the path contains spaces it must be enclosed in double
    Information : IDSHOSTS entry : # spaces.
    Information : IDSHOSTS entry : # 5. An optional IDS Database Set name may be specified after the
    Information : IDSHOSTS entry : # IDS server name, separated by one or more spaces. The IDS
    Information : IDSHOSTS entry : # Database Set name is only used by the Btrieve Win32 Requester.
    Information : IDSHOSTS entry : # 6. Server mappings have to start with two back slashes.
    Information : IDSHOSTS entry : #
    Information : IDSHOSTS entry : #
    Information : IDSHOSTS entry : # j: www.pervasive.com # Drive mapping
    Information : IDSHOSTS entry : # k:\myData\ 10.1.1.1 # IP notation can be used
    Information : IDSHOSTS entry : # \\dataServer\public www.pervasive.com # Server names need \\
    Information : IDSHOSTS entry : # "m:\my data\" www.yourserver.com # If there are spaces in
    Information : IDSHOSTS entry : # # path the whole path must
    Information : IDSHOSTS entry : # # be enclosed by ""
    Information : IDSHOSTS entry : # l:\accounting AcctServer AcctDB # Example with IDS
    Information : IDSHOSTS entry : # # Database Set name
    Information : IDSHOSTS entry :
    Information : Target does not appear to be IDS.
    Warning : NetWare NDS API is not available
    Information : Target name is already a fully qualified name.
    Information : Target server name AMDSERVER2
    Information : Fully qualified name AMDSERVER2\PVSW

    Tuesday, May 23, 2006, 16:53 ---Step 3 : Resolve full target name into a network address.Warning : NetWare NDS API not available for address resolution

    Warning : Unable to query NetWare NDS

    Warning : NetWare API not available for address resolution

    Warning : Unable to read NetWare Bindery via NetWare API

    Information : Using Winsock Name Resolution API to read NetWare Bindery

    Information : There may be a slight delay - please wait

    Warning : Unable to resolve server name via Winsock Name Resolution API

    Information : Attempting to access Windows NT server AMDSERVER2

    Information : Target engine TCP address : 192.168.120.254:3351



    Tuesday, May 23, 2006, 16:53 ---Step 4 : Establish a connection to the target engine.Information : Attempting to connect via WinSock TCP/IP

    Warning : TCP/IP connect error = 10060

    Warning : Unable to connect via TCP/IP.

    Fatal : Unable to establish a connection to the target engine.

    Information : -----

    Information : Test completed on Tue May 23 16:53:40 2006

    Information : -----

    The network test was not successful.

    Tuesday, May 23, 2006, 16:53 ---Network test completed.

    The Applicaten (LevelUp works only when Levelup wants to logion will open the Sql database and shows Error <Error Nr. 3105: Fatal error in filemanager >
    <Fehler Nr. 3105: Fataler Fehler im Dateimanager>

    Hope you can help me.

  6. #6
    Join Date
    Dec 2001
    Posts
    1,109
    Provided Answers: 4
    Information : Target engine TCP address : 192.168.120.254:3351
    Tuesday, May 23, 2006, 16:53 ---Step 4 : Establish a connection to the target engine.Information : Attempting to connect via WinSock TCP/IP
    Warning : TCP/IP connect error = 10060
    Warning : Unable to connect via TCP/IP.
    Fatal : Unable to establish a connection to the target engine.
    Here's your problem. THis client can't connect through TCP/IP to the server.
    If you ping the server (AMDSERVER2), does it return the correct IP address?
    If you go to the console of the server and type "netstat -a" at a command prompt, does it show the server listening on port 3351 and 1583?
    Mirtheil Software
    Certified Pervasive Developer
    Certified Pervasive Technician
    Custom Btrieve/VB development
    http://www.mirtheil.com
    I do not answer questions by email. Please post on the forum.

  7. #7
    Join Date
    Jan 2006
    Posts
    4
    Thanx a lot.

    I solved the problem.
    The IP 192.168.120.x was the IP from AVM Fritz Adapter.
    Port 3351 and 1583 listen

    now by pinging amdserver2 it returns the correct address

    How can I close this thread?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •