This article describes the Infrastructure Update for Windows SharePoint Services 3.0 that is dated July 15, 2008. This article contains information about how to obtain the update and about issues that the update fixes. Additionally, this article contains information about issues that you may experience when you install the update and about how to determine whether the update is installed.
Issues that are fixed in Windows SharePoint Services 3.0 by the Windows SharePoint Services 3.0 Infrastructure Update
Known issues while/after you install the update
The Microsoft GroupBoard Workspace 2007 add-in template for Windows SharePoint Services 3.0 may cause the SharePoint Products and Technologies Configuration Wizard to fail during a build-to-build upgrade.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
The SharePoint Products and Technologies Configuration Wizard does not finish successfully on a computer that also has GroupBoard Workspace 2007 installed
After attaching a Content Database to a farm where the WSS and MOSS updates have been installed, you may receive the following error message
Could not find stored procedure 'dbo.proc_GetDatabaseInformation'
You can safely ignore this error message.
After patching, if you visit the Content Deployment Paths and Jobs page in Central Admin, you may not see any paths or jobs listed. It will seem as if they have been deleted. However, they have not. To work around this problem, click one of the column headers to sort the items. Then, they will all appear again.
After you install this update, the “Email a Post” link for a blog site does not open an e-mail message as expected. To resolve this issue, install the hotfix package that is described in Microsoft Knowledge Base article 953484.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the Windows SharePoint Services 3.0 hotfix package: May 5, 2008
If you install SharePoint Server 2007 Infrastructure Update Release, custom solutions may fail if they call the SharePoint object model while impersonation is suspended.
If you use Windows authentication, and your code calls the SharePoint object model from an IIS worker process, the request must impersonate the calling user’s identity. Windows SharePoint Services configures ASP.NET to impersonate the calling user automatically. However, your code may work unexpectedly or fail if you suspend impersonation. For example, your code may work unexpectedly or fail if you call the RevertToSelf function of the Windows API or if you call the System.Security.Principal.WindowsIdentity. Impersonate method and pass IntPtr.Zero as the value of the user token parameter. Even if your code does not explicitly revert to self, it might be called by ASP.NET after it reverts to self. This happens when you implement a virtual path provider or IHttpHandlerFactory.GetHandler. If your code does not impersonate the calling user, it might not function correctly.
Known issues discovered after release of this update
Installing the Infrastructure Update in a SharePoint farm that uses Alternate Access Mapping with a reverse proxy or a network load balancer, such as in an extranet deployment, may cause some public URLs to become unresponsive.
Microsoft is aware of this issue and is developing a solution. Before installing the Infrastructure Update, customers who use this configuration should use a test environment to verify that public URLs remain accessible after the update is installed.
Installing the Windows SharePoint Services Infrastructure Update that contains the fix for e-mail-triggered workflows was determined not to resolve this problem for document libraries. The fix does correct the e-mail-triggered workflows behavior in generic lists.
Microsoft is aware of this issue and is developing a solution.
To obtain the 32-bit version of the Windows SharePoint Services infrastructure update together with installation instructions and deployment strategies, visit the following Microsoft Web site:
To obtain the 64-bit version of the Windows SharePoint Services infrastructure update together with installation instructions and deployment strategies, visit the following Microsoft Web site:
We strongly recommend that you install Microsoft Windows SharePoint Services 3.0 Service Pack 1 (SP1) before you install this update.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest service pack for Windows SharePoint Services 3.0
Restart information
You do not have to restart the computer after you apply this update.
Update replacement information
This update does not replace any previously released updates.
Registry information
You
do not have to make any changes to the registry
to apply this update.
How to determine whether this update is installed
The global version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
This update consists of a full-file Microsoft Windows Installer (.msp) file. The .msp files are packaged in the self-extracting executable files. The following .msp files are distributed in this update.
Back to the top
