Bill Baer /bɛːr/

Problem: web.config is Read-only Isolation: Check upgrade.log at %commonprogramfiles%Microsoft SharedWeb Server Extensions12BINLOGS, looking for the following error: [IisWebSiteSequence] [ERROR] [10/17/2007 11:38:22 AM]: Access to the path ‘C:InetpubwwwrootwssVirtualDirectories5003web.config’ is denied. Cause: Insufficient user rights on the file (ACL); this can happen if the read-only flag is actively set the for the web.config and/or if using a source code management system to maintain web.config. Solution: Ensure that Everyone has write access to web.

Data protection and recovery is a strategic requirement for most organizations considering Microsoft Office SharePoint Server 2007; until recently most of the information available on item to farm level recovery, both for planning and implementation, were scattered across the Internet, available in pieces on a collection of blogs and sites. Today I’d like to announce the culmination of several weeks of work by many dedicated and bright individuals with the publication of a new whitepaper Data protection and recovery for Office SharePoint Server in small to medium deployments (http://technet2.

A solution is available to administrators of SharePoint Products and Technologies deployments experiencing the following application event after introducing WSS October public update KB934525. Event Type: Error Event Source: Windows SharePoint Services 3 Event Category: Topology Event ID: 6800 Date: 10/17/2007 Time: 8:09:40 PM User: NA Computer: HOME Description: The database WSS_Content on HOMEMicrosoft##SSEE is not accessible to missing Windows Internal Database signatures. 1. Run the following STSADM operations to stop and start the SPWebService:

I was recently asked by one of our Premier Field Engineers in Charlotte, NC about the versioning information displayed in SharePoint 3.0 Central Administration after installing recent Windows SharePoint Services 3.0 security updates and decided it would be beneficial to expand the audience for others seeking an answer to this question. Question: In relation to the October patches for MOSS/WSS – should the database version show up correctly in CA? or is it expected that it would should up like this:

I’ve spent the last couple of weeks using SharePoint Products and Technologies with Windows Server 2008 (WS08), specifically running Microsoft Office SharePoint Server 2007 (MOSS) on Windows Server 2008 IIS 7.0 and Microsoft Office SharePoint Server 2007 SP1 in addition to check-in scenarios such as provisioning WS08 with WSS 3.0, introducing MOSS 2007, and ultimately SP1…I anticipated an improvement in performance, but the new implementation of the TCP/IP protocol suite AKA Next Generation TCP/IP stack exceeded my expectations considering the Web front-ends I used were in our Singapore Data Center - a full 226ms of latency from Redmond.

I was reviewing the Microsoft Office SharePoint Server TechNet article Determine upgrade approach and realized an article I have been working internally over the past few weeks has been published and introduced to the three existing upgrade approaches of in-place, gradual, and database migration. The upgrade approach itself is described/labeled as a hybrid upgrade approach which combines both the gradual and database migration approaches permitting administrators to preview a subset of site collections prior to upgrading the remainder of the environment (for those who have attended my TechReady, etc.

I’ve come across a handful of posts regarding KB934525 for Windows SharePoint Services and failure to start the Windows SharePoint Services Administration service. I’ve attached some basic troubleshooting steps that may provide resolution to issues where psconfig fails with Cannot start service SPAdmin on computer ‘.’. For those who have installed the KB and have experienced issues where the service has failed to start, Option 4 is the recommended solution. UPDATE Oct.

I have had the opportunity over the past two weeks to speak with several customers in regards to SharePoint Products and Technologies as a platform, geographically disperse architectural considerations, but one question stood out that was shared by each of these customers - “How do you [Microsoft] manage customizations in your SharePoint deployments?". Before beginning to answer the question, I immediately realized how both widespread and common customization on this iteration of SharePoint is when compared to its predecessors.

I received word over the weekend Solution Accelerators have updated the SharePoint Manageability Toolkit. See below for a complete list of updates: Linked Reports are added specific to the MOSS and WSS Management Pack. They consists of performance reports, alerts reports, event analysis reports, Most common alerts and Most common Events reports with respect to the target objects of our Mp such as MOSS computer Group, WSS Computer Group, MOSS computer role/ Moss Server and WSS computer Role/ WSS server.

As Daylight Savings Time (DST) approaches it is time again to plan and prepare for impacts on your existing SharePoint Products and Technologies deployments…I intend to keep this post dynamic and updated with the latest information surrounding DST impact and mitigation for Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007. Planning and Preparation A technical product review/ summary webcast is scheduled for 2:00PM Pacific on Monday, September 24th to help customers and partners prepare for change to Daylight Saving Time and various time zones.