question

Dennis F avatar image
Dennis F asked

Error when opening the database folder in SSMS 2008

I am running SSMS 2008. When I connect to SQL Server running 2005 and attempt to open the databases folder I get the following error:

TITLE: Microsoft SQL Server Management Studio

Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Could not find database ID 33. Database may not be activated yet or may be in transition. Reissue the query once the database is available. If you do not think this error is due to a database that is transitioning its state and this error continues to occur, contact your primary support provider. Please have available for review the Microsoft SQL Server error log and any additional information relevant to the circumstances when the error occurred. (Microsoft SQL Server, Error: 913)

I ran sp_helpdb and searched the list of dbid's and ID 33 was not on the list. Has anyone run into this issue, or better yet resolved it?

Thank you in advance for your replies.

ssms
10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

2 Answers

·
Dennis F avatar image
Dennis F answered

The problem is solved. Restarting SQL Server solved the error.

1 comment
10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

TimothyAWiseman avatar image TimothyAWiseman commented ·
Remember you can mark your own solution as accepted. Also, I have had a similar problem in the past and it was fixed by rebooting.
0 Likes 0 ·
DaniSQL avatar image
DaniSQL answered

Dennis,

Am glad it worked out well for you now. However in production environment make sure you research any problem thoroughly before you restart sql server. As an example check out Myth#21 on Paul Randal's blog about the effect of rebooting servers on suspect/corrupted databases.

3 comments
10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Fatherjack avatar image Fatherjack ♦♦ commented ·
Wise advice but in the scenario described in the question there was no database, let alone a corrupt one. The symptoms were connectivity related and as such a reboot potentially 'wouldnt hurt'. I am not saying that any time you get a connectivity issue go straight for the on/off but providing there were no identified issues other than the one described its not wholly surprising that a reboot has not had a negative effect and indeed in this case it has had a positive one. When dealing with a production server look twice and twice again before hitting the On/Off switch - for services or power
0 Likes 0 ·
DaniSQL avatar image DaniSQL commented ·
@Fatherjack: I understand...I restart instances my self from time to time but I am throwing it out there as a reminder that restarting might not be a good solution in case some 'poor DBA' got this thread in the future while looking for a solution and misunderstood it.
0 Likes 0 ·
TimothyAWiseman avatar image TimothyAWiseman commented ·
One should reboot production servers very rarely and cautiously as Dani said. Of course, I have had it fix some very weird problems, including one I had very similar to what Dennis described.
0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.