Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
Exchange Console and Shell Not Working
Running Exchange 2010 with SP1 under Windows Server 2008 R2. After recently installing Exchange SP1 (no rollups installed), I cannot start my EMC nor run any Exchange commands from the PowerShell. When I try executing a command, I get:
Exception calling "GetSteppablePipeline" with "1" argument(s): "The type initializer for Microsoft.Exchange.Configu
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : DotNetMethodException
When I try opening my EMC, I get an unhandled exception.
Within my application event log, I’m seeing event ID 1001 (which may or may not be related) to this:
Version=1
EventType=PowerShell
EventTime=1295003504979508
ReportType=1
Consent=1
ReportIdentifier=33623620-
Response.type=4
Sig[0].Name=NameOfExe
Sig[0].Value=powershell.ex
Sig[1].Name=FileVersionOfS
Sig[1].Value=6.1.7600.1638
Sig[2].Name=InnermostExcep
Sig[2].Value=System.Invali
Sig[3].Name=OutermostExcep
Sig[3].Value=System.TypeIn
Sig[4].Name=DeepestPowerSh
Sig[4].Value=unknown
Sig[5].Name=DeepestFrame
Sig[5].Value=crosoft.Excha
Sig[6].Name=ThreadName
Sig[6].Value=unknown
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.76
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
FriendlyEventName=PowerShe
ConsentKey=PowerShell
AppName=powershell
AppPath=C:\Windows\System3
Is this a known bug? Is it fixed in a roll-up? Are there services I should restart? I’ve looked at other articles but nothing seems to fit. One spoke of ADWS not running (on the domain controllers) but it is; even still, restarting it hasn’t helped. This looks like a programming issue (invalid cast exception) under the covers.
Exception calling "GetSteppablePipeline" with "1" argument(s): "The type initializer for Microsoft.Exchange.Configu
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : DotNetMethodException
When I try opening my EMC, I get an unhandled exception.
Within my application event log, I’m seeing event ID 1001 (which may or may not be related) to this:
Version=1
EventType=PowerShell
EventTime=1295003504979508
ReportType=1
Consent=1
ReportIdentifier=33623620-
Response.type=4
Sig[0].Name=NameOfExe
Sig[0].Value=powershell.ex
Sig[1].Name=FileVersionOfS
Sig[1].Value=6.1.7600.1638
Sig[2].Name=InnermostExcep
Sig[2].Value=System.Invali
Sig[3].Name=OutermostExcep
Sig[3].Value=System.TypeIn
Sig[4].Name=DeepestPowerSh
Sig[4].Value=unknown
Sig[5].Name=DeepestFrame
Sig[5].Value=crosoft.Excha
Sig[6].Name=ThreadName
Sig[6].Value=unknown
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.76
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
FriendlyEventName=PowerShe
ConsentKey=PowerShell
AppName=powershell
AppPath=C:\Windows\System3
Is this a known bug? Is it fixed in a roll-up? Are there services I should restart? I’ve looked at other articles but nothing seems to fit. One spoke of ADWS not running (on the domain controllers) but it is; even still, restarting it hasn’t helped. This looks like a programming issue (invalid cast exception) under the covers.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
The EMC runs on top of powershell and powershell appears to be complaining about .net - I would re-install that before anything else
Pete
Pete
Did the windows update happen recently?
If you have .net 3.5 sp1 installed with KB2449742, remove it and check if the issue gets resolved.
If you have .net 3.5 sp1 installed with KB2449742, remove it and check if the issue gets resolved.
Thanks for your rapid replies!!
The administrative account has all the services listed in that article except Exchange Organization Administrators (which is not a group on my system). Also, there is no MachPanel service on my machine.
This SP1 install was very recent and maybe that led to the problem. I do not see KB2449742 on my system but perhaps, as you suggested, a reinstall of .net (or a reboot) may resolve it. I'll pursue that when time permits (obviously). Thanks again!
The administrative account has all the services listed in that article except Exchange Organization Administrators (which is not a group on my system). Also, there is no MachPanel service on my machine.
This SP1 install was very recent and maybe that led to the problem. I do not see KB2449742 on my system but perhaps, as you suggested, a reinstall of .net (or a reboot) may resolve it. I'll pursue that when time permits (obviously). Thanks again!
As I suspected, a recent unscheduled reboot (power issue) resolved the issue. I suspect the problem will return but it hasn't done this before so I think this needs to be closed. I appreciate your help!!
Running "Set-ExecutionPolicy" (Your choices here are Unrestricted, Restricted, RemoteSigned ect.) returned this error (Running at Elevated Premissions)
Set-ExecutionPolicy : Access to the registry key 'HKEY_LOCAL_MACHINE\SOFTWA
Using Regedit I manually change the Restricted to Unrestricted
Set-ExecutionPolicy : Access to the registry key 'HKEY_LOCAL_MACHINE\SOFTWA
Using Regedit I manually change the Restricted to Unrestricted
Hello !
I have a same problem with EMC Console.
Sorry, i don't understand the solution.
on PowerShell command , i type just" " Set-ExecutionPolicy"
and i type Restricted and type yes ?
or type Set-ExecutionPolicy UnRestricted ???
How to change manually the restricted to unrestricted ???
Thx you !
Best,
I have a same problem with EMC Console.
Sorry, i don't understand the solution.
on PowerShell command , i type just" " Set-ExecutionPolicy"
and i type Restricted and type yes ?
or type Set-ExecutionPolicy UnRestricted ???
How to change manually the restricted to unrestricted ???
Thx you !
Best,
Premium Content
You need an Expert Office subscription to comment.Start Free Trial