Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Can't run Exchange Management Shell - type initializer exception

369 views
Skip to first unread message

peterse...@gmail.com

unread,
Apr 7, 2010, 3:20:16 PM4/7/10
to
I'm unable to run the Exchange Management Shell on a 2008 DC with
Exchange 2007 SP1 Rollup 9 installed.

I've been having problems with the Client Access role and in the
process of uninstalling and reinstalling it somehow my Exchange
Management Shell became corrupted.

All of the other Exchange roles are fine.

This is the error message:

C:\Windows\system32>C:\Windows\System32\WindowsPowerShell
\v1.0\powershell.exe -P
SConsoleFile "C:\Program Files\Microsoft\Exchange Server\bin
\exshell.psc1" -noexit -command ". 'C:\Program Files\Microsoft
\Exchange Server\bin\Exchange.ps1'"

Windows PowerShell terminated with the following error:
The type initializer for
'Microsoft.Exchange.Management.PowerShell.CmdletConfigurationEntries'
threw an exception.


What can I do to correct this issue?

I have tried for a full day to reinstall management tools, but it
won't let me. I've rebooted and reinstalled multiple roles, I've
uninstalled and reinstalled the SP1 rollups, but nothing seems to make
a difference to the ability for PowerShell to load up my Exchange
Management Shell.

In my windows error logs -> power shell logs it has the following:

Log Name: PowerShell
Source: PowerShell
Date: 4/7/2010 12:23:50 PM
Event ID: 403
Task Category: Engine Lifecycle
Level: Information
Keywords: Classic
User: N/A
Computer: <compname>.<domainname>.local
Description:
Engine state is changed from Available to Stopped.

Details:
NewEngineState=Stopped
PreviousEngineState=Available

SequenceNumber=24

HostName=Exchange Management Console
HostVersion=8.0.0.0
HostId=561a3074-ea2e-4195-b77f-640202cffe10
EngineVersion=1.0.0.0
RunspaceId=d294aac3-c4fb-4ae7-aeff-e24a399b95bb
PipelineId=
CommandName=
CommandType=
ScriptName=
CommandPath=
CommandLine=
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="PowerShell" />
<EventID Qualifiers="0">403</EventID>
<Level>4</Level>
<Task>4</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-04-07T18:23:50.000Z" />
<EventRecordID>4136</EventRecordID>
<Channel>PowerShell</Channel>
<Computer><compname>.<domainname>.local</Computer>
<Security />
</System>
<EventData>
<Data>Stopped</Data>
<Data>Available</Data>
<Data> NewEngineState=Stopped
PreviousEngineState=Available

SequenceNumber=24

HostName=Exchange Management Console
HostVersion=8.0.0.0
HostId=561a3074-ea2e-4195-b77f-640202cffe10
EngineVersion=1.0.0.0
RunspaceId=d294aac3-c4fb-4ae7-aeff-e24a399b95bb
PipelineId=
CommandName=
CommandType=
ScriptName=
CommandPath=
CommandLine=</Data>
</EventData>
</Event>

However I don't know what I can do to make the EMS to be able to open.

Please help.

peterse...@gmail.com

unread,
Apr 9, 2010, 1:14:01 PM4/9/10
to
On Apr 7, 1:20 pm, "petersen.aa...@gmail.com"

In the end I set up a totally different CAS server and gave up on that
particular box, and decided to just Migrate the Exchange off of it. I
never did get the EMS to run, but with the new CAS server I didn't
really need it to.

H@discussions.microsoft.com Danny H

unread,
May 28, 2010, 12:07:01 PM5/28/10
to
I'm having the same problem, and spent 3 or 4 days trying to fix it. Is
there any way to repair the management tools without uninstalling and
reinstalling all other exchange roles?

thanks

0 new messages