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 bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Enterprise Manager Problem 2

Status
Not open for further replies.

PM2000

Programmer
Aug 18, 2000
42
BM
Hi,

I hope you can help, I am somewhat of a newcomer to SQL Server 2000. I have been using it for at least 6 months now and all of a sudden, when I open my Enterprise Manager and try to connect to a database, I get the following error:

&quot;A connection could not be established to <DB name>&quot;

&quot;Reason: General OLE Error 16386&quot;

This has me stumped because I test the DSN through the ODBC Data Source Administrator and all is fine. I can also pull up Query Analyzer and read/query the tables with no problems.

Any ideas.

Thanks,
Peter
 
Can you open the server node?
Can you open any of the database folders? JHall
 
Thanks for responding!

I can open the group and see the servers listed there. However, as soon as I try to connect to the server, it gives me the error.

Peter
 
It sounds like your registration is funky.

Whenever I've had this message, this works for me.

Try this

Right click the server in question, Delete SQL Server Registration. This will not do anything untoward to your SQL Server but will just remove it from the Management Console.

The right click the server group and New SQL Server Registration to re-register the server. JHall
 
Check if you have two copies of this file on your system. Sometimes another software package installs an older or different version of the dll and breaks SEM. If you find two copies of the file do the following.

1. Unregister the older or incorrect sqldmo.dll by running regsvr32 /u sqldmo.dll from a command prompt window

2. Rename the old sqldmo.dll to sqldmo.old

3. Register the correct sqldmo.dll by running regsvr32 sqldmo.dll from a command prompt window. The correct version should be in the SQL Server install direstory.

If you don't have two copies, check the version of sqldmo.dll to make sure it is current. The file should be in the SQL Server install directory. Typically this is...

C:\Program Files\Microsoft SQL Server\80\Tools\Binn Terry L. Broadbent - DBA
Computing Links:
faq183-874 contains &quot;Suggestions for Getting Quick and Appropriate Answers&quot; to your questions.
 
Thank you both for your help. It is finally working!

I re-registered the dll and it is fine. I installed zetafax on my PC 2 days ago to test it out and it used the same console as SQL Server. I am guessing that it must have registered an older version of the DLL or something like that.

Thanks again.
Peter
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top