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
Showing posts with label file. Show all posts
Showing posts with label file. Show all posts
Tuesday, March 27, 2012
Connection Problem
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.
>
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.
>
Labels:
appreciated,
connect,
connection,
database,
error,
file,
log,
management,
microsoft,
mysql,
oracle,
serve,
server,
sql,
studio
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.
>
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:
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.
>
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.
>
Thursday, March 22, 2012
connection pooling
is connection pooling something that can be used after moving tables from
mdb file to sql server 2000 and just relinking the tables via ODBC in the
front end file? Or is this something that must be setup in code?Connection pooling is on by default. It's typically used if you make and
break connections with the same connection string parameters. A web server
is a primary candidate for it's use.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.sqlsql
mdb file to sql server 2000 and just relinking the tables via ODBC in the
front end file? Or is this something that must be setup in code?Connection pooling is on by default. It's typically used if you make and
break connections with the same connection string parameters. A web server
is a primary candidate for it's use.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.sqlsql
connection pooling
is connection pooling something that can be used after moving tables from
mdb file to sql server 2000 and just relinking the tables via ODBC in the
front end file? Or is this something that must be setup in code?
Connection pooling is on by default. It's typically used if you make and
break connections with the same connection string parameters. A web server
is a primary candidate for it's use.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
mdb file to sql server 2000 and just relinking the tables via ODBC in the
front end file? Or is this something that must be setup in code?
Connection pooling is on by default. It's typically used if you make and
break connections with the same connection string parameters. A web server
is a primary candidate for it's use.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Connection Pool and MSSql driver
Hi all,
I'm trying to build an application using MSSQL Server and Connection pool.
At my server.xml file I have:
<Context path="/sample" docBase="C:/myprojects/sample" reloadable="true" >
<Resource name="jdbc/StrutsDemoDS" auth="Container"
type="javax.sql.DataSource" scope="Shareable"/>
<ResourceParams name="jdbc/StrutsDemoDS">
<parameter>
<name>factory</name><value>org.apache.commons.dbcp.BasicDataSourc eFactory</value></parameter>
<parameter><name>driverClassName</name><value>com.microsoft.jdbc.sqlserver.SQLServer Driver</value></parameter>
<parameter><name>url</name><value>jdbc:microsoft:sqlserver://myserver:1433</value></parameter>
<parameter><name>username</name><value>sa</value></parameter>
<parameter><name>password</name><value>passwd</value></parameter>
<parameter><name>maxActive</name><value>20</value></parameter>
<parameter><name>maxIdle</name><value>10</value></parameter>
<parameter><name>maxWait</name><value>100</value></parameter>
</ResourceParams>
</Context>
In my class, I have:
protected static DataSource dataSource;
protected Connection getConnection() throws SQLException {
InitialContext ic = new InitialContext();
dataSource = (DataSource)
ic.lookup("java:comp/env/jdbc/StrutsDemoDS");
Connection conn = null;
try {
conn = dataSource.getConnection(); // The error happens at this
line
}
catch (SQLException e) {
throw e;
}
return conn;
}
I can't get successful my connection. Can anyone tell me why?
Thanks.
Lorena
Lorena,
What is the error you're getting? Are you sure the lookup is successful?
If you write a simple class that doesn't use jndi but instead uses
DriverManager, Connection, and the normal db access stuff, with the
connectstring you're passing, can you connect?
Marc
"Lorena" <Lorena@.discussions.microsoft.com> wrote in message
news:E2508C07-F91E-40C2-BF64-34B7E8C23F58@.microsoft.com...
> Hi all,
> I'm trying to build an application using MSSQL Server and Connection pool.
> At my server.xml file I have:
> <Context path="/sample" docBase="C:/myprojects/sample" reloadable="true" >
> <Resource name="jdbc/StrutsDemoDS" auth="Container"
> type="javax.sql.DataSource" scope="Shareable"/>
> <ResourceParams name="jdbc/StrutsDemoDS">
> <parameter>
> <name>factory</name><value>org.apache.commons.dbcp.BasicDataSourc eFactory</value></parameter>
> <parameter><name>driverClassName</name><value>com.microsoft.jdbc.sqlserver.SQLServer Driver</value></parameter>
> <parameter><name>url</name><value>jdbc:microsoft:sqlserver://myserver:1433</value></parameter>
> <parameter><name>username</name><value>sa</value></parameter>
> <parameter><name>password</name><value>passwd</value></parameter>
> <parameter><name>maxActive</name><value>20</value></parameter>
> <parameter><name>maxIdle</name><value>10</value></parameter>
> <parameter><name>maxWait</name><value>100</value></parameter>
> </ResourceParams>
> </Context>
> In my class, I have:
> protected static DataSource dataSource;
> protected Connection getConnection() throws SQLException {
> InitialContext ic = new InitialContext();
> dataSource = (DataSource)
> ic.lookup("java:comp/env/jdbc/StrutsDemoDS");
> Connection conn = null;
> try {
> conn = dataSource.getConnection(); // The error happens at
> this
> line
> }
> catch (SQLException e) {
> throw e;
> }
> return conn;
> }
> I can't get successful my connection. Can anyone tell me why?
> Thanks.
> Lorena
I'm trying to build an application using MSSQL Server and Connection pool.
At my server.xml file I have:
<Context path="/sample" docBase="C:/myprojects/sample" reloadable="true" >
<Resource name="jdbc/StrutsDemoDS" auth="Container"
type="javax.sql.DataSource" scope="Shareable"/>
<ResourceParams name="jdbc/StrutsDemoDS">
<parameter>
<name>factory</name><value>org.apache.commons.dbcp.BasicDataSourc eFactory</value></parameter>
<parameter><name>driverClassName</name><value>com.microsoft.jdbc.sqlserver.SQLServer Driver</value></parameter>
<parameter><name>url</name><value>jdbc:microsoft:sqlserver://myserver:1433</value></parameter>
<parameter><name>username</name><value>sa</value></parameter>
<parameter><name>password</name><value>passwd</value></parameter>
<parameter><name>maxActive</name><value>20</value></parameter>
<parameter><name>maxIdle</name><value>10</value></parameter>
<parameter><name>maxWait</name><value>100</value></parameter>
</ResourceParams>
</Context>
In my class, I have:
protected static DataSource dataSource;
protected Connection getConnection() throws SQLException {
InitialContext ic = new InitialContext();
dataSource = (DataSource)
ic.lookup("java:comp/env/jdbc/StrutsDemoDS");
Connection conn = null;
try {
conn = dataSource.getConnection(); // The error happens at this
line
}
catch (SQLException e) {
throw e;
}
return conn;
}
I can't get successful my connection. Can anyone tell me why?
Thanks.
Lorena
Lorena,
What is the error you're getting? Are you sure the lookup is successful?
If you write a simple class that doesn't use jndi but instead uses
DriverManager, Connection, and the normal db access stuff, with the
connectstring you're passing, can you connect?
Marc
"Lorena" <Lorena@.discussions.microsoft.com> wrote in message
news:E2508C07-F91E-40C2-BF64-34B7E8C23F58@.microsoft.com...
> Hi all,
> I'm trying to build an application using MSSQL Server and Connection pool.
> At my server.xml file I have:
> <Context path="/sample" docBase="C:/myprojects/sample" reloadable="true" >
> <Resource name="jdbc/StrutsDemoDS" auth="Container"
> type="javax.sql.DataSource" scope="Shareable"/>
> <ResourceParams name="jdbc/StrutsDemoDS">
> <parameter>
> <name>factory</name><value>org.apache.commons.dbcp.BasicDataSourc eFactory</value></parameter>
> <parameter><name>driverClassName</name><value>com.microsoft.jdbc.sqlserver.SQLServer Driver</value></parameter>
> <parameter><name>url</name><value>jdbc:microsoft:sqlserver://myserver:1433</value></parameter>
> <parameter><name>username</name><value>sa</value></parameter>
> <parameter><name>password</name><value>passwd</value></parameter>
> <parameter><name>maxActive</name><value>20</value></parameter>
> <parameter><name>maxIdle</name><value>10</value></parameter>
> <parameter><name>maxWait</name><value>100</value></parameter>
> </ResourceParams>
> </Context>
> In my class, I have:
> protected static DataSource dataSource;
> protected Connection getConnection() throws SQLException {
> InitialContext ic = new InitialContext();
> dataSource = (DataSource)
> ic.lookup("java:comp/env/jdbc/StrutsDemoDS");
> Connection conn = null;
> try {
> conn = dataSource.getConnection(); // The error happens at
> this
> line
> }
> catch (SQLException e) {
> throw e;
> }
> return conn;
> }
> I can't get successful my connection. Can anyone tell me why?
> Thanks.
> Lorena
Tuesday, March 20, 2012
Connection Open (Create File()) /SQL server registration
Hello,
i have SQL 7.0 servers A, B, C, D
when tryin to register server (mmC) A on B,C,D i get the errormessage
"Client unable to establish connection Connection Open (Create File())"
This worked 2 weeks ago.. and we didn't change anything..
Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
have this problem
THX a lot
PIrmincheck connection with QA
try TCP and NP connection
"Pirmin" wrote:
> Hello,
> i have SQL 7.0 servers A, B, C, D
> when tryin to register server (mmC) A on B,C,D i get the errormessage
> "Client unable to establish connection Connection Open (Create File())"
> This worked 2 weeks ago.. and we didn't change anything..
> Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> have this problem
> THX a lot
> PIrmin|||Hi,
sorry.. your answer was litl short 4 me..
wht do you mean with "check connection with QA"
Where do i set the connection frm TCP to NamedPipes on the
ServerRegistration..
Thx
Pirmin
"Aleksandar Grbic" wrote:
> check connection with QA
> try TCP and NP connection
> "Pirmin" wrote:
> > Hello,
> >
> > i have SQL 7.0 servers A, B, C, D
> > when tryin to register server (mmC) A on B,C,D i get the errormessage
> > "Client unable to establish connection Connection Open (Create File())"
> >
> > This worked 2 weeks ago.. and we didn't change anything..
> > Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> > have this problem
> >
> > THX a lot
> > PIrmin|||you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
check connectivity with sql server
use tcp:<server> to connect with tcp
or
use np:<server> to connect with Named Pipes
later, configure Client Network utility to use one of these protocol and try
connect from mmc
"Pirmin" wrote:
> Hi,
> sorry.. your answer was litl short 4 me..
> wht do you mean with "check connection with QA"
> Where do i set the connection frm TCP to NamedPipes on the
> ServerRegistration..
> Thx
> Pirmin
> "Aleksandar Grbic" wrote:
> > check connection with QA
> > try TCP and NP connection
> >
> > "Pirmin" wrote:
> >
> > > Hello,
> > >
> > > i have SQL 7.0 servers A, B, C, D
> > > when tryin to register server (mmC) A on B,C,D i get the errormessage
> > > "Client unable to establish connection Connection Open (Create File())"
> > >
> > > This worked 2 weeks ago.. and we didn't change anything..
> > > Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> > > have this problem
> > >
> > > THX a lot
> > > PIrmin|||THX,
well i can't connect via NP nor TCP..
(Pinging works..)
Also checked
"SQL server network config"
TCP and NP are configured..
Anyother idea?
THX
Pirmin
"Aleksandar Grbic" wrote:
> you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
> check connectivity with sql server
> use tcp:<server> to connect with tcp
> or
> use np:<server> to connect with Named Pipes
> later, configure Client Network utility to use one of these protocol and try
> connect from mmc
>
> "Pirmin" wrote:
> > Hi,
> >
> > sorry.. your answer was litl short 4 me..
> > wht do you mean with "check connection with QA"
> > Where do i set the connection frm TCP to NamedPipes on the
> > ServerRegistration..
> >
> > Thx
> >
> > Pirmin
> >
> > "Aleksandar Grbic" wrote:
> >
> > > check connection with QA
> > > try TCP and NP connection
> > >
> > > "Pirmin" wrote:
> > >
> > > > Hello,
> > > >
> > > > i have SQL 7.0 servers A, B, C, D
> > > > when tryin to register server (mmC) A on B,C,D i get the errormessage
> > > > "Client unable to establish connection Connection Open (Create File())"
> > > >
> > > > This worked 2 weeks ago.. and we didn't change anything..
> > > > Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> > > > have this problem
> > > >
> > > > THX a lot
> > > > PIrmin|||firewall?
consult your network admin?
can you connect from server A?
server A listen on 1433?
"Pirmin" wrote:
> THX,
> well i can't connect via NP nor TCP..
> (Pinging works..)
> Also checked
> "SQL server network config"
> TCP and NP are configured..
> Anyother idea?
> THX
> Pirmin
> "Aleksandar Grbic" wrote:
> > you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
> > check connectivity with sql server
> >
> > use tcp:<server> to connect with tcp
> > or
> > use np:<server> to connect with Named Pipes
> >
> > later, configure Client Network utility to use one of these protocol and try
> > connect from mmc
> >
> >
> > "Pirmin" wrote:
> >
> > > Hi,
> > >
> > > sorry.. your answer was litl short 4 me..
> > > wht do you mean with "check connection with QA"
> > > Where do i set the connection frm TCP to NamedPipes on the
> > > ServerRegistration..
> > >
> > > Thx
> > >
> > > Pirmin
> > >
> > > "Aleksandar Grbic" wrote:
> > >
> > > > check connection with QA
> > > > try TCP and NP connection
> > > >
> > > > "Pirmin" wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > i have SQL 7.0 servers A, B, C, D
> > > > > when tryin to register server (mmC) A on B,C,D i get the errormessage
> > > > > "Client unable to establish connection Connection Open (Create File())"
> > > > >
> > > > > This worked 2 weeks ago.. and we didn't change anything..
> > > > > Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> > > > > have this problem
> > > > >
> > > > > THX a lot
> > > > > PIrmin
i have SQL 7.0 servers A, B, C, D
when tryin to register server (mmC) A on B,C,D i get the errormessage
"Client unable to establish connection Connection Open (Create File())"
This worked 2 weeks ago.. and we didn't change anything..
Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
have this problem
THX a lot
PIrmincheck connection with QA
try TCP and NP connection
"Pirmin" wrote:
> Hello,
> i have SQL 7.0 servers A, B, C, D
> when tryin to register server (mmC) A on B,C,D i get the errormessage
> "Client unable to establish connection Connection Open (Create File())"
> This worked 2 weeks ago.. and we didn't change anything..
> Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> have this problem
> THX a lot
> PIrmin|||Hi,
sorry.. your answer was litl short 4 me..
wht do you mean with "check connection with QA"
Where do i set the connection frm TCP to NamedPipes on the
ServerRegistration..
Thx
Pirmin
"Aleksandar Grbic" wrote:
> check connection with QA
> try TCP and NP connection
> "Pirmin" wrote:
> > Hello,
> >
> > i have SQL 7.0 servers A, B, C, D
> > when tryin to register server (mmC) A on B,C,D i get the errormessage
> > "Client unable to establish connection Connection Open (Create File())"
> >
> > This worked 2 weeks ago.. and we didn't change anything..
> > Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> > have this problem
> >
> > THX a lot
> > PIrmin|||you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
check connectivity with sql server
use tcp:<server> to connect with tcp
or
use np:<server> to connect with Named Pipes
later, configure Client Network utility to use one of these protocol and try
connect from mmc
"Pirmin" wrote:
> Hi,
> sorry.. your answer was litl short 4 me..
> wht do you mean with "check connection with QA"
> Where do i set the connection frm TCP to NamedPipes on the
> ServerRegistration..
> Thx
> Pirmin
> "Aleksandar Grbic" wrote:
> > check connection with QA
> > try TCP and NP connection
> >
> > "Pirmin" wrote:
> >
> > > Hello,
> > >
> > > i have SQL 7.0 servers A, B, C, D
> > > when tryin to register server (mmC) A on B,C,D i get the errormessage
> > > "Client unable to establish connection Connection Open (Create File())"
> > >
> > > This worked 2 weeks ago.. and we didn't change anything..
> > > Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> > > have this problem
> > >
> > > THX a lot
> > > PIrmin|||THX,
well i can't connect via NP nor TCP..
(Pinging works..)
Also checked
"SQL server network config"
TCP and NP are configured..
Anyother idea?
THX
Pirmin
"Aleksandar Grbic" wrote:
> you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
> check connectivity with sql server
> use tcp:<server> to connect with tcp
> or
> use np:<server> to connect with Named Pipes
> later, configure Client Network utility to use one of these protocol and try
> connect from mmc
>
> "Pirmin" wrote:
> > Hi,
> >
> > sorry.. your answer was litl short 4 me..
> > wht do you mean with "check connection with QA"
> > Where do i set the connection frm TCP to NamedPipes on the
> > ServerRegistration..
> >
> > Thx
> >
> > Pirmin
> >
> > "Aleksandar Grbic" wrote:
> >
> > > check connection with QA
> > > try TCP and NP connection
> > >
> > > "Pirmin" wrote:
> > >
> > > > Hello,
> > > >
> > > > i have SQL 7.0 servers A, B, C, D
> > > > when tryin to register server (mmC) A on B,C,D i get the errormessage
> > > > "Client unable to establish connection Connection Open (Create File())"
> > > >
> > > > This worked 2 weeks ago.. and we didn't change anything..
> > > > Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> > > > have this problem
> > > >
> > > > THX a lot
> > > > PIrmin|||firewall?
consult your network admin?
can you connect from server A?
server A listen on 1433?
"Pirmin" wrote:
> THX,
> well i can't connect via NP nor TCP..
> (Pinging works..)
> Also checked
> "SQL server network config"
> TCP and NP are configured..
> Anyother idea?
> THX
> Pirmin
> "Aleksandar Grbic" wrote:
> > you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
> > check connectivity with sql server
> >
> > use tcp:<server> to connect with tcp
> > or
> > use np:<server> to connect with Named Pipes
> >
> > later, configure Client Network utility to use one of these protocol and try
> > connect from mmc
> >
> >
> > "Pirmin" wrote:
> >
> > > Hi,
> > >
> > > sorry.. your answer was litl short 4 me..
> > > wht do you mean with "check connection with QA"
> > > Where do i set the connection frm TCP to NamedPipes on the
> > > ServerRegistration..
> > >
> > > Thx
> > >
> > > Pirmin
> > >
> > > "Aleksandar Grbic" wrote:
> > >
> > > > check connection with QA
> > > > try TCP and NP connection
> > > >
> > > > "Pirmin" wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > i have SQL 7.0 servers A, B, C, D
> > > > > when tryin to register server (mmC) A on B,C,D i get the errormessage
> > > > > "Client unable to establish connection Connection Open (Create File())"
> > > > >
> > > > > This worked 2 weeks ago.. and we didn't change anything..
> > > > > Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> > > > > have this problem
> > > > >
> > > > > THX a lot
> > > > > PIrmin
Connection Open (Create File()) /SQL server registration
Hello,
i have SQL 7.0 servers A, B, C, D
when tryin to register server (mmC) A on B,C,D i get the errormessage
"Client unable to establish connection Connection Open (Create File())"
This worked 2 weeks ago.. and we didn't change anything..
Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
have this problem
THX a lot
PIrmin
check connection with QA
try TCP and NP connection
"Pirmin" wrote:
> Hello,
> i have SQL 7.0 servers A, B, C, D
> when tryin to register server (mmC) A on B,C,D i get the errormessage
> "Client unable to establish connection Connection Open (Create File())"
> This worked 2 weeks ago.. and we didn't change anything..
> Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> have this problem
> THX a lot
> PIrmin
|||Hi,
sorry.. your answer was litl short 4 me..
wht do you mean with "check connection with QA"
Where do i set the connection frm TCP to NamedPipes on the
ServerRegistration..
Thx
Pirmin
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> check connection with QA
> try TCP and NP connection
> "Pirmin" wrote:
|||you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
check connectivity with sql server
use tcp:<server> to connect with tcp
or
use np:<server> to connect with Named Pipes
later, configure Client Network utility to use one of these protocol and try
connect from mmc
"Pirmin" wrote:
[vbcol=seagreen]
> Hi,
> sorry.. your answer was litl short 4 me..
> wht do you mean with "check connection with QA"
> Where do i set the connection frm TCP to NamedPipes on the
> ServerRegistration..
> Thx
> Pirmin
> "Aleksandar Grbic" wrote:
|||THX,
well i can't connect via NP nor TCP..
(Pinging works..)
Also checked
"SQL server network config"
TCP and NP are configured..
Anyother idea?
THX
Pirmin
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
> check connectivity with sql server
> use tcp:<server> to connect with tcp
> or
> use np:<server> to connect with Named Pipes
> later, configure Client Network utility to use one of these protocol and try
> connect from mmc
>
> "Pirmin" wrote:
|||firewall?
consult your network admin?
can you connect from server A?
server A listen on 1433?
"Pirmin" wrote:
[vbcol=seagreen]
> THX,
> well i can't connect via NP nor TCP..
> (Pinging works..)
> Also checked
> "SQL server network config"
> TCP and NP are configured..
> Anyother idea?
> THX
> Pirmin
> "Aleksandar Grbic" wrote:
i have SQL 7.0 servers A, B, C, D
when tryin to register server (mmC) A on B,C,D i get the errormessage
"Client unable to establish connection Connection Open (Create File())"
This worked 2 weeks ago.. and we didn't change anything..
Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
have this problem
THX a lot
PIrmin
check connection with QA
try TCP and NP connection
"Pirmin" wrote:
> Hello,
> i have SQL 7.0 servers A, B, C, D
> when tryin to register server (mmC) A on B,C,D i get the errormessage
> "Client unable to establish connection Connection Open (Create File())"
> This worked 2 weeks ago.. and we didn't change anything..
> Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> have this problem
> THX a lot
> PIrmin
|||Hi,
sorry.. your answer was litl short 4 me..
wht do you mean with "check connection with QA"
Where do i set the connection frm TCP to NamedPipes on the
ServerRegistration..
Thx
Pirmin
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> check connection with QA
> try TCP and NP connection
> "Pirmin" wrote:
|||you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
check connectivity with sql server
use tcp:<server> to connect with tcp
or
use np:<server> to connect with Named Pipes
later, configure Client Network utility to use one of these protocol and try
connect from mmc
"Pirmin" wrote:
[vbcol=seagreen]
> Hi,
> sorry.. your answer was litl short 4 me..
> wht do you mean with "check connection with QA"
> Where do i set the connection frm TCP to NamedPipes on the
> ServerRegistration..
> Thx
> Pirmin
> "Aleksandar Grbic" wrote:
|||THX,
well i can't connect via NP nor TCP..
(Pinging works..)
Also checked
"SQL server network config"
TCP and NP are configured..
Anyother idea?
THX
Pirmin
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
> check connectivity with sql server
> use tcp:<server> to connect with tcp
> or
> use np:<server> to connect with Named Pipes
> later, configure Client Network utility to use one of these protocol and try
> connect from mmc
>
> "Pirmin" wrote:
|||firewall?
consult your network admin?
can you connect from server A?
server A listen on 1433?
"Pirmin" wrote:
[vbcol=seagreen]
> THX,
> well i can't connect via NP nor TCP..
> (Pinging works..)
> Also checked
> "SQL server network config"
> TCP and NP are configured..
> Anyother idea?
> THX
> Pirmin
> "Aleksandar Grbic" wrote:
Connection Open (Create File()) /SQL server registration
Hello,
i have SQL 7.0 servers A, B, C, D
when tryin to register server (mmC) A on B,C,D i get the errormessage
"Client unable to establish connection Connection Open (Create File())"
This worked 2 weeks ago.. and we didn't change anything..
Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
have this problem
THX a lot
PIrmincheck connection with QA
try TCP and NP connection
"Pirmin" wrote:
> Hello,
> i have SQL 7.0 servers A, B, C, D
> when tryin to register server (mmC) A on B,C,D i get the errormessage
> "Client unable to establish connection Connection Open (Create File())"
> This worked 2 weeks ago.. and we didn't change anything..
> Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> have this problem
> THX a lot
> PIrmin|||Hi,
sorry.. your answer was litl short 4 me..
wht do you mean with "check connection with QA"
Where do i set the connection frm TCP to NamedPipes on the
ServerRegistration..
Thx
Pirmin
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> check connection with QA
> try TCP and NP connection
> "Pirmin" wrote:
>|||you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
check connectivity with sql server
use tcp:<server> to connect with tcp
or
use np:<server> to connect with Named Pipes
later, configure Client Network utility to use one of these protocol and try
connect from mmc
"Pirmin" wrote:
[vbcol=seagreen]
> Hi,
> sorry.. your answer was litl short 4 me..
> wht do you mean with "check connection with QA"
> Where do i set the connection frm TCP to NamedPipes on the
> ServerRegistration..
> Thx
> Pirmin
> "Aleksandar Grbic" wrote:
>|||THX,
well i can't connect via NP nor TCP..
(Pinging works..)
Also checked
"SQL server network config"
TCP and NP are configured..
Anyother idea?
THX
Pirmin
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
> check connectivity with sql server
> use tcp:<server> to connect with tcp
> or
> use np:<server> to connect with Named Pipes
> later, configure Client Network utility to use one of these protocol and t
ry
> connect from mmc
>
> "Pirmin" wrote:
>|||firewall?
consult your network admin?
can you connect from server A?
server A listen on 1433?
"Pirmin" wrote:
[vbcol=seagreen]
> THX,
> well i can't connect via NP nor TCP..
> (Pinging works..)
> Also checked
> "SQL server network config"
> TCP and NP are configured..
> Anyother idea?
> THX
> Pirmin
> "Aleksandar Grbic" wrote:
>sqlsql
i have SQL 7.0 servers A, B, C, D
when tryin to register server (mmC) A on B,C,D i get the errormessage
"Client unable to establish connection Connection Open (Create File())"
This worked 2 weeks ago.. and we didn't change anything..
Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
have this problem
THX a lot
PIrmincheck connection with QA
try TCP and NP connection
"Pirmin" wrote:
> Hello,
> i have SQL 7.0 servers A, B, C, D
> when tryin to register server (mmC) A on B,C,D i get the errormessage
> "Client unable to establish connection Connection Open (Create File())"
> This worked 2 weeks ago.. and we didn't change anything..
> Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> have this problem
> THX a lot
> PIrmin|||Hi,
sorry.. your answer was litl short 4 me..
wht do you mean with "check connection with QA"
Where do i set the connection frm TCP to NamedPipes on the
ServerRegistration..
Thx
Pirmin
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> check connection with QA
> try TCP and NP connection
> "Pirmin" wrote:
>|||you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
check connectivity with sql server
use tcp:<server> to connect with tcp
or
use np:<server> to connect with Named Pipes
later, configure Client Network utility to use one of these protocol and try
connect from mmc
"Pirmin" wrote:
[vbcol=seagreen]
> Hi,
> sorry.. your answer was litl short 4 me..
> wht do you mean with "check connection with QA"
> Where do i set the connection frm TCP to NamedPipes on the
> ServerRegistration..
> Thx
> Pirmin
> "Aleksandar Grbic" wrote:
>|||THX,
well i can't connect via NP nor TCP..
(Pinging works..)
Also checked
"SQL server network config"
TCP and NP are configured..
Anyother idea?
THX
Pirmin
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
> check connectivity with sql server
> use tcp:<server> to connect with tcp
> or
> use np:<server> to connect with Named Pipes
> later, configure Client Network utility to use one of these protocol and t
ry
> connect from mmc
>
> "Pirmin" wrote:
>|||firewall?
consult your network admin?
can you connect from server A?
server A listen on 1433?
"Pirmin" wrote:
[vbcol=seagreen]
> THX,
> well i can't connect via NP nor TCP..
> (Pinging works..)
> Also checked
> "SQL server network config"
> TCP and NP are configured..
> Anyother idea?
> THX
> Pirmin
> "Aleksandar Grbic" wrote:
>sqlsql
Monday, March 19, 2012
Connection Manager ignores expressions with script component
I have written a script source component and attached a flat file connection. The connection string of which is defined by an expression.
However when I get the connectionstring from the connection in the script it has the default filename value of flat file not the value of the expression. This is proved by passing in the filename variable, and comparing the 2.
The flat file has an expression on the ConnectionString of @.[User::filename]
Can someone confirm this is a bug.
Is this any help to you: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=295220&SiteID=1
-Jamie
|||Looks like it, needs some clarification though.Friday, February 24, 2012
Connection count alert
I`m trying to setup an alert in Windows to shoot an email when the
connections on SQL server exceed a preset amount. The alert will fire
a bat file that executes an OSQL script that sends the email alert.
When I test the .bat file alone it`s fine but when combined with the
alert monitor nothing happens. Any ideas or is there a better way to
achieve the same result?
AF
Is it SQL Server 2000?
"AF" <af.at.work@.gmail.com> wrote in message
news:1170683093.895427.186510@.h3g2000cwc.googlegro ups.com...
> I`m trying to setup an alert in Windows to shoot an email when the
> connections on SQL server exceed a preset amount. The alert will fire
> a bat file that executes an OSQL script that sends the email alert.
> When I test the .bat file alone it`s fine but when combined with the
> alert monitor nothing happens. Any ideas or is there a better way to
> achieve the same result?
>
|||On Feb 5, 8:52 am, "Uri Dimant" <u...@.iscar.co.il> wrote:[vbcol=seagreen]
> AF
> Is it SQL Server 2000?
> "AF" <af.at.w...@.gmail.com> wrote in message
> news:1170683093.895427.186510@.h3g2000cwc.googlegro ups.com...
Yes, sorry it is SQL 2000 Enterprise on Windows Server 2003 Enterprise.
|||On Feb 5, 10:03 am, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:[vbcol=seagreen]
> How about downloading xp_smtp_sendmail fromwww.sqldev.net, and schedule a job which does a SELECT
> COUNT(*) FROM sysprocesses and if > desired number you send the email using xp_smtp_sendmail?
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> "AF" <af.at.w...@.gmail.com> wrote in message
> news:1170684161.788906.278200@.a34g2000cwb.googlegr oups.com...
>
>
ah, good idea. I will try that.
connections on SQL server exceed a preset amount. The alert will fire
a bat file that executes an OSQL script that sends the email alert.
When I test the .bat file alone it`s fine but when combined with the
alert monitor nothing happens. Any ideas or is there a better way to
achieve the same result?
AF
Is it SQL Server 2000?
"AF" <af.at.work@.gmail.com> wrote in message
news:1170683093.895427.186510@.h3g2000cwc.googlegro ups.com...
> I`m trying to setup an alert in Windows to shoot an email when the
> connections on SQL server exceed a preset amount. The alert will fire
> a bat file that executes an OSQL script that sends the email alert.
> When I test the .bat file alone it`s fine but when combined with the
> alert monitor nothing happens. Any ideas or is there a better way to
> achieve the same result?
>
|||On Feb 5, 8:52 am, "Uri Dimant" <u...@.iscar.co.il> wrote:[vbcol=seagreen]
> AF
> Is it SQL Server 2000?
> "AF" <af.at.w...@.gmail.com> wrote in message
> news:1170683093.895427.186510@.h3g2000cwc.googlegro ups.com...
Yes, sorry it is SQL 2000 Enterprise on Windows Server 2003 Enterprise.
|||On Feb 5, 10:03 am, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:[vbcol=seagreen]
> How about downloading xp_smtp_sendmail fromwww.sqldev.net, and schedule a job which does a SELECT
> COUNT(*) FROM sysprocesses and if > desired number you send the email using xp_smtp_sendmail?
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> "AF" <af.at.w...@.gmail.com> wrote in message
> news:1170684161.788906.278200@.a34g2000cwb.googlegr oups.com...
>
>
ah, good idea. I will try that.
Connection count alert
I`m trying to setup an alert in Windows to shoot an email when the
connections on SQL server exceed a preset amount. The alert will fire
a bat file that executes an OSQL script that sends the email alert.
When I test the .bat file alone it`s fine but when combined with the
alert monitor nothing happens. Any ideas or is there a better way to
achieve the same result?AF
Is it SQL Server 2000?
"AF" <af.at.work@.gmail.com> wrote in message
news:1170683093.895427.186510@.h3g2000cwc.googlegroups.com...
> I`m trying to setup an alert in Windows to shoot an email when the
> connections on SQL server exceed a preset amount. The alert will fire
> a bat file that executes an OSQL script that sends the email alert.
> When I test the .bat file alone it`s fine but when combined with the
> alert monitor nothing happens. Any ideas or is there a better way to
> achieve the same result?
>|||On Feb 5, 8:52 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> AF
> Is it SQL Server 2000?
> "AF" <af.at.w...@.gmail.com> wrote in message
> news:1170683093.895427.186510@.h3g2000cwc.googlegroups.com...
> > I`m trying to setup an alert in Windows to shoot an email when the
> > connections on SQL server exceed a preset amount. The alert will fire
> > a bat file that executes an OSQL script that sends the email alert.
> > When I test the .bat file alone it`s fine but when combined with the
> > alert monitor nothing happens. Any ideas or is there a better way to
> > achieve the same result?
Yes, sorry it is SQL 2000 Enterprise on Windows Server 2003 Enterprise.|||How about downloading xp_smtp_sendmail from www.sqldev.net, and schedule a job which does a SELECT
COUNT(*) FROM sysprocesses and if > desired number you send the email using xp_smtp_sendmail?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"AF" <af.at.work@.gmail.com> wrote in message
news:1170684161.788906.278200@.a34g2000cwb.googlegroups.com...
> On Feb 5, 8:52 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
>> AF
>> Is it SQL Server 2000?
>> "AF" <af.at.w...@.gmail.com> wrote in message
>> news:1170683093.895427.186510@.h3g2000cwc.googlegroups.com...
>> > I`m trying to setup an alert in Windows to shoot an email when the
>> > connections on SQL server exceed a preset amount. The alert will fire
>> > a bat file that executes an OSQL script that sends the email alert.
>> > When I test the .bat file alone it`s fine but when combined with the
>> > alert monitor nothing happens. Any ideas or is there a better way to
>> > achieve the same result?
> Yes, sorry it is SQL 2000 Enterprise on Windows Server 2003 Enterprise.
>|||On Feb 5, 10:03 am, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> How about downloading xp_smtp_sendmail fromwww.sqldev.net, and schedule a job which does a SELECT
> COUNT(*) FROM sysprocesses and if > desired number you send the email using xp_smtp_sendmail?
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> "AF" <af.at.w...@.gmail.com> wrote in message
> news:1170684161.788906.278200@.a34g2000cwb.googlegroups.com...
> > On Feb 5, 8:52 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> >> AF
> >> Is it SQL Server 2000?
> >> "AF" <af.at.w...@.gmail.com> wrote in message
> >>news:1170683093.895427.186510@.h3g2000cwc.googlegroups.com...
> >> > I`m trying to setup an alert in Windows to shoot an email when the
> >> > connections on SQL server exceed a preset amount. The alert will fire
> >> > a bat file that executes an OSQL script that sends the email alert.
> >> > When I test the .bat file alone it`s fine but when combined with the
> >> > alert monitor nothing happens. Any ideas or is there a better way to
> >> > achieve the same result?
> > Yes, sorry it is SQL 2000 Enterprise on Windows Server 2003 Enterprise.
ah, good idea. I will try that.
connections on SQL server exceed a preset amount. The alert will fire
a bat file that executes an OSQL script that sends the email alert.
When I test the .bat file alone it`s fine but when combined with the
alert monitor nothing happens. Any ideas or is there a better way to
achieve the same result?AF
Is it SQL Server 2000?
"AF" <af.at.work@.gmail.com> wrote in message
news:1170683093.895427.186510@.h3g2000cwc.googlegroups.com...
> I`m trying to setup an alert in Windows to shoot an email when the
> connections on SQL server exceed a preset amount. The alert will fire
> a bat file that executes an OSQL script that sends the email alert.
> When I test the .bat file alone it`s fine but when combined with the
> alert monitor nothing happens. Any ideas or is there a better way to
> achieve the same result?
>|||On Feb 5, 8:52 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> AF
> Is it SQL Server 2000?
> "AF" <af.at.w...@.gmail.com> wrote in message
> news:1170683093.895427.186510@.h3g2000cwc.googlegroups.com...
> > I`m trying to setup an alert in Windows to shoot an email when the
> > connections on SQL server exceed a preset amount. The alert will fire
> > a bat file that executes an OSQL script that sends the email alert.
> > When I test the .bat file alone it`s fine but when combined with the
> > alert monitor nothing happens. Any ideas or is there a better way to
> > achieve the same result?
Yes, sorry it is SQL 2000 Enterprise on Windows Server 2003 Enterprise.|||How about downloading xp_smtp_sendmail from www.sqldev.net, and schedule a job which does a SELECT
COUNT(*) FROM sysprocesses and if > desired number you send the email using xp_smtp_sendmail?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"AF" <af.at.work@.gmail.com> wrote in message
news:1170684161.788906.278200@.a34g2000cwb.googlegroups.com...
> On Feb 5, 8:52 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
>> AF
>> Is it SQL Server 2000?
>> "AF" <af.at.w...@.gmail.com> wrote in message
>> news:1170683093.895427.186510@.h3g2000cwc.googlegroups.com...
>> > I`m trying to setup an alert in Windows to shoot an email when the
>> > connections on SQL server exceed a preset amount. The alert will fire
>> > a bat file that executes an OSQL script that sends the email alert.
>> > When I test the .bat file alone it`s fine but when combined with the
>> > alert monitor nothing happens. Any ideas or is there a better way to
>> > achieve the same result?
> Yes, sorry it is SQL 2000 Enterprise on Windows Server 2003 Enterprise.
>|||On Feb 5, 10:03 am, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> How about downloading xp_smtp_sendmail fromwww.sqldev.net, and schedule a job which does a SELECT
> COUNT(*) FROM sysprocesses and if > desired number you send the email using xp_smtp_sendmail?
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> "AF" <af.at.w...@.gmail.com> wrote in message
> news:1170684161.788906.278200@.a34g2000cwb.googlegroups.com...
> > On Feb 5, 8:52 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> >> AF
> >> Is it SQL Server 2000?
> >> "AF" <af.at.w...@.gmail.com> wrote in message
> >>news:1170683093.895427.186510@.h3g2000cwc.googlegroups.com...
> >> > I`m trying to setup an alert in Windows to shoot an email when the
> >> > connections on SQL server exceed a preset amount. The alert will fire
> >> > a bat file that executes an OSQL script that sends the email alert.
> >> > When I test the .bat file alone it`s fine but when combined with the
> >> > alert monitor nothing happens. Any ideas or is there a better way to
> >> > achieve the same result?
> > Yes, sorry it is SQL 2000 Enterprise on Windows Server 2003 Enterprise.
ah, good idea. I will try that.
Connection count alert
I`m trying to setup an alert in Windows to shoot an email when the
connections on SQL server exceed a preset amount. The alert will fire
a bat file that executes an OSQL script that sends the email alert.
When I test the .bat file alone it`s fine but when combined with the
alert monitor nothing happens. Any ideas or is there a better way to
achieve the same result?AF
Is it SQL Server 2000?
"AF" <af.at.work@.gmail.com> wrote in message
news:1170683093.895427.186510@.h3g2000cwc.googlegroups.com...
> I`m trying to setup an alert in Windows to shoot an email when the
> connections on SQL server exceed a preset amount. The alert will fire
> a bat file that executes an OSQL script that sends the email alert.
> When I test the .bat file alone it`s fine but when combined with the
> alert monitor nothing happens. Any ideas or is there a better way to
> achieve the same result?
>|||On Feb 5, 8:52 am, "Uri Dimant" <u...@.iscar.co.il> wrote:[vbcol=seagreen]
> AF
> Is it SQL Server 2000?
> "AF" <af.at.w...@.gmail.com> wrote in message
> news:1170683093.895427.186510@.h3g2000cwc.googlegroups.com...
>
Yes, sorry it is SQL 2000 Enterprise on Windows Server 2003 Enterprise.|||How about downloading xp_smtp_sendmail from www.sqldev.net, and schedule a j
ob which does a SELECT
COUNT(*) FROM sysprocesses and if > desired number you send the email using
xp_smtp_sendmail?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"AF" <af.at.work@.gmail.com> wrote in message
news:1170684161.788906.278200@.a34g2000cwb.googlegroups.com...
> On Feb 5, 8:52 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Yes, sorry it is SQL 2000 Enterprise on Windows Server 2003 Enterprise.
>|||On Feb 5, 10:03 am, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:[vbcol=seagreen]
> How about downloading xp_smtp_sendmail fromwww.sqldev.net, and schedule a
job which does a SELECT
> COUNT(*) FROM sysprocesses and if > desired number you send the email usin
g xp_smtp_sendmail?
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asph
ttp://sqlblog.com/blogs/tibor_karaszi
> "AF" <af.at.w...@.gmail.com> wrote in message
> news:1170684161.788906.278200@.a34g2000cwb.googlegroups.com...
>
>
>
>
>
ah, good idea. I will try that.
connections on SQL server exceed a preset amount. The alert will fire
a bat file that executes an OSQL script that sends the email alert.
When I test the .bat file alone it`s fine but when combined with the
alert monitor nothing happens. Any ideas or is there a better way to
achieve the same result?AF
Is it SQL Server 2000?
"AF" <af.at.work@.gmail.com> wrote in message
news:1170683093.895427.186510@.h3g2000cwc.googlegroups.com...
> I`m trying to setup an alert in Windows to shoot an email when the
> connections on SQL server exceed a preset amount. The alert will fire
> a bat file that executes an OSQL script that sends the email alert.
> When I test the .bat file alone it`s fine but when combined with the
> alert monitor nothing happens. Any ideas or is there a better way to
> achieve the same result?
>|||On Feb 5, 8:52 am, "Uri Dimant" <u...@.iscar.co.il> wrote:[vbcol=seagreen]
> AF
> Is it SQL Server 2000?
> "AF" <af.at.w...@.gmail.com> wrote in message
> news:1170683093.895427.186510@.h3g2000cwc.googlegroups.com...
>
Yes, sorry it is SQL 2000 Enterprise on Windows Server 2003 Enterprise.|||How about downloading xp_smtp_sendmail from www.sqldev.net, and schedule a j
ob which does a SELECT
COUNT(*) FROM sysprocesses and if > desired number you send the email using
xp_smtp_sendmail?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"AF" <af.at.work@.gmail.com> wrote in message
news:1170684161.788906.278200@.a34g2000cwb.googlegroups.com...
> On Feb 5, 8:52 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Yes, sorry it is SQL 2000 Enterprise on Windows Server 2003 Enterprise.
>|||On Feb 5, 10:03 am, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:[vbcol=seagreen]
> How about downloading xp_smtp_sendmail fromwww.sqldev.net, and schedule a
job which does a SELECT
> COUNT(*) FROM sysprocesses and if > desired number you send the email usin
g xp_smtp_sendmail?
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asph
ttp://sqlblog.com/blogs/tibor_karaszi
> "AF" <af.at.w...@.gmail.com> wrote in message
> news:1170684161.788906.278200@.a34g2000cwb.googlegroups.com...
>
>
>
>
>
ah, good idea. I will try that.
Sunday, February 19, 2012
Connection and /share file and printer/ option in Windows firewall
Hello
Is there any relation between SQL2005 connection and /share file and
printer/ option in Windows firewall?
When I check the option I can connect from remote client via script, while
not that when I unchecked the option.
I can't easily believe the two entities are related. I checked over and over
again...
If my script matters,
set con=createobject("adodb.connection")
login3="provider=SQLOLEDB; server=w3a; Initial Catalog=air;
Trusted_connection=yes; "
con.open login3
msgbox con.stateOn Dec 26 2006, 2:18 pm, "Han" <hp4...@.kornet.net.korea> wrote:
> Hello
> Is there any relation between SQL2005 connection and /share file andprinte
r/ option in Windows firewall?
> When I check the option I can connect from remote client via script, while
> not that when I unchecked the option.
> I can't easily believe the two entities are related. I checked over and ov
er
> again...
> If my script matters,
> set con=createobject("adodb.connection")
> login3="provider=SQLOLEDB; server=w3a; Initial Catalog=air;
> Trusted_connection=yes; "
> con.open login3
> msgbox con.state
I again experiencde same phenomena? Do anyone know about that?
Is there any relation between SQL2005 connection and /share file and
printer/ option in Windows firewall?
When I check the option I can connect from remote client via script, while
not that when I unchecked the option.
I can't easily believe the two entities are related. I checked over and over
again...
If my script matters,
set con=createobject("adodb.connection")
login3="provider=SQLOLEDB; server=w3a; Initial Catalog=air;
Trusted_connection=yes; "
con.open login3
msgbox con.stateOn Dec 26 2006, 2:18 pm, "Han" <hp4...@.kornet.net.korea> wrote:
> Hello
> Is there any relation between SQL2005 connection and /share file andprinte
r/ option in Windows firewall?
> When I check the option I can connect from remote client via script, while
> not that when I unchecked the option.
> I can't easily believe the two entities are related. I checked over and ov
er
> again...
> If my script matters,
> set con=createobject("adodb.connection")
> login3="provider=SQLOLEDB; server=w3a; Initial Catalog=air;
> Trusted_connection=yes; "
> con.open login3
> msgbox con.state
I again experiencde same phenomena? Do anyone know about that?
Connection and /share file and printer/ option in Windows firewall
Hello
Is there any relation between SQL2005 connection and /share file and
printer/ option in Windows firewall?
When I check the option I can connect from remote client via script, while
not that when I unchecked the option.
I can't easily believe the two entities are related. I checked over and over
again...
If my script matters,
set con=createobject("adodb.connection")
login3="provider=SQLOLEDB; server=w3a; Initial Catalog=air;
Trusted_connection=yes; "
con.open login3
msgbox con.state
On Dec 26 2006, 2:18 pm, "Han" <hp4...@.kornet.net.korea> wrote:
> Hello
> Is there any relation between SQL2005 connection and /share file andprinter/ option in Windows firewall?
> When I check the option I can connect from remote client via script, while
> not that when I unchecked the option.
> I can't easily believe the two entities are related. I checked over and over
> again...
> If my script matters,
> set con=createobject("adodb.connection")
> login3="provider=SQLOLEDB; server=w3a; Initial Catalog=air;
> Trusted_connection=yes; "
> con.open login3
> msgbox con.state
I again experiencde same phenomena? Do anyone know about that?
Is there any relation between SQL2005 connection and /share file and
printer/ option in Windows firewall?
When I check the option I can connect from remote client via script, while
not that when I unchecked the option.
I can't easily believe the two entities are related. I checked over and over
again...
If my script matters,
set con=createobject("adodb.connection")
login3="provider=SQLOLEDB; server=w3a; Initial Catalog=air;
Trusted_connection=yes; "
con.open login3
msgbox con.state
On Dec 26 2006, 2:18 pm, "Han" <hp4...@.kornet.net.korea> wrote:
> Hello
> Is there any relation between SQL2005 connection and /share file andprinter/ option in Windows firewall?
> When I check the option I can connect from remote client via script, while
> not that when I unchecked the option.
> I can't easily believe the two entities are related. I checked over and over
> again...
> If my script matters,
> set con=createobject("adodb.connection")
> login3="provider=SQLOLEDB; server=w3a; Initial Catalog=air;
> Trusted_connection=yes; "
> con.open login3
> msgbox con.state
I again experiencde same phenomena? Do anyone know about that?
connection
Hi
I get this error from sql server 2005 developer edition on windows. I ca't
seem to get any connection to work sqlnative client og file connection. I
have installed all features from the sql developer dvd.
* The connection "SourceConnectionOLEDB" is not found. This error is thrown
by Connections collection when the specific connection element is not found.
({58517491-4481-44D8-BD05-DAA10CBF420E})
/rkri
Have you enabled TCP/IP on your SQL Server developer edition installation? I
think it is disabled by default. Check the Configuration Manager.
Ben Nevarez, M.Sc.
MCDBA, OCP
"Ren K" <rkri000@.foa.dk> wrote in message
news:ObaCPXQ$FHA.356@.TK2MSFTNGP12.phx.gbl...
> Hi
> I get this error from sql server 2005 developer edition on windows. I
> ca't
> seem to get any connection to work sqlnative client og file connection. I
> have installed all features from the sql developer dvd.
> * The connection "SourceConnectionOLEDB" is not found. This error is
> thrown
> by Connections collection when the specific connection element is not
> found.
> ({58517491-4481-44D8-BD05-DAA10CBF420E})
> /rkri
>
>
|||I have a installed the sql server 2005 on a named instance called sql2005
and this is running side-by-side with sqlexpress and msde ( 2000). my tcp/tp
is enabled i checked this under protocols for sql2005, I have enabled named
pipes and shared memory ( this was enabled by default ). I don't understand
I never had any problems whatsoever with sql server 2000 and are already
looking forward to the first service pack.
Thanks for the reply
/rkri
"Ben Nevarez" <bnevarez@.sjm.com> skrev i en meddelelse
news:uJhHClQ$FHA.4028@.tk2msftngp13.phx.gbl...
> Have you enabled TCP/IP on your SQL Server developer edition installation?
> I think it is disabled by default. Check the Configuration Manager.
> Ben Nevarez, M.Sc.
> MCDBA, OCP
>
> "Ren K" <rkri000@.foa.dk> wrote in message
> news:ObaCPXQ$FHA.356@.TK2MSFTNGP12.phx.gbl...
>
I get this error from sql server 2005 developer edition on windows. I ca't
seem to get any connection to work sqlnative client og file connection. I
have installed all features from the sql developer dvd.
* The connection "SourceConnectionOLEDB" is not found. This error is thrown
by Connections collection when the specific connection element is not found.
({58517491-4481-44D8-BD05-DAA10CBF420E})
/rkri
Have you enabled TCP/IP on your SQL Server developer edition installation? I
think it is disabled by default. Check the Configuration Manager.
Ben Nevarez, M.Sc.
MCDBA, OCP
"Ren K" <rkri000@.foa.dk> wrote in message
news:ObaCPXQ$FHA.356@.TK2MSFTNGP12.phx.gbl...
> Hi
> I get this error from sql server 2005 developer edition on windows. I
> ca't
> seem to get any connection to work sqlnative client og file connection. I
> have installed all features from the sql developer dvd.
> * The connection "SourceConnectionOLEDB" is not found. This error is
> thrown
> by Connections collection when the specific connection element is not
> found.
> ({58517491-4481-44D8-BD05-DAA10CBF420E})
> /rkri
>
>
|||I have a installed the sql server 2005 on a named instance called sql2005
and this is running side-by-side with sqlexpress and msde ( 2000). my tcp/tp
is enabled i checked this under protocols for sql2005, I have enabled named
pipes and shared memory ( this was enabled by default ). I don't understand
I never had any problems whatsoever with sql server 2000 and are already
looking forward to the first service pack.
Thanks for the reply
/rkri
"Ben Nevarez" <bnevarez@.sjm.com> skrev i en meddelelse
news:uJhHClQ$FHA.4028@.tk2msftngp13.phx.gbl...
> Have you enabled TCP/IP on your SQL Server developer edition installation?
> I think it is disabled by default. Check the Configuration Manager.
> Ben Nevarez, M.Sc.
> MCDBA, OCP
>
> "Ren K" <rkri000@.foa.dk> wrote in message
> news:ObaCPXQ$FHA.356@.TK2MSFTNGP12.phx.gbl...
>
connection
Hi
I get this error from sql server 2005 developer edition on windows. I ca't
seem to get any connection to work sqlnative client og file connection. I
have installed all features from the sql developer dvd.
* The connection "SourceConnectionOLEDB" is not found. This error is thrown
by Connections collection when the specific connection element is not found.
({58517491-4481-44D8-BD05-DAA10CBF420E})
/rkriHave you enabled TCP/IP on your SQL Server developer edition installation? I
think it is disabled by default. Check the Configuration Manager.
Ben Nevarez, M.Sc.
MCDBA, OCP
"Ren K" <rkri000@.foa.dk> wrote in message
news:ObaCPXQ$FHA.356@.TK2MSFTNGP12.phx.gbl...
> Hi
> I get this error from sql server 2005 developer edition on windows. I
> ca't
> seem to get any connection to work sqlnative client og file connection. I
> have installed all features from the sql developer dvd.
> * The connection "SourceConnectionOLEDB" is not found. This error is
> thrown
> by Connections collection when the specific connection element is not
> found.
> ({58517491-4481-44D8-BD05-DAA10CBF420E})
> /rkri
>
>|||I have a installed the sql server 2005 on a named instance called sql2005
and this is running side-by-side with sqlexpress and msde ( 2000). my tcp/tp
is enabled i checked this under protocols for sql2005, I have enabled named
pipes and shared memory ( this was enabled by default ). I don't understand
I never had any problems whatsoever with sql server 2000 and are already
looking forward to the first service pack.
Thanks for the reply
/rkri
"Ben Nevarez" <bnevarez@.sjm.com> skrev i en meddelelse
news:uJhHClQ$FHA.4028@.tk2msftngp13.phx.gbl...
> Have you enabled TCP/IP on your SQL Server developer edition installation?
> I think it is disabled by default. Check the Configuration Manager.
> Ben Nevarez, M.Sc.
> MCDBA, OCP
>
> "Ren K" <rkri000@.foa.dk> wrote in message
> news:ObaCPXQ$FHA.356@.TK2MSFTNGP12.phx.gbl...
>
I get this error from sql server 2005 developer edition on windows. I ca't
seem to get any connection to work sqlnative client og file connection. I
have installed all features from the sql developer dvd.
* The connection "SourceConnectionOLEDB" is not found. This error is thrown
by Connections collection when the specific connection element is not found.
({58517491-4481-44D8-BD05-DAA10CBF420E})
/rkriHave you enabled TCP/IP on your SQL Server developer edition installation? I
think it is disabled by default. Check the Configuration Manager.
Ben Nevarez, M.Sc.
MCDBA, OCP
"Ren K" <rkri000@.foa.dk> wrote in message
news:ObaCPXQ$FHA.356@.TK2MSFTNGP12.phx.gbl...
> Hi
> I get this error from sql server 2005 developer edition on windows. I
> ca't
> seem to get any connection to work sqlnative client og file connection. I
> have installed all features from the sql developer dvd.
> * The connection "SourceConnectionOLEDB" is not found. This error is
> thrown
> by Connections collection when the specific connection element is not
> found.
> ({58517491-4481-44D8-BD05-DAA10CBF420E})
> /rkri
>
>|||I have a installed the sql server 2005 on a named instance called sql2005
and this is running side-by-side with sqlexpress and msde ( 2000). my tcp/tp
is enabled i checked this under protocols for sql2005, I have enabled named
pipes and shared memory ( this was enabled by default ). I don't understand
I never had any problems whatsoever with sql server 2000 and are already
looking forward to the first service pack.
Thanks for the reply
/rkri
"Ben Nevarez" <bnevarez@.sjm.com> skrev i en meddelelse
news:uJhHClQ$FHA.4028@.tk2msftngp13.phx.gbl...
> Have you enabled TCP/IP on your SQL Server developer edition installation?
> I think it is disabled by default. Check the Configuration Manager.
> Ben Nevarez, M.Sc.
> MCDBA, OCP
>
> "Ren K" <rkri000@.foa.dk> wrote in message
> news:ObaCPXQ$FHA.356@.TK2MSFTNGP12.phx.gbl...
>
Friday, February 17, 2012
connection
Hi
I get this error from sql server 2005 developer edition on windows. I ca't
seem to get any connection to work sqlnative client og file connection. I
have installed all features from the sql developer dvd.
* The connection "SourceConnectionOLEDB" is not found. This error is thrown
by Connections collection when the specific connection element is not found.
({58517491-4481-44D8-BD05-DAA10CBF420E})
/rkriHave you enabled TCP/IP on your SQL Server developer edition installation? I
think it is disabled by default. Check the Configuration Manager.
Ben Nevarez, M.Sc.
MCDBA, OCP
"René K" <rkri000@.foa.dk> wrote in message
news:ObaCPXQ$FHA.356@.TK2MSFTNGP12.phx.gbl...
> Hi
> I get this error from sql server 2005 developer edition on windows. I
> ca't
> seem to get any connection to work sqlnative client og file connection. I
> have installed all features from the sql developer dvd.
> * The connection "SourceConnectionOLEDB" is not found. This error is
> thrown
> by Connections collection when the specific connection element is not
> found.
> ({58517491-4481-44D8-BD05-DAA10CBF420E})
> /rkri
>
>|||I have a installed the sql server 2005 on a named instance called sql2005
and this is running side-by-side with sqlexpress and msde ( 2000). my tcp/tp
is enabled i checked this under protocols for sql2005, I have enabled named
pipes and shared memory ( this was enabled by default ). I don't understand
I never had any problems whatsoever with sql server 2000 and are already
looking forward to the first service pack.
Thanks for the reply
/rkri
"Ben Nevarez" <bnevarez@.sjm.com> skrev i en meddelelse
news:uJhHClQ$FHA.4028@.tk2msftngp13.phx.gbl...
> Have you enabled TCP/IP on your SQL Server developer edition installation?
> I think it is disabled by default. Check the Configuration Manager.
> Ben Nevarez, M.Sc.
> MCDBA, OCP
>
> "René K" <rkri000@.foa.dk> wrote in message
> news:ObaCPXQ$FHA.356@.TK2MSFTNGP12.phx.gbl...
>> Hi
>> I get this error from sql server 2005 developer edition on windows. I
>> ca't
>> seem to get any connection to work sqlnative client og file connection. I
>> have installed all features from the sql developer dvd.
>> * The connection "SourceConnectionOLEDB" is not found. This error is
>> thrown
>> by Connections collection when the specific connection element is not
>> found.
>> ({58517491-4481-44D8-BD05-DAA10CBF420E})
>> /rkri
>>
>
I get this error from sql server 2005 developer edition on windows. I ca't
seem to get any connection to work sqlnative client og file connection. I
have installed all features from the sql developer dvd.
* The connection "SourceConnectionOLEDB" is not found. This error is thrown
by Connections collection when the specific connection element is not found.
({58517491-4481-44D8-BD05-DAA10CBF420E})
/rkriHave you enabled TCP/IP on your SQL Server developer edition installation? I
think it is disabled by default. Check the Configuration Manager.
Ben Nevarez, M.Sc.
MCDBA, OCP
"René K" <rkri000@.foa.dk> wrote in message
news:ObaCPXQ$FHA.356@.TK2MSFTNGP12.phx.gbl...
> Hi
> I get this error from sql server 2005 developer edition on windows. I
> ca't
> seem to get any connection to work sqlnative client og file connection. I
> have installed all features from the sql developer dvd.
> * The connection "SourceConnectionOLEDB" is not found. This error is
> thrown
> by Connections collection when the specific connection element is not
> found.
> ({58517491-4481-44D8-BD05-DAA10CBF420E})
> /rkri
>
>|||I have a installed the sql server 2005 on a named instance called sql2005
and this is running side-by-side with sqlexpress and msde ( 2000). my tcp/tp
is enabled i checked this under protocols for sql2005, I have enabled named
pipes and shared memory ( this was enabled by default ). I don't understand
I never had any problems whatsoever with sql server 2000 and are already
looking forward to the first service pack.
Thanks for the reply
/rkri
"Ben Nevarez" <bnevarez@.sjm.com> skrev i en meddelelse
news:uJhHClQ$FHA.4028@.tk2msftngp13.phx.gbl...
> Have you enabled TCP/IP on your SQL Server developer edition installation?
> I think it is disabled by default. Check the Configuration Manager.
> Ben Nevarez, M.Sc.
> MCDBA, OCP
>
> "René K" <rkri000@.foa.dk> wrote in message
> news:ObaCPXQ$FHA.356@.TK2MSFTNGP12.phx.gbl...
>> Hi
>> I get this error from sql server 2005 developer edition on windows. I
>> ca't
>> seem to get any connection to work sqlnative client og file connection. I
>> have installed all features from the sql developer dvd.
>> * The connection "SourceConnectionOLEDB" is not found. This error is
>> thrown
>> by Connections collection when the specific connection element is not
>> found.
>> ({58517491-4481-44D8-BD05-DAA10CBF420E})
>> /rkri
>>
>
Subscribe to:
Posts (Atom)