Microsoft.Exchange.Management.PowerShell.configuration.dll does not have required strong name
Exchange 2010 SP2 (14.2 Build 247.5)
Getting the following error trying to open almost any properties window in EMC or almost any command in EMS:
Processing data from remote server failed with the following error message: Cannot load Windows PowerShell snap-in Microsoft.Exchange.PowerSh
I cannot find anything online about a 'strong name', I found references to registry keys listed under:
HKLM\Software\Microsoft\Po
And I have compared the keys on this server to our other, working server and aside from the run time paths they are identical in wording and capitalization.
What is this strong name and how can i resolve this error?
Getting the following error trying to open almost any properties window in EMC or almost any command in EMS:
Processing data from remote server failed with the following error message: Cannot load Windows PowerShell snap-in Microsoft.Exchange.PowerSh
I cannot find anything online about a 'strong name', I found references to registry keys listed under:
HKLM\Software\Microsoft\Po
And I have compared the keys on this server to our other, working server and aside from the run time paths they are identical in wording and capitalization.
What is this strong name and how can i resolve this error?
I have seen this once, and it was because Strong Name validation was disabled on the management server. Here is the KB I have used in the past: http://support.microsoft.com/kb/979695
ASKER
I had found this same article.. balked at having to install an SDK just to get that single .exe but was hoping there was another resolution. Guess I will try it and report back.
Let us know if that fixes your issue. I am leaning that it will, although it is a pretty big inconvenience to download the whole SDK for a single file.
ASKER
Ok I installed the tools on my workstation, copied over sn.exe and ran those two commands. Currently sn -Vl returns :
Assembly/Strong Name Users
*,* All Users
I can only assume something like this needs a reboot, I will try to do so late tonight.
Assembly/Strong Name Users
*,* All Users
I can only assume something like this needs a reboot, I will try to do so late tonight.
I dont think you need to reboot. What happens if you try this again (not the Sn.exe portion, the Exchange management shell part)?
ASKER
It was still giving the same error.. I bounced the server tonight, no help. I can't open emc at all, neither emc nor ems works.
Please tell me you guys have another idea.. I've thought about trying sp3 but service packs scare ten rap out of me since the last two I ran resulted in dead servers.
Please tell me you guys have another idea.. I've thought about trying sp3 but service packs scare ten rap out of me since the last two I ran resulted in dead servers.
Is this happening on one server, or all of them? By default, the management tools should be installed on the Exchange servers themselves.
You could attempt to uninstall the Exchange Management Tools and reinstall them, that may resolve the issue.
You could attempt to uninstall the Exchange Management Tools and reinstall them, that may resolve the issue.
ASKER
Ok I got into emc via deleting the reg key listed here:http://www.exchangelog.info/2012/09/the-attempt-to-connect-to.html
But emc still gives the error
Cannot load windows powershell snapin Microsoft.exchange.managem
But emc still gives the error
Cannot load windows powershell snapin Microsoft.exchange.managem
What version of PowerShell are you running? PowerShell 2.0 or PowerShell 3.0?
You also only have WinRM 2.0 installed right, not the new version?
The reason I ask is because PowerShell 3.0 is not compatible with E14 (Exchange 2010), which is what you are running. WinRM 3.0 is also not compatible last time I checked.
Make sure you are not running WinRM3.0, and that WinRM2.0 is installed.
Also, try running this:
You also only have WinRM 2.0 installed right, not the new version?
The reason I ask is because PowerShell 3.0 is not compatible with E14 (Exchange 2010), which is what you are running. WinRM 3.0 is also not compatible last time I checked.
Make sure you are not running WinRM3.0, and that WinRM2.0 is installed.
Also, try running this:
Get-PSSnapin -RegisteredASKER
Ok results of that cmd are
E2010
Support
Setup
All ps version 1.0
E2010
Support
Setup
All ps version 1.0
ASKER
As far as the winrm versions.. I've only installed items that were detected as part of windows update.
Winrm I'd and quickconfig both give errors about the requested http url being not available.
Winrm I'd and quickconfig both give errors about the requested http url being not available.
detected as part of windows update.
This might be your issue. See here: http://blogs.technet.com/b/exchange/archive/2012/12/14/windows-management-framework-3-0-on-exchange-2007-and-exchange-2010.aspx
ASKER
Checked installed updates.. do not have either of those KB's listed (KB2506146 and KB2506143)
ASKER
So yeah.. Im still getting the same error in EMS. EMC however opens and allows me to view object properties and make changes.
ASKER
Oh and also.. this problem is stopping my Backup Exec job from even starting.
ASKER
Ok wait.. I was slightly wrong. the Strong Name is no longer part of the error I get in EMC. My bad on that. The error now is:
Processing data from remote server failed with the following error message: Cannot load windows powershell snap-in Microsoft.Exchange.Managem
Category Info : OpenError: (System.Manage....RemoteRu
FullyQualifiedErrorId: PSSessionOpenFailed
Processing data from remote server failed with the following error message: Cannot load windows powershell snap-in Microsoft.Exchange.Managem
Category Info : OpenError: (System.Manage....RemoteRu
FullyQualifiedErrorId: PSSessionOpenFailed
ASKER
No one?
Ill shoot you a response in a moment.
ASKER
Bump for a new week.
ASKER
No one else even bothered to attempt to help so I had to hire an outside consultant. I should'nt even post what the issue was but just so no one can say that I'm a jerk. The issue was a corrupt local user profile. I logon to my servers with the org admin account, that local profile was corrupted. If I logon with a diff account then run the emc/ems as my org admin account everything works correctly.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for ubadmin's comment #a39420352
for the following reason:
I had to hire a consultant to determine the cause. Only the one guru even bothered to try helping.. i wish I could give him points for trying to help.
Accepted answer: 0 points for ubadmin's comment #a39420352
for the following reason:
I had to hire a consultant to determine the cause. Only the one guru even bothered to try helping.. i wish I could give him points for trying to help.
Hello UBAdmin,
I am sorry I did not get back sooner. Honestly, I did not even know a corrupt local profile would cause this but then again, I have seen crazier things.
Sorry for the lack of response, but I do with you the best in the future.
-evrydayzawrkday
I am sorry I did not get back sooner. Honestly, I did not even know a corrupt local profile would cause this but then again, I have seen crazier things.
Sorry for the lack of response, but I do with you the best in the future.
-evrydayzawrkday
ASKER
Please do not close this question out. It seems the issue persists... locally I can open and use the Console, the shell however is still buggy. I cannot run commands such as get-mailboxdatabase or get-exchangeserver because they are not recognized as valid commands.
I cannot add pssnapins microcoft.exchange.managem
And microsoft...admin is not installed on this machine.
I cannot add pssnapins microcoft.exchange.managem
And microsoft...admin is not installed on this machine.
ASKER
I meant to click on Object.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No one else had any real input.
To do this, open a command prompt, type the following command, and then press Enter:
sn -Vr *
Note: To check your current settings for Strong Name verification, use the following command:
sn -Vl
Hope that this helps.