Runtime-Error: SQL-Server does not exist

  • Hello,

    We are experiencing some strange errors within our MS Windows Server 2008R2 network.

    There are different machines running with OS like MS Windows 8.1 and even Windows XP SP3.

    Under XP in a certain program the connection to the SQL-Server (2008R2, named instance:sql) gets lost.

    Message: SQL-Server does not exist or access denied.

    Under CMD I can ping our Server. Nothing special occurs.

    No Anti-Virus scanner installed.

    The log file is inconspicuous.

    ...

    2015-09-05 17:10:37.05 Server Server is listening on [ 'any' <ipv6> 1433].

    2015-09-05 17:10:37.05 Server Server is listening on [ 'any' <ipv4> 1433].

    2015-09-05 17:10:37.05 Server Server is listening on [ ::1 <ipv6> 1434].

    2015-09-05 17:10:37.05 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].

    2015-09-05 17:10:37.05 Server Dedicated admin connection support was established for listening locally on port 1434.

    2015-09-05 17:10:37.07 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [XXX] for the SQL Server service.

    2015-09-05 17:10:37.07 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [XXX.local:1433 ] for the SQL Server service.

    2015-09-05 17:10:37.07 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.

    2015-09-05 17:10:37.26 spid16s CHECKDB for database 'PPS_Mat_Benutzer' finished without errors on 2014-09-20 17:06:15.830 (local time). This is an informational message only; no user action is required.

    2015-09-05 17:10:37.40 spid10s Starting up database 'tempdb'.

    2015-09-05 17:10:37.72 spid13s The Service Broker protocol transport is disabled or not configured.

    2015-09-05 17:10:37.72 spid13s The Database Mirroring protocol transport is disabled or not configured.

    2015-09-05 17:10:37.75 spid13s Service Broker manager has started.

    2015-09-05 17:10:39.83 spid18s CHECKDB for database 'PPS_Mat_Mandant15' finished without errors on 2014-09-20 17:09:07.733 (local time). This is an informational message only; no user action is required.

    2015-09-05 17:10:42.04 spid17s Recovery is writing a checkpoint in database 'PPS_Mat_Mandant14' (7). This is an informational message only. No user action is required.

    2015-09-05 17:10:42.14 spid17s CHECKDB for database 'PPS_Mat_Mandant14' finished without errors on 2015-08-28 15:50:13.750 (local time). This is an informational message only; no user action is required.

    2015-09-05 17:10:42.17 spid5s Recovery is complete. This is an informational message only. No user action is required.

    ...

    The server is listening to the ports 1433 and 1434.

    Interestingly, the same function of our program DOES work under Windows 8.1.

    ONLY Windows XP is making trouble and is ending with the error message above

    Thank you, cracks, in advance.

    Stephan

  • Quick thought, according to the log the server is listening on TCP 1433 and 1434(DAC) but no mentioning of UDP 1434, is the Browser Service running?

    😎

  • Yes, the SQL Browser is running:

    2015-09-08 10:48:26.02 Server Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64)

    Jun 28 2012 08:36:30

    Copyright (c) Microsoft Corporation

    Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

    2015-09-08 10:48:26.03 Server (c) Microsoft Corporation.

    2015-09-08 10:48:26.03 Server All rights reserved.

    2015-09-08 10:48:26.03 Server Server process ID is 3800.

    2015-09-08 10:48:26.03 Server System Manufacturer: 'To Be Filled By O.E.M.', System Model: 'To Be Filled By O.E.M.'.

    2015-09-08 10:48:26.03 Server Authentication mode is MIXED.

    2015-09-08 10:48:26.03 Server Logging SQL Server messages in file '\ERRORLOG'.

    2015-09-08 10:48:26.03 Server This instance of SQL Server last reported using a process ID of 2724 at 08.09.2015 10:48:25 (local) 08.09.2015 08:48:25 (UTC). This is an informational message only; no user action is required.

    2015-09-08 10:48:26.03 Server Registry startup parameters:

    2015-09-08 10:48:26.04 Server SQL Server is starting at high priority base (=13). This is an informational message only. No user action is required.

    2015-09-08 10:48:26.04 Server Detected 8 CPUs. This is an informational message; no user action is required.

    2015-09-08 10:48:26.27 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.

    2015-09-08 10:48:26.29 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

    2015-09-08 10:48:26.31 spid7s Starting up database 'master'.

    2015-09-08 10:48:26.36 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.

    2015-09-08 10:48:26.45 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.

    2015-09-08 10:48:26.48 spid7s SQL Trace ID 1 was started by login "ZZZ".

    2015-09-08 10:48:26.48 spid7s Starting up database 'mssqlsystemresource'.

    2015-09-08 10:48:26.50 spid7s The resource database build version is 10.50.4000. This is an informational message only. No user action is required.

    2015-09-08 10:48:26.56 spid10s Starting up database 'model'.

    2015-09-08 10:48:26.56 spid7s Server name is 'TELESTO'. This is an informational message only. No user action is required.

    2015-09-08 10:48:26.71 Server A self-generated certificate was successfully loaded for encryption.

    2015-09-08 10:48:26.71 Server Server is listening on [ 'any' <ipv6> 1433].

    2015-09-08 10:48:26.71 Server Server is listening on [ 'any' <ipv4> 1433].

    2015-09-08 10:48:26.72 Server Server is listening on [ ::1 <ipv6> 1434].

    2015-09-08 10:48:26.72 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].

    2015-09-08 10:48:26.72 Server Dedicated admin connection support was established for listening locally on port 1434.

    2015-09-08 10:48:26.72 spid11s A new instance of the full-text filter daemon host process has been successfully started.

    2015-09-08 10:48:26.74 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/XXX ] for the SQL Server service.

    2015-09-08 10:48:26.74 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/XXX:1433 ] for the SQL Server service.

    2015-09-08 10:48:26.74 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.

    2015-09-08 10:48:26.75 spid15s Starting up database 'ReportServerTempDB'.

    2015-09-08 10:48:26.75 spid11s Starting up database 'msdb'.

    2015-09-08 10:48:26.75 spid18s Starting up database 'PPS_Mat_Mandant15'.

    2015-09-08 10:48:26.75 spid17s Starting up database 'PPS_Mat_Benutzer'.

    2015-09-08 10:48:26.75 spid16s Starting up database 'PPS_Mat_Mandant14'.

    2015-09-08 10:48:26.75 spid14s Starting up database 'ReportServer'.

    2015-09-08 10:48:26.75 spid10s Clearing tempdb database.

    2015-09-08 10:48:27.00 spid14s Recovery is writing a checkpoint in database 'ReportServer' (5). This is an informational message only. No user action is required.

    2015-09-08 10:48:27.02 spid17s Recovery is writing a checkpoint in database 'PPS_Mat_Benutzer' (8). This is an informational message only. No user action is required.

    2015-09-08 10:48:27.14 spid17s CHECKDB for database 'PPS_Mat_Benutzer' finished without errors on 2014-09-20 17:06:15.830 (local time). This is an informational message only; no user action is required.

    2015-09-08 10:48:27.22 spid10s Starting up database 'tempdb'.

    2015-09-08 10:48:27.49 spid11s The Service Broker protocol transport is disabled or not configured.

    2015-09-08 10:48:27.49 spid11s The Database Mirroring protocol transport is disabled or not configured.

    2015-09-08 10:48:27.80 spid11s Service Broker manager has started.

    2015-09-08 10:48:28.18 spid51 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.

    2015-09-08 10:48:28.18 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.

    2015-09-08 10:48:28.19 spid51 Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.

    2015-09-08 10:48:28.19 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.

    2015-09-08 10:48:28.27 spid51 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.

    2015-09-08 10:48:28.27 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.

    2015-09-08 10:48:28.93 spid51 Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.

    2015-09-08 10:48:28.94 spid51 Using 'xpsqlbot.dll' version '2009.100.1600' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.

    2015-09-08 10:48:29.26 spid51 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.

    2015-09-08 10:48:29.27 spid51 Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.

    2015-09-08 10:48:29.32 spid51 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.

    2015-09-08 10:48:29.32 spid51 Using 'xplog70.dll' version '2009.100.1600' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.

    2015-09-08 10:48:31.29 spid18s CHECKDB for database 'PPS_Mat_Mandant15' finished without errors on 2014-09-20 17:09:07.733 (local time). This is an informational message only; no user action is required.

    2015-09-08 10:48:31.59 spid16s Recovery is writing a checkpoint in database 'PPS_Mat_Mandant14' (7). This is an informational message only. No user action is required.

    2015-09-08 10:48:31.72 spid16s CHECKDB for database 'PPS_Mat_Mandant14' finished without errors on 2015-08-28 15:50:13.750 (local time). This is an informational message only; no user action is required.

    2015-09-08 10:48:31.76 spid7s Recovery is complete. This is an informational message only. No user action is required.

    2015-09-08 10:48:44.23 spid52 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.

    2015-09-08 10:48:44.23 spid52 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.

    2015-09-08 10:48:44.24 spid52 Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.

    2015-09-08 10:48:44.24 spid52 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.

    2015-09-08 10:48:44.24 spid52 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.

    2015-09-08 10:48:44.24 spid52 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.

    2015-09-08 10:48:45.19 spid52 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.

    2015-09-08 10:48:45.19 spid52 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.

    2015-09-08 10:48:45.19 spid52 Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.

    2015-09-08 10:48:45.19 spid52 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.

    2015-09-08 10:48:45.20 spid52 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.

    2015-09-08 10:48:45.20 spid52 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.

    Another Problem occurs:

    After working some bigger SQL-queries, it seems XP is timing out.

    Hm...

    I am just wondering why Visual Basic does not say "SQL Time out" instead of "SQL Server does not exist".

    Same functions on Windows 8.1

    Any idea ????

    Thank you !

    Stephan

  • Hi

    I found a possible solution:

    ADO SQL is providing two relevant properties for defining a Time-Out in Visual Basic:

    #1 CommandTimeOut

    #2 ConnectionTimeOut

    The last property indicates how long to wait while establishing a connection before terminating the attempt and generating an error.

    Reference:

    In my case, it was set to 15 seconds-what was too short for my query.

    Increasing this value to 5 minutes, it is working fine for me.

    The question that stays in the room is still why a server suited with 8 core CPU working slower than 15 yrs old server before.

    Stephan

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply