[MOSS2007] Version 2.0 of my Installation Guide has just been released

I finally had the time to complete a new version of my MOSS2007 Installation Guide and have just uploaded it. This new version includes installing Service Pack 1 for the .NET 2.0 and 3.0 Frameworks and MOSS2007. I also added the SQL Server 2005 SP2 Cumulative Update Pack and an IIS fix, which solves an issue which caused the error message "Attempted to read or write protected memory" in the event log.

The new version can be downloaded here: HOWTO - Install MOSS2007 v2.0

And again: if you have any comments or additions, please let me know!

Have fun!

[MOSS2007] "Database Default Locations" ignored by SharePoint 2007

PROBLEM:
While installing a new environment today, I changed the "Database Default Locations" setting in SQL Server 2005 to make sure the database files and log files were created on a certain location. Testing by creating a database manually in the SQL Management Studio worked, but when I ran the SharePoint Configuration Wizard the databases were created in the old location.

CAUSE
After some troubleshooting I found out that SharePoint somehow retrieves the old setting until SQL Server 2005 has been restarted (reboot of the server or restart of the services). Why this is I have no clue.

RESOLUTION
Just restart SQL Server 2005 and try again. The new databases are now created in the correct place.

[MOSS] New version of the MOSS Installation Guide

I have just uploaded a new version of the MOSS Installation Guide. This time these things are added:

• Installation of Public Update of October 9th
• Default configuration steps of MOSS
• Some extra steps to correct issues with the Public Update

The new version can be downloaded here

Please let me know if you have any updates/questions about the guide by posting a comment!

Have fun installing!!

[MOSS/WSSv3] Bug in SharePoint Public Hotfix of October 9th

Recently I have installed the MOSS and WSS public hotfix of October 9th (WSS 3.0 - KB934525, MOSS 2007 KB937832) on several environments. After the installation I noticed that DCOM errors were added to the eventlogs. I troubleshooted the issues and it turns out that the WSS and MOSS patches are resetting the permissions on the OSearch and SPSearch DCOM objects.

Before installing the hotfixes the security settings on both objects were:

• Administrators
• <MOSS Configuration Database account>
• <MOSS Search account>
• SYSTEM
• WSS_ADMIN_WPG
• WSS_WPG

All account had "Local Activation" and "Local Launch" permissions.



After installing the WSS patch the security settings on the SPSearch DCOM object were reset to default settings.
After installing the MOSS patch the security settings on the SPSearch DCOM object were reset to default settings.

• Administrators
• LOCAL SERVICE
• SYSTEM

Fortunatelly this was solved easily by adding the WSS_ADMIN_WPG and WSS_WPG groups to the OSearch and SPSearch object and granting them "Local Activation" and "Local Launch" permissions.

How to determine the DCOM settings??

• Start > Run
• dcomcnfg
• Component Services > Computers > My Computer >DCOM Config
• Select object OSearch or SPSearch
• Right click > Properties
• Select tab Security
• Click Edit at "Launch and Activation Permissions"

MOSS2007 Installation guide

Over the past few weeks I have been working on an installation guide for MOSS2007. I have updated a document I created earlier with new insights and am glad to announce that it is available for download!!

Available here:Microsoft Office SharePoint Server 2007 Installation Guide

[UPDATE: A new version has been released. More info, see this post]

[MOSS2007] Issue with starting the Central Admin component on another server

On an environment I have just installed I ran into an issue when I tried to start the Central Admin component on a second server. The environment consisted of two load balanced web servers and an application server. The application server had been installed first, so was running the Central Admin component. IIS had been installed on the D drive on this server.

When I tried to start the Central Admin component on one of the web servers (which only had a C partition), the component refused to start. After looking through the logs the cause turned out to be that SharePoint tried to configure the Central Admin on the D partition, because the application server also had been installed on the D partition. The only way to get around this was to create a D-partition on the web servers.

So when you are installing a SharePoint 2007 environment, make sure all partitions on all servers are the same. Or at least the drive letters.