asp sql server: serve

Showing posts with label serve. Show all posts

Tuesday, March 27, 2012

Connection Problem

Hi All,
I can not connect to sql serve 2005 using SQL Serve Management Studio,
I got these error in ERROR.LOG file. Any help is really appreciated.
Thanks.
2006-09-21 12:48:21.53 Server Microsoft SQL Server 2005 -
9.00.2047.00 (Intel X86)
Apr 14 2006 01:12:25
Copyright (c) 1988-2005 Microsoft Corporation
Developer Edition on Windows NT 5.1 (Build 2600: Service Pack
2)
2006-09-21 12:48:21.54 Server (c) 2005 Microsoft Corporation.
2006-09-21 12:48:21.54 Server All rights reserved.
2006-09-21 12:48:21.54 Server Server process ID is 4948.
2006-09-21 12:48:21.54 Server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2006-09-21 12:48:21.54 Server This instance of SQL Server last
reported using a process ID of 4396 at 9/21/2006 1:05:02 AM (local)
9/21/2006 8:05:02 AM (UTC). This is an informational message only; no
user action is required.
2006-09-21 12:48:21.54 Server Registry startup parameters:
2006-09-21 12:48:21.59 Server -d C:\Program Files\Microsoft
SQL
Server\MSSQL.1\MSSQL\DATA\master.mdf
2006-09-21 12:48:21.59 Server -e C:\Program Files\Microsoft
SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2006-09-21 12:48:21.59 Server -l C:\Program Files\Microsoft
SQL
Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2006-09-21 12:48:21.64 Server SQL Server is starting at normal
priority base (=7). This is an informational message only. No user
action is required.
2006-09-21 12:48:21.64 Server Detected 2 CPUs. This is an
informational message; no user action is required.
2006-09-21 12:48:22.64 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.
2006-09-21 12:48:23.65 Server Attempting to initialize Microsoft
Distributed Transaction Coordinator (MS DTC). This is an informational
message only. No user action is required.
2006-09-21 12:48:24.23 Server The Microsoft Distributed
Transaction Coordinator (MS DTC) service could not be contacted. If
you would like distributed transaction functionality, please start this
service.
2006-09-21 12:48:24.48 Server Database mirroring has been enabled
on this instance of SQL Server.
2006-09-21 12:48:24.84 spid5s Starting up database 'master'.
2006-09-21 12:48:25.42 spid5s SQL Trace ID 1 was started by login
"sa".
2006-09-21 12:48:25.46 spid5s Starting up database
'mssqlsystemresource'.
2006-09-21 12:48:25.54 spid5s The resource database build version
is 9.00.2047. This is an informational message only. No user action is
required.
2006-09-21 12:48:25.98 spid5s Server name is 'BLAHBLAH'. This is
an informational message only. No user action is required.
2006-09-21 12:48:25.98 spid9s Starting up database 'model'.
2006-09-21 12:48:26.46 spid9s Clearing tempdb database.
2006-09-21 12:48:30.10 spid9s Starting up database 'tempdb'.
2006-09-21 12:48:30.54 spid12s The Service Broker protocol
transport is disabled or not configured.
2006-09-21 12:48:30.54 spid12s The Database Mirroring protocol
transport is disabled or not configured.
2006-09-21 12:48:31.12 spid12s Service Broker manager has started.
2006-09-21 12:48:31.39 Server A self-generated certificate was
successfully loaded for encryption.
2006-09-21 12:48:31.40 Server Error: 26055, Severity: 16, State:
1.
2006-09-21 12:48:31.40 Server The SQL Server failed to initialize
VIA support library [QLVipl.dll]. This normally indicates the VIA
support library does not exist or is corrupted. Please repair or
disable the VIA network protocol. Error: 0x7e.
2006-09-21 12:48:31.42 Server Error: 17182, Severity: 16, State:
1.
2006-09-21 12:48:31.42 Server TDSSNIClient initialization failed
with error 0x7e, status code 0x60.
2006-09-21 12:48:31.43 Server Error: 17182, Severity: 16, State:
1.
2006-09-21 12:48:31.43 Server TDSSNIClient initialization failed
with error 0x7e, status code 0x1.
2006-09-21 12:48:31.43 Server Error: 17826, Severity: 18, State:
3.
2006-09-21 12:48:31.43 Server Could not start the network library
because of an internal error in the network library. To determine the
cause, review the errors immediately preceding this one in the error
log.
2006-09-21 12:48:31.43 Server Error: 17120, Severity: 16, State:
1.
2006-09-21 12:48:31.43 Server SQL Server could not spawn FRunCM
thread. Check the SQL Server error log and the Windows event logs for
information about possible related problems.Are you using VIA? If not, try disabling the protocol using
the SQL Server Configuration Manager.
-Sue
On 21 Sep 2006 21:58:12 -0700, "sara" <sarasara82@.gmail.com>
wrote:

>Hi All,
>I can not connect to sql serve 2005 using SQL Serve Management Studio,
>I got these error in ERROR.LOG file. Any help is really appreciated.
>Thanks.
>2006-09-21 12:48:21.53 Server Microsoft SQL Server 2005 -
>9.00.2047.00 (Intel X86)
> Apr 14 2006 01:12:25
> Copyright (c) 1988-2005 Microsoft Corporation
> Developer Edition on Windows NT 5.1 (Build 2600: Service Pack
>2)
>2006-09-21 12:48:21.54 Server (c) 2005 Microsoft Corporation.
>2006-09-21 12:48:21.54 Server All rights reserved.
>2006-09-21 12:48:21.54 Server Server process ID is 4948.
>2006-09-21 12:48:21.54 Server Logging SQL Server messages in file
>'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
>2006-09-21 12:48:21.54 Server This instance of SQL Server last
>reported using a process ID of 4396 at 9/21/2006 1:05:02 AM (local)
>9/21/2006 8:05:02 AM (UTC). This is an informational message only; no
>user action is required.
>2006-09-21 12:48:21.54 Server Registry startup parameters:
>2006-09-21 12:48:21.59 Server -d C:\Program Files\Microsoft
>SQL
>Server\MSSQL.1\MSSQL\DATA\master.mdf
>2006-09-21 12:48:21.59 Server -e C:\Program Files\Microsoft
>SQL
>Server\MSSQL.1\MSSQL\LOG\ERRORLOG
>2006-09-21 12:48:21.59 Server -l C:\Program Files\Microsoft
>SQL
>Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
>2006-09-21 12:48:21.64 Server SQL Server is starting at normal
>priority base (=7). This is an informational message only. No user
>action is required.
>2006-09-21 12:48:21.64 Server Detected 2 CPUs. This is an
>informational message; no user action is required.
>2006-09-21 12:48:22.64 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.
>2006-09-21 12:48:23.65 Server Attempting to initialize Microsoft
>Distributed Transaction Coordinator (MS DTC). This is an informational
>message only. No user action is required.
>2006-09-21 12:48:24.23 Server The Microsoft Distributed
>Transaction Coordinator (MS DTC) service could not be contacted. If
>you would like distributed transaction functionality, please start this
>service.
>2006-09-21 12:48:24.48 Server Database mirroring has been enabled
>on this instance of SQL Server.
>2006-09-21 12:48:24.84 spid5s Starting up database 'master'.
>2006-09-21 12:48:25.42 spid5s SQL Trace ID 1 was started by login
>"sa".
>2006-09-21 12:48:25.46 spid5s Starting up database
>'mssqlsystemresource'.
>2006-09-21 12:48:25.54 spid5s The resource database build version
>is 9.00.2047. This is an informational message only. No user action is
>required.
>2006-09-21 12:48:25.98 spid5s Server name is 'BLAHBLAH'. This is
>an informational message only. No user action is required.
>2006-09-21 12:48:25.98 spid9s Starting up database 'model'.
>2006-09-21 12:48:26.46 spid9s Clearing tempdb database.
>2006-09-21 12:48:30.10 spid9s Starting up database 'tempdb'.
>2006-09-21 12:48:30.54 spid12s The Service Broker protocol
>transport is disabled or not configured.
>2006-09-21 12:48:30.54 spid12s The Database Mirroring protocol
>transport is disabled or not configured.
>2006-09-21 12:48:31.12 spid12s Service Broker manager has started.
>2006-09-21 12:48:31.39 Server A self-generated certificate was
>successfully loaded for encryption.
>2006-09-21 12:48:31.40 Server Error: 26055, Severity: 16, State:
>1.
>2006-09-21 12:48:31.40 Server The SQL Server failed to initialize
>VIA support library [QLVipl.dll]. This normally indicates the VIA
>support library does not exist or is corrupted. Please repair or
>disable the VIA network protocol. Error: 0x7e.
>2006-09-21 12:48:31.42 Server Error: 17182, Severity: 16, State:
>1.
>2006-09-21 12:48:31.42 Server TDSSNIClient initialization failed
>with error 0x7e, status code 0x60.
>2006-09-21 12:48:31.43 Server Error: 17182, Severity: 16, State:
>1.
>2006-09-21 12:48:31.43 Server TDSSNIClient initialization failed
>with error 0x7e, status code 0x1.
>2006-09-21 12:48:31.43 Server Error: 17826, Severity: 18, State:
>3.
>2006-09-21 12:48:31.43 Server Could not start the network library
>because of an internal error in the network library. To determine the
>cause, review the errors immediately preceding this one in the error
>log.
>2006-09-21 12:48:31.43 Server Error: 17120, Severity: 16, State:
>1.
>2006-09-21 12:48:31.43 Server SQL Server could not spawn FRunCM
>thread. Check the SQL Server error log and the Windows event logs for
>information about possible related problems.|||Yes. It was VIA protocol problem. Thanks.
Sue Hoegemeier wrote:[vbcol=seagreen]
> Are you using VIA? If not, try disabling the protocol using
> the SQL Server Configuration Manager.
> -Sue
> On 21 Sep 2006 21:58:12 -0700, "sara" <sarasara82@.gmail.com>
> wrote:
>sql sql

Connection Problem

Hi All,
I can not connect to sql serve 2005 using SQL Serve Management Studio,
I got these error in ERROR.LOG file. Any help is really appreciated.
Thanks.
2006-09-21 12:48:21.53 Server Microsoft SQL Server 2005 -
9.00.2047.00 (Intel X86)
Apr 14 2006 01:12:25
Copyright (c) 1988-2005 Microsoft Corporation
Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2006-09-21 12:48:21.54 Server (c) 2005 Microsoft Corporation.
2006-09-21 12:48:21.54 Server All rights reserved.
2006-09-21 12:48:21.54 Server Server process ID is 4948.
2006-09-21 12:48:21.54 Server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2006-09-21 12:48:21.54 Server This instance of SQL Server last
reported using a process ID of 4396 at 9/21/2006 1:05:02 AM (local)
9/21/2006 8:05:02 AM (UTC). This is an informational message only; no
user action is required.
2006-09-21 12:48:21.54 Server Registry startup parameters:
2006-09-21 12:48:21.59 Server -d C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\master.mdf
2006-09-21 12:48:21.59 Server -e C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2006-09-21 12:48:21.59 Server -l C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2006-09-21 12:48:21.64 Server SQL Server is starting at normal
priority base (=7). This is an informational message only. No user
action is required.
2006-09-21 12:48:21.64 Server Detected 2 CPUs. This is an
informational message; no user action is required.
2006-09-21 12:48:22.64 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.
2006-09-21 12:48:23.65 Server Attempting to initialize Microsoft
Distributed Transaction Coordinator (MS DTC). This is an informational
message only. No user action is required.
2006-09-21 12:48:24.23 Server The Microsoft Distributed
Transaction Coordinator (MS DTC) service could not be contacted. If
you would like distributed transaction functionality, please start this
service.
2006-09-21 12:48:24.48 Server Database mirroring has been enabled
on this instance of SQL Server.
2006-09-21 12:48:24.84 spid5s Starting up database 'master'.
2006-09-21 12:48:25.42 spid5s SQL Trace ID 1 was started by login
"sa".
2006-09-21 12:48:25.46 spid5s Starting up database
'mssqlsystemresource'.
2006-09-21 12:48:25.54 spid5s The resource database build version
is 9.00.2047. This is an informational message only. No user action is
required.
2006-09-21 12:48:25.98 spid5s Server name is 'BLAHBLAH'. This is
an informational message only. No user action is required.
2006-09-21 12:48:25.98 spid9s Starting up database 'model'.
2006-09-21 12:48:26.46 spid9s Clearing tempdb database.
2006-09-21 12:48:30.10 spid9s Starting up database 'tempdb'.
2006-09-21 12:48:30.54 spid12s The Service Broker protocol
transport is disabled or not configured.
2006-09-21 12:48:30.54 spid12s The Database Mirroring protocol
transport is disabled or not configured.
2006-09-21 12:48:31.12 spid12s Service Broker manager has started.
2006-09-21 12:48:31.39 Server A self-generated certificate was
successfully loaded for encryption.
2006-09-21 12:48:31.40 Server Error: 26055, Severity: 16, State:
1.
2006-09-21 12:48:31.40 Server The SQL Server failed to initialize
VIA support library [QLVipl.dll]. This normally indicates the VIA
support library does not exist or is corrupted. Please repair or
disable the VIA network protocol. Error: 0x7e.
2006-09-21 12:48:31.42 Server Error: 17182, Severity: 16, State:
1.
2006-09-21 12:48:31.42 Server TDSSNIClient initialization failed
with error 0x7e, status code 0x60.
2006-09-21 12:48:31.43 Server Error: 17182, Severity: 16, State:
1.
2006-09-21 12:48:31.43 Server TDSSNIClient initialization failed
with error 0x7e, status code 0x1.
2006-09-21 12:48:31.43 Server Error: 17826, Severity: 18, State:
3.
2006-09-21 12:48:31.43 Server Could not start the network library
because of an internal error in the network library. To determine the
cause, review the errors immediately preceding this one in the error
log.
2006-09-21 12:48:31.43 Server Error: 17120, Severity: 16, State:
1.
2006-09-21 12:48:31.43 Server SQL Server could not spawn FRunCM
thread. Check the SQL Server error log and the Windows event logs for
information about possible related problems.I googled for TDSSNIClient and had several hits, for instance
http://blogs.msdn.com/sql_protocols/archive/2005/10/31/487090.aspx.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"sara" <sarasara82@.gmail.com> wrote in message
news:1158882314.356874.272310@.h48g2000cwc.googlegroups.com...
> Hi All,
> I can not connect to sql serve 2005 using SQL Serve Management Studio,
> I got these error in ERROR.LOG file. Any help is really appreciated.
> Thanks.
> 2006-09-21 12:48:21.53 Server Microsoft SQL Server 2005 -
> 9.00.2047.00 (Intel X86)
> Apr 14 2006 01:12:25
> Copyright (c) 1988-2005 Microsoft Corporation
> Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
> 2006-09-21 12:48:21.54 Server (c) 2005 Microsoft Corporation.
> 2006-09-21 12:48:21.54 Server All rights reserved.
> 2006-09-21 12:48:21.54 Server Server process ID is 4948.
> 2006-09-21 12:48:21.54 Server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
> 2006-09-21 12:48:21.54 Server This instance of SQL Server last
> reported using a process ID of 4396 at 9/21/2006 1:05:02 AM (local)
> 9/21/2006 8:05:02 AM (UTC). This is an informational message only; no
> user action is required.
> 2006-09-21 12:48:21.54 Server Registry startup parameters:
> 2006-09-21 12:48:21.59 Server -d C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\DATA\master.mdf
> 2006-09-21 12:48:21.59 Server -e C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\LOG\ERRORLOG
> 2006-09-21 12:48:21.59 Server -l C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
> 2006-09-21 12:48:21.64 Server SQL Server is starting at normal
> priority base (=7). This is an informational message only. No user
> action is required.
> 2006-09-21 12:48:21.64 Server Detected 2 CPUs. This is an
> informational message; no user action is required.
> 2006-09-21 12:48:22.64 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.
> 2006-09-21 12:48:23.65 Server Attempting to initialize Microsoft
> Distributed Transaction Coordinator (MS DTC). This is an informational
> message only. No user action is required.
> 2006-09-21 12:48:24.23 Server The Microsoft Distributed
> Transaction Coordinator (MS DTC) service could not be contacted. If
> you would like distributed transaction functionality, please start this
> service.
> 2006-09-21 12:48:24.48 Server Database mirroring has been enabled
> on this instance of SQL Server.
> 2006-09-21 12:48:24.84 spid5s Starting up database 'master'.
> 2006-09-21 12:48:25.42 spid5s SQL Trace ID 1 was started by login
> "sa".
> 2006-09-21 12:48:25.46 spid5s Starting up database
> 'mssqlsystemresource'.
> 2006-09-21 12:48:25.54 spid5s The resource database build version
> is 9.00.2047. This is an informational message only. No user action is
> required.
> 2006-09-21 12:48:25.98 spid5s Server name is 'BLAHBLAH'. This is
> an informational message only. No user action is required.
> 2006-09-21 12:48:25.98 spid9s Starting up database 'model'.
> 2006-09-21 12:48:26.46 spid9s Clearing tempdb database.
> 2006-09-21 12:48:30.10 spid9s Starting up database 'tempdb'.
> 2006-09-21 12:48:30.54 spid12s The Service Broker protocol
> transport is disabled or not configured.
> 2006-09-21 12:48:30.54 spid12s The Database Mirroring protocol
> transport is disabled or not configured.
> 2006-09-21 12:48:31.12 spid12s Service Broker manager has started.
> 2006-09-21 12:48:31.39 Server A self-generated certificate was
> successfully loaded for encryption.
> 2006-09-21 12:48:31.40 Server Error: 26055, Severity: 16, State:
> 1.
> 2006-09-21 12:48:31.40 Server The SQL Server failed to initialize
> VIA support library [QLVipl.dll]. This normally indicates the VIA
> support library does not exist or is corrupted. Please repair or
> disable the VIA network protocol. Error: 0x7e.
> 2006-09-21 12:48:31.42 Server Error: 17182, Severity: 16, State:
> 1.
> 2006-09-21 12:48:31.42 Server TDSSNIClient initialization failed
> with error 0x7e, status code 0x60.
> 2006-09-21 12:48:31.43 Server Error: 17182, Severity: 16, State:
> 1.
> 2006-09-21 12:48:31.43 Server TDSSNIClient initialization failed
> with error 0x7e, status code 0x1.
> 2006-09-21 12:48:31.43 Server Error: 17826, Severity: 18, State:
> 3.
> 2006-09-21 12:48:31.43 Server Could not start the network library
> because of an internal error in the network library. To determine the
> cause, review the errors immediately preceding this one in the error
> log.
> 2006-09-21 12:48:31.43 Server Error: 17120, Severity: 16, State:
> 1.
> 2006-09-21 12:48:31.43 Server SQL Server could not spawn FRunCM
> thread. Check the SQL Server error log and the Windows event logs for
> information about possible related problems.
>

Sunday, March 25, 2012

Connection Problem

Hi All,
I can not connect to sql serve 2005 using SQL Serve Management Studio,
I got these error in ERROR.LOG file. Any help is really appreciated.
Thanks.
2006-09-21 12:48:21.53 Server Microsoft SQL Server 2005 -
9.00.2047.00 (Intel X86)
Apr 14 2006 01:12:25
Copyright (c) 1988-2005 Microsoft Corporation
Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2006-09-21 12:48:21.54 Server (c) 2005 Microsoft Corporation.
2006-09-21 12:48:21.54 Server All rights reserved.
2006-09-21 12:48:21.54 Server Server process ID is 4948.
2006-09-21 12:48:21.54 Server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2006-09-21 12:48:21.54 Server This instance of SQL Server last
reported using a process ID of 4396 at 9/21/2006 1:05:02 AM (local)
9/21/2006 8:05:02 AM (UTC). This is an informational message only; no
user action is required.
2006-09-21 12:48:21.54 Server Registry startup parameters:
2006-09-21 12:48:21.59 Server -d C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\master.mdf
2006-09-21 12:48:21.59 Server -e C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2006-09-21 12:48:21.59 Server -l C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2006-09-21 12:48:21.64 Server SQL Server is starting at normal
priority base (=7). This is an informational message only. No user
action is required.
2006-09-21 12:48:21.64 Server Detected 2 CPUs. This is an
informational message; no user action is required.
2006-09-21 12:48:22.64 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.
2006-09-21 12:48:23.65 Server Attempting to initialize Microsoft
Distributed Transaction Coordinator (MS DTC). This is an informational
message only. No user action is required.
2006-09-21 12:48:24.23 Server The Microsoft Distributed
Transaction Coordinator (MS DTC) service could not be contacted. If
you would like distributed transaction functionality, please start this
service.
2006-09-21 12:48:24.48 Server Database mirroring has been enabled
on this instance of SQL Server.
2006-09-21 12:48:24.84 spid5s Starting up database 'master'.
2006-09-21 12:48:25.42 spid5s SQL Trace ID 1 was started by login
"sa".
2006-09-21 12:48:25.46 spid5s Starting up database
'mssqlsystemresource'.
2006-09-21 12:48:25.54 spid5s The resource database build version
is 9.00.2047. This is an informational message only. No user action is
required.
2006-09-21 12:48:25.98 spid5s Server name is 'BLAHBLAH'. This is
an informational message only. No user action is required.
2006-09-21 12:48:25.98 spid9s Starting up database 'model'.
2006-09-21 12:48:26.46 spid9s Clearing tempdb database.
2006-09-21 12:48:30.10 spid9s Starting up database 'tempdb'.
2006-09-21 12:48:30.54 spid12s The Service Broker protocol
transport is disabled or not configured.
2006-09-21 12:48:30.54 spid12s The Database Mirroring protocol
transport is disabled or not configured.
2006-09-21 12:48:31.12 spid12s Service Broker manager has started.
2006-09-21 12:48:31.39 Server A self-generated certificate was
successfully loaded for encryption.
2006-09-21 12:48:31.40 Server Error: 26055, Severity: 16, State:
1.
2006-09-21 12:48:31.40 Server The SQL Server failed to initialize
VIA support library [QLVipl.dll]. This normally indicates the VIA
support library does not exist or is corrupted. Please repair or
disable the VIA network protocol. Error: 0x7e.
2006-09-21 12:48:31.42 Server Error: 17182, Severity: 16, State:
1.
2006-09-21 12:48:31.42 Server TDSSNIClient initialization failed
with error 0x7e, status code 0x60.
2006-09-21 12:48:31.43 Server Error: 17182, Severity: 16, State:
1.
2006-09-21 12:48:31.43 Server TDSSNIClient initialization failed
with error 0x7e, status code 0x1.
2006-09-21 12:48:31.43 Server Error: 17826, Severity: 18, State:
3.
2006-09-21 12:48:31.43 Server Could not start the network library
because of an internal error in the network library. To determine the
cause, review the errors immediately preceding this one in the error
log.
2006-09-21 12:48:31.43 Server Error: 17120, Severity: 16, State:
1.
2006-09-21 12:48:31.43 Server SQL Server could not spawn FRunCM
thread. Check the SQL Server error log and the Windows event logs for
information about possible related problems.
I googled for TDSSNIClient and had several hits, for instance
http://blogs.msdn.com/sql_protocols/...1/487090.aspx.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"sara" <sarasara82@.gmail.com> wrote in message
news:1158882314.356874.272310@.h48g2000cwc.googlegr oups.com...
> Hi All,
> I can not connect to sql serve 2005 using SQL Serve Management Studio,
> I got these error in ERROR.LOG file. Any help is really appreciated.
> Thanks.
> 2006-09-21 12:48:21.53 Server Microsoft SQL Server 2005 -
> 9.00.2047.00 (Intel X86)
> Apr 14 2006 01:12:25
> Copyright (c) 1988-2005 Microsoft Corporation
> Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
> 2006-09-21 12:48:21.54 Server (c) 2005 Microsoft Corporation.
> 2006-09-21 12:48:21.54 Server All rights reserved.
> 2006-09-21 12:48:21.54 Server Server process ID is 4948.
> 2006-09-21 12:48:21.54 Server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
> 2006-09-21 12:48:21.54 Server This instance of SQL Server last
> reported using a process ID of 4396 at 9/21/2006 1:05:02 AM (local)
> 9/21/2006 8:05:02 AM (UTC). This is an informational message only; no
> user action is required.
> 2006-09-21 12:48:21.54 Server Registry startup parameters:
> 2006-09-21 12:48:21.59 Server -d C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\DATA\master.mdf
> 2006-09-21 12:48:21.59 Server -e C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\LOG\ERRORLOG
> 2006-09-21 12:48:21.59 Server -l C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
> 2006-09-21 12:48:21.64 Server SQL Server is starting at normal
> priority base (=7). This is an informational message only. No user
> action is required.
> 2006-09-21 12:48:21.64 Server Detected 2 CPUs. This is an
> informational message; no user action is required.
> 2006-09-21 12:48:22.64 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.
> 2006-09-21 12:48:23.65 Server Attempting to initialize Microsoft
> Distributed Transaction Coordinator (MS DTC). This is an informational
> message only. No user action is required.
> 2006-09-21 12:48:24.23 Server The Microsoft Distributed
> Transaction Coordinator (MS DTC) service could not be contacted. If
> you would like distributed transaction functionality, please start this
> service.
> 2006-09-21 12:48:24.48 Server Database mirroring has been enabled
> on this instance of SQL Server.
> 2006-09-21 12:48:24.84 spid5s Starting up database 'master'.
> 2006-09-21 12:48:25.42 spid5s SQL Trace ID 1 was started by login
> "sa".
> 2006-09-21 12:48:25.46 spid5s Starting up database
> 'mssqlsystemresource'.
> 2006-09-21 12:48:25.54 spid5s The resource database build version
> is 9.00.2047. This is an informational message only. No user action is
> required.
> 2006-09-21 12:48:25.98 spid5s Server name is 'BLAHBLAH'. This is
> an informational message only. No user action is required.
> 2006-09-21 12:48:25.98 spid9s Starting up database 'model'.
> 2006-09-21 12:48:26.46 spid9s Clearing tempdb database.
> 2006-09-21 12:48:30.10 spid9s Starting up database 'tempdb'.
> 2006-09-21 12:48:30.54 spid12s The Service Broker protocol
> transport is disabled or not configured.
> 2006-09-21 12:48:30.54 spid12s The Database Mirroring protocol
> transport is disabled or not configured.
> 2006-09-21 12:48:31.12 spid12s Service Broker manager has started.
> 2006-09-21 12:48:31.39 Server A self-generated certificate was
> successfully loaded for encryption.
> 2006-09-21 12:48:31.40 Server Error: 26055, Severity: 16, State:
> 1.
> 2006-09-21 12:48:31.40 Server The SQL Server failed to initialize
> VIA support library [QLVipl.dll]. This normally indicates the VIA
> support library does not exist or is corrupted. Please repair or
> disable the VIA network protocol. Error: 0x7e.
> 2006-09-21 12:48:31.42 Server Error: 17182, Severity: 16, State:
> 1.
> 2006-09-21 12:48:31.42 Server TDSSNIClient initialization failed
> with error 0x7e, status code 0x60.
> 2006-09-21 12:48:31.43 Server Error: 17182, Severity: 16, State:
> 1.
> 2006-09-21 12:48:31.43 Server TDSSNIClient initialization failed
> with error 0x7e, status code 0x1.
> 2006-09-21 12:48:31.43 Server Error: 17826, Severity: 18, State:
> 3.
> 2006-09-21 12:48:31.43 Server Could not start the network library
> because of an internal error in the network library. To determine the
> cause, review the errors immediately preceding this one in the error
> log.
> 2006-09-21 12:48:31.43 Server Error: 17120, Severity: 16, State:
> 1.
> 2006-09-21 12:48:31.43 Server SQL Server could not spawn FRunCM
> thread. Check the SQL Server error log and the Windows event logs for
> information about possible related problems.
>

Connection Problem

Hi All,
I can not connect to sql serve 2005 using SQL Serve Management Studio,
I got these error in ERROR.LOG file. Any help is really appreciated.
Thanks.
2006-09-21 12:48:21.53 Server Microsoft SQL Server 2005 -
9.00.2047.00 (Intel X86)
Apr 14 2006 01:12:25
Copyright (c) 1988-2005 Microsoft Corporation
Developer Edition on Windows NT 5.1 (Build 2600: Service Pack
2)
2006-09-21 12:48:21.54 Server (c) 2005 Microsoft Corporation.
2006-09-21 12:48:21.54 Server All rights reserved.
2006-09-21 12:48:21.54 Server Server process ID is 4948.
2006-09-21 12:48:21.54 Server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2006-09-21 12:48:21.54 Server This instance of SQL Server last
reported using a process ID of 4396 at 9/21/2006 1:05:02 AM (local)
9/21/2006 8:05:02 AM (UTC). This is an informational message only; no
user action is required.
2006-09-21 12:48:21.54 Server Registry startup parameters:
2006-09-21 12:48:21.59 Server -d C:\Program Files\Microsoft
SQL
Server\MSSQL.1\MSSQL\DATA\master.mdf
2006-09-21 12:48:21.59 Server -e C:\Program Files\Microsoft
SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2006-09-21 12:48:21.59 Server -l C:\Program Files\Microsoft
SQL
Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2006-09-21 12:48:21.64 Server SQL Server is starting at normal
priority base (=7). This is an informational message only. No user
action is required.
2006-09-21 12:48:21.64 Server Detected 2 CPUs. This is an
informational message; no user action is required.
2006-09-21 12:48:22.64 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.
2006-09-21 12:48:23.65 Server Attempting to initialize Microsoft
Distributed Transaction Coordinator (MS DTC). This is an informational
message only. No user action is required.
2006-09-21 12:48:24.23 Server The Microsoft Distributed
Transaction Coordinator (MS DTC) service could not be contacted. If
you would like distributed transaction functionality, please start this
service.
2006-09-21 12:48:24.48 Server Database mirroring has been enabled
on this instance of SQL Server.
2006-09-21 12:48:24.84 spid5s Starting up database 'master'.
2006-09-21 12:48:25.42 spid5s SQL Trace ID 1 was started by login
"sa".
2006-09-21 12:48:25.46 spid5s Starting up database
'mssqlsystemresource'.
2006-09-21 12:48:25.54 spid5s The resource database build version
is 9.00.2047. This is an informational message only. No user action is
required.
2006-09-21 12:48:25.98 spid5s Server name is 'BLAHBLAH'. This is
an informational message only. No user action is required.
2006-09-21 12:48:25.98 spid9s Starting up database 'model'.
2006-09-21 12:48:26.46 spid9s Clearing tempdb database.
2006-09-21 12:48:30.10 spid9s Starting up database 'tempdb'.
2006-09-21 12:48:30.54 spid12s The Service Broker protocol
transport is disabled or not configured.
2006-09-21 12:48:30.54 spid12s The Database Mirroring protocol
transport is disabled or not configured.
2006-09-21 12:48:31.12 spid12s Service Broker manager has started.
2006-09-21 12:48:31.39 Server A self-generated certificate was
successfully loaded for encryption.
2006-09-21 12:48:31.40 Server Error: 26055, Severity: 16, State:
1.
2006-09-21 12:48:31.40 Server The SQL Server failed to initialize
VIA support library [QLVipl.dll]. This normally indicates the VIA
support library does not exist or is corrupted. Please repair or
disable the VIA network protocol. Error: 0x7e.
2006-09-21 12:48:31.42 Server Error: 17182, Severity: 16, State:
1.
2006-09-21 12:48:31.42 Server TDSSNIClient initialization failed
with error 0x7e, status code 0x60.
2006-09-21 12:48:31.43 Server Error: 17182, Severity: 16, State:
1.
2006-09-21 12:48:31.43 Server TDSSNIClient initialization failed
with error 0x7e, status code 0x1.
2006-09-21 12:48:31.43 Server Error: 17826, Severity: 18, State:
3.
2006-09-21 12:48:31.43 Server Could not start the network library
because of an internal error in the network library. To determine the
cause, review the errors immediately preceding this one in the error
log.
2006-09-21 12:48:31.43 Server Error: 17120, Severity: 16, State:
1.
2006-09-21 12:48:31.43 Server SQL Server could not spawn FRunCM
thread. Check the SQL Server error log and the Windows event logs for
information about possible related problems.
Are you using VIA? If not, try disabling the protocol using
the SQL Server Configuration Manager.
-Sue
On 21 Sep 2006 21:58:12 -0700, "sara" <sarasara82@.gmail.com>
wrote:

>Hi All,
>I can not connect to sql serve 2005 using SQL Serve Management Studio,
>I got these error in ERROR.LOG file. Any help is really appreciated.
>Thanks.
>2006-09-21 12:48:21.53 Server Microsoft SQL Server 2005 -
>9.00.2047.00 (Intel X86)
> Apr 14 2006 01:12:25
> Copyright (c) 1988-2005 Microsoft Corporation
> Developer Edition on Windows NT 5.1 (Build 2600: Service Pack
>2)
>2006-09-21 12:48:21.54 Server (c) 2005 Microsoft Corporation.
>2006-09-21 12:48:21.54 Server All rights reserved.
>2006-09-21 12:48:21.54 Server Server process ID is 4948.
>2006-09-21 12:48:21.54 Server Logging SQL Server messages in file
>'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
>2006-09-21 12:48:21.54 Server This instance of SQL Server last
>reported using a process ID of 4396 at 9/21/2006 1:05:02 AM (local)
>9/21/2006 8:05:02 AM (UTC). This is an informational message only; no
>user action is required.
>2006-09-21 12:48:21.54 Server Registry startup parameters:
>2006-09-21 12:48:21.59 Server -d C:\Program Files\Microsoft
>SQL
>Server\MSSQL.1\MSSQL\DATA\master.mdf
>2006-09-21 12:48:21.59 Server -e C:\Program Files\Microsoft
>SQL
>Server\MSSQL.1\MSSQL\LOG\ERRORLOG
>2006-09-21 12:48:21.59 Server -l C:\Program Files\Microsoft
>SQL
>Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
>2006-09-21 12:48:21.64 Server SQL Server is starting at normal
>priority base (=7). This is an informational message only. No user
>action is required.
>2006-09-21 12:48:21.64 Server Detected 2 CPUs. This is an
>informational message; no user action is required.
>2006-09-21 12:48:22.64 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.
>2006-09-21 12:48:23.65 Server Attempting to initialize Microsoft
>Distributed Transaction Coordinator (MS DTC). This is an informational
>message only. No user action is required.
>2006-09-21 12:48:24.23 Server The Microsoft Distributed
>Transaction Coordinator (MS DTC) service could not be contacted. If
>you would like distributed transaction functionality, please start this
>service.
>2006-09-21 12:48:24.48 Server Database mirroring has been enabled
>on this instance of SQL Server.
>2006-09-21 12:48:24.84 spid5s Starting up database 'master'.
>2006-09-21 12:48:25.42 spid5s SQL Trace ID 1 was started by login
>"sa".
>2006-09-21 12:48:25.46 spid5s Starting up database
>'mssqlsystemresource'.
>2006-09-21 12:48:25.54 spid5s The resource database build version
>is 9.00.2047. This is an informational message only. No user action is
>required.
>2006-09-21 12:48:25.98 spid5s Server name is 'BLAHBLAH'. This is
>an informational message only. No user action is required.
>2006-09-21 12:48:25.98 spid9s Starting up database 'model'.
>2006-09-21 12:48:26.46 spid9s Clearing tempdb database.
>2006-09-21 12:48:30.10 spid9s Starting up database 'tempdb'.
>2006-09-21 12:48:30.54 spid12s The Service Broker protocol
>transport is disabled or not configured.
>2006-09-21 12:48:30.54 spid12s The Database Mirroring protocol
>transport is disabled or not configured.
>2006-09-21 12:48:31.12 spid12s Service Broker manager has started.
>2006-09-21 12:48:31.39 Server A self-generated certificate was
>successfully loaded for encryption.
>2006-09-21 12:48:31.40 Server Error: 26055, Severity: 16, State:
>1.
>2006-09-21 12:48:31.40 Server The SQL Server failed to initialize
>VIA support library [QLVipl.dll]. This normally indicates the VIA
>support library does not exist or is corrupted. Please repair or
>disable the VIA network protocol. Error: 0x7e.
>2006-09-21 12:48:31.42 Server Error: 17182, Severity: 16, State:
>1.
>2006-09-21 12:48:31.42 Server TDSSNIClient initialization failed
>with error 0x7e, status code 0x60.
>2006-09-21 12:48:31.43 Server Error: 17182, Severity: 16, State:
>1.
>2006-09-21 12:48:31.43 Server TDSSNIClient initialization failed
>with error 0x7e, status code 0x1.
>2006-09-21 12:48:31.43 Server Error: 17826, Severity: 18, State:
>3.
>2006-09-21 12:48:31.43 Server Could not start the network library
>because of an internal error in the network library. To determine the
>cause, review the errors immediately preceding this one in the error
>log.
>2006-09-21 12:48:31.43 Server Error: 17120, Severity: 16, State:
>1.
>2006-09-21 12:48:31.43 Server SQL Server could not spawn FRunCM
>thread. Check the SQL Server error log and the Windows event logs for
>information about possible related problems.
|||Yes. It was VIA protocol problem. Thanks.
Sue Hoegemeier wrote:[vbcol=seagreen]
> Are you using VIA? If not, try disabling the protocol using
> the SQL Server Configuration Manager.
> -Sue
> On 21 Sep 2006 21:58:12 -0700, "sara" <sarasara82@.gmail.com>
> wrote:

Connection Problem

Hi All,
I can not connect to sql serve 2005 using SQL Serve Management Studio,
I got these error in ERROR.LOG file. Any help is really appreciated.
Thanks.
2006-09-21 12:48:21.53 Server Microsoft SQL Server 2005 -
9.00.2047.00 (Intel X86)
Apr 14 2006 01:12:25
Copyright (c) 1988-2005 Microsoft Corporation
Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2006-09-21 12:48:21.54 Server (c) 2005 Microsoft Corporation.
2006-09-21 12:48:21.54 Server All rights reserved.
2006-09-21 12:48:21.54 Server Server process ID is 4948.
2006-09-21 12:48:21.54 Server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2006-09-21 12:48:21.54 Server This instance of SQL Server last
reported using a process ID of 4396 at 9/21/2006 1:05:02 AM (local)
9/21/2006 8:05:02 AM (UTC). This is an informational message only; no
user action is required.
2006-09-21 12:48:21.54 Server Registry startup parameters:
2006-09-21 12:48:21.59 Server -d C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\master.mdf
2006-09-21 12:48:21.59 Server -e C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2006-09-21 12:48:21.59 Server -l C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2006-09-21 12:48:21.64 Server SQL Server is starting at normal
priority base (=7). This is an informational message only. No user
action is required.
2006-09-21 12:48:21.64 Server Detected 2 CPUs. This is an
informational message; no user action is required.
2006-09-21 12:48:22.64 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.
2006-09-21 12:48:23.65 Server Attempting to initialize Microsoft
Distributed Transaction Coordinator (MS DTC). This is an informational
message only. No user action is required.
2006-09-21 12:48:24.23 Server The Microsoft Distributed
Transaction Coordinator (MS DTC) service could not be contacted. If
you would like distributed transaction functionality, please start this
service.
2006-09-21 12:48:24.48 Server Database mirroring has been enabled
on this instance of SQL Server.
2006-09-21 12:48:24.84 spid5s Starting up database 'master'.
2006-09-21 12:48:25.42 spid5s SQL Trace ID 1 was started by login
"sa".
2006-09-21 12:48:25.46 spid5s Starting up database
'mssqlsystemresource'.
2006-09-21 12:48:25.54 spid5s The resource database build version
is 9.00.2047. This is an informational message only. No user action is
required.
2006-09-21 12:48:25.98 spid5s Server name is 'BLAHBLAH'. This is
an informational message only. No user action is required.
2006-09-21 12:48:25.98 spid9s Starting up database 'model'.
2006-09-21 12:48:26.46 spid9s Clearing tempdb database.
2006-09-21 12:48:30.10 spid9s Starting up database 'tempdb'.
2006-09-21 12:48:30.54 spid12s The Service Broker protocol
transport is disabled or not configured.
2006-09-21 12:48:30.54 spid12s The Database Mirroring protocol
transport is disabled or not configured.
2006-09-21 12:48:31.12 spid12s Service Broker manager has started.
2006-09-21 12:48:31.39 Server A self-generated certificate was
successfully loaded for encryption.
2006-09-21 12:48:31.40 Server Error: 26055, Severity: 16, State:
1.
2006-09-21 12:48:31.40 Server The SQL Server failed to initialize
VIA support library [QLVipl.dll]. This normally indicates the VIA
support library does not exist or is corrupted. Please repair or
disable the VIA network protocol. Error: 0x7e.
2006-09-21 12:48:31.42 Server Error: 17182, Severity: 16, State:
1.
2006-09-21 12:48:31.42 Server TDSSNIClient initialization failed
with error 0x7e, status code 0x60.
2006-09-21 12:48:31.43 Server Error: 17182, Severity: 16, State:
1.
2006-09-21 12:48:31.43 Server TDSSNIClient initialization failed
with error 0x7e, status code 0x1.
2006-09-21 12:48:31.43 Server Error: 17826, Severity: 18, State:
3.
2006-09-21 12:48:31.43 Server Could not start the network library
because of an internal error in the network library. To determine the
cause, review the errors immediately preceding this one in the error
log.
2006-09-21 12:48:31.43 Server Error: 17120, Severity: 16, State:
1.
2006-09-21 12:48:31.43 Server SQL Server could not spawn FRunCM
thread. Check the SQL Server error log and the Windows event logs for
information about possible related problems.I googled for TDSSNIClient and had several hits, for instance
http://blogs.msdn.com/sql_protocols...31/487090.aspx.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"sara" <sarasara82@.gmail.com> wrote in message
news:1158882314.356874.272310@.h48g2000cwc.googlegroups.com...
> Hi All,
> I can not connect to sql serve 2005 using SQL Serve Management Studio,
> I got these error in ERROR.LOG file. Any help is really appreciated.
> Thanks.
> 2006-09-21 12:48:21.53 Server Microsoft SQL Server 2005 -
> 9.00.2047.00 (Intel X86)
> Apr 14 2006 01:12:25
> Copyright (c) 1988-2005 Microsoft Corporation
> Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
> 2006-09-21 12:48:21.54 Server (c) 2005 Microsoft Corporation.
> 2006-09-21 12:48:21.54 Server All rights reserved.
> 2006-09-21 12:48:21.54 Server Server process ID is 4948.
> 2006-09-21 12:48:21.54 Server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
> 2006-09-21 12:48:21.54 Server This instance of SQL Server last
> reported using a process ID of 4396 at 9/21/2006 1:05:02 AM (local)
> 9/21/2006 8:05:02 AM (UTC). This is an informational message only; no
> user action is required.
> 2006-09-21 12:48:21.54 Server Registry startup parameters:
> 2006-09-21 12:48:21.59 Server -d C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\DATA\master.mdf
> 2006-09-21 12:48:21.59 Server -e C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\LOG\ERRORLOG
> 2006-09-21 12:48:21.59 Server -l C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
> 2006-09-21 12:48:21.64 Server SQL Server is starting at normal
> priority base (=7). This is an informational message only. No user
> action is required.
> 2006-09-21 12:48:21.64 Server Detected 2 CPUs. This is an
> informational message; no user action is required.
> 2006-09-21 12:48:22.64 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.
> 2006-09-21 12:48:23.65 Server Attempting to initialize Microsoft
> Distributed Transaction Coordinator (MS DTC). This is an informational
> message only. No user action is required.
> 2006-09-21 12:48:24.23 Server The Microsoft Distributed
> Transaction Coordinator (MS DTC) service could not be contacted. If
> you would like distributed transaction functionality, please start this
> service.
> 2006-09-21 12:48:24.48 Server Database mirroring has been enabled
> on this instance of SQL Server.
> 2006-09-21 12:48:24.84 spid5s Starting up database 'master'.
> 2006-09-21 12:48:25.42 spid5s SQL Trace ID 1 was started by login
> "sa".
> 2006-09-21 12:48:25.46 spid5s Starting up database
> 'mssqlsystemresource'.
> 2006-09-21 12:48:25.54 spid5s The resource database build version
> is 9.00.2047. This is an informational message only. No user action is
> required.
> 2006-09-21 12:48:25.98 spid5s Server name is 'BLAHBLAH'. This is
> an informational message only. No user action is required.
> 2006-09-21 12:48:25.98 spid9s Starting up database 'model'.
> 2006-09-21 12:48:26.46 spid9s Clearing tempdb database.
> 2006-09-21 12:48:30.10 spid9s Starting up database 'tempdb'.
> 2006-09-21 12:48:30.54 spid12s The Service Broker protocol
> transport is disabled or not configured.
> 2006-09-21 12:48:30.54 spid12s The Database Mirroring protocol
> transport is disabled or not configured.
> 2006-09-21 12:48:31.12 spid12s Service Broker manager has started.
> 2006-09-21 12:48:31.39 Server A self-generated certificate was
> successfully loaded for encryption.
> 2006-09-21 12:48:31.40 Server Error: 26055, Severity: 16, State:
> 1.
> 2006-09-21 12:48:31.40 Server The SQL Server failed to initialize
> VIA support library [QLVipl.dll]. This normally indicates the VIA
> support library does not exist or is corrupted. Please repair or
> disable the VIA network protocol. Error: 0x7e.
> 2006-09-21 12:48:31.42 Server Error: 17182, Severity: 16, State:
> 1.
> 2006-09-21 12:48:31.42 Server TDSSNIClient initialization failed
> with error 0x7e, status code 0x60.
> 2006-09-21 12:48:31.43 Server Error: 17182, Severity: 16, State:
> 1.
> 2006-09-21 12:48:31.43 Server TDSSNIClient initialization failed
> with error 0x7e, status code 0x1.
> 2006-09-21 12:48:31.43 Server Error: 17826, Severity: 18, State:
> 3.
> 2006-09-21 12:48:31.43 Server Could not start the network library
> because of an internal error in the network library. To determine the
> cause, review the errors immediately preceding this one in the error
> log.
> 2006-09-21 12:48:31.43 Server Error: 17120, Severity: 16, State:
> 1.
> 2006-09-21 12:48:31.43 Server SQL Server could not spawn FRunCM
> thread. Check the SQL Server error log and the Windows event logs for
> information about possible related problems.
>

Tuesday, February 14, 2012

Connecting to to Sql server through ODBC

I am having problems accessing the sql server through ODBC.
I got the follong error:
Connection Failed:
SQL State: 01000
SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
(Connect()). Connection failed.
I then upgraded to Sql sp3a
Now I am receiving the error:
Connection Failed:
SQL State: 01000
SQL Server Error: 011001
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()). Connection failed.
Connection Failed:
SQL State: 08001
SQL Server Error: 6
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
Not found.
Let me give you an idea of our network structure and some of the issues:
We now have 2 servers. Win 2000 server and the Win 2003 server which is
running sql server 2000(This is a new server just bought).
The Win2000 server is running Active directory and is the main domain
controller.
The win 2003 server is not running Active directory.
I want all user to login to this server (Win 2000) and those requiring Great
Plains will then attach to the Win2003 Server after completing login to the
network through the win 2000 server.
The win 2003 server is running sql service pack3a
I can access shared folders on this Win 2003 server from Network places on
any machine on the network.
I can ping the 2003 server using the Ip address and Name.
Any ideas please?
--
cool ladyWas the SQL Server installed as the default or a named instance? What port
was it assigned to? What server name are you using in your ODBC connection?
Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
you have permission to connect to this SQL Server installation?
Sincerely,
Anthony Thomas
"Betmck" wrote:
> I am having problems accessing the sql server through ODBC.
> I got the follong error:
> Connection Failed:
> SQL State: 01000
> SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
> (Connect()). Connection failed.
> I then upgraded to Sql sp3a
> Now I am receiving the error:
> Connection Failed:
> SQL State: 01000
> SQL Server Error: 011001
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> (Connect()). Connection failed.
> Connection Failed:
> SQL State: 08001
> SQL Server Error: 6
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
> Not found.
>
> Let me give you an idea of our network structure and some of the issues:
> We now have 2 servers. Win 2000 server and the Win 2003 server which is
> running sql server 2000(This is a new server just bought).
> The Win2000 server is running Active directory and is the main domain
> controller.
> The win 2003 server is not running Active directory.
> I want all user to login to this server (Win 2000) and those requiring Great
> Plains will then attach to the Win2003 Server after completing login to the
> network through the win 2000 server.
> The win 2003 server is running sql service pack3a
> I can access shared folders on this Win 2003 server from Network places on
> any machine on the network.
> I can ping the 2003 server using the Ip address and Name.
> Any ideas please?
>
> --
> cool lady|||SQL Server installed with a named instance.
Port is 1433 which is automatically assigned
Server Name in the ODBC connection is SVBNTSQL\MBSGP
I have tried connecting via both Enterprise manager and query Analyzer.
Not sure if I have permission to connect. Where should I check for this?
Thanks
"AnthonyThomas" wrote:
> Was the SQL Server installed as the default or a named instance? What port
> was it assigned to? What server name are you using in your ODBC connection?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
> > I am having problems accessing the sql server through ODBC.
> > I got the follong error:
> >
> > Connection Failed:
> > SQL State: 01000
> > SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
> > (Connect()). Connection failed.
> >
> > I then upgraded to Sql sp3a
> >
> > Now I am receiving the error:
> >
> > Connection Failed:
> > SQL State: 01000
> > SQL Server Error: 011001
> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> > (Connect()). Connection failed.
> >
> > Connection Failed:
> > SQL State: 08001
> > SQL Server Error: 6
> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
> > Not found.
> >
> >
> > Let me give you an idea of our network structure and some of the issues:
> >
> > We now have 2 servers. Win 2000 server and the Win 2003 server which is
> > running sql server 2000(This is a new server just bought).
> >
> > The Win2000 server is running Active directory and is the main domain
> > controller.
> >
> > The win 2003 server is not running Active directory.
> >
> > I want all user to login to this server (Win 2000) and those requiring Great
> > Plains will then attach to the Win2003 Server after completing login to the
> > network through the win 2000 server.
> >
> > The win 2003 server is running sql service pack3a
> >
> > I can access shared folders on this Win 2003 server from Network places on
> > any machine on the network.
> >
> > I can ping the 2003 server using the Ip address and Name.
> >
> > Any ideas please?
> >
> >
> > --
> > cool lady|||I also tried to Telnet the sql server. If I just use the Ip adress alone I
will get through. When I attached 1433 at the end I get an error "could not
open a connection to host on port 1433: connect failed.
"AnthonyThomas" wrote:
> Was the SQL Server installed as the default or a named instance? What port
> was it assigned to? What server name are you using in your ODBC connection?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
> > I am having problems accessing the sql server through ODBC.
> > I got the follong error:
> >
> > Connection Failed:
> > SQL State: 01000
> > SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
> > (Connect()). Connection failed.
> >
> > I then upgraded to Sql sp3a
> >
> > Now I am receiving the error:
> >
> > Connection Failed:
> > SQL State: 01000
> > SQL Server Error: 011001
> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> > (Connect()). Connection failed.
> >
> > Connection Failed:
> > SQL State: 08001
> > SQL Server Error: 6
> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
> > Not found.
> >
> >
> > Let me give you an idea of our network structure and some of the issues:
> >
> > We now have 2 servers. Win 2000 server and the Win 2003 server which is
> > running sql server 2000(This is a new server just bought).
> >
> > The Win2000 server is running Active directory and is the main domain
> > controller.
> >
> > The win 2003 server is not running Active directory.
> >
> > I want all user to login to this server (Win 2000) and those requiring Great
> > Plains will then attach to the Win2003 Server after completing login to the
> > network through the win 2000 server.
> >
> > The win 2003 server is running sql service pack3a
> >
> > I can access shared folders on this Win 2003 server from Network places on
> > any machine on the network.
> >
> > I can ping the 2003 server using the Ip address and Name.
> >
> > Any ideas please?
> >
> >
> > --
> > cool lady|||This is what the error log.:
2004-11-08 14:37:30.40 server Microsoft SQL Server 2000 - 8.00.194
(Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: )
2004-11-08 14:37:30.40 server Copyright (C) 1988-2000 Microsoft
Corporation.
2004-11-08 14:37:30.40 server All rights reserved.
2004-11-08 14:37:30.40 server Server Process ID is 1532.
2004-11-08 14:37:30.40 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$MBSGP\log\ERRORLOG'.
2004-11-08 14:37:30.43 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2004-11-08 14:37:30.67 server SQL Server configured for thread mode
processing.
2004-11-08 14:37:30.68 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2004-11-08 14:37:30.71 server Attempting to initialize Distributed
Transaction Coordinator.
2004-11-08 14:37:35.48 spid4 Starting up database 'master'.
2004-11-08 14:37:40.40 server Using 'SSNETLIB.DLL' version '8.0.194'.
2004-11-08 14:37:40.40 spid5 Starting up database 'model'.
2004-11-08 14:37:40.40 spid4 Server name is 'SVBNTSQL\MBSGP'.
2004-11-08 14:37:40.40 spid8 Starting up database 'msdb'.
2004-11-08 14:37:40.40 spid9 Starting up database 'pubs'.
2004-11-08 14:37:40.40 spid10 Starting up database 'Northwind'.
2004-11-08 14:37:40.40 spid11 Starting up database 'DYNAMICS'.
2004-11-08 14:37:40.40 spid12 Starting up database 'TWO'.
2004-11-08 14:37:40.43 spid13 Starting up database 'SVB'.
2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
Named Pipes.
2004-11-08 14:37:40.43 server SQL Server is ready for client connections
2004-11-08 14:37:40.53 spid5 Clearing tempdb database.
2004-11-08 14:37:40.73 spid5 Starting up database 'tempdb'.
2004-11-08 14:37:40.75 spid4 Recovery complete.
2004-11-08 14:37:40.78 spid4 Launched startup procedure
'smDEX_Build_Locks'
2004-11-08 14:51:39.97 spid51 Using 'xpsqlbot.dll' version '2000.80.194'
to execute extended stored procedure 'xp_qv'.
2004-11-08 14:53:43.56 spid4 SQL Server is terminating due to 'stop'
request from Service Control Manager.
"AnthonyThomas" wrote:
> Was the SQL Server installed as the default or a named instance? What port
> was it assigned to? What server name are you using in your ODBC connection?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
> > I am having problems accessing the sql server through ODBC.
> > I got the follong error:
> >
> > Connection Failed:
> > SQL State: 01000
> > SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
> > (Connect()). Connection failed.
> >
> > I then upgraded to Sql sp3a
> >
> > Now I am receiving the error:
> >
> > Connection Failed:
> > SQL State: 01000
> > SQL Server Error: 011001
> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> > (Connect()). Connection failed.
> >
> > Connection Failed:
> > SQL State: 08001
> > SQL Server Error: 6
> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
> > Not found.
> >
> >
> > Let me give you an idea of our network structure and some of the issues:
> >
> > We now have 2 servers. Win 2000 server and the Win 2003 server which is
> > running sql server 2000(This is a new server just bought).
> >
> > The Win2000 server is running Active directory and is the main domain
> > controller.
> >
> > The win 2003 server is not running Active directory.
> >
> > I want all user to login to this server (Win 2000) and those requiring Great
> > Plains will then attach to the Win2003 Server after completing login to the
> > network through the win 2000 server.
> >
> > The win 2003 server is running sql service pack3a
> >
> > I can access shared folders on this Win 2003 server from Network places on
> > any machine on the network.
> >
> > I can ping the 2003 server using the Ip address and Name.
> >
> > Any ideas please?
> >
> >
> > --
> > cool lady|||Your server has not been set up to use TCP/IP. If you look at your error
log, about 1/3 of the way through, you will see the line:
2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
Named Pipes.
No, TCP/IP. Usually, this is because it was never selected as part of the
installation or there was an IP Bind error. The Bind error also would have
shown up in the list. On the server, you need to, or have your server admin,
run the Server Network utility and add the TCP/IP protocol to the list. You
will also have to specify the port. If the Named Instance is the only
instance, then you can use 1433.
Sincerely,
Anthony Thomas
"Betmck" wrote:
> This is what the error log.:
> 2004-11-08 14:37:30.40 server Microsoft SQL Server 2000 - 8.00.194
> (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Standard Edition on Windows NT 5.2 (Build 3790: )
> 2004-11-08 14:37:30.40 server Copyright (C) 1988-2000 Microsoft
> Corporation.
> 2004-11-08 14:37:30.40 server All rights reserved.
> 2004-11-08 14:37:30.40 server Server Process ID is 1532.
> 2004-11-08 14:37:30.40 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$MBSGP\log\ERRORLOG'.
> 2004-11-08 14:37:30.43 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2004-11-08 14:37:30.67 server SQL Server configured for thread mode
> processing.
> 2004-11-08 14:37:30.68 server Using dynamic lock allocation. [2500] Lock
> Blocks, [5000] Lock Owner Blocks.
> 2004-11-08 14:37:30.71 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2004-11-08 14:37:35.48 spid4 Starting up database 'master'.
> 2004-11-08 14:37:40.40 server Using 'SSNETLIB.DLL' version '8.0.194'.
> 2004-11-08 14:37:40.40 spid5 Starting up database 'model'.
> 2004-11-08 14:37:40.40 spid4 Server name is 'SVBNTSQL\MBSGP'.
> 2004-11-08 14:37:40.40 spid8 Starting up database 'msdb'.
> 2004-11-08 14:37:40.40 spid9 Starting up database 'pubs'.
> 2004-11-08 14:37:40.40 spid10 Starting up database 'Northwind'.
> 2004-11-08 14:37:40.40 spid11 Starting up database 'DYNAMICS'.
> 2004-11-08 14:37:40.40 spid12 Starting up database 'TWO'.
> 2004-11-08 14:37:40.43 spid13 Starting up database 'SVB'.
> 2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
> Named Pipes.
> 2004-11-08 14:37:40.43 server SQL Server is ready for client connections
> 2004-11-08 14:37:40.53 spid5 Clearing tempdb database.
> 2004-11-08 14:37:40.73 spid5 Starting up database 'tempdb'.
> 2004-11-08 14:37:40.75 spid4 Recovery complete.
> 2004-11-08 14:37:40.78 spid4 Launched startup procedure
> 'smDEX_Build_Locks'
> 2004-11-08 14:51:39.97 spid51 Using 'xpsqlbot.dll' version '2000.80.194'
> to execute extended stored procedure 'xp_qv'.
> 2004-11-08 14:53:43.56 spid4 SQL Server is terminating due to 'stop'
> request from Service Control Manager.
> "AnthonyThomas" wrote:
> > Was the SQL Server installed as the default or a named instance? What port
> > was it assigned to? What server name are you using in your ODBC connection?
> > Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> > you have permission to connect to this SQL Server installation?
> >
> > Sincerely,
> >
> >
> > Anthony Thomas
> >
> >
> > "Betmck" wrote:
> >
> > > I am having problems accessing the sql server through ODBC.
> > > I got the follong error:
> > >
> > > Connection Failed:
> > > SQL State: 01000
> > > SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
> > > (Connect()). Connection failed.
> > >
> > > I then upgraded to Sql sp3a
> > >
> > > Now I am receiving the error:
> > >
> > > Connection Failed:
> > > SQL State: 01000
> > > SQL Server Error: 011001
> > > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> > > (Connect()). Connection failed.
> > >
> > > Connection Failed:
> > > SQL State: 08001
> > > SQL Server Error: 6
> > > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
> > > Not found.
> > >
> > >
> > > Let me give you an idea of our network structure and some of the issues:
> > >
> > > We now have 2 servers. Win 2000 server and the Win 2003 server which is
> > > running sql server 2000(This is a new server just bought).
> > >
> > > The Win2000 server is running Active directory and is the main domain
> > > controller.
> > >
> > > The win 2003 server is not running Active directory.
> > >
> > > I want all user to login to this server (Win 2000) and those requiring Great
> > > Plains will then attach to the Win2003 Server after completing login to the
> > > network through the win 2000 server.
> > >
> > > The win 2003 server is running sql service pack3a
> > >
> > > I can access shared folders on this Win 2003 server from Network places on
> > > any machine on the network.
> > >
> > > I can ping the 2003 server using the Ip address and Name.
> > >
> > > Any ideas please?
> > >
> > >
> > > --
> > > cool lady|||Thanks for you help Anthony. However after taking a closer look at the error
log, I realize that Sql Sp3 was not installed properly. After installing it
again, everything is working fine now.
"AnthonyThomas" wrote:
> Your server has not been set up to use TCP/IP. If you look at your error
> log, about 1/3 of the way through, you will see the line:
> 2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
> Named Pipes.
> No, TCP/IP. Usually, this is because it was never selected as part of the
> installation or there was an IP Bind error. The Bind error also would have
> shown up in the list. On the server, you need to, or have your server admin,
> run the Server Network utility and add the TCP/IP protocol to the list. You
> will also have to specify the port. If the Named Instance is the only
> instance, then you can use 1433.
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
> > This is what the error log.:
> >
> > 2004-11-08 14:37:30.40 server Microsoft SQL Server 2000 - 8.00.194
> > (Intel X86)
> > Aug 6 2000 00:57:48
> > Copyright (c) 1988-2000 Microsoft Corporation
> > Standard Edition on Windows NT 5.2 (Build 3790: )
> >
> > 2004-11-08 14:37:30.40 server Copyright (C) 1988-2000 Microsoft
> > Corporation.
> > 2004-11-08 14:37:30.40 server All rights reserved.
> > 2004-11-08 14:37:30.40 server Server Process ID is 1532.
> > 2004-11-08 14:37:30.40 server Logging SQL Server messages in file
> > 'C:\Program Files\Microsoft SQL Server\MSSQL$MBSGP\log\ERRORLOG'.
> > 2004-11-08 14:37:30.43 server SQL Server is starting at priority class
> > 'normal'(2 CPUs detected).
> > 2004-11-08 14:37:30.67 server SQL Server configured for thread mode
> > processing.
> > 2004-11-08 14:37:30.68 server Using dynamic lock allocation. [2500] Lock
> > Blocks, [5000] Lock Owner Blocks.
> > 2004-11-08 14:37:30.71 server Attempting to initialize Distributed
> > Transaction Coordinator.
> > 2004-11-08 14:37:35.48 spid4 Starting up database 'master'.
> > 2004-11-08 14:37:40.40 server Using 'SSNETLIB.DLL' version '8.0.194'.
> > 2004-11-08 14:37:40.40 spid5 Starting up database 'model'.
> > 2004-11-08 14:37:40.40 spid4 Server name is 'SVBNTSQL\MBSGP'.
> > 2004-11-08 14:37:40.40 spid8 Starting up database 'msdb'.
> > 2004-11-08 14:37:40.40 spid9 Starting up database 'pubs'.
> > 2004-11-08 14:37:40.40 spid10 Starting up database 'Northwind'.
> > 2004-11-08 14:37:40.40 spid11 Starting up database 'DYNAMICS'.
> > 2004-11-08 14:37:40.40 spid12 Starting up database 'TWO'.
> > 2004-11-08 14:37:40.43 spid13 Starting up database 'SVB'.
> > 2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
> > Named Pipes.
> > 2004-11-08 14:37:40.43 server SQL Server is ready for client connections
> > 2004-11-08 14:37:40.53 spid5 Clearing tempdb database.
> > 2004-11-08 14:37:40.73 spid5 Starting up database 'tempdb'.
> > 2004-11-08 14:37:40.75 spid4 Recovery complete.
> > 2004-11-08 14:37:40.78 spid4 Launched startup procedure
> > 'smDEX_Build_Locks'
> > 2004-11-08 14:51:39.97 spid51 Using 'xpsqlbot.dll' version '2000.80.194'
> > to execute extended stored procedure 'xp_qv'.
> > 2004-11-08 14:53:43.56 spid4 SQL Server is terminating due to 'stop'
> > request from Service Control Manager.
> >
> > "AnthonyThomas" wrote:
> >
> > > Was the SQL Server installed as the default or a named instance? What port
> > > was it assigned to? What server name are you using in your ODBC connection?
> > > Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> > > you have permission to connect to this SQL Server installation?
> > >
> > > Sincerely,
> > >
> > >
> > > Anthony Thomas
> > >
> > >
> > > "Betmck" wrote:
> > >
> > > > I am having problems accessing the sql server through ODBC.
> > > > I got the follong error:
> > > >
> > > > Connection Failed:
> > > > SQL State: 01000
> > > > SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
> > > > (Connect()). Connection failed.
> > > >
> > > > I then upgraded to Sql sp3a
> > > >
> > > > Now I am receiving the error:
> > > >
> > > > Connection Failed:
> > > > SQL State: 01000
> > > > SQL Server Error: 011001
> > > > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> > > > (Connect()). Connection failed.
> > > >
> > > > Connection Failed:
> > > > SQL State: 08001
> > > > SQL Server Error: 6
> > > > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
> > > > Not found.
> > > >
> > > >
> > > > Let me give you an idea of our network structure and some of the issues:
> > > >
> > > > We now have 2 servers. Win 2000 server and the Win 2003 server which is
> > > > running sql server 2000(This is a new server just bought).
> > > >
> > > > The Win2000 server is running Active directory and is the main domain
> > > > controller.
> > > >
> > > > The win 2003 server is not running Active directory.
> > > >
> > > > I want all user to login to this server (Win 2000) and those requiring Great
> > > > Plains will then attach to the Win2003 Server after completing login to the
> > > > network through the win 2000 server.
> > > >
> > > > The win 2003 server is running sql service pack3a
> > > >
> > > > I can access shared folders on this Win 2003 server from Network places on
> > > > any machine on the network.
> > > >
> > > > I can ping the 2003 server using the Ip address and Name.
> > > >
> > > > Any ideas please?
> > > >
> > > >
> > > > --
> > > > cool lady

Tuesday, March 27, 2012

Connection Problem

Connection Problem

Sunday, March 25, 2012

Connection Problem

Connection Problem

Connection Problem

Tuesday, February 14, 2012

Connecting to to Sql server through ODBC

Connecting to to Sql server through ODBC

Connecting to to Sql server through ODBC

asp sql server

Blog Archive

About Me