SQL 2008 [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

Hi,
I have a user that is unable to open an Excel document properly. It has a bunch of connections it uses that go back to an SQL server on the network called LS1. It was working correctly until we added TCP and Named pipes using the cliconfg.exe to fix the connection that broke between their ERP software and the database. It did fix the ERP but this spreadsheet spits out [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. It then prompts for SQL server login and populates the Server box with the correct LS1MSSQL_08 but both Trusted Connection and putting in his credentials spits out:Connection Failed:SQLState: '08001'
SQL Server Error: 17
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.


The weirdest part(s) is that he can connect to the server using SQL Server Management Studio just fine and a user in an office next door to him can access the Excel doc without receiving any errors at all and she had the same tcp and named pipes alias added to her machine as described above. I'm lost.
Any help would be greatly appreciated.



jhill777att - Do us a favor and provide more detail in your question titles. You wouldn't believe how many questions we have in the SQL Server zone titled something like 'SQL 2008', and a more descriptive question title will better encourage experts that are skilled in what you're trying to solve to click on it and read your question.

Thanks in advance.



jhill777att - Do us a favor and provide more detail in your question titles. You wouldn't believe how many questions we have in the SQL Server zone titled something like 'SQL 2008', and a more descriptive question title will better encourage experts that are skilled in what you're trying to solve to click on it and read your question.

Thanks in advance.



It has several connections. As an example, one of the connection strings looks like this_Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=True;Initial Catalog=ActiveM_Companyname;Data Source=LS1MSSQL_08;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=LFSERVERONE;Use Encryption for Data=False;Tag with column collation when possible=False

**Above, I substituted "Companyname" for our name.**



I take that back. The girl next door to him was on it all morning but is getting the same error now.



What is it exactly you configured with cliconfig? Did you only define an alias? If so, that should not change anything. However, if you have added Named Pipes in preference over TCP, it might make a difference.



In the users computers run a PING LS1 to see if reaches the server. If so, then run a telnet command to verify if it reaches the SQL Server instance.

Share this

Related Posts

There was an error in this gadget