Monday, 20 September 2010

'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'

Friday, 17 September 2010

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......................

Tuesday, 14 September 2010

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

Friday, 10 September 2010

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.

Tuesday, 7 September 2010

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"

Friday, 3 September 2010

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

Sunday, 22 August 2010

Setting up the Search Service Application in PowerShell for SharePoint 2010

The below commands will do this, and avoid the horrible GUID's on the database names for the three Search databases that are created. You will need to amend the first few lines where indicated in RED. If you use different naming conventions then just adjust as required.

IMPORTANT NOTE: There is a character which is used in the below script on more than one occasion, that doesn't show on this blog!!!!! This is the breaker character, which looks like an 'I' and is normally located next to the left shift key.

Essentially you will not be able to copy the below, its more of a reference piece.

###################

$app = new-spserviceapplicationpool –name "SERVERNAME Search Application" –account Rob-Hardy\Search
$searchapp = new-spenterprisesearchserviceapplication -name "SERVERNAME Search Service" -applicationpool $app
$proxy = new-spenterprisesearchserviceapplicationproxy -name "SERVERNAME Search Service" -Uri $searchapp.uri.absoluteURI
$proxy.status

#####IF THE PROXY IS OFFLINE ENTER THIS##### $proxy.status = “online”
#####IF THE PROXY IS OFFLINE ENTER THIS##### $changestatus.update()

$si = get-spenterprisesearchserviceinstance –local
$si.status
Start-SpEnterpriseSearchServiceInstance -identity $SI
set-spenterprisesearchadministrationcomponent –searchapplication $searchapp –searchserviceinstance $si
$ct = $searchapp new-spenterprisesearchcrawltopology
$csid = $SearchApp.CrawlStores select id
$CrawlStore = $SearchApp.CrawlStores.item($csid.id)
$hname = hostname
new-spenterprisesearchcrawlcomponent -crawltopology $ct -crawldatabase $Crawlstore -searchserviceinstance $hname
$ct set-spenterprisesearchcrawltopology -active
$qt = $searchapp new-spenterprisesearchquerytopology -partitions 1
$p1 = ($qt get-spenterprisesearchindexpartition)
new-spenterprisesearchquerycomponent -indexpartition $p1 -querytopology $qt -searchserviceinstance $si
$PSID = $SearchApp.PropertyStores Select id
$PropDB = $SearchApp.PropertyStores.Item($PSID.id)
$p1 set-spenterprisesearchindexpartition -PropertyDatabase $PropDB
$qt Set-SPEnterpriseSearchQueryTopology -Active

Cannot reuse a deleted Managed Service Application name in SharePoint 2010

If you arrive in a situation where you cannot reuse an old deleted service application name because its supposedly in use or similar, then you can run the following commands.

The first one is as follows - in powershell;

C:\Users\installation> get-SpServiceApplicationPool

This will now show up the names for the Application Pools. Simply identify which one you need to delete, and then run the below command and adjust with the relevant name;

C:\Users\installation> Remove-SpServiceApplicationPool "APPLICATION NAME HERE"

Friday, 13 August 2010

This item and all items under it will not be crawled because the owner has set the NoCrawl flag to prevent it from being searchable

“This item and all items under it will not be crawled because the owner has set the NoCrawl flag to prevent it from being searchable"

In order to fix this issue (and this is true for any Site Collection), is to navigate to your MySite host and click on Site Actions > Site Settings.

From here, click on “Search and offline availability” under Site Administration, and ensure that you have Allow this site to appear in search results? set to Yes.

Sunday, 1 August 2010

PSConfig Checks

Below are some typical things you can check when running the PSConfig command when it fails:

1. Check the text carefully, is the server name and logon correct?
2. Is Windows 2008 being used? You may need to make firewall exceptions such as port 1433-1434 (SQL Database Engine)
3. Check that TCP/IP is enabled in SQL Configuration Manager
4. Do the servers ping each other?
5. Do the service accounts (installation and farmadmin) have the relevant SQL rights? (dbcreator, securityadmin and public?)

Wednesday, 14 July 2010

How to disable MySites in SharePoint 2007

Simply follow these steps:

1) Go to the Central Administration Web Page

2) Click on Shared Services Administration on the left hand navigation that you created for your site collection..in this case it's called 'SharedServices1'

3) From here, look under "User Profiles and My Sites" click Personalization Services Permissions

4) Select the group you want to limit the functionality for. (More than likely you will just have NTAuthority\Authenticated Users. )

5) On the next screen you will see a list of checkboxes:

--To disable MySites uncheck "Create Personal Site"
--To disable MyLinks uncheck "Use Personal Features"

6) Click Save

Tuesday, 29 June 2010

Disabling Windows Loopback Check for SharePoint Server 2007

The loopback check will cause constant password prompts appear whenever using host headers in SharePoint 2007. To get around this, you can make exceptions in the Loopback Check security feature, or completely disable it. The steps on how to sort this, are below:

Dev Environments (Less Secure Method)
  1. Click Start > Run > type 'regedit' > OK
  2. In Registry Editor, locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
  3. Right-click Lsa, point to New, and then click DWORD Value.
  4. Type 'DisableLoopbackCheck' and then press ENTER.
  5. Right-click DisableLoopbackCheck, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Quit Registry Editor, and then restart your computer.

Live Environments (More Secure Method)

  1. Click Start > Run > type 'regedit' > OK
  2. In Registry Editor, locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
  3. Right-click MSV1_0, point to New, and then click Multi-String Value.
  4. Type BackConnectionHostNames, and then press ENTER.
  5. Right-click BackConnectionHostNames, and then click Modify.
  6. In the Value data box, type the host name or the host names for the sites that are on the
  7. local computer, and then click OK.
  8. Quit Registry Editor
  9. Restart the Computer

If you are doing this on SharePoint, you will need to do this on all SharePoint servers in the Farm.

SharePoint 2007 Anonymous Access and STSADM Lockdown

To setup Anonymous Access, please see the below basic steps (remember to change the URL):
  1. Logon to the SharePoint Server
  2. Open Command Prompt
  3. Edit and type the following command: stsadm -o activatefeature -url http://intranet -filename ViewFormPagesLockDown\feature.xml
  4. Still in command prompt, edit and type the following command: stsadm -o deactivatefeature -url http://intranet -filename ViewFormPagesLockDown\feature.xml
  5. Finally, open Central Administration and click Application Management > Authentication Providers and select the relevant Web App you wish to enable Anonymous Access on
  6. Toggle Enable Anonymous Access check box (go in and out of this screen, essentially leaving Anoynmous Access turned on and thus toggling it)

From here, as long as the site collection should be ready to go.

Configuring the Adobe PDF iFilter for SharePoint 2007

Below are steps for installing the x64 Adobe PDF iFilter for SharePoint 2007:


  1. First of all, install the x64 Adobe PDF iFilter to the SharePoint index server. This file can be found on the Adobe website, or by searching Google
  2. When installed, open Central Administration on the index server
  3. Open the SSP thats relevant to the iFilter
  4. Click Search Administration under the Search heading
  5. Click File Types
  6. Click New File Type
  7. Type pdf and click OK

Next, we need to verify that PDF has been added to the registry correctly:

  1. Run Regedit by browsing to c:\Windows\system32\regedt32.exe
  2. Within the left hand side tree, browse to: \\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Applications\{site GUID}\Gather\Portal_Content\Extensions\ExtensionList
  3. If PDF extension is present, skip to Step 8 to verify the second location. If PDF extension is not present, continue with the next step
  4. Right click on right-side Extension List pane and choose New > String Value
  5. Add a name to the new Registry Key (e.g. “38” - basically the next in line)
  6. Double click the new Registry Key. For Value data, enter pdf
  7. This would automatically add an entry for ‘pdf’ filetype as mentioned above
  8. Verify that PDF has the correct settings in a second registry location.
  9. While still in Regedit, within the left-side tree, browse to: \\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\Filters\.pdf
  10. Verify the following values. If values are not as shown, edit them.
    i. Default =
    ii. Extension = pdf
    iii. FileTypeBucket = 1
    iv. MimeTypes = application/pdf
  11. Verify that PDF has the correct settings in a third registry location.
  12. While still in RegEdit, within the left-side tree, browse to: \\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.pdf
  13. Verify the following values. If values are not as shown, edit them.
    i. Default = {E8978DA6-047F-4E3D-9C78-CDBE46041603} OR {56BD18AD-CF9C-4110-AAAA-B2F96887D123}

The final part, is to sort out the PDF Icon. If you search on the internet, there are plenty of 16x16 PDF Icons about. Firstly obtain this, and proceed with the following steps on the index server.

  1. Copy the 16x16 PDF Icon you have downloaded to the following location:
    C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\IMAGES
  2. Add an entry in docicon.xml for the pdf icon by copying/pasting and adjusting one of the other entries on a new line. The location for this XML file is:
    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\XML

The last thing to do is restart all SharePoint services as well as IIS:

  1. Launch the Command Prompt by clicking Start > All Programs > Accessories > Command Prompt
  2. Type the following at the prompt: “net stop osearch”. Wait for success message.
  3. Type the following at the prompt: “net start osearch”. Wait for success message.
  4. Type the following at the prompt: “iisreset”. Wait for success message.
  5. Close the Command Prompt window.

Microsoft Office SharePoint Server can now index PDF files. Also, the PDF icon should show in File Types list in Central Administration and therefore along side the search results that appear.

Moving SQL Databases

SQL Steps for moving databases to another drive are outlined below. This example is for SharePoint 2007 databases, that are on SQL 2005:

  1. Logon to SharePoint and stop the relevant IIS Website
  2. Logon to SQL, and right click the server name and click Properties
  3. In the dialog box, click Database Settings on the left, and change the default locations for all new databases
  4. Now, right click a relevant database and click Tasks > Detach...
  5. When the box appears, check the exact database and log file names and make NOTES of them
  6. Select the Drop Connection checkbox
  7. Click OK
  8. The database should now dissapear from the left pane
  9. Still on SQL, open Windows Explorer and locate the MDF and LDF files, and copy and paste them to the new drives and make a note of the new location
  10. In SQL Manager, Right click Databases and select Attach and point to the new locations for the MDF and LDF Files
  11. Start the Website in IIS on SharePoint

From here, check the site works. If the pages cannot be displayed, it maybe due to the SQL Database permissions being incorrect. You may need to check to see if there is a DBOwner etc.

There maybe different considerations for databases that aren't for SharePoint 2007.

SharePoint 2007 Version Numbers

Below is a list of SharePoint 2007 and WSS 3.0 Version Numbers, which you can find in Central Administration's Site Actions > Site Settings screen.

12.0.0.6535
SP2 + April 10 CU (KB981042 + KB981043)

12.0.0.6529
SP2 + February 10 CU (KB978396 + KB978395)

12.0.0.6524
SP2 + December 09 CU (KB977027 + KB977026)

12.0.0.6520
SP2 + October 09 CU (KB974989 + KB974988)

12.0.0.6514
SP2 + August 09 CU (KB973400 + KB973399)

12.0.0.6510
SP2 + June 09 CU (KB971538 + KB971537)

12.0.0.6504
SP2 + April 09 CU (KB968850 + KB968851)

12.0.0.6421
SP2 (KB953338 + KB953334)

12.0.0.6341
February 09 CU (KB961755 + KB961756)

12.0.0.6335
December 08 CU (KB960010 + KB960011)

12.0.0.6331
October 08 CU (KB957691 + KB957693, KB958567 + KB958569)

12.0.0.6327
August 08 CU (KB956056 + KB956057)

12.0.0.6318
Infrastructure Update (KB951695 + KB951297)

12.0.0.6303
Post-SP1 Hotfix (KB948945)

12.0.0.6301
Post-SP1 Hotfix (KB941274)

12.0.0.6300
Post-SP1 Hotfix (KB941422)

12.0.0.6219
SP1

12.0.0.6039
October 2007 Public Update

12.0.0.6036
August 2007 Hotfix package

12.0.0.4518
RTM

12.0.0.4407
Beta 2 TR

12.0.0.4017
Beta 2

12.0.0.3111
Office 12 (PDC image - pre-beta) - This version of Office does not have a support link in the Add/Remove programs dialog box.