Add new user wizard not running in windows server 2003 SBS

When I try to add a new user on my small business server I get to the first screen of the wizard which tells what is going to happen, then when I click next, there is a hesitation and then that window disappears and I am back to the list of users.

I have restarted the server and looked at the licensing (I thought that might be relevant).  if anyone has seen this before or can advise me where to start troubleshooting I would appreciate it,.

Thanks,

Sky
Schuyler KuhlAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Schuyler KuhlAuthor Commented:
In the application log is this error after I try to run the add user wizard:

Faulting application addusr.exe, version 5.2.2651.0, faulting module unknown, version 0.0.0.0, fault address 0x064c6088.

So I guess this is the problem, but I'm still not sure how to get around this.

Best regards,

Sky
0
AdamRobinsonCommented:
I've seen this associated with a failed/bad install of the SBS Components.  You may want to try re-installing the administrative tools.

0
Schuyler KuhlAuthor Commented:
I figured it out.  Amazingly, it was way over my head.

I found someone on a newsgroup who had the same problem and he wrote this when he worked it out:

Just to let you know that I solved the problem by mistake.
All the wizards were disabled in the Data Execution Prevention screen. I
guess it was a side effect of the CA's security program.

I wasn't familiar with the Data Executation Preventation screen but I googled it and found this support doc:
http://support.microsoft.com/kb/875352

I used this to edit the bootini file so that the noexecute command was set to OptIn, somehow it had become OptOut.

Thanks
0
AdamRobinsonCommented:
sky:

That's also a symptom of a failed install, at least in my experience.  I've seen that happen in three cases, and in all three cases the 2003 components had bee installed but the SBS components were put on much later.   Don't know if that's the case with you, but I also found it to be a very big annoyance the first time I saw it.  :)
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Schuyler KuhlAuthor Commented:
AdamRobinson:

I think you are correct, because I am working on a swing migration and I just added a second domain controller that was made from the sbs disks but I only allowed it to run for the server 2003 part and not install the sbs components.

Thanks for your help

Sky
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.