Friday, July 10, 2009

Out Of Office

On the 18th July 2009 I set off driving 10,000 miles from Hyde Park, London to Ulaanbaatar, Mongolia. For more information and what happened visit my website

I will be out of office, travelling until August 2010 so appologies for the lack of new posts but if you are inclined check out my travel blog here:

And I do also have a professional website with full client list and examples of past work. If you want to get in touch this is probably the easiest way to find me:

Wednesday, July 01, 2009

MOSS July Infrastructure Update

  1. Download the infrastructure updates for both WSS and MOSS
  2. Install the WSS infrastructure update on all the servers in the farm. Do not run the Wizard at the end
  3. Install the MOSS infrastructure update on all servers in the farm. Again, do not run the Wizard at the end
  4. Run the Wizard on the server hosting the Central Administration Web Site
  5. Run the Wizard on the remaining servers in the farm one at a time
  6. Once all the servers are upgraded, verify in Central Administration that the version number is bumbed to

Wednesday, April 01, 2009

Connecting PPS to MOSS Sub Site Master Pages

When you deploy a dashboard from Performance Point Server you have the option of choosing which master page you want to use. By default you will see all the master pages in the SharePoint master page gallery of the site collection you are publishing too.

If you are in a subsite of your portal unless you have copied your custom master pages to the site collection master page gallery you will only see the default.master in the PPS dropdown since this is the only master page in the subsite master page gallery.

For example:
To solve this simply copy your custom master page to the subsite master page gallery.

Tuesday, March 31, 2009

Ping Commands!

This comes from:


[-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS]
[-r count] [-s count] [[-j host-list] | [-k host-list]]
[-w timeout] destination-list


-t - Pings the specified host until stopped.

To see statistics and continue - type Control-Break;
To stop - type Control-C.

-a - Resolve addresses to hostnames.
-n - countNumber of echo requests to send.
-l - sizeSend buffer size.
-f - Set Don't Fragment flag in packet.
-i TTL Time To Live.
-v TOS - Type Of Service.
-r count - Record route for count hops
-s count - Timestamp for count hops.
-j host-list - Loose source route along host-list.
-k host-list - Strict source route along host-list.
-w timeout - Timeout in milliseconds to wait for each reply.


ping localhost

Pings the local host, this will allow you to see if the computer is able to send information out and receive the information back. Note that this does not send information over a network but may allow you to see if the card is being seen.


Allows you to ping another computer where the x's are located are where you would place the IP address of the computer you are attempting to ping. If this is not able to complete this should relay back an unsuccessful message which could be an indication of cable issues, network card issues, hub issue, etc.


PING ( 56(84) bytes of data.
64 bytes from ( icmp_seq=1 ttl=63 time=0.267 ms

--- ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.267/0.267/0.267/0.000 ms

Friday, March 27, 2009

Adding users to Project Server PWA site

To grant users access to the PS PWA site they need to be added via the Server Settings / Manage Users page in the PWA site. Simply adding them through Site Settings / Advanced Permissions will not work.

Installing Project Server 2007 on an existing MOSS farm with Kerberos enabled

I have a medium server farm running MOSS 2007. There are three servers (2 WFE, 1 Index & 1 SQL).

Note - Project Server cannot be uninstalled from a joint MOSS / PS installation

To install Project Server 2007:
  1. Copy Project Server installer on to each server - i put them in C:\Temp
  2. Quiesce the MOSS farm via Central Administration / Operations
  3. Run the PS install files on each server in the farm
  4. Unquiesce the farm
  5. Run the MOSS configuration wizard on each server one by one
Start the Project Server Service:
  1. Open Central Administration and select the Operations tab
  2. Select Services on Server
  3. Select the server you want to run the Project Server service
  4. If the Project Server Service is not dispayed change the server role to Custom

  5. Start the Project Server service
Provision the Project Server site:
  1. Open Central Administration and navigate to Shared Services Administration
  2. Open the SSP that on to which you want to provsion Project Web Access (PWA)

  3. On the SSP homepage select Project Web Access Sites
  4. Select Create Project Web Access Site

  5. Select the MOSS web application to host the PWA
  6. Assign a PWA path for example: projectserver
  7. Assign the Administrator Account for the PS instance
  8. Assign the primary database SQL server
  9. Name the four PS databases
  10. Click OK
  11. When provisioning is complete Provisioned will appear in the status column - to refresh the status click Refresh Status

  12. To enable access you must ensure that you have registered the server SPNs for Kerberos delegation and for the web application process accounts. Until you do this you will get an access denied error when you try to access the PWA site.

Thursday, February 12, 2009

A theme with the name "CustomMySite 1011" and version already exists on the server.

You receive this error when trying to apply a custom theme to your SharePoint site:

"A theme with the name "CustomMySite 1011" and version already exists on the server. "
  1. Open your site in SharePoint Designer.
  2. Expand _themes and delete the CustomMySite theme folder
  3. Re-apply the custom theme to your site.

Thursday, January 15, 2009

Enabling MOSS Anonymous Access

  1. From Central Administration > Application Management > Application Security > Authentication Providers, select a Web application and the zone you want to modify. This is usually default.

  2. In the middle of the page, check Enable Anonymous Access and choose Save

  3. All site collections in that Web application can now have anonymous access enabled.

  4. Go to a site collection in the Web application you just enabled anonymous access for

  5. From Site Actions > Site Settings, open Advanced Permissions

  6. From the Settings drop-down menu, select Anonymous Access

  7. For this example, enable anonymous access for Lists and Libraries and click OK

  8. Browse to any document library in this site collection

  9. From the Settings drop-down menu, select Document Library Settings

  10. In the Permissions and Management column, select Permissions for this document library

  11. From the Actions menu, select Edit Permissions to break inheritance

  12. From the newly appeared Settings drop-down menu, select Anonymous Access

  13. Check View Items and click OK.

Monday, January 12, 2009

Issues after restoring MOSS to a previous VM snapshot

We restored our VM MOSS farm this morning from a snapshot taken a couple of months ago. Various issues occurred. Please note i am still working through some of the errors and will update this post as i find the answers.
  1. I could no longer login to the server because the snapshot was older than 30 days - the computer account for the server had expired and so needed to be reset and reconnected to the domain. See this blog for steps to fix this.
  2. The MOSS environment although appearing correct in Central Administration was not configured in IIS. The Central Administration site was the only site appearing in IIS even though all the web applications were still there.

    To fix this:

    1. Delete the old web application using Central Administration.
    2. Delete all the SSP web apps & DBs, apart from the default SSP which cannot be deleted.
    3. Recreate the web applications with Temp DB names.
    4. Recreate the SSPs with new DBs.
    5. Change the default SSP to one of the newly created SSPs, then delete the original default SSP inc DB, then recreate it's web app and set back to the default updating any associations as required.

      At this point I ran in to some issues recreating the SSP with the following errors. First of all the SSP failed to provision with the error:

      Provisioning failed: A transport-level error has occurred when sending the request to the server.

      Looking in the Event Log i found the following related errors:

      Event ID 5554
      Failure during sweep synch. Exception was A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).

      Event ID 7888
      A runtime exception was detected. Details follow.
      Message: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)

      Event ID 5586
      Unknown SQL Exception 10054 occured. Additional error information from SQL Server is included below.

      A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)

      Reboot the server and kill any remaining connections (delete the Admin accounts from local users & groups, reboot, add the Admin accounts back in).

      Also in the event log were the following errors:

      Event ID 10016
      The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

      Add the WSS_WPG, WSS_ADMIN_WPG, Search & Admin accounts to the OSearch DCOM Servic

      Event ID 6141
      The site /ssp/admin could not be created. The following exception occured: This page has encountered a critical error. Contact your system administrator if this problem persists.

      Event ID 6610
      Safe mode did not start successfully. This page has encountered a critical error. Contact your system administrator if this problem persists.

      Event ID 5629
      Failed to load the SafeControl assembly paths for web.config. C:\Inetpub\wwwroot\wss\VirtualDirectories\ssp180

      Error importing WebPart. Assembly Microsoft.Office.Server.Search, Version=OAssemblyAssemblyVer, Culture=neutral, PublicKeyToken=OAssemblyPublicKey, TypeName. Microsoft.Office.Server.Search.WebControls.ActiveCrawls

    1. I deleted the SSP web apps again.
    2. Stop the search query & index services.
    3. Start the search query & index services.
    4. Restart IIS.
    5. Recreate the SSP web app.
    6. Recreate the SSP & set back to default with any associations required.

      Success - the SSP provisioned correctly.

    1. Restore the DB from by opening the Content Database page in Central Administration. Delete the Temp DB then in STSADM associate the original DB:

      cd C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN

      stsadm.exe -o addcontentdb -url http://portal -databasename MOSS_MyDB_WSS_Content -databaseserver MyServer

  3. If you receive the error 'An unexpected error has occured' open the web.config and update as follows:
    1. Change <SafeMode MaxControls=“200“ CallStack=“false“ to <SafeMode MaxControls=“200“ CallStack=“true“…>
    2. Set custom errors to 'Off' <customErrors mode=“Off“/>

Friday, January 09, 2009

Adding New SSP Administrators

When you add a new user account to the SSP site, even if you grant them Full Control permissions or add them as a Site Collection Administrator, initially they will experience access denied error messages when they click on any of the following links on the SSP Admin page:

* User profiles and properties
* Profile services policies
* My Site settings
* Personalization services permissions
* Audiences
* Import application definition
* Business Data Catalog permissions

These sections need to have permissions explicitly set. Initially, the setup account will have full access to the SSP, so use that account to grant rights to new SSP administrators you wish to delegate SSP administrative duties to.

Notice the items highlighted in bold in the list above. These are where you assign the remaining SSP permissions. Adding new SSP administrators to the "Personalization services permissions" section and granting appropriate rights will grant rights related to the first five links in the list above. Repeating the process in the "Business Data Catalog permissions" section will grant rights related to the last two links.

At this point, the new SSP administrator has all the appropriate access permissions they need to administrate the SSP.