No tables returned with "The specified module could not be found."

Hi All;

Attempting to expand the tables folder in our database on the esql2k501 server has suddenly returned the following error message:

-------------------------------------------------------------------------
TITLE: Microsoft SQL Server Management Studio Express
------------------------------

Failed to retrieve data for this request. (Microsoft.SqlServer.Express.SmoEnum)

------------------------------
ADDITIONAL INFORMATION:

The specified module could not be found. (Exception from HRESULT: 0x8007007E) (Microsoft.SqlServer.Express.ConnectionInfo)

-------------------------------------------------------------------------

We have not made any changes to either the pc, Server Management Studio Express or the connection details since the last successful connection 2 days ago. The website using this db is fine though.

Any idea what could cause this?

 

Were you referencing the correct DB? Please open a support ticket and include all the necessary information so we could take a look

 

"Were you referencing the correct DB?" --> yes

As mentioned, no changes have been made to the connection or login properties and we are able to connect without any problems.

The error only pop's up when we attempt to expand the "tables" folder in our db.

We have a second database hosted on esql2k502 and the same error is returned there.

"Please open a support ticket ..."

Before bothering support with this I thought it might be helpfull to check if somebody in the community might have a solution.

 

Is there anything in the windows event log?
Have you tried to create a local database to test this same action with?

Based on your description, this sounds like a local client side problem rather than a DASP server side problem.

 

Thanks CrystalCMS, you are spot on, it is a "client-side" issue and specifically the SSMS that somehow became corrupted.

I attempted to reinstall just the Management studio component, but ran into errors along the way. It seems that Windows 7 and MS SQL Server 2005 are not friends. Microsoft suggests that one uses 2008 R2 on a Windows 7 platform, again however it would not install correctly. The solution for me was to simply run a system image that I had made at a time when the SSMS was still acting correctly.

So in short, should you run into the errors I mentioned...reinstall MS SQL Server.

Thanks for your help.