Refresh your SSMS display of databases and see if it actually attached despite your original error. It may have attached and then threw an error with some post-attach step.

I'm not sure what's going on then. The files may have been corrupted in the transfer?

Did you move between drives on the same server...to a different server...just...

That fact that you don't see them in the tree is odd...it should show up anything with a .mdf extension (or if you select All Files, it should show them...

Yep.

Either detatch the database, move the files to where you want them and reattach.

Or do a full backup of it, and restore it over itself usuing WITH MOVE in...

Also read the entry in books online about returning things...

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/afe3d86d-c9ab-44e4-b74d-4e3dbd9cc58c.htm

Our network gury finally called Microsoft. We were also having other issues on some of the servers. Turns out all we needed to do was rebuild every index...

The log isn't full.

restarting services does help, but has...

Thanks. It suggests in that post to "defragment your virtual memory". Anyone know how to do that?

We rebooted that server last night for other reasons, and magically it is working fine now. I don't know why, but I'm not going to complain!

Thanks

Service account is local admin on the server, and I log in with windows authentication, with my windows user being a sysadmin.

What would cause the linked servers to work just fine, but SSMS not be able to manage them? I can manage them with scripts fine also. Strange.

I don't think it's a(n) SSMS issue. I don't use the SSMS on the server, I use a copy installed on my workstation. But just for grins I...

Oh...if it's a 3rd party application, you might want to check with them first. Sometimes if you mess with things they set up it can cause you to lose...

I wouldn't think you would need your msdb database to be in full recovery model. What are you doing that necessitates full recovery model for that database?

Taking out the parentesis arround the select statement fixed it.