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

Error when adding a new user to Windows 2003 AD Domain

Tried to create a new user using Active Directory Users and Computers from My PC as i have done heaps of times before with no issue.

AD Users and computers took a while to load which is unusual. After i created the user by copying an existing user i tried to select properties which after a while popped up the error message

"The operation failed. ID No: 80004005 Microsoft Active Directory - Exchange Extension"

In the properties window there are no tabs for exchange so it is not loading the exchange extensions for some reason.

I get the same issue when trying to create the user on the DC.However using AD Users and computers from the exchange server worked fine.

any help would be appreciated.
0
PACSAdmin
Asked:
PACSAdmin
  • 8
  • 6
1 Solution
 
PeterSingerCommented:
It sounds like you have an orphaned object in the AD, follow the following procedure to find the entry;

http://support.microsoft.com/kb/284928/en-us

Once found use ADSI EDIT to delete the orphaned object.

Peter
0
 
PACSAdminAuthor Commented:
Followed the steps got the following output

***Searching...
ldap_search_ext_s(ld, "DC=benrad,DC=local", 2, "(isDeleted=*)", attrList,  0, svrCtrls, ClntCtrls, 10, 0 ,&msg)
Result <0>: (null)
Matched DNs:
Getting 0 entries:
-----------

This seems to say there are no orphaned objects
0
 
PeterSingerCommented:
Could this be the issue?

http://support.microsoft.com/kb/314034
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
PACSAdminAuthor Commented:
No i have already looked at this before posting. Thanks for the post anyway.
0
 
PeterSingerCommented:
0
 
PACSAdminAuthor Commented:
Cant see how this will help. We do not run Vista.

Just tried re installing the exchange tools and service pack but this did not work.

Any more suggestions?
0
 
PeterSingerCommented:
What I am saying is to re-register the exchange server DLLs.
0
 
PACSAdminAuthor Commented:
Sorry was not trying to be disrespectfull appreciate your help

trying to re register the dll's i get for example

escprint.dll was loaded, but the DllRegisterServer entry point was not found. This file cannot be registered.
0
 
PeterSingerCommented:
Sorry, not at all, I know it can be frustrating.
Can you please check that the following file exists and try to register it, then try again.
regsvr32 \windows\system32\maildsmx.dll  
And have you looked at this?
http://forums.techarena.in/active-directory/622018.htm 
0
 
PeterSingerCommented:
Could you also confirm you are on a stand alone exchange server (ONE Server in the enterprise) Windows Server 2003 SP2 and Exchange SP2?
What version of windoes Standard or enterprise?
Peter
0
 
PACSAdminAuthor Commented:
i can confirm we are have a stand alone exchange server  Windows Server 2003 SP2 and Exchange SP2?
0
 
PACSAdminAuthor Commented:
the file maildsmx.dll  exists in c:\program files\exchsvr\bin on my workstation. Is this what you are eluding too or the file on the exchange server

0
 
PACSAdminAuthor Commented:
I am convinced the issue is related to my computer and it is a DNS Issue albeit a strange one. Here is why i think it is DNS Related

I am unable to resolve the DC name from MMC Snap-ins without using the FQDN.

If i open event viewer and select connect to another computer i cannot connect to the domain controller unless i use the FQDN. However if i try one of the other 3 domain controllers there is no problem i can just connect by name.

I can ping the name of the DC and it resolves the I.P OK. I can MSTSC into the domain controller by just using the name and it connects OK so DNS is working. I have looked at DNS and can see no misconfiguration.

Can anyone point me in the right direction to troubleshoot this.
0
 
PACSAdminAuthor Commented:
fixed the issue by doing a restore on my workstation. Do not know what was causing the issue but it was DNS related. after the restore i was able to connect to the DC using name only and the ADUC also worked perfectly.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

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