This article describes the Microsoft Office SharePoint Server 2007 issues that are fixed in the SharePoint Server 2007 post-2007 Microsoft Office servers Service Pack 1 hotfix package that is dated May 29, 2008.
This article describes the following items about the hotfix package:
The issues that the hotfix package fixes.
The prerequisites for installing the hotfix package.
Whether you must restart the computer after you install the hotfix package.
Whether the hotfix package is replaced by any other hotfix package.
This hotfix package
fixes the following issues that are not previously documented in a Microsoft
Knowledge Base article:
You enable BlobCache in the Web.config file for a
SharePoint Server 2007 Web site. The configuration in the Web.config file
resembles the following configuration:
When you try to view a .jpg image or a .gif image on the SharePoint
Server 2007 Web site, you may receive an error message resembles the following:
Updates are currently disallowed on GET requests. To
allow updates on a GET, set the 'AllowUnsafeUpdates' property on
spweb.
You create a Custom Dictionary in SharePoint Server 2007.
You add some characters to the Custom Dictionary. Then, you spelling
check
an article. However, words that were added in the
Custom Dictionary are detected as misspelled words if the words contain any
extended
characters.
You publish a SharePoint Server 2007 Web
site that is installed through Internet Security and
Acceleration (ISA) Server 2006. However, you find that the thumbnails in the
picture libraries of the SharePoint
Web
site are not visible.
In the Shared Services Administration page
of your shared services, you click User Profiles and
Properties to import user profiles. You set the Data source
field to map option for one of your user profile properties to
Not mapped. For example, you set the Name property. Then, you import the user profiles. However, the Name property is still updated even though the Data source
field to map option is set
to Not mapped.
When you create a SharePoint Server 2007 subsite, you set
the Use the top link bar from the parent site? option to
No. In this subsite, you can add links and delete links under
Global Navigation. However, you cannot delete the last
remaining link.
After you perform a crawl on a computer that is running
SharePoint Server 2007, you may receive an error message in the crawl log that
resembles the following error message:
Filtering of this
file ended because the file reached the maximum filter output limit. Check that
the filter does not generate a large amount of data relative to the size of the
document.
Important This section, method, or task contains steps that tell you how to
modify the registry. However, serious problems might occur if you modify the
registry incorrectly. Therefore, make sure that you follow these steps
carefully. For added protection, back up the registry before you modify it.
Then, you can restore the registry if a problem occurs. For more information
about how to back up and restore the registry, click the following article
number to view the article in the Microsoft Knowledge Base:
Double-click MaxGrowFactor, type
4096, click to select Decimal, and then
click OK.
Exit Registry Editor.
You install the 2007 Microsoft Office servers Service Pack
1 (SP1) on a computer that is running the release version of SharePoint Server
2007. However, the DCOM permissions for the WSS_ADMIN_WPG security group and
for the WSS_WPG security group are removed from the OSearch DCOM application.
Additionally, if the SharePoint Server service is running under an account that
is not in the Administrators group, the search function will not
work.
Note To work around this issue, you can manually add DCOM permissions
for the WSS_ADMIN_WPG security group and for the WSS_WPG security group. To do
this, follow these steps:
Click Start, click
Run, type dcomcnfg, and then press
ENTER.
Expand Component Services, expand
Computers, expand My Computer, and then click
DCOM Config.
In the details pane, right-click
OSearch, and then click Properties.
Click the Security tab.
Under Launch and Activation
Permissions, click Customize, and then click
Edit.
Click Add to add the local
WSS_ADMIN_WPG security group and the local WSS_WPG security group, grant them
Local Launch and Local Activation
permissions, and then click OK.
Under Access Permissions, click
Customize, and then click Edit.
Click Add to add the local
WSS_ADMIN_WPG security group and the local WSS_WPG security group, grant them
Local Access Activation permission, and then click
OK two times.
Restart the computer.
Consider the following scenario. You try to publish a page
in a SharePoint list. Before you publish the page, you click the
Close button on the upper-right corner while you are editing
the page. A pop-up dialog box appears. Then, you return to the page that you are editing by clicking Cancel in the pop-up dialog box. The pop-up dialog
box shows the following message:
Are you sure you want
to navigate away from this page?
Then, you again click the
Close button on the upper-right corner. However, you do not
see the pop-up dialog box. In this scenario, if you browse directly to the page
that you just created, and then you click Publish, you can
publish the page without any required fields.
Consider the following scenario. You
try to publish a page in a SharePoint list. Before you publish the page, you
click the Close button on the upper-right corner while you are
editing the page. A pop-up dialog box appears. Then, you return to the page that you are editing by clicking Cancel in the pop-up dialog box. The pop-up dialog box will show the
following message:
Are you sure you want to navigate
away from this page?
Then, you again click the Close
button on the upper-right corner. However, in this scenario, you do not see the pop-up dialog
box, and you are redirected to the home page.
A
supported hotfix is available from Microsoft. However, this hotfix is intended
to correct only the problem that is described in this article. Apply this
hotfix only to systems that are experiencing this specific problem. 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.
Prerequisites
There are no
prerequisites for installing this hotfix package.
Restart information
You do not have to restart the computer after you apply this
hotfix package.
Hotfix replacement information
This hotfix package is not replaced by any
later hotfix package.
Registry information
To use the hotfixes in this package, you do not have to make any
changes to the registry.
File information
This hotfix package
may not contain all the files that you must have to fully update a product to
the latest build. This hotfix package contains only the files that you must
have to correct the issues that are listed in this article.
32-bit hotfix package
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.
Download information
Collapse this tableExpand this table
File name
File version
File
size
Date
Time
Platform
Office-kb953138-fullfile-x86-glb.exe
12.0.6300.5000
73,212,936
10-Jul-2008
11:02
x86
Microsoft Windows Installer .msp file information
Collapse this tableExpand this table
File name
File version
File
size
Date
Time
Platform
Coreserver.msp
Not
Applicable
78,023,680
21-May-2008
22:19
Not
Applicable
After the hotfix package is installed, the global
version of this hotfix package has the file attributes, or a later version of
the file attributes, that are listed in the following table:
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.
Download information
Collapse this tableExpand this table
File name
File version
File
size
Date
Time
Platform
Office-kb953138-fullfile-x64-glb.exe
12.0.6300.5000
79,807,168
10-Jul-2008
11:01
x86
Microsoft Windows Installer .msp file information
Collapse this tableExpand this table
File name
File version
File
size
Date
Time
Platform
Coreserver.msp
Not
Applicable
85,931,520
21-May-2008
22:19
Not
Applicable
After the hotfix package is installed, the global
version of this hotfix package has the file attributes, or a later version of
the file attributes, that are listed in the following table: