'Property Owner is not available for Database' Error Message in SQL Management Studio

When trying to open the properties for a database in SQL Management Studio, you may encounter a message that states 'Property Owner is not available for Database'

This can happen on restored databases. To solve this, adjust the below query;

USE SampleDB
EXEC sp_changedbowner 'DOMAINNAME\USERNAME'

Creaing a new Application Proxy Group in SharePoint 2010

In PowerShell, type the following command and adjust the name as required;

New-SPServiceApplicationProxyGroup –Name "Project 2010 Proxy Group"

Project Server 2010 - Installation Notes

Below are some installation notes that have created, during various installations. This will be added to where required.

1. For backup purposes, it is best to have a SEPARATE content database for PWA with a Site Collection limit of just ONE. This doesn't restrict the amount of project workspaces that are created as they are not site collections.

2. Check the other note sections for things such as PerformancePoint for considerations to make there. These are on this site.

3. If applying server updates, you will need to download the Project Server 2010 update that you want. This will contain the SharePoint Server update. You do not need SharePoint Foundation update!! This is included in the main update itself, unlike 2007 where you needed to install the WSS update beforehand.

More to come......................

SharePoint/Project 2010 - PerformancePoint Configuration Notes

Below are some notes that I have made, for the configuration of PerformancePoint. These are notes when I have come across problems, for example when I couldn't connect to a data source in the designer, or couldn't even get in the designer without error.

1. Check the PerformancePoint service has been started
2. Check a suitable Unattended Service account has been applied
If using a unique unattended service account for performancepoint (e.g. not the farmadmin or similar), you will need to open SQL Management Studio and connect to Analysis Services. From here you will need to add the performancepoint account to the ProjectServerViewOLAPData role. this error sometimes throws ACL related messages!
3. Check the Secure Store has been setup properly
4. Maybe try checking the Unattended Service Account has DB Owner rights on the relevant Content DB
5. You could also check that Excel Services can connect, as this may generate more helpful error messages or logs

Changing Web Application Account in SharePoint 2010

In order to change the web application account, you need to open central administration and click Security > Change Service Accounts.

I found this useful for when I had a faulty Windows Profile for one of my accounts.

You can change the Farm Admin account here, as well.

Changing Index locations in SharePoint 2010

The below commands are useful if you didn't setup the Index Location when originally configuring the farm. It is also useful if you want to move the indexes to a new drive or similar.

Two of the below are for index locations, and the PowerShell command is for the default index location for any newly created indexes.

Index Location (See what it currently is)
stsadm -o spsearch -action list

Index Location (Change what it is)
stsadm -o spsearch -indexlocation "E:\SharePoint Indexes" (This is your new index location)

Default Index Location (Change in PowerShell)
1. Get-SPEnterpriseSearchServiceInstance
2. Set-SPEnterpriseSearchServiceInstance –DefaultIndexLocation "E:\SharePoint Indexes"

Windows account logs on as a temporary profile

This sometimes happens on Windows 7 and Windows 2008 after a profile is deleted. The solution:

1) login to the box as an administrator

2) open regedit and navigate to:

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

3) expand ProfileList so that you can see a list of SIDS of loaded user profiles

4) click on each SID in turn and look at the ProfileImagePath value to determine which user profile the SID belongs to

NOTE: You can at this point simply delete the profile however you will loose the data. This is the only option at the time of this post which I have tested. Step 5 below may avoid this! But I havent tested it.

5) add .old to any SIDs (including ones ending with .bak!!! - i.e. .bak becomes .bak.old ) belonging to the user profile that keeps logging in on a TEMP user profile

6) reboot

7) now login as the user and you should log in as that user now