asp sql server: studio

Showing posts with label studio. Show all posts

Tuesday, March 27, 2012

Connection Problem

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

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

Connection Problem

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

Sunday, March 25, 2012

Connection Problem

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

Connection Problem

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

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

Connection Problem

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

Tuesday, March 20, 2012

Connection Manager in SSIS packages

I am trying to run a package outside of the Business Intelligence development Studio. It continuously fails and tell me that my username cannot logon due to a password failure. When I check my connections the password never shows in the connection string and remains blank in the connection properties although I have checked Save Password in the connection properties. Does anyone know how I can save the password in the connection string being utilized in the SSIS package?Passwords are not shown in the properties due to security. I am assuming you are using SQL Server authentication instead of Windows Authentication. When you specify the password and save password, it saves it. But if you open the connection manager again, it won't show you the password (though it is still saved). However, to be able to leave it in the current state, you should now click Cancel to exit the connection manager, instead of OK. If you press OK, it will expect you to enter the password again. I think you must have opened the connection manager, and then pressed Ok, instead of Cancel, which erased the password.|||

I don't think that's the problem. I experiencing the same problem in my development Environment (using SQL Server authentication):

We're a group of developers working on the same package. after setting the connection managers with the correct username and password (and checking the save option) and saving the package by a certain user, when a different user accessing it, he cannot run the package and have to go through all the connection managers and ser the user and passwords all over again.

Any solution?

|||

Liran,

Check the ProtectionLevel property of your package. My guess is that you have ProtectionLevel=EncryptSensitiveWithUserKey

This means that all passwords are encrypted with a user-specific value meaning that only that user can run it.

If you follow best practice (http://blogs.conchango.com/jamiethomson/archive/2006/01/05/2554.aspx) of making your packages location-independant (http://www.windowsitpro.com/SQLServer/Article/ArticleID/47688/SQLServer_47688.html) then this should not be a problem.

-Jamie

sql sql

connection manager in SQL 2005

I am writing a new Ole DB connection thru connection manager in Visual
Studio in SQL 2005. I used Native OLE DB\MS Jet 4.0 OLE DB Provider and I
specify a database path as d:\temp\database.dbf and set up the extended
proporties in advance tab to dBase 5.0 and when I click "test connection"
button, I gives me an error:
"Test connection failed because of an error in initializing provider.
'd:\temp\database.dbf ' is not a valid path. Mare sure that path name is
spelled correctly and that you are connected to the server on which the file
resided. "
I used browser button to get the file and path and therefore I am sure it is
correct. Can anyone please help to fix this problem? Many thanks.Hi
"00EricClapton" wrote:
> I am writing a new Ole DB connection thru connection manager in Visual
> Studio in SQL 2005. I used Native OLE DB\MS Jet 4.0 OLE DB Provider and I
> specify a database path as d:\temp\database.dbf and set up the extended
> proporties in advance tab to dBase 5.0 and when I click "test connection"
> button, I gives me an error:
> "Test connection failed because of an error in initializing provider.
> 'd:\temp\database.dbf ' is not a valid path. Mare sure that path name is
> spelled correctly and that you are connected to the server on which the file
> resided. "
>
> I used browser button to get the file and path and therefore I am sure it is
> correct. Can anyone please help to fix this problem? Many thanks.
>
Are you sure that the file has the correct permissions and is not locked by
another application?
John

Monday, March 19, 2012

Connection Manager - No available servers

Windows XP Pro, SQL Server 2005 (Developer) & Visual Studio 2005 (Pro)

New SSIS project (Visual Studio)

New OLE DB/SQL Native client connection.

There's no servers available in the drop down box.

All the services that need to be running are running.

Guess I've missed the obvious here

Cheers

Dave

Hi,

did you try to enter the nae manually ?

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||Yes I did. Will re-try and then post the error.|||

Just tried entering the name manually and it worked...

Any ideas why I can't browse to the instance/server?

|||Do you use another port than the default one 1433 ? If so, you will have to make sure that SQL Server browser is started. What for ? See the link here for more information about the SQL Browser.

http://msdn2.microsoft.com/en-us/library/ms181087.aspx

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

connection issue with enterprise manager but works with management studio

Hi,

I have an interesting scenario.

I have a SQL Server 2000 Standard Edition instance running on Computer A. I'm trying to access it through computers B and C.

Computer B has Sql Server 2005 Express Edition installed and I was able to use its Management Studio and
connect to instance on Computer A.

Computer C has SQL Server 2000 Standard Edition installed. When I try to connect to the instance on Computer A,
I get connection failed message.

I checked some settings. Both TCP/IP and Named pipes are enabled on the instance in A. The TCP/IP port is set to 1433 for
both client and server.

Please give me some ideas as to how I can solve this problem.

-Thanks

What is the error message that is displayed?|||I am assuming all three are on the same network then it is a simple right click at the top of Management Studio and register the 2000 then it becomes local to you. I have registered 68 7/2000 in one box so it works . Hope this helps.|||

The error said something like

Invalid Connection.ConnetionOpen(Invalid Instance)

|||

I figured it out.

Both A and C had Sql Server 2000 instances. When you try to connect to one Sql Server 2000 instance from another, Enterprise Manager automatically sets "Dynamically determine port" option and hence the connection fails. What you can do is use the Client Network Utility in C and create a new TCP/IP alias and uncheck the "dynamically determine port" option and manually set it to 1433. Then u can use Enterprise Manager in C and select the new alias that you created and finish registering the 2000 instance from A.

Thanks for your replies.

|||

shiversticks:
I figured it out.
Both A and C had Sql Server 2000 instances. When you try to connect to one Sql Server 2000 instance from another, Enterprise Manager automatically sets "Dynamically determine port" option and hence the connection fails. What you can do is use the Client Network Utility in C and create a new TCP/IP alias and uncheck the "dynamically determine port" option and manually set it to 1433. Then u can use Enterprise Manager in C and select the new alias that you created and finish registering the 2000 instance from A.
Thanks for your replies.

(on the same network then it is a simple right click at the top of Management Studio and register the 2000 then it becomes local to you. I have registered 68 7/2000 in one box so it works )

For the reference of future readers of this thread you just right click and register the other SQL Server as I originally posted and leave your port setings alone in eigth years I have not had reason to touch port settings it is not needed. Port settings could lead to SQL injection attacks.

Sunday, March 11, 2012

Connection Help!

I can't connect to my sql server 2000 database from Visual Studio using vb.net.

I'm trying to use the gotdotnet quickstart tutorials but they just throw dumb errors all the time ...

For example, I'm trying to perform a simple SELECT query

Dim myConnection As New SqlConnection("server=(local)\NetSDK;database=pubs;Trusted_Connection=yes")
Dim myCommand As New SqlDataAdapter("select * from Authors", myConnection)
Dim ds As New DataSet()
myCommand.Fill(ds, "Authors")

My error - "Too many arguments to 'public sub New()' " for the SQLConnection.

I then tried this


 Dim dbconn As New SqlClient.SqlConnection
 dbconn.ConnectionString = "server=(local);Database=northwind;User ID=sa;trusted_connection=true"
 dbconn.Open() Dim myCommand As New SqlDataAdapter("select top 1 categoryname from Categories", dbconn)
 Dim ds As New DataSet
 myCommand.Fill(ds, "Authors")

Now this seems to work but I'm not sure if I need to bind the SELECT information to a textbox or something (response.write(ds) doesn't work.)

Any help appreciated as this is getting bloody annoying!

CheersThe quickest way to see all the data is to open the web form in design view and drop a DataGrid control from the Toolbox window onto the form. Then switch back to code view and add the follwing lines after the Fill:


DataGrid1.DataSource = ds
DataGrid1.DataBind()

connection from SQLS database to Visual Studio. Timeout failed.

I have a databse in SQL Server 2005 Sept Beta 2. On another partition I have Visual Studio 8. I want to establish a connection between the two.

Doing it programmatically in a C# code program fails.The connection string does not give me an error on debug.

Doing it via GUI in VS fails on the account of "timeout failed..."

I tried to copy the whole database from SQL Server directory into VS directory - the same result.

Amazingly, I was able to connect to my FoxPro 9 database with no problem. Also an Access database is connected.

Is there a way to increase this parameter: timeout? Where is set up?

Thanks.Most likely the SQL Server is not running. Is this the same machine (SQL Server and VS)? Copying files is not necessary. Being on different partitions is ok as well. Can you connect using sqlcmd? If not, what is the error message you get?

When you type 'net start' in the command line do you see SQL Server started? Or check services in the Control Panel.

Boris.

Wednesday, March 7, 2012

Connection Error when trying to run MDX-queries

To learn MDX (on SQL Server 2005 dev edition) I decided to put up some sample cubes and run MDX-queries from SQL Server Management Studio. When processing the cube in BI Studio I get the following error:

"The datasource , 'Adventure Works DW', contains an ImpersonationMode that that is not supported for processing operations."

Fair enough, then I change the impersonationmode in the datasource to service account. It all processes/deploys well and I can browse the cube in BI Studio. Off to Management studio to run some mdx-queries. Here however I get the error:

"Error (Data mining): Either the user, ######, does not have permission to access the referenced mining model, Analysis Services Tutorial, or the object does not exist."

That is of course due to me using the current user credentials for the query. So I try to change the current connection in management studio but the helpbutton informs me that as of now only windowsauthentication can be used for analysis services. So the only connectionway I can use from here is the only one not supported when processing?! This must mean I've done some childishly simple newbiemistake and I would be very grateful if you pointed it out so I could get started with the MDX.

Perhaps I should add that the user ##### is administrator for the entire server. The server administrator role should take precedence over database roles, right (not that it helped when I added one of those and included me)? The user is also a member of the SQLServer2005OLAPUser group. I also have full access to the underlying relational database. So I can delete or create elements or entire databases at will but not ask simple questions to them...

The other option - that the cube doesn't exist seems dispelled by being able to browse it and the dimensions etc. showing up in object explorers and in the left pane of the MDX Query interface.

Which leaves me at some permission problem again - some help would REALLY be appreciated.

|||Please provide more information as something strange is going on here - given what you have provided, you should not be having a permission error - but, the error message does not make sense as the Analysis Services Tutorial has no data mining component.|||

I don't have the queries I tested with anymore since I got it to work but the bottomline was that I didn't have any "ON ROW|COLUMNS" etc. part of the selection clause which obviously sent the engine looking for something that didn't exist. I.e. just had queries with variations on the form:

SELECT dim

FROM cube

Looked at what the browser sent with the profiler and changed to:

SELECT dim ON 0

FROM cube

and everything has been working well since then. Perhaps a bit strange errormessage but otherwise my mistake. Sorry for taking up your time with this one

|||

I am new to Analysis services. I migared on of the Sql 2000 cube to sql 2005 .I am getting the same message , when i use Pivot table to dipaly data from sql 2005 Cube.With sql 2000, it works great.Here is the eror message.

Error (Data mining): Either the user, Domain/User doen not have permission to access the referenced mining model, SalesHistoryData , or the object does not exist. Error (Data mining): Either the user, DOMAIN\USER , does not have permission to access the referenced mining model, SalesHistoryData , or the object does not exist.

When i ran Profiler , it is trying to run the following sql statement.

SELECT * FROM "SalesHistoryData "

I have granted all high level rights.Still not working.

Expecting fix from someone.

|||

hi, i recv the same while trying to query the cube from SSMS...

Error (Data mining): Either the user, domain\account, does not have permission to access the referenced mining model, MaxMinSalesDM, or the object does not exist.

no error building or deploying the cube..

can see the cube in the database folder as well

please help...

|||

sorry, my mistake...

it should be select from [Cube Name], not select * from [Cube Name]

|||

My issue solved.I just had to change the Data Source Provider to msolap.2 to msolap.3 in the Pivot table properties.

You may also have to try with just msolap(No vesion) in case the above change doesn't fix it.

Connection Error when trying to run MDX-queries

"The datasource , 'Adventure Works DW', contains an ImpersonationMode that that is not supported for processing operations."

"Error (Data mining): Either the user, ######, does not have permission to access the referenced mining model, Analysis Services Tutorial, or the object does not exist."

The other option - that the cube doesn't exist seems dispelled by being able to browse it and the dimensions etc. showing up in object explorers and in the left pane of the MDX Query interface.

Which leaves me at some permission problem again - some help would REALLY be appreciated.

SELECT dim

FROM cube

Looked at what the browser sent with the profiler and changed to:

SELECT dim ON 0

FROM cube

and everything has been working well since then. Perhaps a bit strange errormessage but otherwise my mistake. Sorry for taking up your time with this one

|||

When i ran Profiler , it is trying to run the following sql statement.

SELECT * FROM "SalesHistoryData "

I have granted all high level rights.Still not working.

Expecting fix from someone.

|||

hi, i recv the same while trying to query the cube from SSMS...

Error (Data mining): Either the user, domain\account, does not have permission to access the referenced mining model, MaxMinSalesDM, or the object does not exist.

no error building or deploying the cube..

can see the cube in the database folder as well

please help...

|||

sorry, my mistake...

it should be select from [Cube Name], not select * from [Cube Name]

|||

My issue solved.I just had to change the Data Source Provider to msolap.2 to msolap.3 in the Pivot table properties.

You may also have to try with just msolap(No vesion) in case the above change doesn't fix it.

Connection Error when trying to run MDX-queries

"The datasource , 'Adventure Works DW', contains an ImpersonationMode that that is not supported for processing operations."

"Error (Data mining): Either the user, ######, does not have permission to access the referenced mining model, Analysis Services Tutorial, or the object does not exist."

The other option - that the cube doesn't exist seems dispelled by being able to browse it and the dimensions etc. showing up in object explorers and in the left pane of the MDX Query interface.

Which leaves me at some permission problem again - some help would REALLY be appreciated.

SELECT dim

FROM cube

Looked at what the browser sent with the profiler and changed to:

SELECT dim ON 0

FROM cube

and everything has been working well since then. Perhaps a bit strange errormessage but otherwise my mistake. Sorry for taking up your time with this one

|||

When i ran Profiler , it is trying to run the following sql statement.

SELECT * FROM "SalesHistoryData "

I have granted all high level rights.Still not working.

Expecting fix from someone.

|||

hi, i recv the same while trying to query the cube from SSMS...

Error (Data mining): Either the user, domain\account, does not have permission to access the referenced mining model, MaxMinSalesDM, or the object does not exist.

no error building or deploying the cube..

can see the cube in the database folder as well

please help...

|||

sorry, my mistake...

it should be select from [Cube Name], not select * from [Cube Name]

|||

My issue solved.I just had to change the Data Source Provider to msolap.2 to msolap.3 in the Pivot table properties.

You may also have to try with just msolap(No vesion) in case the above change doesn't fix it.

Connection Error when trying to run MDX-queries

"The datasource , 'Adventure Works DW', contains an ImpersonationMode that that is not supported for processing operations."

"Error (Data mining): Either the user, ######, does not have permission to access the referenced mining model, Analysis Services Tutorial, or the object does not exist."

The other option - that the cube doesn't exist seems dispelled by being able to browse it and the dimensions etc. showing up in object explorers and in the left pane of the MDX Query interface.

Which leaves me at some permission problem again - some help would REALLY be appreciated.

SELECT dim

FROM cube

Looked at what the browser sent with the profiler and changed to:

SELECT dim ON 0

FROM cube

and everything has been working well since then. Perhaps a bit strange errormessage but otherwise my mistake. Sorry for taking up your time with this one

|||

When i ran Profiler , it is trying to run the following sql statement.

SELECT * FROM "SalesHistoryData "

I have granted all high level rights.Still not working.

Expecting fix from someone.

|||

hi, i recv the same while trying to query the cube from SSMS...

Error (Data mining): Either the user, domain\account, does not have permission to access the referenced mining model, MaxMinSalesDM, or the object does not exist.

no error building or deploying the cube..

can see the cube in the database folder as well

please help...

|||

sorry, my mistake...

it should be select from [Cube Name], not select * from [Cube Name]

|||

My issue solved.I just had to change the Data Source Provider to msolap.2 to msolap.3 in the Pivot table properties.

You may also have to try with just msolap(No vesion) in case the above change doesn't fix it.

Connection error to remote SQL instance, over VPN

I am trying to connect to an instance of SQL Express through a vpn, simply using the SQL Management Studio, providing the server ip address x.x.x.x\MSSQLSERVER, and using SQL authentication login. I receive the following message:

Cannot connect to <server>, etc., etc.

error 25: - Connection string is not valid

Does anyone understand this? I am trying to connect through the SQL Server Management interface, not with a client program that would utilize a connection string. Is there something which prevents Management Studio from working over a vpn?

To connect, I am using SQL authentication, and have verified the login and password locally on the target pc. The SQL browser service is running on the target pc, and I can telnet to the port which it is monitoring, through the same vpn connection. Remote connections are enabled for TCP/IP in the Surface Area configuration on the target pc.

Any help appreciated.

x.x.x.x\MSSQLSERVER is not correct. You cannot use MSSQLSERVER as the instance name because it is reserved for default instance. Since your instance is SSE, you should use x.x.x.x\sqlexpress. Based on your description, your connection should work with the fix. Please make sure UDP port 1434 (used by sql browser) is blocked by firewall.|||

SSE is installed as the default instance, so /MSSQLSERVER does work, as tested locally. Also the assigned port is opened through the firewall, as tested by telnetting through the vpn.

However here is additional information since I posted the problem: Using a packet tracker, I can see no handshaking messages are transmitted on the vpn network when the connection is attempted by SSE Studio. If I connect to a local SQL pc (on my local, non-virtual network), I see the TCP messages, handshaking, etc. and it instantly connects. Why does SSE Studio not attempt to connect over the vpn network? Ping and telnet do work over that network, so the operating system correctly distinguishes the networks. Just not SSE Studio. Is there a way to force it to this network?

|||If it's default instance, you should remove MSSQLSERVER, use x.x.x.x only. Also, use c:\windows\system32\cliconfg.exe on your client machine to check whether TCP is enabled on the client. Is your server listening on TCP port 1433? If not, please confirm sql browser is running and UDP port 1434 is in firewall's exception list. Thanks.|||

I figured it out, the connection text must specify the port after the ip address. Format:

x.x.x.x,1433 (or whatever port #)

It works in SSE Studio, and in the client app. (Access project). An example is here: http://www.connectionstrings.com/, under SQL Server connections -> SqlConnection(.NET) -> connection via ip address.

What is confusing is that the port specification is apparently not required if connecting to another pc on the same lan, only if connecting over the internet/vpn.

|||

If x.x.x.x,1433 workes, x.x.x.x should work unless your have any alias defined for x.x.x.x. You use c:\windows\system32\cliconfg.exe to check it.

If you tcp port is not 1433, then you must make sure sql browser is running and UDP port 1434 is not blocked. "x.x.x.x,port" can bypass the requirement of sql browser.

Saturday, February 25, 2012

connection error

hi,

I installed sql server 2005 ,when i try to connect to sql server management studio iam getting this error.

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)

I searched internet and found this :under sql server surface area configuration

So I followed the following steps to change the setting from local connection to local and remote connection:

1. Click Start, point to Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Surface Area Configuration. 2. On the SQL Server 2005 Surface Area Configuration page, click Surface Area Configuration for Services and Connections. 3. On the Surface Area Configuration for Services and Connections page, expand Database Engine, click Remote Connections, click Local and remote connections, click the appropriate protocol to enable for your environment, and then click Apply.

Note Click OK when you receive the following message:

Changes to Connection Settings will not take effect until you restart the Database Engine service.

4. On the Surface Area Configuration for Services and Connections page, expand Database Engine, click Service, click Stop, wait until the MSSQLSERVER service stops, and then click Start to restart the MSSQLSERVER service.

But there is no DATABASE ENGINE It contain ANALYSIS SERVICES.

Then How Get rid from the above error.

Thanks in advance.

hi,

I installed sql server 2005 ,when i try to connect to sql server management studio iam getting this error.

I searched internet and found this :under sql server surface area configuration

So I followed the following steps to change the setting from local connection to local and remote connection:

Note Click OK when you receive the following message:

Changes to Connection Settings will not take effect until you restart the Database Engine service.

But there is no DATABASE ENGINE It contain ANALYSIS SERVICES.

Then How Get rid from the above error.

Thanks in advance.

|||

Look in the SCM (service Control manager of Windows) There you will find the SQL Server Service "SQL Server (MSSQLSERVER)" (or probably and instance name in the parenth.) Restart this service and you′ll be fine.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Friday, February 24, 2012

Connection Error

I am having a problem with creating any report in Visual Studio 2003 and
Reporting Services 2000.
I can create a datasource and test the connection without any problems.
However, when I create a report that uses this datasource (or try to create
an new one) it fails with the error message "A connection cannot be made to
the database. Set and check the connection string". This problem occurs using
a brand new VS Project and report and all existing projects/reports.
All my existing reports fail now too with the same error in all projects.
Unfortunately, I do no know what would have changed that would cause this
error. Did any recent security patches cause any problems?
Any suggestions would be most appreciated.
--
WCUI was able to determine the solution. The data source is for Oracle. The
password for the account that I was using was expiring. Oracle throws and ORA
error message when connecting with a password that is about to expire.
Testing the connection in Visual Studio must trap and ignore this password
expire warning (oracle error) while trying to use this data source in a
report just fails.
Hope this helps someone in the future...
--
WCU
"StanleyHammer" wrote:
> I am having a problem with creating any report in Visual Studio 2003 and
> Reporting Services 2000.
> I can create a datasource and test the connection without any problems.
> However, when I create a report that uses this datasource (or try to create
> an new one) it fails with the error message "A connection cannot be made to
> the database. Set and check the connection string". This problem occurs using
> a brand new VS Project and report and all existing projects/reports.
> All my existing reports fail now too with the same error in all projects.
> Unfortunately, I do no know what would have changed that would cause this
> error. Did any recent security patches cause any problems?
> Any suggestions would be most appreciated.
> --
> WCU

Connection cannot be made to http://localhost/ReportServer

I have developed a reports in Business Intelligence Development studio and when I am tring to deploy it.
It says that
Connection cannot be made to http://localhost/ReportServer
What does it really mean.Is SSRS service running ?|||

Do you have Reporting Services install on Localhost?

Has it been configured?

Is IIS running?

That's a start.

BobP

|||Yess, it is runnning .|||IIS install - > start, control panel, add remove progs, add/remove windows components ->
tick IIS, click next etc...

Think you need to be running XP pro to do this, don't think you can do it from Home edition

Shurely you need to do this before you install RS, no? I can't remember the install process of RS....|||

It wont let you install SSRS without IIS.

BobP

|||If IIS is running then it must be user permissions on the IIS folder.

Friday, February 17, 2012

Connecting With Visual Studio .net

Hello,
I have MSDE Installed on a different computer (WIndows 2003) within my
network. I also have MSDE Installed on my production computer for
development.
I have successfully created databases on both computers using OSQL. What I
would really like to accomplish is a connection from the Server Explorer in
Visual Studio .NET.
I have a successful connection to the local instance of MSDE and I added my
server to the server list with no problems.
But, this is where the problem comes in.
Lets Say my Server is called Moon, The Servers Tree in Server Explorer
shows Moon, I can access the Event Logs, Message Queues, Performance
Counters and Services with on problem. But, when I click on SQL Servers
Moon is shown with a Red X, I click the Plus (+) sign, type in the Login and
Password, I receive the following Error:
{DBNETLIB}{ConnectionOpen (Connect().]SQL Server does not exist or access
denied.
Any Suggestions will be greatly appreciated,
Chuck
hi Chuck,
Charles A. Lackman wrote:
> Hello,
> I have MSDE Installed on a different computer (WIndows 2003) within my
> network. I also have MSDE Installed on my production computer for
> development.
> I have successfully created databases on both computers using OSQL.
> What I would really like to accomplish is a connection from the
> Server Explorer in Visual Studio .NET.
> I have a successful connection to the local instance of MSDE and I
> added my server to the server list with no problems.
> But, this is where the problem comes in.
> Lets Say my Server is called Moon, The Servers Tree in Server
> Explorer shows Moon, I can access the Event Logs, Message Queues,
> Performance Counters and Services with on problem. But, when I click
> on SQL Servers Moon is shown with a Red X, I click the Plus (+) sign,
> type in the Login and Password, I receive the following Error:
> {DBNETLIB}{ConnectionOpen (Connect().]SQL Server does not exist or
> access denied.
>
the most probable causes of this problem are listed in
http://support.microsoft.com/default...06&Product=sql
... please check with the Server Network Utility that the Moon MSDE instance
has enabled network protocols, as MSDE installs by default allowing local
connections only...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Read my How to (Msde related) at:
http://spaces.msn.com/members/sholliday/
12/16/2005 entry date.
The key is the
[Options]
DISABLENETWORKPROTOCOLS=0
SECURITYMODE=SQL
stuff.
Use the KB mentioned earlier, to manually make the fix.
My stuff will teach you how to avoid the issue in the future, if you
ever install MSDE again.
(Or if you get really really stuck and need to start over)
Charles A. Lackman wrote:
> Hello,
> I have MSDE Installed on a different computer (WIndows 2003) within my
> network. I also have MSDE Installed on my production computer for
> development.
> I have successfully created databases on both computers using OSQL. What I
> would really like to accomplish is a connection from the Server Explorer in
> Visual Studio .NET.
> I have a successful connection to the local instance of MSDE and I added my
> server to the server list with no problems.
> But, this is where the problem comes in.
> Lets Say my Server is called Moon, The Servers Tree in Server Explorer
> shows Moon, I can access the Event Logs, Message Queues, Performance
> Counters and Services with on problem. But, when I click on SQL Servers
> Moon is shown with a Red X, I click the Plus (+) sign, type in the Login and
> Password, I receive the following Error:
> {DBNETLIB}{ConnectionOpen (Connect().]SQL Server does not exist or access
> denied.
>
> Any Suggestions will be greatly appreciated,
> Chuck
|||Hello,
I found a way to fix the problem,
Below is what I needed to do.
Run the svrnetcn.exe on which you installed MSDE It will show you SQL Server
Network Utility Dialogbox, Make sure that TCP/IP is enabled and the port is
1433.
Chuck
"Charles A. Lackman" <Charles@.CreateItSoftware.net> wrote in message
news:O%23rnzwCGGHA.344@.TK2MSFTNGP11.phx.gbl...
Hello,
I have MSDE Installed on a different computer (WIndows 2003) within my
network. I also have MSDE Installed on my production computer for
development.
I have successfully created databases on both computers using OSQL. What I
would really like to accomplish is a connection from the Server Explorer in
Visual Studio .NET.
I have a successful connection to the local instance of MSDE and I added my
server to the server list with no problems.
But, this is where the problem comes in.
Lets Say my Server is called Moon, The Servers Tree in Server Explorer
shows Moon, I can access the Event Logs, Message Queues, Performance
Counters and Services with on problem. But, when I click on SQL Servers
Moon is shown with a Red X, I click the Plus (+) sign, type in the Login and
Password, I receive the following Error:
{DBNETLIB}{ConnectionOpen (Connect().]SQL Server does not exist or access
denied.
Any Suggestions will be greatly appreciated,
Chuck

Tuesday, March 27, 2012

Connection Problem

Connection Problem

Sunday, March 25, 2012

Connection Problem

Connection Problem

Connection Problem

Tuesday, March 20, 2012

Connection Manager in SSIS packages

connection manager in SQL 2005

Monday, March 19, 2012

Connection Manager - No available servers

connection issue with enterprise manager but works with management studio

Sunday, March 11, 2012

Connection Help!

connection from SQLS database to Visual Studio. Timeout failed.

Wednesday, March 7, 2012

Connection Error when trying to run MDX-queries

Connection Error when trying to run MDX-queries

Connection Error when trying to run MDX-queries

Connection Error when trying to run MDX-queries

Connection error to remote SQL instance, over VPN

Saturday, February 25, 2012

connection error

Friday, February 24, 2012

Connection Error

Connection cannot be made to http://localhost/ReportServer

Friday, February 17, 2012

Connecting With Visual Studio .net

asp sql server

Blog Archive

About Me