Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Right click on a Database, select properties Error, cannot show requested dialog. Expand / Collapse
Author
Message
Posted Wednesday, July 03, 2013 6:54 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Saturday, April 12, 2014 4:30 PM
Points: 4,050, Visits: 4,190
I right click on a Database, select properties Error, cannot show requested dialog.

The error reads:

cannot show requested dialog (SqlMgmt)

Property Size is not available for Database '[DataWarehouse]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SQLServer.Smo)

I'm running Database Consistency Checker.

Has anyone experienced this problem?



For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Post #1470025
Posted Wednesday, July 03, 2013 6:58 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, April 11, 2014 6:51 AM
Points: 1,371, Visits: 2,590
I've seen this in SQL 2005 while running index rebuilds. It would not allow me to see DB properties via GUI, I could query the properties though.

I'm inclined to think it has something to do with too many locks on the database. Not sure though
Post #1470028
Posted Wednesday, July 03, 2013 9:01 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 4:21 AM
Points: 41,507, Visits: 34,422
Check that the database owner is set to a valid account. SA is often used.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1470099
Posted Wednesday, July 17, 2013 4:07 AM


SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Saturday, April 12, 2014 3:50 AM
Points: 79, Visits: 341
Maybe related also to your access rights on the server.

Cheers!
[url=http://coffeeandsql.com/][/url]

Post #1474478
Posted Wednesday, July 17, 2013 4:23 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 2:00 AM
Points: 2,078, Visits: 2,409
GilaMonster (7/3/2013)
Check that the database owner is set to a valid account. SA is often used.


In my experience this is most time the cause of the error. The login of the current database owner is removed/altered and not valid anymore.


** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **
Post #1474483
Posted Wednesday, July 17, 2013 10:39 AM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Friday, March 28, 2014 2:32 PM
Points: 503, Visits: 1,460
I've seen this happen with a funky installation of Management Studio. Try it from another computer.
Post #1474728
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse