ERROR: Cannot show requested dialog

Question

Post reply

ERROR: Cannot show requested dialog

James Darnell

SSC-Addicted

Points: 452
More actions
April 3, 2006 at 12:45 pm

#168902

Good afternoon ladies and gentlemen. We recently set up our first SQL2005 test box in house and began slowly restoring old SQL 70 databases to this machine for testing. Everything was working fine as of last week. However, this week I went in to change the compatibility mode on one of the databases and received the error detailed below. This is very strange and happens regardless of which database I choose. I've even logged in under the sa account and still receive the same message. Has anyone seen this before? Any help, even educated guesses, would be greatly appreciated. Thank you in advance!
TITLE: Microsoft SQL Server Management Studio
------------------------------
Cannot show requested dialog.
------------------------------
ADDITIONAL INFORMATION:
Cannot show requested dialog. (SqlMgmt)
------------------------------
Property Owner is not available for Database '[coda]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.PropertyCannotBeRetrievedExceptionText&EvtID=Owner&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
April 6, 2006 at 8:00 am

This was removed by the editor as SPAM

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply

Maximilian Haru Raditya SSC Enthusiast Points: 145 More actions · Answer 1

Maybe you can try this:

ALTER AUTHORIZATION ON DATABASE::coda TO sa

Hope helps.

--
Regards,

Maximilian Haru Raditya

Ameena Lalani-347953 Old Hand Points: 332 More actions · Answer 2

Did this command worked for anybody? I am getting the same exact error.

Thanks

Mohamed-416781 SSC Enthusiast Points: 138 More actions · Answer 3

Cause.

The above error happened because the original dbo login of that database was removed recently from the SQL Server 2000 instance.

Solution.

Change the owner of the database. This will fix your issue.

For example:

USE SampleDB

EXEC sp_changedbowner 'sa'

abeljda Say Hey Kid Points: 675 More actions · Answer 4

had the same issue, running:

USE xxxx

EXEC sp_changedbowner 'sa'

fixed the error

Steve Callan-432616 Valued Member Points: 65 More actions · Answer 5

Use sp_helpdb to see list of databases - missing owner will be shown as NULL. If no owner, then several tool/utilities will not work. Easiest fix is to set the owner to sa (an account that will always be present).

The syntax is different between 2000 and 2005:

2005: ALTER AUTHORIZATION ON DATABASE(two colons)DatabaseName to sa;

2000: EXEC DatabaseName..sp_changedbowner ‘sa’;

I know this post is old, but this site comes up near the top on a Google search on how to find/change the owner, so a complete answer would be useful.