Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a WSS 3.0 running on Server 2008 R1. The log files have grown to almost 15GB and need to be compressed/purged as we are running out of space on the hard drive. I have connected to the database "\.\pipe\mssql$microsoft##ssee\sql\query" using SQL Studio Express, however I get the following error when right-clicking on the SharePoint_Config database and selecting Properties:


Property Owner is not available for Database '[SharePoint_Config_29c26fca-17b8-48c1-9704-b869932abcb6]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SqlServer.Express.Smo)

------------------------------ For help, click:

------------------------------ Program Location:

at Microsoft.SqlServer.Management.Smo.PropertyCollection.HandleNullValue(Int32 index) at Microsoft.SqlServer.Management.Smo.PropertyCollection.GetValueWithNullReplacement(String propertyName, Boolean throwOnNullValue) at Microsoft.SqlServer.Management.Smo.Database.get_Owner() at Microsoft.SqlServer.Management.SqlManagerUI.CreateDatabaseData.DatabasePrototype.DatabaseData..ctor(CDataContainer context, String databaseName) at Microsoft.SqlServer.Management.SqlManagerUI.CreateDatabaseData.DatabasePrototype.LoadDefinition(String newName) at Microsoft.SqlServer.Management.SqlManagerUI.CreateDatabaseData.DatabasePrototype..ctor(CDataContainer context) at Microsoft.SqlServer.Management.SqlManagerUI.DBPropSheet..ctor(CDataContainer context)

I am trying to follow the procedure as explained here:

share|improve this question
up vote 2 down vote accepted

I've seen this before on Windows Small Business Server 2008 where the SharePoint_Config database owner was NULL. I don't know how or why it happens, but you can see if it's the case in your situation using sp_helpdb. If you find it is you can use sp_changedbowner to set the owner. On the SharePoint_Config database setting the owner to sa will work fine.

Basically, you'd connect to the database with SSMS and run a query like:

USE [SharePoint_Config_29c26fca-17b8-48c1-9704-b869932abcb6]
EXEC sp_changedbowner ‘sa’

That'll set the owner.

share|improve this answer
That was exactly what the problem was! Executing sp_changedbowner fixed it right away. Thank you :) – Brett Anspach Nov 23 '11 at 19:04

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.