ODBC and Enterprise Manager (still) don't show databases with users other than sa

I have several Win2000 servers running SQL Server 2000, SP2 (8.00.665)
and only one of them developed this problem. When trying to set up a
new ODBC setting using any other login than sa, it doesn't show any
databases besides the system db's. When logging in with Enterprise
manager (all other logins except sa), the Databases list shows 'No
items'. All logins work fine with Query Analyzer. I already recreated
missing guest accounts in some of the databases, but that didn't help.
I've also installed the latest MDAC (2.7 SP1) and after that didn't
correct the problem, I installed SP3a. It's still not working.
I'm thinking about reinstalling SQL Server, but my client doesn't like
the idea. So if anyone has any idea what might help, I'd be greatful.
Thank you!
br,
AnnaAnna
Firstly you need to have SQL SP3 if you have not applied the patch to stop
the SQL Slammer on the server.
Are you using ODBC/ Query Analyzer from the server or the client?
I am getting a few problems as well after install MDAC 2.71 which has
somehow deleted my ODBC drivers from the Drivers tab window.
Regards
Z
Is the SQL a named instance?
"Anna N." <amnikol@.hotmail.com> wrote in message
news:6e225598.0307160146.5fadd9f2@.posting.google.com...
> I have several Win2000 servers running SQL Server 2000, SP2 (8.00.665)
> and only one of them developed this problem. When trying to set up a
> new ODBC setting using any other login than sa, it doesn't show any
> databases besides the system db's. When logging in with Enterprise
> manager (all other logins except sa), the Databases list shows 'No
> items'. All logins work fine with Query Analyzer. I already recreated
> missing guest accounts in some of the databases, but that didn't help.
> I've also installed the latest MDAC (2.7 SP1) and after that didn't
> correct the problem, I installed SP3a. It's still not working.
> I'm thinking about reinstalling SQL Server, but my client doesn't like
> the idea. So if anyone has any idea what might help, I'd be greatful.
> Thank you!
>
> br,
> Anna|||FYI:
First, I would try determine if it is an Server or Client Problem. ( The
Server has both Client and Server DLLs on it.)
To see if it is an client problem try to make the ODBC from a machine
without the problem to the Server with the problem.
If the problem is NOT there then it is an client problem.
If the problem is there confirm it by making an ODBC connect to one of the
Good Servers from the same test client.
If it is an server problem, I have nothing to suggest.
( Note my company spent over 40 man hours on an "Server Problem" that
turned out to be an client DLL issuse in SQL SP3)
If an client problem.
First check the version of SQLSRV32.dll ; is the correct one.
Link to version of SQLSRV32.dll
http://support.microsoft.com/default.aspx?scid=http%3a%2f%2fsupport.microsoft.com%2fservicedesks%2ffileversion%2fdllinfo.asp&fp=1
Then, I would try running the component checker ( on the MDAC ).
Link to info on component checker
http://support.microsoft.com/default.aspx?scid=kb;EN-US;307255
Link to download componet checker
http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-BF53-14332EF092C9&displaylang=en
Tim S
"Zenduce" <james@.zenduce.net> wrote in message
news:%238XHwp4SDHA.1664@.TK2MSFTNGP11.phx.gbl...
> Anna
> Firstly you need to have SQL SP3 if you have not applied the patch to
stop
> the SQL Slammer on the server.
> Are you using ODBC/ Query Analyzer from the server or the client?
> I am getting a few problems as well after install MDAC 2.71 which has
> somehow deleted my ODBC drivers from the Drivers tab window.
> Regards
> Z
>
> Is the SQL a named instance?
> "Anna N." <amnikol@.hotmail.com> wrote in message
> news:6e225598.0307160146.5fadd9f2@.posting.google.com...
> > I have several Win2000 servers running SQL Server 2000, SP2 (8.00.665)
> > and only one of them developed this problem. When trying to set up a
> > new ODBC setting using any other login than sa, it doesn't show any
> > databases besides the system db's. When logging in with Enterprise
> > manager (all other logins except sa), the Databases list shows 'No
> > items'. All logins work fine with Query Analyzer. I already recreated
> > missing guest accounts in some of the databases, but that didn't help.
> > I've also installed the latest MDAC (2.7 SP1) and after that didn't
> > correct the problem, I installed SP3a. It's still not working.
> >
> > I'm thinking about reinstalling SQL Server, but my client doesn't like
> > the idea. So if anyone has any idea what might help, I'd be greatful.
> > Thank you!
> >
> >
> > br,
> > Anna
>|||"Zenduce" <james@.zenduce.net> wrote in message news:<#8XHwp4SDHA.1664@.TK2MSFTNGP11.phx.gbl>...
> Firstly you need to have SQL SP3 if you have not applied the patch to stop
> the SQL Slammer on the server.
I already have SP3a installed, as you can see from my original post.
> Are you using ODBC/ Query Analyzer from the server or the client?
Several clients.
> I am getting a few problems as well after install MDAC 2.71 which has
> somehow deleted my ODBC drivers from the Drivers tab window.
This problem emerged BEFORE installing MDAC 2.71, as you can see from
my original post.
> Is the SQL a named instance?
No.
- Anna|||"Tim S" <stahta01@.juno.com> wrote in message news:<XamRa.4637$C71.307@.fe01.atl2.webusenet.com>...
> First, I would try determine if it is an Server or Client Problem. ( The
> Server has both Client and Server DLLs on it.)
It is most definitely a server problem. I wouldn't have posted a
question without making sure where the problem is exactly.
- Anna