Error updating public folder with busy
Get-Storage Group Copy Status : Microsoft Exchange Replication service RPC failed : Microsoft. Check the network connectivity and name resolution. The directory \ascoex101be491d6f-3691-49e7-b1b8-3e563b495c6b$ required by the Microsoft Exchange Replication Service for ASCOEX101V1\Public Folder Group does not exist. On the server that is active I'm seeing this error at about the same time.
Now the replication won't run and when I try and query for the replication status using either the UI or the CLI I get the following. Rpc Exception: Error e0434f4d from cli_Get Copy Status Ex at Microsoft. The list of aliases is now 'ascoex101b', and the alias 'was' removed from the list. The directory '\ascoex101be491d6f-3691-49e7-b1b8-3e563b495c6b$' required by the Microsoft Exchange Replication Service for ASCOEX101V1\Public Folder Group could not be accessed.
Few administrators understand how clients publish free/busy data as users update their calendars, where Exchange stores the data, and what the data actually represents.Error updating public folder with free/busy information on virtual machine ASCOEX101V1. The machine which is currently active is ascoex101b, the machine which is currently passive is ascoex101a, and the virtual name is ascoex101v1.I'm assuming that the problem is related to something with the network shares but according to the share rights and folder rights everything should be working correctly. Although Tech Net and the Exchange development team blog (at provide good information about free/busy data, this article aims to give you comprehensive coverage of the topic, bringing different sources of information together to illuminate one of the more esoteric parts of Exchange.Let’s start demystifying free/busy data by looking at where Exchange stores it and how clients publish it.