Microsoft KB Archive/925253

= Error message when you run the Information Store Integrity Checker (Isinteg.exe) tool in Exchange Server 2003: &quot;Unable to identify local server row in Replication state table for this FID&quot; =

Article ID: 925253

Article Last Modified on 10/25/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Standard Edition
 * Microsoft Exchange Server 2003 Enterprise Edition

-



SYMPTOMS
You run the Information Store Integrity Checker (Isinteg.exe) tool in Microsoft Exchange Server 2003. When you do this, the tool cannot fix some errors in the replication table of the public folder.

Additionally, you may receive an error message that resembles the following error message:

Error: ReplState 3856: (FID 0144-00000105DF5C): Unable to identify local server row in Replication state table for this FID.

Error: ReplState 3858: (FID 0144-00000105DF5D): Unable to identify local server row in Replication state table for this FID. ... . . . ..

SUMMARY. . . ..

Total number of tests : 1

Total number of warnings : 0

Total number of errors : 51

Total number of fixes : 0

Total time : 0h:0m:1s

Additionally, public folders are replicated slowly or not at all.

Note To run the Isinteg.exe tool, open a command prompt, and then locate the following folder:



Then, run the following command at the command prompt. isinteg -s Server name -fix -test replstate



RESOLUTION
To resolve the errors that occur in the replication table, apply the hotfix that is described in this article. However, if the public folders are replicated slowly or not at all, this hotfix will not resolve that problem.

Hotfix information
A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
Because of file dependencies, this hotfix requires that you install Microsoft Exchange Server 2003 Service Pack 2 on the server.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

836993 How to obtain the latest service packs for Exchange Server 2003

Restart requirement
You do not have to restart the computer after you apply this hotfix. However, the following services are automatically stopped and then restarted when you apply this hotfix:
 * Microsoft Exchange Information Store
 * Microsoft Search
 * IIS Admin Service and all dependent services

Hotfix replacement information
This hotfix does not replace any other hotfix.

File information
The English version of this hotfix 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.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

Additional query words: ISINTEG

Keywords: kbexchtransport kbhotfixserver kbqfe kbfix kbbug kbpubtypekc KB925253

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.