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

Hi Folks,

Lets get this out of the way first - I KNOW NOTHING ABOUT SQL SERVER, MSDE or MDAC

Sorry I don't mean to shout but I really don't know anything at all so please make your answers as simple as possible.

I have an application (Webmarshall) that has a SQL database from which certain reports are run. Whenever I try to run the reports it asks me for database details.

According to the application it is using LANCELOT\WEBMARSHALL\Webmarshall as the database

As this is all happening on one server, I presume it is local and not remote.

When I am presented with the dialogue box for the reporting module it asks for a server and a database, I have tried the following :

Server: local Auth: Windows

Server: local Auth: SQL

Server lancelot (both authorisation methods)

Server: lancelot\webmarshall (both authorisation methods)

Server: \\lancelot\webmarshall (both authorisation methods)

Each time, I get the message

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

and I can't select a database.

Can someone help me please...its a long time since I went fishing in the dark (with no net) but thats how I feel right now!!!!

Thanks

In the SQL Server menu options on your Start menu, do you have Enterprise Manager? (you may not depending on which version of SQL Server you have and which installation options were selected, but if you do things will be simpler)

When you try to connect with SQL Auth, are you using a user name and password that are known to be correct? Windows Auth may not work simply because your Windows user may not have permission to connect.

|||

Hi Guys,

Thanks for the response, in the end I was so confused by it all that I got a (SQL experienced and very trusted) colleague to remote onto my server.

It turns out that it was MSDE, and that for some reason the connection details had all been lost during the upgrade process. We eventually found the user buried deep in the properties of the application, changed the password and now it all works OK

Perhaps I need to start learning more about SQL, and stop playing with exchange all day!!!!!!

Thanks again