HELP: Can't connect to database instance (SQL 2005)

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

DetRich - 02 Jul 2009 16:10 GMT

Hello,

Background:
I am running SQL 2005 on W2K3 in a lab environment. This is for a BizTalk
test deployment. I have a cluster setup and a SQL instance is installed on
Node-A. In the cluster, I have a group for Node-A of the cluster. It has a
Network Name resource called RAS040SQLA. The instance name is:
RAS040SQLA\INST1.

Problem:
I cannot connect to the database from SSMS using this instance name.
When attempting to connect, I get the following error:
Title Bar: Connect to Server.
Message: Cannot connect to RAS040SQLA\INST1.
Additional info: An exception occurred while executing a T-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
Could not continue scan with NOLOCK due to data movement. (Microsoft SQL,
Error: 601)

Everything I find on the web for this error message looks to assume a client
application is throwing the error. Not the SSMS console.

Can anyone shed any light on the cause of this error?

TIA,

DetRich

Reply to this Message

Rick Byham, MSFT - 02 Jul 2009 18:04 GMT

Odd that you would get that during the connection process. I'm wondering if
this is a connection problem, or a problem with SQL Server.
Some things to test:
Can you connect using SQLCMD? It's a simpler client.
If you can connect with SQLCMD execute SELECT name, state_desc FROM
sys.databases
I'm wondering if there is a database that didn't recover properly. Perhaps
the default database for your login.
Do other logins have the same error?
Are there any clues in the SQL Server error log?

Also, is your SSMS executing on the computer (node) where SQL Server is
running? If not, there are lots of connectivity things you could check. I'm
not listing those, because your 601 error implies that the connection is
made and then you get the error.

Signature

Rick Byham, MSFT
(Implies no warranty or rights)

> Hello,
>
[quoted text clipped - 27 lines]
>
> DetRich

Reply to this Message

DetRich - 02 Jul 2009 18:24 GMT

Hello and thanks for the reply Rick.

I don't know the syntax for SQLCMD.

The SQL instance (all servers) is in another domain. So, I have a remote
(Terminal services client) connection to either server. From the server, I
run SSMS to connect to SQL.
I can also try connecting from my desktop if you can help with the command
syntax.

The SQL instance is: RAS040SQLA\INST1
Or, RAS040SQLB\INST2

Also, currently, there are no database other than the system databases. I
can't connect with the server to deploy any databases. (DB deployment is
normally done from the BizTalk Configuration Tool).

> Odd that you would get that during the connection process. I'm wondering if
> this is a connection problem, or a problem with SQL Server.
[quoted text clipped - 42 lines]
> >
> > DetRich

Reply to this Message

Rick Byham, MSFT - 02 Jul 2009 19:01 GMT

For SQLCMD, open a command prompt. Then type
sqlcmd -SRAS040SQLA\INST1
If it works you will get 1>
Then type two lines
SELECT name, state_desc FROM sys.databases
GO

And you can check the error log with notepad. It's probably somewhere like:
C:\Program Files\Microsoft SQL Server\MSSQL.<instancename>\MSSQL\Log
But on a cluster the path could be considerable different.

Signature

Rick Byham, MSFT
(Implies no warranty or rights)

> Hello and thanks for the reply Rick.
>
[quoted text clipped - 68 lines]
>> >
>> > DetRich

Reply to this Message

DetRich - 02 Jul 2009 19:06 GMT

I finally was able to get with our DBA.

The SQL instances do not show up in the Cluster Admin. They do show up in
Services. Because the instances don't show up in the Cluster, I cannot
connect. Therefore, he says SQL must be un-installed/re-installed.

Booooooooooo

> Hello and thanks for the reply Rick.
>
[quoted text clipped - 59 lines]
> > >
> > > DetRich

Reply to this Message

Rick Byham, MSFT - 02 Jul 2009 21:42 GMT

Ah. Yes, there is an option in setup that offers a cluster installation.

Signature

Rick Byham, MSFT
(Implies no warranty or rights)

>I finally was able to get with our DBA.
>
[quoted text clipped - 79 lines]
>> > >
>> > > DetRich

Reply to this Message