Had a server recently that needed to have Power shell re-installed onto the server. After performing the re-install a heap of strange errors starting to occur on the server. The main one that triggered the alert of is that the Exchange Management Console wouldn’t start and would present an error like
The type initalizer for ‘Microsoft.Exchange.Configuration.MonadDataProvider.ConnectionPool’ threw an exception
After the initial troubleshooting I attempted to load Power Shell which gave the following error.
The shell cannot be started. A failure occurred during initialization: Object reference not set an instanace of an object.
After trying the usually troubleshooting issues I found some information that says this issue can occur if the HKEY_CURRENT_USER\Environment key is missing from the registry. So I check for that key and sure enough it is missing.
Re-created the key and Power shell started successfully.
Once Power Shell was working all of the other services started working with no trouble.
What are the details in the registry that you left ourt of the posting.
Thanks for the question.
I dont believe there were any sub values. It was just the key that was missing.
Where did you find this? This definitely fixed the issue. A previous IT provider of one of our clients had a failed PowerShell 2.0 upgrade. It sounds like they must have deleted this key during their attempts because adding a generic HKCU\Environment key worked perfectly. We were about to schedule time to reinstall EMC/EMS completely.
Seriously curious where you found this solution.
Hi.
I don’t remember specifically where I tracked this information down from sorry.
I must say I was skeptical, but just adding that key worked!
Thank you
Dean: you’re a genius! Thanks for sharing this fix.