After setup of Exchange2013 Exchange Management Shell fails

I am upgrading from Exchange2007 to Exchange 2013

Exchange 2007 is on Server2003, Rollup 15 SP3

 The name of the Exchange2007 server is hermes2, the name of the new Exchange2013 server is hermes3.
 The name of our AD is "forsyth"

After I finished the install on of Exchange2013 on a Server 2012R2 When I opened the Exchange Management Shell: I received the following error (this is part of the output from the shell window let me know if you need all of it),  it looks like it tried 3 times .

Any ideas?  Thank you!                                     
                                      ------------------------------------------------------------------------------------------
                                      VERBOSE: Connecting to hermes3.forsythpl.org.
                                      New-PSSession : [hermes3.forsythpl.org] Processing data from remote server hermes3.forsythpl.org failed with the
                                      following error message: [ClientAccessServer=HERMES3,BackEndServer=hermes3.forsythpl.org,RequestId=2d2dcfef-3753-4c3e-b
                                      207-3845ca5d6833,TimeStamp=2/23/20152:31:07 AM]
                                      [AuthZRequestId=45093630-4a0f-4c08-a5ff-4d6bf230c5b5][FailureCategory=AuthZ-SetupVersionInformationCorruptException]
                                      Unable to determine the installed file version from the registry key
                                      'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine'. For more information, see the
                                      about_Remote_Troubleshooting Help topic.
                                      At line:1 char:1
                                      + New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
                                      + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                          + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
                                         gTransportException
                                          + FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
                                      WARNING: No Exchange servers are available in the Active Directory site HP. Connecting to an Exchange server in another
                                       Active Directory site.

                                      Failed to connect to an Exchange server in the current site.
                                      Enter the server FQDN where you want to connect.:

February 22nd, 2015 11:18pm

Make sure all the Exchange Services are running fine. If it's not than restart it manually and check the issue.
Free Windows Admin Tool Kit Click here and download it now
February 23rd, 2015 2:16am

Also, when upgrading from Exchange 2007 to 2013, I would be referring you on this informative technet article that covers all the required aspects and helps to achieve the goal without any problem :http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx

Moreover, if the issue still persist, you may also consider on this automated solution (http://www.exchangemailboxmigration.com/) that provides a very hassle-free environment to get this job done in more secure way.

February 23rd, 2015 4:50am

Here is what I see in the Event Log I see numerous events that have the following in common:

Microsoft.Exchange.Diagnostics.SetupVersionInformationCorruptException: Unable to determine the installed file version from the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine'.

When I look at the registry "PowerShellEngine'" does not exist under PowerShell\1\ but I do see it under PowerShell\3\

Free Windows Admin Tool Kit Click here and download it now
February 23rd, 2015 11:13am

Do you have any other server? If yes, than make sure you have same entry as its on the working server.
Is this what you see?
February 24th, 2015 2:18am

Hi,

Moving these keys from other servers or creating all the 6 strings manually should solve this issue.

  1. Created the Key "PowerShellEngine" under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1.
  2. Created all 6 Strings under "PowerShellEngine"
  • ApplicationBase    (C:\Windows\System32\WindowsPowerShell\v1.0)
  • ConsoleHostAssemblyName    (Microsoft.PowerShell.ConsoleHost, Version=1.0.0.0, Culture=neutral,PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=msil)
  • ConsoleHostModuleName    (C:\Windows\System32\WindowsPowerShell\v1.\Microsoft.PowerShell.ConsoleHost.dll)
  • PowerShellVersion    (2.0)
  • PSCompatibleVersion    (1.0, 2.0)
  • RuntimeVersion    (v2.0.50727)

Best Regards.


  • Edited by Lynn-Li 3 hours 52 minutes ago
Free Windows Admin Tool Kit Click here and download it now
February 24th, 2015 3:01am

Hi,

Moving these keys from other servers or creating all the 6 strings manually should solve this issue.

  1. Created the Key "PowerShellEngine" under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1.
  2. Created all 6 Strings under "PowerShellEngine"
  • ApplicationBase    (C:\Windows\System32\WindowsPowerShell\v1.0)
  • ConsoleHostAssemblyName    (Microsoft.PowerShell.ConsoleHost, Version=1.0.0.0, Culture=neutral,PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=msil)
  • ConsoleHostModuleName    (C:\Windows\System32\WindowsPowerShell\v1.\Microsoft.PowerShell.ConsoleHost.dll)
  • PowerShellVersion    (2.0)
  • PSCompatibleVersion    (1.0, 2.0)
  • RuntimeVersion    (v2.0.50727)

Best Regards.


February 24th, 2015 7:58am

Thank you for your help this fixed the issue!

now onto step 7 of the install

Free Windows Admin Tool Kit Click here and download it now
March 4th, 2015 5:12pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics