cancel
Showing results for 
Search instead for 
Did you mean: 

Corrupt Contacts

Jamison_West
Level 3
Partner
I have a client with BE 11d on SBS 2003 Standard. They moved a bunch of personal Contacts to the shared Public Contacts folder. Everything looks perfect in Outlook and on Exchange. I have run ESEUTIL to do an offline defrag of the Exchange 2003 DB. Yet, we continue to get the following errors. Note that these contacts do not exist in these users' contact folders. Please advise:


Backup- \\SERVER\Microsoft Exchange Mailboxes V-79-57344-33928 - Access is denied.
Access denied to file Charles Birnbach Top of Information StoreContactsRich Kaner MD.
V-79-57344-33928 - Access is denied.
Access denied to file Charles Birnbach Top of Information StoreContactsBruce A. Beaularier OD.
V-79-57344-33928 - Access is denied.
Access denied to file Charles Birnbach Top of Information StoreContactsMark H. Cohn OD.
V-79-57344-33928 - Access is denied.
Access denied to file Charles Birnbach Top of Information StoreContactsSuzan B. Grimm OD.
V-79-57344-33928 - Access is denied.
Access denied to file Charles Birnbach Top of Information StoreContactsShauna M. Mazzulla OD.
V-79-57344-33928 - Access is denied.
Access denied to file Charles Birnbach Top of Information StoreContactsRick L. McManus OD.
V-79-57344-33928 - Access is denied.
Access denied to file Charles Birnbach Top of Information StoreContactsCurtis A. Ono OD.
V-79-57344-33928 - Access is denied.
Access denied to file Charles Birnbach Top of Information StoreContactsWilliam J. Prothero OD.
V-79-57344-33928 - Access is denied.
8 REPLIES 8

Philip_Pearson
Level 6
May not be corrupt, they may just not have inherrited the permissions of the destination folder, I'm not too familiar with sbs but in in the exchange system manager you can drill right down into the public folders, from there you can check permissions.

Jamison_West
Level 3
Partner
This is the same as Exchange 2003, SBS has no bearing on the feature. The problematic files exist in two user's personal contacts PLUS the public contacts folder. What permissions are required for Backup Exec to backup these individual items? Their personal contact folders do not have different permissions than other individual contact folders for other users on the network, and the issue is with the same set of contacts that got copied around. Thoughts?

Jamison_West
Level 3
Partner
Still no feedback on this one. Can anyone suggest any options? This is driving us crazy because backup logs are huge with corruption even though these items shouldn't exist. Is there a way to purge the corrupt items easily? Any thoughts would be helpful.

Philip_Pearson
Level 6
Try exporting the user's copntacts, delete the entire contents of the contacts folder then re-import.

Worth a shot.Message was edited by:
Philip Pearson

DanielBickford
Level 6
Employee Certified
Jamison,
It appears the permissions problem is coming from the Public folder you put the contacts in. You need to give the BE account used the "owner role" on those public folders. If you are still having a problem with the individual contacts folders the suggestion to export them and delete and re-create is correct also.
I hope this helps, please let us know if it doesn't.
Thanks,
Daniel

Jamison_West
Level 3
Partner
Administrator is the account and does have the owner role. The contacts shouldn't even appear here, they were deleted long ago. They do not appear in OWA or in Outlook, but there must be some corruption somewhere. We have run every tool for Exchange (ESEUTIL, etc.) and found no issues. The only software that seems to see these old contacts is Backup Exec 11d. Backup Exec 10d, by the way, did NOT see these corrupt items, if in fact that's what they are.

DanielBickford
Level 6
Employee Certified
Jamison,
Apparently, there is something unusual going on here, it would be best if you call into support and open a case for this issue.
Thanks,
Daniel

St-3
Not applicable
Did you try deselecting those items in the backup job? Sometimes, even though you have moved items, the backup job doesn't update and it continues to try and backup the items it has been told to backup, and since they are no longer there, it gives the Top of Store error, and fails the job.