Exchange Console and Shell Not Working

ejefferson213
ejefferson213 used Ask the Experts™
on
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.Configuration.Tasks.Task' threw an exception."
    + 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=129500350497950880
ReportType=1
Consent=1
ReportIdentifier=33623620-7fd5-11e0-9bed-000c29316fd9
Response.type=4
Sig[0].Name=NameOfExe
Sig[0].Value=powershell.exe
Sig[1].Name=FileVersionOfSystemManagementAutomation
Sig[1].Value=6.1.7600.16385
Sig[2].Name=InnermostExceptionType
Sig[2].Value=System.InvalidCastException
Sig[3].Name=OutermostExceptionType
Sig[3].Value=System.TypeInitializationException
Sig[4].Name=DeepestPowerShellFrame
Sig[4].Value=unknown
Sig[5].Name=DeepestFrame
Sig[5].Value=crosoft.Exchange.Configuration.Tasks.Task.Finalize
Sig[6].Name=ThreadName
Sig[6].Value=unknown
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7600.2.0.0.274.10
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
FriendlyEventName=PowerShell
ConsentKey=PowerShell
AppName=powershell
AppPath=C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

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.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Technical Consultant
Commented:
The EMC runs on top of powershell and powershell appears to be complaining about .net - I would re-install that before anything else

Pete
ckeshavSr. Infrastructure Specialist
Commented:
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.
Pete LongTechnical Consultant

Commented:
Also have you read this
Success in ‘20 With a Profitable Pricing Strategy

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!

Author

Commented:
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!

Author

Commented:
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\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell' is denied.
 
Using Regedit I manually change the Restricted to Unrestricted
Hi Guys,
Just wanted to say that Set-ExecutionPolicy Restricted in powershell as resolved my issue.

Commented:
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,

Commented:
OK, i unterstand :-)

After reading the help on command about_signing, i execute "set Execution Policy Remotesigned" and resolve me this issue .

thx you !

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial