ID no: 80070005
I m having Microsoft Exchange 2003 SP2, I m having error inMs Exchange manager ---- Expand ---- Administrator
---- Server ---- Queues ---- when i right click on queues to do force connection. I m getting error ........
Access Denied
Faulty: LDAP
ID no. 80070005
Exchange System Manager
Can someone Reslove this problem!!!
I'm can't having any access in Exchange Managerthrough Administrator User ID, on other server with same ID i canable to access...
July 29th, 2008 9:45am
@ddy,
better post this on the Exchange forum, like :
http://forums.microsoft.com/TechNet/ShowForum.aspx?ForumID=833&SiteID=17
HTH,
Peter
Free Windows Admin Tool Kit Click here and download it now
July 29th, 2008 10:23am
BTW :
In the Exchange Forum, this post refers to http://support.microsoft.com/kb/323915
And search the Exchange forum for error 80070005http://forums.microsoft.com/TechNet/default.aspx?ForumGroupID=235&SiteID=17
Or you could searchTechnet with "Access Denied LDAP 80070005Exchange System Manager"
But still, posting to the Exchange forum, will probably get better results.
HTH,
Petr
July 29th, 2008 10:46am
Hi,
Please follow the steps listing below to troubleshoot this issue.
1. Please apply the latest update for Exchange 2003 Server.
2. Please make sure that the account which you used to perform message tracking has Exchange administrative privilege.
3. Check the permissions for the Exchange Domains Servers object. (From the SERVERNAME object in ESM, select the Security tab.)
If not at Full Control, set it to Full Control. Click the Apply, then OK buttons to apply the change.
4. Check whether it has enabled "Enable message tracking".
Note: Open the properties of the SERVERNAME object and select the General tab. Select the Apply and OK button to apply the changes.
Hope it helps.
Xiu
Free Windows Admin Tool Kit Click here and download it now
July 30th, 2008 12:02pm
This error was strange.
I restarted my server and appear the error when I tried to access to the queus in the Front-End.
After 5 minutes, I can see the queue
I didn't make any changes except I upgrade my Exchange organization to No Pre-Exchange 2000, the reason of this is to prepare my scenario for migrate to Exchange 2007.
Maybe is a bug of Exchange 2003.
Thanks
September 13th, 2008 8:41am