Windows updates came out on Tuesday. Reviewed them, approved them, installed all of them successfully -- notably (to me) KB2787763, Update Rollup 8 for Exchange Server 2010 SP1.
And now I find that mail sent outside the organization bounces with the error: "[ISP's mail server] #550 relaying mail to[recipient domain] is not allowed ##"
When I open the SBS 2011 Standard Console, "Smart Host for Internet e-mail" has a status of "Not Configured." It was originally configured to use the ISP's SMTP server a year ago when it was installed. Attempting to reconfigure it using the SBS console wizard results in a window where all the options (server, username and password) are grayed out and it fails with the message "The Configure Internet E-Mail wizard cannot continue."
There's a log file, CIMW.log:
---------------------------------------------------------
[9936] 121214.015540.6182: General: Initializing...C:\Program Files\Windows Small Business Server\Bin\CIMW.exe
[8084] 121214.015540.8994: Messaging: Begin Microsoft.WindowsServerSolutions.Messaging.Management.MessagingTasks.Initialize
[8084] 121214.015540.9150: Messaging: Begin Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.Initialize
[8084] 121214.015541.0713: Messaging: Openning remote runspace failed due to the error: Connecting to remote server [redacted] failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.. Retry...
[9936] 121214.015542.3994: WizardChainEngine Next Clicked: Going to page {0}.: Messaging.ConfigureInternetMail.OutboundConnector
[8084] 121214.015551.0713: Messaging: Openning remote runspace failed due to the error: Connecting to remote server [redacted] failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.. Retry...
[8084] 121214.015601.0869: Messaging: MessagingTaskException: Unexpected failure creating runspace -- Error# (800001)
[8084] 121214.015601.0869: Messaging: Inner exception: Connecting to remote server[redacted] failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.
[8084] 121214.015601.0869: Messaging: Stack Trace:
[8084] 121214.015601.0869: Messaging: at System.Management.Automation.Runspaces.Internal.RunspacePoolInternal.EndOpen(IAsyncResult asyncResult)
at System.Management.Automation.RemoteRunspace.Open()
at Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.Initialize()
[9400] 121214.015601.1025: Messaging: Microsoft.WindowsServerSolutions.Messaging.Management.MessagingTaskException: Unexpected failure creating runspace ---> System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server[redacted] failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.
at System.Management.Automation.Runspaces.Internal.RunspacePoolInternal.EndOpen(IAsyncResult asyncResult)
at System.Management.Automation.RemoteRunspace.Open()
at Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.Initialize()
--- End of inner exception stack trace ---Server stack trace:
at Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.Initialize()
at Microsoft.WindowsServerSolutions.Messaging.Management.MessagingTasks.Initialize(Boolean InitializeWebServices, ProgressChangedHandler progressHandler)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
at Microsoft.WindowsServerSolutions.Messaging.Management.MessagingTasks.DelegateInitializeMethod.EndInvoke(IAsyncResult result)
at Microsoft.WindowsServerSolutions.Messaging.Wizards.InternetMailWizard.OutboundConnectorPagePresenter.m_backgroundWorker_DoWork(Object sender, DoWorkEventArgs e)
[9936] 121214.015604.1650: Messaging: Begin Smart Host name validation
[9936] 121214.015604.1650: Messaging: Smart Host name has no value and empty.
[9936] 121214.015604.1807: Messaging: End Smart Host name validation
[9936] 121214.015606.9932: Wizard: User opted to cancel the wizard.
Running the "Fix my network" wizard finds an un-repairable error: "An error occurred while trying to connect to Exchange Management Shell."
Details of that error are: "Connecting to remote server [name] failed with the following error message: Access is denied. For more information, see the about_Remote_Troubleshooting Help topic."
When I look at the Exchange Management Console, in Organization Configuration > Hub Transport > Send Connectors > Windows SBS Internet Send [name], it shows the Smart Host in the Network tab with what looks to be proper configuration... but it clearly isn't using it.
This was worse earlier this evening, if you can believe it... WinRM was failing outright and the Exchange Management Console wouldn't even start; that looks like it was a PowerShell authentication issue in IIS. For some reason, all authentication types in IIS Manager > [Server] > Sites > Default Web Site > PowerShell were set asDisabled. (Current setting is now Windows Authentication.)
And for the final kick in the teeth... I have three other clients with Small Business Servers (both 2008 and 2011 versions) and they're all doing this!
Any insight would be greatly appreciated.
And thank you to Mohitkapoor for the links; that was indeed the cause, and uninstalling that update (KB2506143 on 2011, KB2506146 on 2008) was the solution. I did have to open the SBS Console and reconfigure the Smart Host, but now it works, reports success and external email is once again flowing. It makes me worry what else that update may have broken...
And I should probably bookmark the SBS Diva blog, by the looks of it.