# Tuesday, 26 September 2006

Having trouble getting through to a local SQL Server using the SQLOLEDB provider? I sure did. I’m trying to get a base VPC setup with some Microsoft server products which need access to a local SQL Server. The obvious answer is to use (local) or . to get at the local SQL Server and not have to worry about changes in the machine name. This, however, turns out not to work with the default settings of SQL Server 2005.

You basically have to enable TCP/IP using SQL Server Configuration Manager for it to work. I little gotcha for ya

Tuesday, 26 September 2006 22:38:10 (Romance Daylight Time, UTC+02:00)
I am currently experiencing problems connecting to a local Sql Server 2005 Express named instance in a Windows Vista RC1 environment. The client software that I am trying to connect with seems to use an ODBC driver, not an SQLOLEDB driver, but I think the problem still could be related to what you have experienced. I am able to connect to the database with Sql Server Management Studio, whilst the other client software I am trying to use yields the following error message: [Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.

As your blog post popped up in my RSS reader I thought it would save my day, but unfortunately I seem to get the same error even with TCP/IP enabled for the server instance. Do you (or anyone else reading this) have any other suggestions on how to troubleshoot on this problem? I feel pretty stuck myself at the moment =\
Tuesday, 16 September 2008 23:00:58 (Romance Daylight Time, UTC+02:00)
most helpful,

racked my brain for ages trying to work out why couldnt connect!
Comments are closed.