Deciphering IISSYNC Status Codes

Article translations Article translations
Article ID: 224801
This article was previously published under Q224801
This article has been archived. It is offered "as is" and will no longer be updated.
We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 7.0 running on Microsoft Windows Server 2008. IIS 7.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:
http://www.microsoft.com/technet/security/prodtech/IIS.mspx
For more information about IIS 7.0, visit the following Microsoft Web site:
http://www.iis.net/default.aspx?tabid=1
Expand all | Collapse all

Summary

The IISSYNC utility is used to synchronize Internet Information Server (IIS) metabase and Transaction Server packages on one Node with IIS on a Microsoft Cluster Server on the other Node.

The IISSYNC utility returns a status code upon completion. This status code is always a numeric message whether the synchronization was successful or whether an error occurred.

This article contains a list of status codes that are most often encountered and what the possible or probable cause of the status code is.

More information

IISSYNC Status Codes

Collapse this tableExpand this table
Status CodeMeaning & Probable Cause
0Successful Synchronization
3metabase is inaccessible on Target Server. (The metabase may be corrupt or in use.)
1060Communications problem between Nodes. (This occurs when the Dcom default protocols do not match on both Nodes.)
1722The RPC server is unavailable. Invalid Target Server Name or Communications Problem between Nodes
1726The remote procedure call failed
2147500037MTS Replication is not configured. (See the Knowledge Base article 191138)
2148007941Administrator account not logged in on Target Server. (If MTS is configured for Local Administration instead of Remote Administration, it is necessary to have a Local Administrator Equivalent account logged on the Target Server when IISSYNC is run.)
2148598792Communications problem between Nodes. (Possible IP Conflict. Make sure all IP addresses on both Nodes and in the IIS Resource group are all in the same subnet and valid.)
2148598794Invalid share in MTS replication settings. (Set the MTS replication share to the administration share on which MTS is installed on the Target Server.)
2148599041User logged on to Target Server has insufficient rights for MTS replication. (Log on to Target Server as Local Administrator.)
2148598801The component's CLSID is missing or corrupt.
2148598808 Application file CLSIDs or IIDs do not match corresponding DLLs
2148598800One or more users in the application file are not valid
2148598785Errors occurred accessing one or more objects
2148598797An error occurred copying the file
2148598828The server catalog version is not supported


As further status codes are encountered and a cause has been determined, the information will be added to this Knowledge Base article.

Properties

Article ID: 224801 - Last Review: October 26, 2013 - Revision: 6.0
Keywords: 
kbnosurvey kbarchive kbhowto KB224801

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