Member Avatar for sklingb1

I am running SBS 2003 SP2 and when I go to add a user using wizard, as soon as it launches, I get an error that states SBS add user wizard encountered a problem and needs to shut down. I went into the event viewer and the only error I seem to get is a .NET Runtime 2.0 error:

Faulting application addusr.exe, version 5.2.2651.0, stamp 3f5fb736, faulting module unknown, version , stamp 00000000, debug? 0, fault address 0x06739410.

Is there any other way to add a user or can I correct this error.

THanks

  • 2 Contributors
  • 7 Replies
  • 269 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by JustinNH

Dani AI

Generated

Quick summary tied to the thread: saw addusr.exe fail immediately with a .NET Runtime 2.0 crash, and ’s ADUC workaround let you add accounts manually. Below are safe immediate alternatives plus a practical diagnostic path that fixes the underlying causes Microsoft has documented (so the wizard stops crashing, not just a one-off workaround).

A quick, reliable workaround is to create the Active Directory user from the command line on the domain controller. Example (run an elevated CMD on the SBS server and adjust the DN/password to your environment):

dsadd user "CN=John Smith,OU=SBS Users,DC=domain,DC=local" -samid jsmith -pwd P@ssw0rd -disabled no

See Microsoft’s Directory Service command-line reference for syntax and related tools. (learn.microsoft.com)

Diagnose the wizard crash before changing system-wide protections. Microsoft documented a case where the Add User Wizard throws a .NET System.ArgumentException because duplicate Exchange recipient/email address policies had identical priorities; correcting the policy order (msExchPolicyOrder) restored the wizard. Inspect your Exchange recipient policies (for example with Get-EmailAddressPolicy) and confirm no two policies share the same priority. If you must edit msExchPolicyOrder directly, use ADSIEdit only as a last resort and only after an Active Directory System State backup — ADSIEdit can break AD if used incorrectly. ()

If you’re considering DEP changes because addusr.exe crashes: prefer adding addusr.exe to DEP’s per-process exception list instead of disabling DEP globally, then restart and retest. For persistent .NET-related crashes, run Microsoft’s .NET Framework Repair Tool or collect a crash dump (WinDbg/ProcMon) for deeper analysis. Test any change in a lab and back up AD/Exchange before making production edits. (microsoft.com)

This approach lets you (1) add users immediately, (2) check the specific Exchange/AD cause Microsoft found, and (3) avoid broad, risky configuration changes.

Recommended Answers

All 7 Replies

Member Avatar for JustinNH

You may want to check out this:

You're attempting to create a new user while logged into the server as an admin, correct?

Can you create new users under the Users, Groups container under the Administrative Tools?

Member Avatar for sklingb1

I am logged in as Admin.

I am not sure how to create a new user within Administrative Tools unless I am in Computer Management which only uses the wizard that won't open.

Member Avatar for JustinNH

Ok, I'm looking at one of my 2003 SBS servers...

The way I add new users is the following

- Start>All Programs>Administrative Tools>Active Directory Users And Computers(being that its an SBS server, I am going to assume that you are running AD)

- Browse down to My Business container >Users > SBS Users... Right click in any open space and click New.

This should prompt you then to create a new user which is a bit of a work around to your issue.

I've been reading that issues like this may pop up if you have a failed SP1 install... Can you verified this was updated properly?

-

Member Avatar for JustinNH

And check this out...

Pay attention to the part about the Data Execution option, this has fixed similar issues to yours.

Member Avatar for sklingb1

I will look into this on monday. I know it is not running SP1 and it is on SP2 or 3 now, I can't remember. I think SP1 installed under automatic updates if I remember correctly.

Member Avatar for sklingb1

Server is running SP2.

I was able to add user using your method, thanks.

I will try the DEP setting in the morning before everyone gets in being that I have to restart the server.

Are there any adverse effects in changing that DEP setting? What about for programs I am running on the server? I am just concerned that I might mess up something else by trying to fix this.

Member Avatar for JustinNH

That's a mighty good question :p

I'm not sure what effect it will have on other programs...

http://en.wikipedia.org/wiki/Data_Execution_Prevention

If I understand DEP correctly, you should be able to allow specific software to run under it. The wikipedia article explains it in good detail though.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.