Event id 1020 ms exchange storage driver

To sending out mail. So what is the solution for this specific case where it is the anonymous account. Is there a way to see what IP is generating this? Post : 4. Post : 5.

BrAtKo Posts: 2 Joined: 7. Hello, anyone have solved this problem? I have set up the connector this way when I installed the Exchange. Would you mind specify the commands with solution please. Thank you. Post : 6. Here is what I can say on my issue which I resolved. I have 3 receive connectors setup. When you try to replicate the public folder content to Microsoft Exchange Server , it won't replicate.

In an environment in which Exchange Server or Exchange Server previously existed, and all those servers have been removed, there's a chance that an Administrative Group First Administrative Group or another custom Administrative Group remains with a Servers container, but no servers inside it. During the replication, when the Exchange Store Driver sees the empty Servers container in Active Directory, it's expecting a System Attendant object inside the container. If the driver can't find the object, the error occurs.

To work around the issue, delete the empty Servers container. This can't be done through Exchange System Manager. Base on my research the error message MSExchange Store Driver tells us that one corresponding has been delivered successfully One message with the same Internet Message ID and the client submit time.

Actually, event is one enhanced feature in Exchange SP1. Before SP1, duplicated message will not be explicitly logged since it is not a true transport issue. It just for some troubleshooting analysis. If you prefer to have a further check on it, we could have a look at the following things:. What about the frequency of the error message being logged on the server? Whether the error message is related to one particular public folder server? Or other messages not for public folder server also have similar events logged?

Do we have some diagnostic logging enabled for public folder on the server? To check diagnostic logging, we could follow the steps:. Go to the Exchange server. Open below registries, check whether some items are not 0. Check public folder replication.