Uncategorized

Service Pack 1 for SharePoint Products and Technologies

I’ve spent the past several days in Portland, Oregon speaking at a SharePoint Products and Technologies governance event and completely neglected to post any information on the now released Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007 Service Pack 1.  For more information visit:  http://blogs.msdn.com/sharepoint/archive/2007/12/11/announcing-the-release-of-wss-3-0-sp1-and-office-sharepoint-server-2007-sp1.aspx.

Standard
Uncategorized

Moving site collections between domains…

Moving site collections between domains is not a common operation, but occurs frequently enough to provide some prescriptive guidance. 


User Accounts


SharePoint maintains the security identifiers of user accounts as opposed to just usernames, as a result, when restoring a site collection to a farm in a domain other than that where the original source site collection was located, those usernames are no longer recognized regardless as to whether or not those usernames were recreated in the target domain.  STSADM provides an operation suited to address this potential issue in the migrateuser operation which will effectively resolve the security identifiers of the users.


Migrating User Accounts


STSADM -o migrateuser migrates a user account in Microsoft Windows SharePoint Services 3.0 to a new user name and binary identifier (security identifier).


Syntax


stsadm -o migrateuser


   -oldlogin <domainname>


   -newlogin <domainname>


   [-ignoresidhistory]


-oldlogin specifies the credentials of the source account (account to be migrated) and -newlogin the target account or destination credentials of the new account replacing the source account.  When specifying the -ignoresidhistory argument the security identifier history of the destination user is checked to determine and match the name of the old user or otherwise the meta data is ignored.

Standard
Uncategorized

Slipstream, not a phenomenon in Physics

Slipstream is a common term used at Microsoft to define the merging of patches or updates into the original installation sources of a program.

What are the benefits of slipstreaming….

Creating a slipstream image reduces the operational overhead required to introduce a specific build of software to include Windows SharePoint Services 3.0 and/or Microsoft Office SharePoint Server 2007 into an environment.  For example, if an organization has standardized on a specific set of updates and/or patches that will be applied in a given configuration, these updates and/or patches can be included in the original installation sources and subsequently installed with the source application.  Slipstreaming a Windows SharePoint Services 3.0 and/or Microsoft Office SharePoint Server 2007 is a simple process providing you have access to the original and update sources…

Example (Windows SharePoint Services 3.0 + KB941422):

To install a specific Windows SharePoint Services 3.0 build such as 12.0.6039 which is the build number associated with KB941422:

  1. Download Windows SharePoint Services 3.0 to C:TEMP on a Web front-end server
  2. Open a Command Prompt and navigate to C:TEMP
  3. Enter C:TEMPSharePoint.exe /extract:C:WSS and depress Enter

    image

  4. The contents of SharePoint.exe will be extracted to C:WSS

image

image

image

 

  1. Download Windows SharePoint Services 3.0 KB941422 to C:TEMP on a Web front-end server
  2. Open a Command Prompt and navigate to C:TEMP
  3. Enter C:TEMPwss-kb941422-fullfile-x64-glb.exe /extract:C:WSSUpdates and depress Enter

    image

  4. The contents of wss-kb941422-fullfile-x64-glb.exe will be extracted to C:WSSUpdates

image

image

image

When setup.exe is executed from C:WSS, Windows SharePoint Services 3.0 (RTM – build 12.0.4518) will be installed and KB941422 applied during the installation process.  The end result is an installation of Windows SharePoint Services 3.0 build 12.0.6039 without the requirement of installing KB941422 separately and the requirement of running the SharePoint Products and Technologies Configuration Wizard to upgrade binaries on each server machine in the server farm.

Standard
Uncategorized

Installing Windows SharePoint Services 3.0 on Windows Server 2008

On October 29, 2007 we announced that Windows SharePoint Services 3.0 bits will not be included on the Windows Server 2008 media; however, will remain available as a separate download, as a result changing the installation routine.  For those who used evaluation and release candidate builds of Windows Server 2008, Windows SharePoint Services 3.0 was included as a server role, adding the role subsequently configured supporting roles and role services – as a clean installation, this configuration must be performed by the server administrator and includes adding the Web Server (IIS)) role and role services.


Prerequisites for Windows SharePoint Services 3.0


Adding the Web Server (IIS)) Role using Server Manager


The Server Manager is designed to guide server administrators through the process of installing, configuring, and managing server roles and features that are part of Windows Server 2008, for more information on using the Server Manager visit http://technet2.microsoft.com/windowsserver2008/en/library/18dd1257-2cd1-48f0-91f1-3012cf0fcc831033.mspx?mfr=true.



  1. Open Server Manager
  2. Click Start, Administrative Tools, and then click Server Manager
  3. Select Add Roles under Roles Summary

    image


  4. Follow the onscreen prompts and select Web Server (IIS)) from the list of available roles

Adding Web Server (IIS)) Role Services


Role services provide the functionality aspects of a role, role services are typically configured when a role is added.  Use the list below to determine what Web Server (IIS)) role services are required by Windows SharePoint Services 3.0.


Web Server (IIS) Role and Role Services Required by SharePoint Products and Technologies


Web Server

  • Common HTTP Features

    • Static Content
    • Default Document
    • Directory Browsing
    • HTTP Errors
Application Development

  • ASP.NET
  • .NET Extensibility
  • ISAPI Extensions
  • ISAPI Filters
Health and Diagnostics

  • HTTP Logging
  • Logging Tools
  • Request Monitor
  • Tracing
Security

  • Basic Authentication
  • Windows Authentication
  • Digest Authentication
  • Request Filtering
Performance

  • Static Content Compression
  • Dynamic Content Compression
Management Tools

  • IIS Management Console
IIS 6 Management Compatibility

  • IIS 6 Metabase Compatibility

Features


Features describe an auxiliary or supporting function of a server and augment the functionality of an existing role.



  • .NET Framework 3.0 Features *Required

    • .NET Framework 3.0


  • Network Load Balancing *Optional


  • Remote Server Administration Tools *Optional

    • Remote Administration Tools

      • Web Server (IIS)) Tools


  1. Open Server Manager
  2. Select Add Features under Features Summary

    image


  3. Select .NET Framework 3.0 Features and click Next

    image


  4. Follow the onscreen prompts to complete the installation, you can return to the Server Manager at any time to add additional roles

Installing Windows SharePoint Services 3.0



  1. Download Windows SharePoint Services 3.0
  2. Run SharePoint.exe and follow the onscreen prompts to complete the installation

For more information on installing/deploying Windows SharePoint Services see the Windows SharePoint Services 3.0 Technical Library Deployment for Windows SharePoint Services 3.0 Technology content.


NOTE On current Windows Server 2008 builds use the /RMTLAUNCH parameter with setup.exe to install Windows SharePoint Services 3.0.

Standard
Uncategorized

More KB934525 Troubleshooting…

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.config when running the SharePoint Products and Technologies Configuration Wizard and in addition ensure that the read-only flag is not enabled on the file and that no other process lock this file, for example, a virus scanning application.

Problem:  ASP.NET not Correctly Registered in the IIS Metabase

Isolation: Check upgrade.log at %commonprogramfiles%Microsoft SharedWeb Server Extensions12BINLOGS, looking for the following error:

[SPIisWebSiteWssSequence] [ERROR] [10/10/2007 10:21:25 AM]: Action 3.0.3.0 of Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence failed.
[SPIisWebSiteWssSequence] [ERROR] [10/10/2007 10:21:25 AM]: InstallAspNet 566609673 failed.
[SPIisWebSiteWssSequence] [ERROR] [10/10/2007 10:21:25 AM]:    at Microsoft.SharePoint.Upgrade.EnsureAspNetScriptMapInstalled.Upgrade()
   at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()


Be aware that the number between InstallAspNet and failed will vary this is the ID of the affected IIS site.

Cause: The ASP.NET registration in the Metabase is not correct and requires remediation.

Solution:



  1. Open a Command Prompt and navigate to the following directory “%windir%microsoft.netframeworkv2.0.50727”
  2. Execute the following command: “aspnet_regiis.exe -i”

NOTE This will update all IIS Web sites/Virtual Servers to use .NET framework 2.0.  In the event that some IIS Web sites/Virtual Servers should use .NET Framework 1.1 or 1.0 they will need to be adjusted after executing aspnet_regiis.exe -i successfully as an alternative you can try to run “aspnet_regiis.exe –s W3SVC/number/ROOT” where number is the number between InstallAspNet and failed in the upgrade log.


Problem:  web.config is Missing


Isolation: Check upgrade.log at %commonprogramfiles%Microsoft SharedWeb Server Extensions12BINLOGS, looking for the following error:

[AssemblyReferenceFixUp] [3.0.4.0] [ERROR] [10/18/2007 11:47:40 AM]: Application Web Config for this IIS site (944564711) could not be found at D:wwwrootwssVirtualDirectories5003web.config.


Cause: web.config has been deleted by an administrator.

Resolution: Ensure that all web.config files for all configured SharePoint web applications exists before running the SharePoint Products and Technologies Configuration Wizard.

For all other issues, consider the following steps:

Clear Cache



  1. Navigate to C:Documents and SettingsAll UsersApplication DataMicrosoftSharePointConfig<GUID> in Windows Explorer
  2. Backup and delete the XML files in the <GUID> directory
  3. Change the content of the cache.ini to „1”
  4. Restart the Windows SharePoint Services Timer Service
  5. Restart the Windows SharePoint Services Administration Service
  6. Open a Command Prompt and navigate to the following directory %commonprogramfiles%Microsoft SharedWeb Server Extensions12BIN
  7. Execute the following command “psconfig -cmd upgrade -inplace b2b –force”

NOTE Do not use the SharePoint Products and Technologies user interface.

Standard
Uncategorized

The database on serverMicrosoft##SSEE is not accessible to missing Windows Internal Database signatures.

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:


stsadm -o provisionservice -action stop -servicetype spwebservice -servicename “”

stsadm -o provisionservice -action start -servicetype spwebservice -servicename “”

2.  Instantiate the upgrade by executing psconfig.exe or psconfigui.exe.


The cause of this issue is the SPWebService instance failed to finish provisioning. The status of that service is marked as provisioning. However, it has done enough provisioning work so that the user sites are working and/or during upgrade, the upgrade code skipped any web service instances that are not online, upgrading the administration sites; however, skipping the user sites.

Standard