Those permissions are present.
Main Topics
Browse All TopicsI'm having the following issue when attempting to access OWA for Exchange 2007. I have attempted the fixes that have previously been posted for this issue. The accounts are set to allow inheritable permissions, and the setup.com /preparead command has been executed. I've also created a new account and user mailbox that was originally setup in the Exchange 2k7 environment, and I still have this issue with that account. Any suggestions?
Url: https://<servername>:443/o
User host address: <client IP address>
Exception
Exception type: Microsoft.Exchange.Data.St
Exception message: There was a problem accessing Active Directory.
Call stack
Microsoft.Exchange.Data.St
Microsoft.Exchange.Clients
Microsoft.Exchange.Clients
Microsoft.Exchange.Clients
Microsoft.Exchange.Clients
Microsoft.Exchange.Clients
System.Web.HttpApplication
System.Web.HttpApplication
Inner Exception
Exception type: Microsoft.Exchange.Data.Di
Exception message: Active Directory operation failed on et3kdc01.FKNC.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation. Active directory response: 00002098: SecErr: DSID-03150A45, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
Call stack
Microsoft.Exchange.Data.Di
Microsoft.Exchange.Data.Di
Microsoft.Exchange.Data.Di
Microsoft.Exchange.Data.St
Inner Exception
Exception type: System.DirectoryServices.P
Exception message: The user has insufficient access rights.
Call stack
System.DirectoryServices.P
System.DirectoryServices.P
Microsoft.Exchange.Data.Di
Microsoft.Exchange.Data.Di
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
This usually occurs when Allow inheritable permissions& is not checked on either an OU or user object in AD Users and Computers.
To confirm, open ADUC and click Advanced Features on the View menu. Open the properties of an affected user and go to the Security tab. Click the Advanced button and confirm if this setting is checked or not. If it is, then repeat the process for each OU container between the user object and the top-level container.
be sure that the top-level container includes the Exchange Servers group. This is required and must propagate down to the users for them to successfully access OWA.
One other solution, as I discovered at 2am this monring, is that if you have a forest root domain with child domains, it is possible that the child domains were not properly preped for the Exchange Schema changes. I ran setup.com /preparedomain on one DC in each child domain (the exchange server in my domain is a member of the Forest Root) and Viola!
One again, here's the step by step...
1. Log into a DC in the domain with the ofending account
2. Insert your EXC07 media in the system (or expand the 32bit installer in a easy to locate location in the C Drive)
3. Navigate to the setup.com file and run it from the command line as such:
<path to file>\setup.com /prepairdomain
4. All good. But remember to log in with domain admin priv's on the DC you are running this on.
Cheers!
B
well not really, all of the rights inheritance was setup correctly, infact i did look at first like the domain was preped correctly (after really digging into the permissions which is what was posted everywhere else I looked). I believe we had two different issues with the same set of symptoms and errors...
B
I ran into the same problem a few minutes ago and ran this cmdlet set-mailbox "name" -ApplyMandatoryProperties and I was able to get into OWA. Here is the article that clued me in....http://www.msexchang
Regards
I first tried set-mailbox "user" -ApplyMandatoryProperties but no settings were changed.
When I enabled Advanced View and took a look at the Security tab for the user object, I found that it was not inheriting permissions so the Exchange Enterprise Servers group did not have any write permissions as well as some others that appeared when I enabled inheritance.
One more point for the inheritance checkbox :-)
Business Accounts
Answer for Membership
by: kristinawPosted on 2007-08-06 at 12:39:52ID: 19640966
do you still have a server around with the 2003 esm on it? take a look at aduc, for both the security tab and the mailbox permissions tab. Make sure the NT AUTHORITY\Self right is present.
Kris.