You are currently offline, waiting for your internet to reconnect

XADM: Exssrv.exe Does Not Work with ISTREAM Error 80030005 During Free and Busy Replication

This article was previously published under Q286693
This article has been archived. It is offered "as is" and will no longer be updated.
When you use the Exchange Public Folder Synchronization Agent (Exssrv.exe) to replicate free and busy folders from one organization to another organization, the following error message may be logged in the Ex00yymmdd.log file in the Exchsync folder (where stream_name is the stream that is used to import the changes to the destination server server_name in the Exchange site that is represented by /o=org/ou=site):
ERROR: Unable to open ISTREAM 'stream_name' in replication state file, failed [80030005].
ERROR: Unable to get collector for folder 'EX:/o=org/ou=site' on server [server_name].
This error message is logged only when you are replicating free and busy folders for multiple organizations.
The stream name is generated by using the following information:
  • The free and busy folder name.
  • The type of information that is being replicated.
  • Whether or not the folder is the source or the destination.
This algorithm generates the same destination stream name for every task that replicates a free and busy folder. This problem can occur if the first task to create the stream locks it for exclusive read/write access; therefore, all subsequent tasks that attempt to access the stream generate an access denied (80030005) error.
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
To work around this problem, set the configuration file (.esc) to use one session for each organization free and busy folder. Each session should only replicate a single free and busy folder and use a single task.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 2.
EXCHSYNC exch2kp2w

Article ID: 286693 - Last Review: 10/23/2013 15:59:20 - Revision: 4.3

Microsoft Exchange 2000 Server Standard Edition, Microsoft Exchange Server 5.5 Standard Edition, Microsoft Exchange Server 5.5 Service Pack 1, Microsoft Exchange Server 5.5 Service Pack 2, Microsoft Exchange Server 5.5 Service Pack 3, Microsoft Exchange Server 5.5 Service Pack 4, Microsoft Exchange 2000 Enterprise Server

  • kbnosurvey kbarchive kbbug kberrmsg kbexchange2000sp2fix kbfix KB286693