December 15, 2003 at 10:38 am
Win2k Advanced with SP3
SQL2k Enterprise with SP3
Open Enterprise Manager on my workstation or on the server and the Databases section for this server shows 'no items'. Check Management and do not get anything, no icons. But I can go to the log folder and see the error logs there. Have tried with 'sa' and with my NT account(which is sysadmin). I can access all databases in QA and see all databases in the Object Browser in QA. The other servers I have registered in EM appear fine.
I saw MS 315523 about a deleted guest account and ran their script to detect if a guest account had been deleted, but that turned up negative.
Any ideas?
TIA,
Michelle Morris
Michelle
December 15, 2003 at 10:46 am
Something must be wrong with EM. Have you applied SP3? Might want to reapply to your workstation.
Steve Jones
http://www.sqlservercentral.com/columnists/sjones
The Best of SQL Server Central.com 2002 - http://www.sqlservercentral.com/bestof/
December 15, 2003 at 10:51 am
I reapplied SP3 on my workstation and still have the same problem. It is happening with any EM I use, my workstation, the server's copy of EM, other Server's EM. If it was just my workstation, I would easily say it is EM, but with 3 different instances of EM using 2 different authentication methods, I am stumped.
Michelle Morris
Michelle
December 15, 2003 at 11:09 am
Hmmm, that's strange. Can you run profiler and see if it's actually sending queries. Have you changed your pwd recently? Can you run queries through QA to this server with the same authentication?
Steve Jones
http://www.sqlservercentral.com/columnists/sjones
The Best of SQL Server Central.com 2002 - http://www.sqlservercentral.com/bestof/
December 15, 2003 at 11:29 am
1. Are you getting any errors in the Windows Event logs? (check both your workstation and the server hosting SQL Server)
2. In Enterprise Manager, Tools Option, select Query Analyzer. Run a query. Did it work? (This is different than openning Query Analyzer on it's own).
3. Open a command prompt window (Start>Run type cmd and click ok). Type: (replace <servername> with your actual SQL Server server name).
PING <servername>
4. If #3 didn't work, try using the server IP address instead of the name.
If #3 failed and #4 worked, your DNS server is not converting the name to the IP address and you will need to register the SQL Server by IP Address and not the name (or have the DNS server fixed).
-SQLBill
December 15, 2003 at 12:21 pm
--I haven't changed the password recently.
--I can run queries with either authentication.
--profiler shows all the queries/sp generated by EM and I don't see any errors.
--No errors in my event log or the servers' event log.
--DNS appears fine...can ping, can reach servers with terminal server and query anaylyzer by name.
--Accessing QA from EM works with both authentications.
Tonight I will reinstall Service Pack 3a and see if that helps with anything. I have compared *.dll from a server that is working correctly, that I thought had the exact same patches as this one, but see some differences.
Michelle Morris
Michelle
December 16, 2003 at 8:42 am
For completeness and future reference:
The problem must have been a corruption in ODBC. SQL was processing all the commands EM sent, but for some reason not sending them back???
I found out Friday that the admins uninstalled and reinstalled Symantec AV on this system. Maybe that caused a corruption somehow.
Last night, before I had a chance to install SP3 again, the admins installed Windows Update files. This included 823718 which updated the MDAC to 2.8 which would replace all the ODBC files. Problem solved, but I don't know why it happened.
Thanks to everyone!
Michelle Morris
Michelle
December 16, 2003 at 10:16 am
Thanks for the update. A good reason to keep track of everything that happens on a system. No matter how unrelated it seems.
Steve Jones
http://www.sqlservercentral.com/columnists/sjones
The Best of SQL Server Central.com 2002 - http://www.sqlservercentral.com/bestof/
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply