Article ID: 925253 - Last Review: October 25, 2007 - Revision: 2.3 Error message when you run the Information Store Integrity Checker (Isinteg.exe) tool in Exchange Server 2003: "Unable to identify local server row in Replication state table for this FID"
On This PageSYMPTOMSYou 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 Note To run the Isinteg.exe tool, open a command prompt, and then locate the following folder: Drive:\Program
Files\Exchsrvr\Bin Then, run the following command at the command prompt. RESOLUTIONTo
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 informationA 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
(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.PrerequisitesBecause 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
(http://support.microsoft.com/kb/836993/
)
How to obtain the latest service packs for Exchange Server 2003
Restart requirementYou 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:
Hotfix replacement informationThis hotfix does not replace any other hotfix.File informationThe 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.Collapse this table
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. | Article Translations
|
Back to the top
