I keep getting this error when creating a new Distribution Group thru 'Sites And Workspaces', any help would be greatly appreicated. "The group operation succeeded, but the distribution group could not be updated because of the following error: The Directory Management Service reported the following error: Access denied."

I have a SP 2007 Server Enterprise, SQL 2005 Backend and AD. I got the same error and finally got around it by turning off inherit group policy's. So my first site and my mysite works fine. I then created another web application for training and found out that this site now has the the problem, but the other one still works. No errors entries in event log even though I have auditing of failures. Not sure what's going on. I checked the new appliction pool account in the sharepoint_ou Org Unit and it has the correct permissions. The group operation succeeded, but the distribution group could not be updated because of the following error: The Directory Management Service reported the following error: Access denied. Any suggestions?

I have the same problem, however I have one site working great all email features work. I created a second base site with FBA and it now wont create a email list or account, I've check settings the other site works great but this onegivesthe same error as above and no event in the logs. Recap: Incoming Email Intranet Site Works with Email all features Project Site (Domain Security) Project Site (FBA) Both fail when creation any email account anywhere in these site. This is the only error I've seen.

Has anybody solved this yet?

I too am having issues with the Directory Management Services (DMS) returning an "Access is Denied" message anytime I try to add the Incoming E-Mail features of a document library. Under SharePoint Central Admin>Operations>Incoming Email Settings. I answered No to the DMS feature and tested my incoming email functionality. Without DMS turned on I was able to successfully create a Document Library capable of receiving email. When I turned the DMS back on the "Access is Denied" messages returned. I've added the appropriate permissions to the Active Directory OU I created to house SharePoint created object. I made sure the Identity of the user launching the SharePoint Central Administration site's application pool had permissions to this OU but I still get the error. Would love to hear about any other findings people may have seen recently! Thanks, Ron

I'm having the same issues as Martinro73. I don't believe it's actually related to this threadsoriginal post, although the title still fits well. I took the same action asRon, testing the list with the DMS turned off. With DMS off I can mail enable any list (and have the list successfully receive email). I can even manually write contacts into AD for all users to see. I just can't get DMS to do it! Turning DMS on I get "Access is Denied" if I attempt to do anything that would use DMS. As with Martinthe AD OU has been createdwith full permissions granted to theWSS Application Pool account. The same account is used for both the central admin pool and the sites pool. I can't even find an Event log or trace log entry for the error so my troubleshooting has ground to a halt. Google hasn't been my friend on thisso far :-( Anyone know where we're going wrong? Failing that can someone point me to advanced troubleshooting techniques for WSS 3.0. James

Has anyone resolved this or got any ideas to try? Gavin Network Admin Sussex Downs College UK

This might be a long shot, but it worked for me. In your IIS settings goto your application pools, select the application pool that the email or distribution groups are erroring out on. Open properties then goto Identity under Identity make sure the format of your domain\admin is this and not domain.local\admin. I had the second option with the domain.local\admin and be removing this and updating it to domain\admin fixed my email creation errors and solution some other minor issues. This is stupid as they are technically both the same and correct. I hope this helps.

Okay, after several long phone conversations with Microsoft about this issue the main resolution we came to is this....we made sure that the domain identity used to run your Central Admin Site application poolshould be the same domain identity used to run any top-level site application pool. While this conflicts with some of the documentation I read from either a book or from Microsoft documentation this partially resolved the issue for me and hopefully will help several others of you. Ron

Oh Thank You, Thank You!!!!That did the trick. The top level site has to use the same account as the Central Admin Site.

This has been fixed in the August CU. Grant the following to the windows account that the IIS "Application Pool" is running under for the SharePoint "Web Application" in question: Design permissions on "Central Administration > Distribution Groups" http://lambertqin.spaces.live.com/blog/cns!E93C48B467E6B3E1!200.entry The same applies for SharePoint 2010.