• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 505
  • Last Modified:

Exchange - One domain user can't send email after a hard recovery.


I am having some troubles with one user after we had to do a hard recovery of our exchange mailbox database.

We apply eseutil /p as a last resort follow with a eseutil /d than we went with a isenteg --fix.
At the end, the isenteg is reporting no more errors and we can mount the database without any problems

But, since then, a user can't send email from his outlook 2003, but he can still send email using OWA.

The error he his getting in his outlook :

"You do not have sufficient permission to perform this operation on this object. See the folder contact or your system administrator."

It seen that the user is lacking permission to send with his own mailbox.

The exchange 2003 is host on a Windows SBS 2003.

I would appreciate any tips to resolve this issue.

Thank you.


1 Solution
If OWA is working then the mailbox seems to be OK

Has the users PC been restarted at all since the rebuild of the database?
Open Active Directory and search for the user account. Under security inherit the permission from the parent.
ktiniteckAuthor Commented:
Yes, the computer been restart and we did try from a other computer with the same behavior.

Actually we tried from a outlook 2003, a outlook 2007 and a outlook 2003 connect throught a VPN with the same probleme.

We tried to create a new domain account with a mailbox and it seen to work perfectly.

It seen that it only that single account that got this problem.
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Open Active Directory and search for the user account. Under security inherit the permission from the parent.
ktiniteckAuthor Commented:
I apply the "security inherit the permission from the parent" and I guess I am gonna have to wait for exchange to flush it cache.

Let us know the result once it is done
As an alternate solutions to these type of problems. Try the following.

1. Use Exmerge to export all contents of this mailbox to a PST file as a backup. To ensure nothing is lost.

2. Ensure you have a retention higher than 1 day to automatically Purge the mailbox after deletion.

3. find the user in AD and delete the mailbox. This will only disconnect the active mailbox in Exchange.

4. Wait for replication if needed until you see a "red x" on the mailbox in ESM.

5. Check that the user's account shows there is no mailbox associated to it.

6. Find the mailbox with the Red X and do a "Reconnect" . Select the user it was associated to.

Give time for each step to take place.

7. WORST case scenario, recreate the broken account with new mailbox and IMPORT the exmerged PST back into the mailbox via outlook.
ktiniteckAuthor Commented:
The modification took longer than expected to be taken into account by the exchange server, but the information was accurate and answers in a matter of few minutes.


Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now