"Case sharing" Exchange 2013EMS command failed to load

Environment: Dc+exchange 2013 (front and back in all)
Fault:

Using the EMS input command prompt error

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M01/6E/5A/wKiom1V5j3bj05ykAAGmHZPiAOY282.jpg "height=" 171 "/>

Using Exchange tools to open also prompt for errors cannot load cmdlet commands

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M02/6E/5A/wKiom1V5j3ugBdAeAACAEHNNysc839.jpg "height="/>

Exclusion Method:
1. The absence of a PowerShell script for Exchange with the installation path causes the command to fail to load.
Solution: ISO Copy PowerShell script from Exchange 2013 in the past installation path \ bin file, the fault is still as usual

2. is not a bug caused.
Solution: Query The current version number of Exchange 2013, for CU6, look at the latest CU7 updates, there is no explanation.

3. Look over the wall for a foreign KB (many of Microsoft's products actually share few case in the country)
Solution: Find a blog that also happens in Exchange 2010, with PowerShell input from the administrator on the server
Add-pssnapin *exchange*-erroraction silentlycontinue, restart the server, the EMS command input is normal.

This article from "Gs_hao" blog, declined reprint!

"Case sharing" Exchange 2013EMS command failed to load