I have installed default instance of SQLServer 2005 DE on Windows Server 2003 host. I also installed a named instance of MSDE rel A. I can connect to the MSDE instance from Management Studio but it does not appear in the list of servers when I try to add the connection in VS2005 server explorer. What am I doing wrong?
- Dick
Anybody?
I can connect to the named MSDE instance (now upgraded to SP4) with management studio and osql, but it does not appear in the server list in VS2005 studio explorer, or in the OS ODBC DataSources utility.
The log shows the MSDE instance is listening on shared memory. I cannot configure it for named pipes because I can only see the default SS2K5 instance in SQL Server Configuration Manager.
All contributions massively appreciated.
|||
MSDE instances listening only on shared memory generally do not show up in the list boxes you mention.
You can configure the MSDE to listen on named pipes (or TCP) through the Server Network Utility.
|||Thanks Peter
That cracked it. Here's what I did:
- I ran Microsoft SQL Server\80\Tools\binn\SVRNETCN.exe and enabled Named Pipes and TCP/IP
- restarted the server instance but it did not fix it.
- rebooted the machine, got various system errors e.g. reporting services could not connect to db. There was a conflict on port 1433.
- re-ran Server Network Configuration utility, set TCP/IP port to 0. (Bit confused by this, I thought MSDE sp 3 sorted out port sharing issue ...? I havn't tried a remote connection yet)
- Ran SQL Configuration Manager and created np aliases for both the default and named instances.
- rebooted and everything fixed. Able to create a System DSN. MSDE instance did not appear in server list when I tried to add a new a connection in VS2005 server explorer, but I was able to type in the server name and connect ok.
As a general observation I have to say I am not a member of SQL Server 2005 fan club yet. It promises simplicity, but delivers frustration.
No comments:
Post a Comment