Description of the SharePoint Portal Server 2003 post-Service Pack 2 hotfix package: June 16, 2006

Article translations Article translations
Article ID: 919175 - View products that this article applies to.
Expand all | Collapse all

On This Page

SUMMARY

This article describes the Microsoft Office SharePoint Portal Server 2003 issue that is fixed in the SharePoint Portal Server 2003 post-Service Pack 2 hotfix package that is dated June 16, 2006.
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.
  • Whether you must make any registry changes.
  • The files that the hotfix package contains.

INTRODUCTION

Issues that the hotfix package fixes

This hotfix package fixes the following issues:
  • 898546 When you filter an Index search by a view in a Lotus Notes content source on a server that is running SharePoint Portal Server 2003, all the items in the content source are indexed
  • 905216 You cannot query a specific search server in a server farm deployment of SharePoint Portal Server 2003
  • 910293 A content source crawl takes longer than expected in SharePoint Portal Server 2003
  • 914386 No option is available to configure SharePoint Portal Server 2003 to crawl files that do not have a file name extension as HTML files
  • 915427 Double-byte character set (DBCS) characters are corrupted when you use the Research pane to search for documents on a SharePoint Portal Server 2003 portal site
  • 899449 An event ID 110 warning message or an event ID 109 error message may be logged in the Application log on a computer that is running Microsoft Office SharePoint Portal Server 2003
  • 918742 Description of a new command-line operation that is available for the Spsadm.exe command line tool that you can use to clean up orphaned items in the configuration database in SharePoint Portal Server 2003
This hotfix package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:
  • Event ID 1053 and 7051 messages are logged in the Application log after you apply a SharePoint Portal Server 2003 post-Service Pack 2 hotfix package

    You apply a SharePoint Portal Server 2003 post-Service Pack 2 hotfix package on a computer that is running SharePoint Portal Server 2003 Service Pack 2 (SP2). When you view the Application log after the SharePoint Portal Server 2003 post-Service Pack 2 hotfix package is applied, the following event ID 1053 and event ID 7051 messages are logged in the Application log. This problem occurs every time that you stop and then restart the Microsoft SharePointPS Search Service.

    Type: Warning
    Source: Microsoft SharePointPS Search Service
    Category: Gatherer
    Event ID: 1053
    Description:
    The system exception c0000005 occurred, and will be handled. If this causes problems, contact Microsoft Product Support Services and include the stack trace in the event. DllUnregisterServer+0x00017068 (0x00FC4A83) _CxxLongjmpUnwind+0x000000FE (0x77BB3461) _CxxExceptionFilter+0x000001D1 (0x77BB2BD4) _CxxExceptionFilter+0x0000058F (0x77BB2F92) _CxxExceptionFilter+0x00000661 (0x77BB3064) _CxxFrameHandler2+0x00000028 (0x77BB334E) RtlRaiseStatus+0x000000DA (0x7C82EEB2) RtlRaiseStatus+0x000000AC (0x7C82EE84) KiUserExceptionDispatcher+0x0000000E (0x7C82ECC6) DllUnregisterServer+0x000A3ACA (0x010514E5) DllUnregisterServer+0x0003CD3B (0x00FEA756) DllUnregisterServer+0x0003CFEC (0x00FEAA07) DllUnregisterServer+0x0003A166 (0x00FE7B81) DllUnregisterServer+0x0003A9CA (0x00FE83E5) DllUnregisterServer+0x0003ABFE (0x00FE8619) GetModuleFileNameA+0x000000EB (0x77E66063)

    Type: Error
    Source: Microsoft SharePointPS Search Service
    Category: Search service
    Event ID: 7051
    Description:
    Index propagation to search server <%2> was not accepted.

    Context: Application, 5c5bd0c7-03d3-42f7-9760-d78fff2c1835 Portal_Content Catalog

    Details: (0xc0000005 - )

    For more information visit http://www.microsoft.com/servers/redirect/contentredirect2.asp

  • Office documents that are protected with a password are not included in the content index, and a "A document IFilter cannot be initialized' error message is logged in the gatherer log

    After you install SharePoint Portal Server 2003 SP2, the properties of Microsoft Office documents that are protected with a password are not included in the content index. When you perform an update of the content index, the following error message is logged in the gatherer log:
    The address could not be found, (0x80042404 - A document IFilter cannot be initialized. The document or IFilter may contain errors.
    Therefore, when users search the portal site for Office documents, Office documents that are protected with a password are not returned in the search results.

  • You cannot access the Configure Server Farm Account Settings page after you apply the SharePoint Portal Server 2003 post-Service Pack 2 hotfix package that is documented in article 897722 in the Microsoft Knowledge Base

    You apply the SharePoint Portal Server 2003 post-Service Pack 2 hotfix package that is documented in article 897722 in the Microsoft Knowledge Base. You start SharePoint Central Administration. However, the Configure Server Farm Account Settings page is not displayed. Instead, the Web browser repeatedly displays the Access Denied Web page and the Configure Server Farm Account Settings Web page. Then, the Web browser displays an error message that states that the server is not found.

    This problem occurs in scenarios in which SharePoint Portal Server 2003 settings are not configured on the server. For example, this problem occurs if the following conditions are true:
    • You install the original release version of SharePoint Portal Server 2003. However, you do not configure SharePoint Portal Server 2003 settings.
    • You install SharePoint Portal Server 2003 SP2.
    • You apply the SharePoint Portal Server 2003 post-Service Pack 2 hotfix package that is documented in article 897722 in the Microsoft Knowledge Base.
  • The Preferred Name property values in search results are replaced with the Public.aspx value

    If the Include this property check box is not selected when you perform an advanced search, the PreferredName property values in the search results are replaced with the Public.aspx value. Additionally, the Mapping to this property option between the PreferredName property and the displaytitle property (urn:schemas.microsoft.com:fulltextqueryinfo:displaytitle) is removed.
  • You receive an "An error occurred while attempting to update audience membership" error message when you try to run the Audience Compilation feature

    When you try to run the Audience Compilation feature on a portal site on a server that is running SharePoint Portal Server 2003, the audience may not be compiled. Additionally, you receive the following error message:
    Audience# : An error occurred while attempting to update audience membership. Unable to retrieve group membership from Active Directory directory service for this group:

    DL Member of root\Group#
    This issue may occur if groups in Active Directory list each other as a member.
  • You receive a "Type a valid e-mail address" error message when you try to create an alert in a document library

    When you try to create an alert in a SharePoint Portal Server 2003 document library, you receive the following error message:
    Type a valid e-mail address.
    Note This issue may occur if the e-mail address contains a dollar sign ($).

  • The index is not completed successfully, and error 7034 is logged in the System log

    When you run a full update on a SharePoint Portal Server 2003 site that contains much German language content, the index is not completed successfully. Additionally, error 7034 is logged in the System log of the Service Control Manager. This error states that "the Microsoft SharePointPS Search terminated unexpectedly."

  • Alerts and alert results are not deleted, and you receive a "Transaction count after EXECUTE" error message

    You update a computer that is running SharePoint Portal Server 2003 to SharePoint Portal Server 2003 SP2. When you try to delete all alerts and alert results for a site, the alerts and alert results are not deleted. Additionally, you receive the following error message:
    Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = 0, current count = 1.
  • The icon for an uploaded document in a document library uses the default icon instead of the program icon

    Consider the following scenario. You open a Web page that uses the "Your recent documents" Web Part. On the "Your recent documents" Web Part, there is a document that has been uploaded to a document library on a SharePoint Portal Server 2003 site. In this scenario, the icon for the uploaded document may appear with the default icon instead of with the program icon for the document.
  • You receive a generic "Internal server error" error message when you run a query that contains only noise words after you install SharePoint Portal Server 2003 SP2 on the computer

    Consider the following scenario. A computer is running either the original release version of SharePoint Portal Server 2003 or Microsoft Office SharePoint Portal Server 2003 Service Pack 1 (SP1). You use the Search Web service to run a query that contains only noise words. You receive an error message that contains information that helps you identify the cause of the error. For example, you receive an error message that resembles the following:
    A clause of the query contained only ignored words
    However, this behavior changes after you install SharePoint Portal Server 2003 SP2 on the computer. When you use the Search Web service to run a query that contains only noise words on a computer that is running SharePoint Portal Server 2003 SP2, you receive the following error message:
    Internal server error
    The error message is generic and does not contain any information that helps you identity the cause of the error.

  • A restore operation is not completed successfully when you use the SharePoint Portal Server Backup and Restore tool (Spsbackup.exe) to restore a portal site from backup

    You use the SharePoint Portal Server Backup and Restore tool to back up the portal site. However, when you try to restore the portal site from backup, the operation is not completed successfully. This problem occurs if the following conditions are true:
    • You use Microsoft SQL Server 2005 as the database back end for SharePoint Portal Server 2003.
    • You configure the Enable full-text search and index component option for content that is hosted on the portal site.
    In this situation, the restore operation is not completed successfully because of a file naming conflict that occurs in SharePoint Portal Server 2003.

  • The Mssdmn.exe process crashes intermittently when SharePoint Portal Server 2003 crawls an Exchange Server public folder

    When SharePoint Portal Server 2003 crawls a Microsoft Exchange Server public folder that you added as a content source in SharePoint Portal Server 2003, the Mssdmn.exe process crashes intermittently. The following text is an example of the call stack that is generated when this problem occurs:
    0:032> r
    eax=00000000 ebx=031be140 ecx=0000005f edx=017e8f02 esi=031be298 edi=031be2a0
    eip=0293448b esp=017e9110 ebp=017e919c iopl=0         nv up ei pl zr na po nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010246
    mimefilt!CMimeFilter::BindEmbeddedObjectToIFilter+36a:
    0293448b 8b10             mov     edx,[eax]         ds:0023:00000000=????????
    0:032> kb 99
    ChildEBP RetAddr  Args to Child              
    017e938c 02934652 00000000 0000c42c 017fff70 mimefilt!CMimeFilter::BindEmbeddedObjectToIFilter+0x36a 
    017e93ac 0293493f 031be140 031be140 00000000 mimefilt!CMimeFilter::GetNextBodyPart+0x14d 
    017e93f0 3000fa96 031be140 017fff70 00000000 mimefilt!CMimeFilter::GetChunk+0x2cf 
    017fffb8 7c826063 300304e8 00000000 00000000 mssdmn!CFilterThread::Thread+0x1bf5 
    017fffec 00000000 3000dea1 300304e8 00000000 kernel32!BaseThreadStart+0x34 
    
  • You unexpectedly receive an e-mail message when you link a document to a keyword Best Bet

    Consider the following scenario. You enable versioning on a document library that is located in an area on the portal site. You configure the Alerts feature to send e-mail messages to notify users when content in the document library changes. You add keyword Best Bets to a keyword. Then, you link a document in the document library to a keyword Best Bet. In this scenario, SharePoint Portal Server 2003 unexpectedly generates an e-mail message.

  • An "The address could not be found, 0x80040D7B - Document filtering cannot be completed because the document server did not respond within the specified timeout" error message is logged in the gatherer log

    Consider the following scenario. A user uploads a document to a document library in a Microsoft Windows SharePoint Services Web site. The document exceeds the maximum download size that you specified for the SharePoint Portal Server 2003 index management server. When you perform an update of the content index in SharePoint Portal Server 2003, the following error message is logged in the gatherer log:
    The address could not be found, (0x80040D7B - Document filtering cannot be completed because the document server did not respond within the specified timeout. Try crawling the server later, or increase the timeout values.)
    The error message indicates that the SharePoint Portal Server 2003 index management server downloaded the document to the temporary folder, and then tried to index the document. You expect documents that exceed the maximum download size not to be downloaded to the temporary folder or indexed by SharePoint Portal Server 2003.

  • You may experience a decrease in crawl performance after you install SharePoint Portal Server 2003 SP2

    You may experience a decrease in crawl performance after you install SharePoint Portal Server 2003 SP2. This issue may occur when SharePoint Portal Server 2003 with SP2 installed incorrectly processes certain data mappings.

    For example, this issue may occur if the content contains data that maps a String property to a Date property. This situation causes the Srch_sessionstringprops_Number tables and the Srch_sessionstringpropsalt_Number tables to be incorrectly loaded and incorrectly cleared.
  • The value of the DAV:getcontenttype property is missing in documents that are located in a SharePoint Portal Server 2001 content source

    You configure a Microsoft SharePoint Portal Server 2001 workspace as a content source in SharePoint Portal Server 2003. If you run a query that returns the properties of the documents in the SharePoint Portal Server 2001 content source, the value of the DAV:getcontenttype property is missing for those documents. Additionally, you can customize SharePoint Portal Server 2003 so that users can sort by content type the documents that are returned in the search results. In this case, the sort functionality does not work for documents in the SharePoint Portal Server 2001 content source.

    For example, if a user searches the portal site for documents in the SharePoint Portal Server 2001 content source, the documents are returned in the search results as expected. However, the user cannot sort the documents by content type.

    This issue occurs if the value of the DAV:getcontenttype property in the documents is dropped during the crawl operation when SharePoint Portal Server 2003 crawls the SharePoint Portal Server 2001 workspace. Therefore, the values are not included in the content index.

  • The LastSecurityChange time is listed in the search results instead of the LastModified time

    When you search a list on a Microsoft Windows SharePoint Services site, the LastSecurityChange time is listed in the search results instead of the LastModified time

  • The number of profiles that are listed on the View user profiles page is incorrect

    When you open the View user profiles page, the total number of user profiles that is listed on the page is incorrect.

  • The name that appears in the Manager field of a user profile is the Domain\Username instead of the preferred name

    You import the Active Directory directory service to a Windows SharePoint Services site. Then, you view the Manager field in a user profile. When you do this, you see that the Manager field has been overwritten by the Domain\Username instead of by the preferred name.

  • Indexes do not propagate, and an event ID error message is logged

    When an Index search is performed on a server that is running SharePoint Portal Server 2003, indexes do not propagate. Additionally, the following message is logged in the event log:

    Event Type: Error
    Event Source: Microsoft SharePointPS Search Service
    Event Category: Services
    Event ID:?
    Date: Date
    Time: Time
    User: N/A
    Computer: ComputerName
    Description:
    Index propagation to search server <ComputerName (IP address)> was not accepted. Context: http://URL, SPS02Portal_CI Catalog
    Details:
    The process cannot access the file because it is being used by another process. (0x80070020)

  • User names are not indexed, and a "The address could not be found, (0x80042616 – Error in the Site Data Web Service)" error message is logged in the gatherer log

    When user names are displayed with a mask such as ??"?\??"?\??"?, the indexing of the server that is running SharePoint Portal Server 2003 does not index the user names. Additionally, the following message is found in the gatherer log:
    sts://username-dc-sql/newarea/webid=008/listid={LONG----GUID}
    "The address could not be found, (0x80042616 – Error in the Site Data Web Service.)*** This '"' character, hexadecimal  value 0x22, cannot be included in a name. Line 1, position 204."
    
    
  • You receive a "Some parts of your personal site cannot be created" error message when you click My Site to create a personal site

    You click My Site to create your site on a server that is running SharePoint Portal Server 2003. If the Readers site group does not contain any user accounts, you receive the following error message:
    Some parts of your personal site cannot be created. Contact your site administrator for more information.
    Additionally, text that resembles the following text may be found in the worker process log:
    date time UNK 00000000 00001E90 Personal Site: server\share, URL, Failed to add default users to the Reader Role. Microsoft.SharePoint.SPException: The parameter 
    loginName cannot be empty or bigger than 255 characters. at Microsoft.SharePoint.g.a(String A_0, Int32 A_1, String A_2) at 
    Microsoft.SharePoint.SPGroup.AddUser(String loginName, String email, String name, String notes) at 
    Microsoft.SharePoint.SPRole.AddUser(String loginName, String email, String name, String notes) at 
    Microsoft.SharePoint.Portal.UserProfiles.UserProfile.a(String A_0, Boolean A_1)
    
    date time UNK 00000000 00001E90 Personal Site: server\share, , Exception.,
     Microsoft.SharePoint.Portal.UserProfiles.PersonalSitePartialCreateException: Failed to add default users to the Reader Role. 
    Microsoft.SharePoint.SPException: The parameter loginName cannot be empty or bigger than 255 characters. at 
    Microsoft.SharePoint.g.a(String A_0, Int32 A_1, String A_2) at Microsoft.SharePoint.SPGroup.AddUser(String loginName, String 
    email, String name, String notes) at Microsoft.SharePoint.SPRole.AddUser(String loginName, String email, String name, String 
    notes) at Microsoft.SharePoint.Portal.UserProfiles.UserProfile.a(String A_0, Boolean A_1) at 
    Microsoft.SharePoint.Portal.UserProfiles.UserProfile.a(String A_0, Boolean A_1) at 
    Microsoft.SharePoint.Portal.UserProfiles.UserProfile.a(String A_0, Boolean A_1) at 
    Microsoft.SharePoint.Portal.UserProfiles.UserProfile.a(Uri A_0)
    
    
  • The Items Detail button is missing on the Search Results page when you search a list

    When you search a list on a Windows SharePoint Services site, the Items Detail button is missing on the Search Results page. This issue may occur after you apply the hotfix that is described in the following article in the Microsoft Knowledge Base:
    894322 Description of the SharePoint Portal Server 2003 post-Service Pack 1 hotfix package: February 15, 2005
  • SharePoint Portal Server 2003 stops responding when it crawls a content source

    When SharePoint Portal Server 2003 crawls a content source that contains a corrupted .pdf file, the crawl is not completed successfully. Instead, SharePoint Portal Server 2003 may stop responding when SharePoint Portal Server 2003 crawls the content source.

  • You receive a "No results were found. The results returned by this service could not be displayed" error message when you search for documents in a document library


    You use the Office Research task pane to search for documents that are contained in a document library. The document library is on a server that is running SharePoint Portal Server 2003. When you search for the documents, the documents are not found. Additionally, you receive the following error message:
    No results were found. The results returned by this service could not be displayed.
    This issue may occur because of invalid characters in the XML that is returned by the Search.asmx file.
  • You receive a "Could not find user with corresponding SID in the domain" error message when you try to remove a user from a SharePoint Portal Server 2003 site

    You try to remove a user from a SharePoint Portal Server 2003 site. If the user has already been removed from Active Directory, you cannot remove the user. Additionally, you receive the following error message:
    Could not find user with corresponding SID in the domain. Check the spelling of the account name and try again.
  • You receive a "The system cannot find the file specified. (0x80070003)" error message

    If you try to run an Index backup when SharePoint Portal Server 2003 crawls a content source, the backup may not be completed successfully. Additionally, you may receive the following error message:
    The system cannot find the file specified. (0x80070003).
    Note You may also receive one of the following error messages:
    • 0x80040db6
    • 0x800703e6
  • You receive a "Cannot complete this action. Please try again" error message when you click a hyperlink to view a specific area of a site

    You log on to a SharePoint Portal Server 2003 site as a member of a group that has Creator permissions. Then, you click a hyperlink to move to a specific area of the site. You then click Back to return to the previous page. After some minutes, if you click the same hyperlink again to return to the specific area of the site, you are not returned to the specific area. Instead, you receive the following error message:
    Cannot complete this action. Please try again.
    This issue may occur when the Use Personal Features permission has been removed from the group.

  • You are directed to http://localhost or to http://ServerName instead of to Lotus Notes search results when you click a link on the Search Results page

    You create a search result display mapping to map Lotus Notes search results. If you click a link on the Search Results page, the display text of the link appears correctly. However, the link may direct you to http://localhost/ or to http://ServerName. This issue occurs because there is an empty HREF link in the HTML source.

  • You receive an "Index out of bound" error message when you try to administer an area tree

    When you try to administer an area tree that is not at the root level on a server that is running SharePoint Portal Server 2003, you receive the following error message:
    Index out of bound.

MORE INFORMATION

Service pack information

This problem was first corrected in SharePoint Portal Server 2003 Service Pack 3.To resolve this problem, obtain the latest service pack for SharePoint Portal Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889380 How to obtain the latest service pack for SharePoint Portal Server 2003

Hotfix information

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:
http://support.microsoft.com/contactus/?ws=support
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

The following list contains prerequisites for the hotfix package:
  • This hotfix is a post-SharePoint Portal Server 2003 Service Pack 2 hotfix. To install the hotfix, you must have post-SharePoint Portal Server 2003 Service Pack 2 installed. For more information about SharePoint Portal Server 2003 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
    887623 Description of Microsoft Office SharePoint Portal Server 2003 Service Pack 2

Restart information

You do not have to restart your computer after you apply this hotfix package.

Hotfix replacement information

This hotfix package that is documented in this article replaces the hotfix package that was documented in article 897722 in the Microsoft Knowledge Base.

Registry information

To use one of the hotfixes in this package, you must either create a registry key or modify a registry key.
  • 898546 When you filter an Index search by a view in a Lotus Notes content source on a server that is running SharePoint Portal Server 2003, all the items in the content source are indexed
  • 905216 You cannot query a specific search server in a server farm deployment of SharePoint Portal Server 2003
  • 910293 A content source crawl takes longer than expected in SharePoint Portal Server 2003
  • 914386 No option is available to configure SharePoint Portal Server 2003 to crawl files that do not have a file name extension as HTML files
  • 915427 Double-byte character set (DBCS) characters are corrupted when you use the Research pane to search for documents on a SharePoint Portal Server 2003 portal site

File information

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 uses a Microsoft Windows Installer package to install the hotfix. The dates and 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 nameFile versionFile sizeDateTime
Sps2003-kb919175-server-gbl.exe11.0000.8216.00198,357,88816-Jun-200622:07
Microsoft Windows Installer .msp file information
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Spsv2hot2-gbl.msp9,888,25616-Jun-200619:48
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:
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Content.sql419,77616-Jun-200619:35
Contentup.sql400,45216-Jun-200619:36
Mimefilt.dll11.0.8126.1946,87216-Jun-200619:36
Mssdmn.exe11.0.8126.19202,00816-Jun-200619:36
Mssearch.exe11.0.8126.19118,04016-Jun-200619:37
Mssph.dll11.0.8126.19534,29616-Jun-200619:37
Mssrch.dll11.0.8126.192,290,45616-Jun-200619:38
Nls400.dll5.0.4301.012,286,74416-Jun-200619:39
Offfilt.dll11.0.8126.19173,33616-Jun-200619:39
Portal.dll11.0.8126.194,655,93616-Jun-200619:40
Profile.sql288,75716-Jun-200619:41
Profilup.sql222,60616-Jun-200619:41
Propdefs.dll11.0.8126.19150,29616-Jun-200619:41
Putildm.dll11.0.8126.1913,31216-Jun-200619:42
Resmgru.dll11.0.8126.19133,91216-Jun-200619:42
Service.sql224,84916-Jun-200619:43
Serviceup.sql201,94516-Jun-200619:43
Spsadm.exe11.0.8126.1916,66416-Jun-200619:44
Spsadmin.exe11.0.8126.19101,14416-Jun-200619:44
Spsutil.dll11.0.8126.198,19216-Jun-200619:44
Sqlbakup.dll11.0.8126.1950,45616-Jun-200619:45
Ximage3b.dll6.0.5jj1,794,10816-Jun-200619:45
Xocr3.psp6.0.5jj1,949,75316-Jun-200619:46

Additional notes

  • For more information about how to install this hotfix, see the Readme.txt file that is included in the hotfix package.
For more information about the terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 919175 - Last Review: November 15, 2007 - Revision: 3.4
APPLIES TO
  • Microsoft Office SharePoint Portal Server 2003
Keywords: 
kbautohotfix kbconfig kbbackup kberrmsg kbhotfixrollup kbfix kbshareptportalsvr2003sp3fix kbexpertiseinter kbqfe kbhotfixserver KB919175

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com