Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2008 Forums
 SQL Server Administration (2008)
 This can't be right

Author  Topic 

elwoos
Master Smack Fu Yak Hacker

2052 Posts

Posted - 2011-06-09 : 09:53:30
A little while ago I installed SQL Server Express 2008 R2 onto my Windows XP machine. As far as I recall it all worked fine. As we are intending to move from SQL Server 2000 to 2008 I started to use the Management studio with our SQL Server 2000 instances to become a little more familiar with it.

Now we are nearer the time where we are more likely to make the move I found some time to take a look at 2008 and something very strange is happening. If I run a query e.g. a simple select on one of the 2008 tables it will return the data as expected, however if I try to create a new query (on a seperate tab) I get an error -
quote:

Cannot connect to MyMachine\MySQLServer2008R2.

------------------------------
ADDITIONAL INFORMATION:

A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) (Microsoft SQL Server, Error: 10054)




I'm using Windows Authentication to connect and I am an administrator of both the local machine and the SQL Server.

I've checked the machine logs and the only thing I can see is a series of DCOM errors -
quote:

DCOM was unable to communicate with the computer MyComputerName using any of the configured protocols



So I went to the configuration manager and made sure TCP and named pipes were enabled for both the network and the client. I also gave the SQL Server a new port that is definitely not used by anything else. Since doing this I have restarted the machine. After all this the same happened again. If I use management studio with SQL Server 2000 it works just as expected.

So now I am at something of a loss to know where to start to troubleshoot. Does anyone have any suggestions or ideas?

thanks

Steve

-----------

If debugging is the process of removing software bugs, then programming must be the process of putting them in.

Bustaz Kool
Master Smack Fu Yak Hacker

1834 Posts

Posted - 2011-06-10 : 18:42:24
If you are using SQL 2000 tools to try to communicate with a SQL 2008 engine, I'm surprised that you are getting any query to run. Rather then bang your head against the wall, would it be possible to load the 2008 tools only onto your 2000 box?

=======================================
Elitism is the slur directed at merit by mediocrity. -Sydney J. Harris, journalist (1917-1986)
Go to Top of Page

Jahanzaib
Posting Yak Master

115 Posts

Posted - 2011-06-13 : 03:16:06
check Shared Memory Protocol and Number of connections restriction,use SQL Server Management Studio of SQL Server 2008 to familiar with it

Regards,

Syed Jahanzaib Bin Hassan
MCTS,MCITP,OCA,OCP,OCE,SCJP,IBMCDBA

My Blog
www.aureus-salah.com
Go to Top of Page

elwoos
Master Smack Fu Yak Hacker

2052 Posts

Posted - 2011-06-13 : 07:12:11
I was using the 2008 tools to query the 2008 server, perhaps I didn't explain that very well.

I think, at least at one point, that shared memory was enabled on client and server. I don't really understand how that could have caused the symptoms I saw.

In the end I re-installed 2008 and it all seems to be working as expected now.

steve

-----------

If debugging is the process of removing software bugs, then programming must be the process of putting them in.
Go to Top of Page

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2011-06-13 : 07:16:09
Shared memory can only be used when the client machine and the server are the same machine. Hence when you're running the tool that connects to SQL on the same server that hosts SQL.

--
Gail Shaw
SQL Server MVP
Go to Top of Page

elwoos
Master Smack Fu Yak Hacker

2052 Posts

Posted - 2011-06-13 : 10:58:07
Thanks Gail, that's what I suspected. In this case they were both on the same machine. If it's disabled then surely TCP or named pipes should work for the connection shouldn't they?

steve

-----------

If debugging is the process of removing software bugs, then programming must be the process of putting them in.
Go to Top of Page

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2011-06-13 : 11:24:26
Yes, they will.

--
Gail Shaw
SQL Server MVP
Go to Top of Page
   

- Advertisement -