Subject: Archiving policy does not create the archive database
We encountered this problem when a person’s record in the NAB had an incorrect server, specifically, the server was lower-case. By reselecting the server from the server list, and waiting for the change to replicate to the person’s mail server copy of the NAB, we could then archive successfully. Hope this helps.
Subject: RE: Archiving policy does not create the archive database
I’ve got the same problem.I’ve checked the NAB and can’t find any person records with incorrect server entries, even wrong case.
I’m suprised that one incorrect person document could effect the initial archive for all users as I specified all databases in the mail directory to be archived.
All the mail files seem to think that there is an archive there as they are showing the two rule options that I specified under the archive section, however, I get the notes message “Server Error: File does not exist” when either is clicked.
I was thinking that this might be more of a “user does not have access to create databases on the server” type issue as I’ve set it up to be client based archiving.