You send a message to a document library. If the message has a long subject and its attachment has a long file name, the attachment is dropped. Then, you cannot find the attachment in the document library.
Some application pages do not follow restrictions applied by the Enterprise Content Management Lockdown feature. For example, if you create a site collection by using the Publishing Portal template, anonymous users can access the /_layouts/webpartgallerypickerpage.aspx page. By default, the Publishing Portal template enables the Enterprise Content Management lockdown feature.
You move a sub-site to another location, and then delete its previous parent site. After that, if you run an incremental deployment job, the incremental deployment job fails.
You have limited access permission on a library level for a document library. Some Excel workbooks have their own item level permissions and you have edit permissions on those Excel workbooks. When you try to open one of those Excel workbooks, you receive the following error message:
• Excel Web Access
• An error has occurred.
• Please contact your system administrator if this problem persists.
If you use the SPFolder.MoveTo method or the SPFolder.CopyTo method to move items and folders between document libraries, an incremental crawl does not obtain the moved or copied items.
If you move a folder to its own subfolder, the folder is unaccessible.
A user is a member of more than 200 site groups. If you log on as that user, and then call the SPWeb.AllRolesForCurrentUser API method for obtaining the SPRoleDefinition class, you receive an "HRESULT 0x80040E14" error.
If a content deployment job is running on Microsoft Office SharePoint Server 2007 sites when you are updating content, the deployment job fails randomly. Additionally, you receive the following error message:
System.IO.FileNotFoundException: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
You import a team site that had custom site content types that were created in a parent and child relationship. Then, you cannot create a new child content type based on the imported parent content type.
When you try to view a page that contains a calculated column, you receive a "The SQL server might not be started" error message.
If you rename a folder name and then open a document in the folder, the approval comments for the document are removed unexpectedly.
If you delete a document from an Office SharePoint Server 2007 site when a content deployment job is running on the site, you receive an error message that resembles the following:
System.IndexOutOfRangeException - There is no row at position 0.
You have some custom fields that have the PropertySchema field type. After you upgrade to Office SharePoint Server 2007 Service Pack 2, you cannot create a column by using those custom fields at the site column level.
You have a Web application that has more than five incoming URLs. You cannot change Alternate Access Mappings (AAM) settings after you install the 2007 Microsoft Office system cumulative update that was released in April 2008.
You visit user-created pages in a pages library. In this situation, the currently highlighted site in a SharePoint navigation bar is no longer highlighted.
When anonymous users try to view the properties of a file or the properties of a page that is checked-out, they receive an "An unexpected error has occurred" error message.
When you run a full crawl, certain .xml files that have no spaces between tags are not indexed properly.
You create lookup columns that enable multiple values in lists with items that do not inherit permissions from the list. When you try to visit a view of the list, you receive a "RENDER FAILED" error message. When you try to view the properties of an item in the list, you receive a "Must declare the table variable @_scopeTbl" error message.
You have some documents in external binary large object (BLOB) storage. You notice an inconsistency between the metadata property values that are stored at the item level and the metadata property values that are stored in the external BLOB storage.
You build a custom Web part to collect all the checked-out files that are present on a site collection. When you try to use the custom Web part, you find the following error message in the Application event log.
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Database
Event ID: 5586
Unknown SQL Exception 4104 occurred. Additional error information from SQL Server is included below.
The multi-part identifier "ListOrds.JoinKeyId1" could not be bound.
When you try to add a new user to a SharePoint group, you open the People Picker dialog box. Then, the "Title" column is mistranslated in the Hungarian version of Office SharePoint Server 2007. The People Picker dialog box uses "Megszólítás" instead of "Beosztás" in Hungarian as the name of "Title" column.
You install Office SharePoint Server 2007 Service Pack 2 and the cumulative update that was released in April 2009. You create some sites in the Server_Name\sites format. However, you do not create a root site collection (\). When you run a full crawl, you receive the following error message in the Application event log:
You use document libraries with versioning enabled. You use site collection auditing to audit all view events. When any action occurs, an audit event log is created. However, the auditing only works for the current versions of documents. It does not work in earlier versions of documents.
After you install Office SharePoint Server 2007 Service Pack 2, you receive the following error message when you try to visit the SiteSubs.aspx page:
If you have enabled the stack trace in the Web.config file for the Web application you recieve the following error:
Object reference not set to an instance of an object. at Microsoft.SharePoint.ApplicationPages.SiteSubsPage.OnLoad(EventArgs e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
A supported hotfix is available from Microsoft. However, this hotfix is
intended to correct only the problems that are described in this article. Apply
this hotfix only to systems that are experiencing the problems described in
this article. This hotfix might receive additional testing. Therefore, if you
are not severely affected by this problem, we recommend that you wait for the
next software update that contains this hotfix.
If the hotfix is
available for download, there is a "Hotfix download available" section at the
top of this Knowledge Base article. If this section does not appear, contact
Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required,
you might have to create a separate service request. The usual support costs
will apply to additional support questions and issues that do not qualify for
this specific hotfix. For a complete list of Microsoft Customer Service and
Support telephone numbers or to create a separate service request, visit the
following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for
which the hotfix is available. If you do not see your language, it is because a
hotfix is not available for that language.
To install this hotfix, you must have Windows SharePoint Services
3.0 Service Pack 2 or Windows SharePoint Services
3.0 Service Pack 1 installed.
For more information,
click the following article number to view the article in the Microsoft
How to obtain the latest service
pack for Windows SharePoint Services 3.0
not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released
To use one of the hotfixes in
this package, you do not have to make any changes to the
This hotfix may not
contain all the files that you must have to fully update a product to the
latest build. This hotfix contains only the files that you must have to correct
the issues that are listed in this article.
global version of this hotfix package uses a Microsoft Windows Installer
package to install the hotfix package. The dates and the times for these files
are listed in Coordinated Universal Time (UTC) in the following table. When you
view the file information, the date 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.
Collapse this tableExpand this table
Microsoft Windows Installer .msp file information
Collapse this tableExpand this table
After the hotfix is installed, the global version of
this hotfix has the file attributes, or a later version of the file attributes,
that are listed in the following table: