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:
>sqlsql

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.
>

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.
>

Connection information in a table trigger?

Is it possible to log or insert into a table the connection information (Application & Login) from an table trigger?

We have tough problem where data in a particular table is getting 'wiped-out' (rows are getting set to all NULLs) and we are unable to correlate this with any particular piece of software. My hope is that we can write an table trigger that can log or create an row in a temp table or the like to allow us to track this down to the offending application so that we can finallly get rid of the problem entirely.

Thanks,

You really should be using Profiler for this kind of activity. It will be able to give you more information than a TRIGGER. Profiler will allow you to capture the entire query (or queries) that are being sent to the server.

A TRIGGER would only allow you to log parameter and system values -NOT the actual query.

|||

Agree with Arnie for the most part, you can use profiler for this most likely. You would want to get really granular and track statements inside procedures too. You might also filter on the name of the table. Profiler can be kind of noisy/picky, so it might take a few tries, but it is the greatest thing to have in a crisis

As far as a trigger, you can get some of this information from sys.sysprocesses (or master.dbo.sysprocesses for 2000 and earlier.) You could join some of the values with the values in the inserted and deleted tables to see what is happening at a granular way. What I might do is to add a trigger that does:

if exists (select * from inserted where columnIDon'tWantSetToNull is null)

begin

raiserror ('DON''T DO THIS!',16,1)

rollback transaction

end

insert into log

select inserted.key, sysprocesses.columns
from inserted
join sysprocesses

on sysprocesses.spid = @.@.spid

If the operation was not in a transaction, you will get a log row, but your data will certainly not be hosed. If your application/process doesn't just ignore errors, you can track it down that way.

|||

Thank you both for your help. I'm not very good/handy with profiler, but I'll give it a try if I don't get anywhere with it, I'll try with an trigger on the table and the sysprocess table information.

George

|||

You definitely need to get good with profiler. In my opinion, it is the greatest thing about SQL Server, and for a person who has worked only with SQL Server for 15 years, that is saying something. Diagnosing problems with SQL Server is so much easier than pretty much any other programming tool, simply because I can see, immediately what the "heathen" user is trying to do to it and stop them.

Of course it has made it easy to simply force the DBA to prove that the database is not the culprit first since it is so easy, but that is another story

|||

How do I see the parameter values sent in a parameterized query in Profiler?

George

|||Profiler will show you the entire query, with parameters placed in the correct locations.

Connection fails and currupt log

One of our customers has SQL server 2000 installed
This has been working perfectly for over a year
Now various databases have started to return errors when queries are
run on the data from VB or Query Analyser.
A typical error is:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckForData()).
Server: Msg 11, Level 16, State 1, Line 0
General Network Error. Check your network documentation
Connection broken
Not all the database produce errors but there appears to be no pattern
to which databases still work.
I have two backup copies of the main database they use. The main
database its self and one of the backups produce errors yet the other
backup, taken on the same day does not.
Looking at the error log (attached) there seems to be a lot of
"corrupt" entires.
Any suggestions* If you see corruption, then --
1. Check system and app event logs for details on any hardware corruption.
2. contact your hardware vendors to run some tests, diagnostics, etc and
also check for firmware upgrades.
3. Only then, RESTORE from your last healthy SQL Backup.
4. If you dont have a backup, then you could try to "Repair" the database
using "dbcc checkdb".
Thanks,
Vikram
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

connection failed... not associated with a trusted SQL Server connection

Using Query Analyser, I cannot log in using the SQL 'sa' user name and
password. I get an error saying "connection failed... not associated with a
trusted SQL Server connection" When and where can the 'sa' credential be
used without creating this error?
thanks,
KeithHi,
Change the authentication mode to Windows and SQL server and try connecting
using SA.
How to change:-
1. In Enterprise Manager -- Expand the Server
2. Right click on the server name and select propertirs
3. Choose the security Tab and select SQL Server and Windows
4. Click ok and restart the windows service.
Thanks
hari
SQL Server MVP
"keithb" <k31thb@.yahoo.com> wrote in message
news:utbk$LIuFHA.3740@.TK2MSFTNGP14.phx.gbl...
> Using Query Analyser, I cannot log in using the SQL 'sa' user name and
> password. I get an error saying "connection failed... not associated with
> a trusted SQL Server connection" When and where can the 'sa' credential be
> used without creating this error?
> thanks,
> Keith
>

connection failed... not associated with a trusted SQL Server connection

Using Query Analyser, I cannot log in using the SQL 'sa' user name and
password. I get an error saying "connection failed... not associated with a
trusted SQL Server connection" When and where can the 'sa' credential be
used without creating this error?
thanks,
Keith
Hi,
Change the authentication mode to Windows and SQL server and try connecting
using SA.
How to change:-
1. In Enterprise Manager -- Expand the Server
2. Right click on the server name and select propertirs
3. Choose the security Tab and select SQL Server and Windows
4. Click ok and restart the windows service.
Thanks
hari
SQL Server MVP
"keithb" <k31thb@.yahoo.com> wrote in message
news:utbk$LIuFHA.3740@.TK2MSFTNGP14.phx.gbl...
> Using Query Analyser, I cannot log in using the SQL 'sa' user name and
> password. I get an error saying "connection failed... not associated with
> a trusted SQL Server connection" When and where can the 'sa' credential be
> used without creating this error?
> thanks,
> Keith
>