Desktop

Ask something
Discussion Locked

Enterprise Manager Error (SQL)

0 helpful
5 replies

by ehoffman

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Installed SQL 2000 on my XP machine to test the trial version....MDAC 2.7 installed, comcheck says its a good install. However, when I try to open a table in enterprise manager, I get an error that says "specified module not found". Do I need to reregister something? What can I do to fix. Tried uninstalling, went back to the 7 edition I have, smae problem, uninstalled, regcleaned, reinstalled 2000, still there. Any help desperately appreciated!

5 replies

by maxwell edison

You may need to register COM based DLLs through the Regsvr32 utility.

You may need to place native Win32 DLLs in the application path.

You may also place native Win32 DLLs into the Win32 directory.

These suggestions are from a larger Microsoft article, Q248241 titled, "Enabling SQL DMO Clients Without Installing the Client Side Utilities". You may find it helpful.

See the entire article at the following link:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q248241(REMOVE SPACES from the pasted URL.)

Maxwell

by ehoffman

Nothing in that article helped....regsvred the dmo.dll, but no effect. Everything else panned out considering I am looking at 2000 versus that info for MSSQL 7. Again, in EM, I right click on a table, choose open table...new window pops up, bam, "Specified Module Cannot be Found". Click on help, this comes up: "ODBC error: <0s>.
An ODBC error has been generated."

This is true whether I browse tables locally or on another remote SQL Server.

by timthetoolman

Hi,

The following is an extract from the page...

http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=14347

(remove spaces from the above URL)

The error message is different but the general problem is the same. I suggest copying all the DLLs from "SQL Server 7.0 CD \x86\other\sdi" to \BINN

But not which ones you copy and perhaps dont overwrite any - so you can back back out.

Here's the extract...

Q. I'm getting an error message - "Cannot Load DLL 'SDI' Reason 126( The specified Module Cannot be found)" when doing a stored-procedure debug on SQL Server. Or breakpoints just don't fire.

A. With SQL 6.5/VC5/VB5 copy the sdi.dll file from your VB/VC/VS enterprise CD into the \binn directory.

For SQL 7.0 get the files from the SQL Server 7.0 CD \x86\other\sdi.

VB 6.0 copy SDI60.DLL into the \BINN directory
VC 6.0 copy SDI.DLL into the \BINN directory
VI 6.0 copy MSSDI98.DLL into the \BINN directory

(You can't debug SQL 7 with VB5/VC5)

Cheers,
Tim.

This discussion is closed to new replies.