Issue/Introduction:
During SMSMSE 7.0 installation (fresh or upgrade from previous version), the product fails during the installation of SMSMSE Transport Agents.
Log "%TEMP%/ExeMonadE2k10_E2k15.log":
< 2013-08-30 12:37:20Z > Logging started
< 2013-08-30 12:37:20Z > In main of ExeMonadE2k10_E2k15
< 2013-08-30 12:37:20Z > ExeMonadE2k10_E2k15 : tracing set to off
< 2013-08-30 12:37:20Z > In ExecCmdLet
< 2013-08-30 12:37:20Z > Arguments are:
< 2013-08-30 12:37:20Z > Arg0 is : install-transportagent
< 2013-08-30 12:37:20Z > Arg1 is : -name
< 2013-08-30 12:37:20Z > Arg2 is : SMSMSERoutingAgent
< 2013-08-30 12:37:20Z > Arg3 is : -transportagentfactory
< 2013-08-30 12:37:20Z > Arg4 is : Symantec.MailSecurity.Server.TransportAgent.SMSMSERoutingAgentFactory
< 2013-08-30 12:37:20Z > Arg5 is : -assemblypath
< 2013-08-30 12:37:20Z > Arg6 is : 'D:\Program Files (x86)\Symantec\SMSMSE\7.0\Server\Symantec.MailSecurity.Server.TransportAgent.dll'
< 2013-08-30 12:37:20Z > In CreateRunSpace
< 2013-08-30 12:37:20Z > In GetLocalhostFqdn
< 2013-08-30 12:37:20Z > FQDN is:SERVER.local
< 2013-08-30 12:37:20Z > FQDN URL =
< 2013-08-30 12:37:20Z > ExeMonadE2k10_E2k15 : Creating Local Powershell Runspace Factory.
< 2013-08-30 12:37:21Z > ExeMonadE2k10_E2k15 : Creating Local Powershell Pipeline for command execution.
< 2013-08-30 12:37:21Z > ExeMonadE2k10_E2k15 : Creating New Remote PS-Session with Exchange 2010 Snapin.
< 2013-08-30 12:37:21Z > PowerShellCommand= New-PSSession
< 2013-08-30 12:37:21Z > Argumets are:NameConfigurationNameValueMicrosoft.Exchange.Management.PowerShell.E2010
< 2013-08-30 12:37:21Z > Argumets are:NameConnectionUriValuehttp://server.local/powershell?serializationLevel=Full
< 2013-08-30 12:37:21Z > Argumets are:NameAuthenticationValueKerberos
< 2013-08-30 12:37:21Z > Argumets are:NameSessionOptionValueSystem.Management.Automation.Remoting.PSSessionOption
< 2013-08-30 12:37:35Z > ExeMonadE2k10_E2k15 : Error: Creating Remote PS Session with Exchange SnapinFailed:
< 2013-08-30 12:37:35Z > ExeMonadE2k10_E2k15 : [server.local] Connecting to remote server failed with the following error message : The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see the about_Remote_Troubleshooting Help topic.
< 2013-08-30 12:37:35Z > ResultCount is zero or less
< 2013-08-30 12:37:35Z > Return Code:106
< 2013-08-30 12:37:35Z > Exiting ExecCmdLet
< 2013-08-30 12:37:35Z > End of Main
Resolution:
Testing procedure to confirm the cause:
Step 1 - Open the Windows Powershell
Step 2 - Run the command "New-PsSession"
If an error is returned (rather than notification that a new powershell session has been invoked) then this error is confirmed and the next several steps are likely resolution of the issue.
Step 3 - Run the command "Enable-PsRemoting"
Confirm that this is successful and follow any prompts that appear.
Step 4 - Re-Try the command "New-PsSession"
Confirm that a new powershell session is returned as being successfully created
Step 5 - Complete the manual uninstall to resolve the error 1722 if present (http://www.symantec.com/docs/TECH200443)
Step 6 - Run the installer again.
Applies To
Exchange 2010 (probably applicable with Exchange 2013)