Emailxtender: Error adding volume 20051110162828 to Lost and Found, Error: 203

Greetings,

What appears to be happening that when EmailXtender services came online after a restart they found a EMX file for which it could not see entries at its desired location (Registry key in earlier EX builds and entry within FolderPlan table of EmailXtender Database in the recent builds). In this case the volume is meant to be added to Lost&found section of the EmailXtender so that admin could add the volume back into the system. To perform this operation EmailXtender needed existence of following registry key on the EX server

HKEY_LOCAL_Machine\Software\OTG\EmailXtender\Lost&Found\Default\

At some sites we found that the Default key under Lost&Found goes missing (mostly because someone exported the entries below it and deleted the key). If that is the case in your environment go ahead, create the key and restart EmailXtender services. If you still encounter the error messages please let us know.

Thanks,

Rajan

Thanks Rajan

The key is there but there is no value set for it.

Should it be set to 1?

Thanks

Here is the screenshot from a test machine:

Do you have this key ?

Regards.

Rajan

Hello again,

The new errors you saw will depend on if you have connection mailbox added or not. Once SourceOne is introduced to the environment most of the time connection mailbox is removed to make sure even by mistake EX do not start pulling emails from this mailbox (usually journal mailbox).

Error messages means that EX was unable to talk to Exchange/notes server to refresh EmailXtender.DLC (Dictribution list cache) file. Connection mailbox is needed to create this file. When you restart services or server then for services to initialise they try to talk to mail servers. If connection mailbox is not present that is not going to hapen.

As you mentioned your server is in read only mode, if no new emails are being ingested into the system then these could be ignored. If you check OTG even log you should have seen similar error messages ever 24 hours in past (unless services were restarted in that time frame).

Thanks,

Rajan

Thanks Rajan for the clarifications.

All good then

Yes I have the key.

I have rebooted the server one more time, and this time the error is gone.

I noticed 2 new one, not sure if it is normal:

“Creation of the distribution list cache or rules failed” and “Policy engine failed to initialize”