Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

EM lost connection to server

Status
Not open for further replies.

SQLBill

MIS
May 29, 2001
7,777
US
I have Enterprise Manager on a remote machine. Each day I select my SQL Server and check my jobs, security, etc. No problem. Today I selected the Server and got the error message:
-----------------------
A connection could not be established to MyServerName.

Reason: General OLE Error 16386

Please verify SQL Server is running and check your SQL Server registration properties.
---------------------------
SQL Server Service and SQL Server Agent Service are both running. The registration hasn't changed. I can connect and do queries with Query Analyzer. I can PING the SQL Server. I just can't connect to it via Enterprise Manager.

Does anyone have any suggestions as to what happened and what I can do to solve this? As I said, it worked fine when I left work yesterday but it's not working today. No one else has 'messed' with my remote machine nor the actual SQL Server. I can use EM on the actual SQL Server just fine.

-SQLBill
 
Bill,

Check the version of SQLDMO.DLL. Make sure it matches the version of Enterprise Manager installed. You may have multiple copies on your hard drive and an incorrect version may be registered. You will need to unregister the "bad" version and register a good version of the DLL.

Of course, if nothing was installed on the PC, you won't find multiple copies of the DLL and there may be some other problem. A necesary DLL may be missing or corrrupted. You might need to reinstall the client tools. If you want to get the best answer for your question read faq183-874 and faq183-3179.
Terry L. Broadbent - DBA
SQL Server Page:
 
Terry,

Thanks for the info. After some testing, here's what happened.

I had the Client tools previously loaded. On April 9th, I was installing a part of Veritas' Backup Exec (the ExecView portion). This installs MSDE (which I wasn't aware of at the time of my posting). Then EM quit working. I eventually found out that MSDE 7.0 was installed on my system by Veritas. Once I uninstalled MSDE and reinstalled the SQL client tools, everything works right.

What I can't figure out is why MSDE being installed caused a problem with EM. But now I'm guessing (based on your input) that Veritas updated the sqldmo.dll and since Veritas installed ver 7 and my EM is 2000; the two weren't compatable.

Oh well, my EM is working again and I'm going to have to do some more tests/trials to get the Veritas program to work.

-SQLBill
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top