tag:blogger.com,1999:blog-2228947945609574437.post5137644709052493307..comments2024-03-29T02:38:58.455-04:00Comments on Terence Luk: Attempting to run Test-ExchangeServerHealth.ps1 throws the error: "Mail flow test: WARNING: Connecting to remote server webmail.domain.com failed with the following error message..."Terence Lukhttp://www.blogger.com/profile/02612575579652280306noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-2228947945609574437.post-70043398298104870322021-03-19T08:18:54.577-04:002021-03-19T08:18:54.577-04:00Many thanks! It worked as described.Many thanks! It worked as described.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-66527937736810447292020-10-28T10:13:49.638-04:002020-10-28T10:13:49.638-04:00Another reason can be a wrong language.
The script...Another reason can be a wrong language.<br />The script expects the Value "Success", but if you are running the script on a German language Exchange server, you will receive the value "Erfolgreich".<br />If you look at the script around line 1202, you will find some "if" <br /> if ($testmailflowresult -eq "Erfolgreich" -or $testmailflowresult -eq $success)<br />Here it checks, if the testmailresult equals "Success" - in our case, we had to change it to "Erfolgreich" to get the magic done! :-)<br /><br />Greetz from germany<br />Bikerpete<br />https://linuxpeter.deBikerpetehttps://linuxpeter.denoreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-19439767970950860472019-03-09T03:17:03.729-05:002019-03-09T03:17:03.729-05:00Thanks! It's working fine.Thanks! It's working fine.Troubleshoutinghttps://www.blogger.com/profile/08877787826109919210noreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-32243095159872514862018-06-24T02:15:34.797-04:002018-06-24T02:15:34.797-04:00thanks so much for your solution , you've save...thanks so much for your solution , you've saved my day<br />thanks againAnonymoushttps://www.blogger.com/profile/04416266197583759711noreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-3340707536022131432018-05-09T05:57:59.999-04:002018-05-09T05:57:59.999-04:00I ended up installing exchange management tools on...I ended up installing exchange management tools on another server, then running the script from there. Both servers can then be accessed remotely without errors.<br /><br />The issue is caused by this line trying to open a remote session to itself<br />"$session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri $url -ErrorAction STOP"Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-89544090549303225142018-05-03T10:41:37.648-04:002018-05-03T10:41:37.648-04:00Thanks for this
We are now getting a different er...Thanks for this<br /><br />We are now getting a different error against the server the script runs from, for example:<br /> run script on server1, server 1 fails, server 2 passes<br /> run script on server2, server 2 fails, server 1 passes<br /><br />Mail flow test: WARNING: Connecting to remote server HOSTNAME failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.<br />WARNING: Cannot validate argument on parameter 'Session'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.<br />Remove-PSSession : Cannot validate argument on parameter 'Id'. The argument is null. Provide a valid value for the<br />argument, and then try running the command again.<br />At C:\scripts\healthcheck\Test-ExchangeServerHealth.ps1:452 char:22<br />+ Remove-PSSession $session.Id<br />+ ~~~~~~~~~~~<br /> + CategoryInfo : InvalidData: (:) [Remove-PSSession], ParameterBindingValidationException<br /> + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.RemovePSSessionCommand<br /><br />Fail<br />------ Finishing<br />Done.<br /><br />Almost like the server does not understand itself!<br />Do you have any idea how to resolve this?<br /><br />ThanksAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-52675436273212878852017-10-15T01:11:49.027-04:002017-10-15T01:11:49.027-04:00Thank you...Thank you...Anonymousnoreply@blogger.com