The official blog for Windows Server Essentials and Small Business Server support and product group communications.
[Today’s post comes to us courtesy of Damian Leibaschoff from Commercial Technical Support ]
The symptoms for this case were that after a few seconds of launching the Add User Wizard, the wizard would crash, without any user input.
When we face a user mode crash like this we usually try to get our hands on the dump that is generated so we can review what triggered the crash. Depending on the crash, the associated wizard log might also contain valuable information (this was not the case here). Furthermore, we might also rely on tools such as Sysinternal’s Process Monitor.
For this case we launched the application within our Windows Debugger to see what was taking place, here is a summary of what we found and how we found it:
This was a very strange situation, the most likely cause was that the original Default Policy had been manually renamed to the Windows SBS Email Address Policy and a subsequent service pack for Exchange tried to recreate the missing Default Policy or it could have been as simple as some incorrect manipulation of AD objects..
I really appreciate this information. I have been experiencing this problem for several months and I have been unable to find any information about it at all.
When I tried the powershell script I did not get an error message and when I used ADSI edit I found that the value for msExchPolicyOrder was already set to 1. However, my Exchange Console, Organization Configuraltion, Hub Transport, Email Address Policies, Priority is stil showing 1 instead of lowest. Are there more items that can be checked/modified? Oh yeah, the console still crashes.