Property Owner is not available for Database.. err | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Property Owner is not available for Database.. err

Sometimes when trying to get to database Properties I get an SMO error:
Property Owner is not available for Database…. This property may not exist for this object, or may not be retrievable due to insufficient access rights. When logging as sa I get the same error.
Did you try from different server?
If you don’t get the same error on different machine try to reistall client tools..
MohammedU.
Moderator
SQL-Server-Performance.com All postings are provided “AS IS” with no warranties for accuracy.
same thing on a different server.
What version of service pack you have?
Such SMO bug has been fixed in SP1 –http://www.microsoft.com/downloads/…aa-b4bd-4705-aa0a-b477ba72a9cb&displaylang=en fyi. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.
I have SP1 running
How about on the client tools? Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.
Microsoft SQL Server Management Studio9.00.2047.00, which I beleive is SP1.
How would I upgrade the client tools that are on the server without upgrading the sql server?
I have not done this but…
When you run service pack setup at some point you see the option where you can uncheck the check boxes if you don’t want to apply the SP.
MohammedU.
Moderator
SQL-Server-Performance.com All postings are provided “AS IS” with no warranties for accuracy.
it seems to matter not. I ave SP1 on both the server and MS, on my desktop and all the servers, you name it.. Still getting the ugly error.
The way I got around that is altering authorization manually.
Thanks anyway.
]]>