Can''t access database
-
I know you guys must see these kinds of threads all the time, where some guy with no experience comes along and tells you his problem which is easily fixed. Or at least, thats how I'm hoping this will play out.
I've recently advanced a bit in my company, and now seem to be in charge of a lot of things, and also a lot of problems, like this one database for a client. Not a big step up, some of you may think, but it's kinda large for me. The advance was not because of any great merit on my part, but rather due to someone else leaving.
My problem is thus:
We have a database, or rather a client has one. The server was installed with a trial version 64 bit windows 2003. (Not sure what kind. I joined the company after the server was installed, and then the trial ran out.) I was called onsite to fix this, but had time constraints as they had no backup server. I was told to just install another version of windows over and and sort it out later. The client had Windows 2003 server: DataCenter edition. SO I installed that on top, got the database running (They didn't want a format as they hadn't backed up their data, which they now do.) and everything was ok.
Now, however, I've been asked to work with another guy on a program he wrote which is going to take information from the database. To do this, he needs access to the server and so the database. For some reason he can't get access. I tried, and I can't do it either. He gets this error:
Error [08001][Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
Error [01000][Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect()).
I got a different error while using Query Analyzer on the server to test user access:
Server: Msg 17, level 16, state 1
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] SQL Server does not exist or access denied.
Now, I'm fairly sure the answer to this is simple. So I'll tell you what I did, and what I know (Which isn't much).
I've set up a username and password for the database, I've set up the same username and password for the server. I've set up the same username and password in every place I could find that wants a username and password. Now, that's not to say there I've put it everwhere, because at the moment I'm "winging it". I don't know anything about windows 2003 server: Datacenter edition. I've been running around trying to find information about it, and SQL servers (Which I also know next to nothing about). Since I am sitting here with all this new stuff to learn, and it's not going to go away, I'm keen to learn as much as I can. However, I'd like to learn while I get this problem fixed.
Since I don't know much about any of this, I don't know what other information anyone might need to help me out. So let me know what you need to know and I'll find out for you.
Please, be kind.
-
The first thing I would check is whether there is a firewall blocking you. Windows 2003 has a fire wall and the normal approach is to start with most ports disabled. When SQL Server starts up it writes a record to the SQL Server ErrorLog that has info about the protocols and ports it is using. Check that it is using TCP/IP and the port it is using. If it is using TCP/IP, check that the firewall is permiting connections to this port.
If SQL Server is not configured to use TCP/IP, you may need to run the "Server Network Utility" to change this. You should find this in the same prgram group as Enterprise Manager.
-
Thanks for the reply.
I've checked the ports (That at least is something I know about.) and they are all fine.
While trying to find the solution to this I've managed to get a connection, and then get it refused. Perhaps I'm just missing authentication somewhere?
Like I said, I know nothing of what I'm doing here, so don't be too fast running over the obvious reasons this doesn't work. I've made a username and password for the database I want to connect to, yet there were quite a few places for me to put this username and password. I'm wondering if I missed one of these places.
The firewall is off on the server, it's sitting behind a firewall machine/file server. TCP/IP is enabled and running fine. I also remote to the server from off site (It's how I'm doing my work, as the server is quite far away.)
PS: It seems punctuation in topic headdings is a bad thing.
-
We recently have started seeing this error on our Sql Server 2000 sp4 on Windows 2000 server SP4.
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access
denied.
[Background] This server has both IIS and Sql Server, it host some of our websites, when the connection problem occurs it affects all our web driven apps except one that is a dotNet application. We are having difficulty figuring out how to resolve this issue since EM, QA and other tools can connect remotly and locally w/o any issues.
-- Francisco
-
Garth:
the first thing I do when I get this error is make sure that I can ping the Server from the client I am using. (Addressing the SQL server does not exists)
Are you trying to connect locally or from a remote client?
This might lead to you checking the SQL Server Client Network utility configuration.
Address the access denied:
Next , You might want use an account that has System Administrator role to see if you have access with that account.
Dan Pitta
-
Dan,
When this hits my server I can connect via EM and QA and my Idera Diagnostic Manager. I can even create a .udl link to test the conneciton against the server and it works fine. Like I mentioned before. Our one dot Net product is able to connect just fine, it's when our ASP pages try that we have a problem. And it is a big problem for us as our webstore is an ASP written site.
Has worked for years, no code changes and this week it went a-wall-- Francisco
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply