I had to install SQL Server, Developer edition, on DEFAULT instance name.

The key was with #4; my SQL server was installed by Visual Studio 2008 kit and thus was default instance; the ‘lizm’ I was connecting to was an alias that I previously created for testing, and although it seemed to work just fine from Management Studio, it wouldn’t allow connections from another computer, or, apparently, our application.

I’ve tried reinstalling an SQL server, with instance name=’LIZM’; it created the name LIZM\LIZM, which is of no use to me. What should I do to get the name LIZM? Uninstall everything and try again? Is there a renaming process? Searching for ‘install same name as machine’ only turns up linkage errors, so I’m forced to ask.

1. Check Browser Service ( For SQL Server 2005 and above)
2. Check Windows Firewall or Anti Virus, if that is blocking…
3. Check the service you are trying to connect is actually running.
4. Check the Server Name to which you are connecting, if it is a named instance of default instance.

~ IM.

Two days ago, my hard drive failed. After reinstalling Windows and SQL, the connection string I’ve previously used without problems started throwing the error in the title.

What really vexes me is that everything seems to be fine:
– in SQL SERVER Surface Area Configuration, Remote Connections accept both TCP/IP and named pipes (we’re using pipes)
– when trying to connect to the server via SQL Server Management Studio, with Server Name=lizm (instance name is same as computer name), and user name and password. Connection happens without problems.
– on a quick look through cliconfg.exe, I’ve had both protocols enabled, and no aliases (which I’ve read are causing problems) present.

The relevant excerpt from my original connection string :
Data Source=(local)\;Initial Catalog=SMA;Integrated Security=True;
I’ve tried variations on it, even though it used to be functional; still no luck.

Two days ago, my hard drive failed. After reinstalling Windows and SQL, the connection string I’ve previously used without problems started throwing the error in the title.

What really vexes me is that everything seems to be fine:
– in SQL SERVER Surface Area Configuration, Remote Connections accept both TCP/IP and named pipes (we’re using pipes)
– when trying to connect to the server via SQL Server Management Studio, with the

- connection string (original, excerpt): Data Source=(local)\;Initial Catalog=SMA;Integrated Security=True;

Ensure {server name} is written/spelled properly. If computer name is {lambda}, {server name} should be something like {lambda\sqlexpress}.

regards.

Please apply SQL Server 2005 Service Pack 2. To both client tools and database engine and see if you still face the same issue.

I searched on web for this issue, below was the conclusion.

Error Message :
Could not load file or assembly ‘Microsoft.SqlServer.CustomControls, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91′ or one of its dependencies. The system cannot find the file specified. (SQLSAC)

1. This error occurs when the version of Client tools is not same as SQL Server Database Engine.
Resolution : Apply Service pack and make version of Client tool same as SQL Server Database Engine.

2. Some issue with SQL Express, few people suggested after they installed SP2, they got rid of this issue.

Try installing SP2, and apply it on Client tools as well as your database engine.

Download Link for SQL Server 2005 Express Edition Sp2:

http://www.microsoft.com/downloads/details.aspx?FamilyId=31711d5d-725c-4afa-9d65-e4465cdff1e7&displaylang=en

Leave a comment, if this does not solve your problem.

Also please provide below information

1. Is SQL Server installed on the same box where you have your sql client tools.
2. What version of SQL Server is that (RTM, Sp1, Sp2, Sp3)
3. If it a default instance of Named instance ? ( From what you have mentioned in the post, it is clear it is a named instance, but want to confirm, if you installed a default instance of named instance.)

Thanks,
~ IM.

TITLE: Connect to Server
——————————

Cannot connect to ALEX\SQLEXPRESS.

——————————
ADDITIONAL INFORMATION:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

I disabled my user account control on my laptop because that was a reason why I couldn’t attach databases to my server before.
Also, I made my default port 1433 for TCP/IP protocol and made exceptions for sql server and sql browser in firewall.

And my surface gives me that:

TITLE: Surface Area Configuration
——————————

Could not load file or assembly ‘Microsoft.SqlServer.CustomControls, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91′ or one of its dependencies. The system cannot find the file specified. (SQLSAC)

Honestly to say I don’t know what else to do.
Thanks for your time

The account under which SQL Server Service is running, is it expired ? Did you check if password is still valid.

Go to Configuration Manager , double click SQL Server Service and change user name and password.

This could one of many reasons, why this could happen.

Also, please post exact error message.

~ IM.

Another sql quirk: using VB6 to Open ADODB.Recordset from Exec proc and an ADODB.Connection using SQLOLDDB.1 breaks the statement: while not Recs.EOF wend. BUT using DSN the exec populates recs no problem.

The target server is 2k8, and the sql user the apps uses has full rights (privileged to the crown), and the usual firewalls, etc. issues don’t apply.

What “SQLOLDDB.1″ does a DSN use? What’s the difference DSN / my connection string?

Eish!
Habeeb

I am facing the same problem Error : 40 – could not open a connection to SQL server but I am using SQL SERVER 2008. I tried out all the options you all mentioned above that are applicable to SQL server 2008 but it still not working. Please help

maina

I am getting the same 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) ) for one of my application on running on SQL 2000 on OS Window 2000 Terminal.

I tried and tested all the possibilities but all were unsuccessful.

The same Application is running successfully on other server having same configuration.

Please help in above matter.