You can access the Office SharePoint Central Admin page and its sub sites. When you try to access the main production home page, you have to wait a long time for the home page to load. Additionally, you receive the following error message:
An unexpected error has occurred
This issue occurs when the Office SharePoint server tries to fetch a cached Web page and another Web page has the same ID in the cache.
After you change the navigation heading in Office SharePoint Server 2007, you try to rename one page. However, the navigation is no longer usable. This issue occurs after you apply the hotfix that is described in Microsoft Knowledge Base (kb) article 974988.
You break the permission inheritance for a sub site.Then, you grant a member of the Members site group theFull Control permission on the sub site. The member can delete the sub site. However, the corresponding Relationship List entry that should be deleted is not deleted.
Search based alerts do not work if you configure the alerts on a sub site collection in Office SharePoint Server 2007. However, the search based alerts work if you configure the alerts on the root site collection.
You map the SPS-SipAddress profile property to a custom field in the Lightweight Directory Access Protocol (LDAP) directory. After you import user profiles and properties in Office SharePoint Server 2007, the first four characters of the SIP address attribute are truncated.
When you try to add a new property to user profiles in the Add profile property page in Office SharePoint Server, there is no property mapping field in the Property Import Mapping section. This issue may occur when you define multiple profile import connections.
When the regional settings time zone for the MySite site collection differs from time zone of the server, the current availability status that is displayed on a person's profile page is incorrect.
The custom dictionary in Office SharePoint Server 2007 does not work for Japanese katakana entries.
A user accesses the root of MySite host in Office SharePoint Server 2007.If the user’s logon name contains a space, an HTTP 400 or an HTTP 404 error occurs and the user’s MySite is not opened in the browser. This issue occurs because of invalid encoding of the space in the user’s name.
If there is a badly formed URL in the header of an http request, usage import logging fails with an error in the Unified Logging Service (ULS) log. For example, you receive the following message:
Portal Analytics import job failed: Invalid URI: The host name could not be parsed
Later usage reports do not contain data for requests that occur from that point forward.
You run the command stsadm -o sync -ignoreisactive 1to let the inactive users of Office SharePoint sites to have their user information synchronized. You grant an Active Directory group permission to access an Office SharePoint site. In this case,the synchronization does not work for users in the group who log on to the site for the first time after the first sync of the site is completed.
You enable the binary large object (BLOB) Cache on an Office SharePoint Web application. Then, you use the Explorer View to manage files in an Office SharePoint site. In this scenario, you receive an error message when you try to delete files.
You have an Office SharePoint page that receives a high volume of requests.On this page, the variation label control intermittently does not display. This issue is caused by removing the variation group ID from the PublishingVariationGroupID field.
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.
There are no prerequisites for installing this hotfix.You must have 2007 Microsoft Office suite Service Pack 1 or 2007 Microsoft Office suite Service Pack 2 installed to apply this hotfix package.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
To use one of the hotfixes in this package, you do not have to make any changes to the registry.
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.
The 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. x86 Download information