Exchange 2013 - Outlook no connection to server but OWA works

Hi,

i have a strange Problem with my Exchange 2013. The Exchnage runs with cu2 on a Server 2012 VMware machine. After the successfull Migration to Hyper-V i installed directly cu8 - there is no Information on the MS download site (https://www.microsoft.com/en-us/download/details.aspx?id=46373) that this is not possible. During the update there were only Problems with the connectors - example:

Error:
The following error was generated when "$error.Clear(); 
          $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
          foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };
        " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "EXCHANGE\Default Frontend EXCHANGE". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

We solved this with this solution: https://exchangeshare.wordpress.com/2014/07/14/exchange-2013-setup-error-a-receive-connector-must-have-a-unique-combination-of-a-local-ip-address-port-bindings-and-remote-ip-address-ranges/

We use two own connectors and there is no screenshot (or something else) how the connectors (also the Exchange own one) look like before the update.

Users can use OWA with no Problem and also a CRM System can use his receive connector on port 587. If i open the autodiscover.XML in a browser i get following:

<?xml version="1.0" encoding="utf-8" ?> 
- <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
- <Response>
- <Error Time="12:31:35.6706834" Id="3007185755">
  <ErrorCode>600</ErrorCode> 
  <Message>Invalid Request</Message> 
  <DebugData /> 
  </Error>
  </Response>
  </Autodiscover>

The creation of a Exchange Mailbox with the control Panel brings following:

The user Name and the mail address is filled in and the next step Shows that no Connection to the Exchange Server is available. The window that Shows up next Shows the Mailbox ID is available. There are no entries in the Exchange Server logs and the Microsoft Office Alert log on the Client Shows:

MAPI
The action cannot be completed.  The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
P1: 350569
P2: 6.3.9600.17415
P3:
P4: 

A DNS CNAME for the autodiscover exists, only the _autodiscover entry under _tcp is missing - before and after the update. A manuelly created one solved not the Problem.

Get-AutodiscoverVirtualDirectory Shows the Server but the InternalUrl is empty.

One hint is there maybe:

After a reboot of the Exchange Server we get this error:

"Event ID 15021, HTTPEvent "error occurred while using SSL configuration for endpoint 0.0.0.0:444" Exchange Server 2013"

and we solved it with: http://www.exchangedictionary.com/solutions/event-id-15021-error-occurred-while-using-ssl-configuration

The "old" Exchange Server under VMware is running without LAN but i was not able to see there any infromations - without LAN the System seems to be useless.

I hope that this are all informations and i have also screenshots - thanks to everyone who read this Topic and make some hints!

Kind regards

Bernd


May 27th, 2015 10:00am

Hi,

Does this issue occur on all users in your organization?

The returned error code 600 of opening the autodiscover.XML means the autodiscover service is working fine. So I suggest to recreate outlook profile to check this issue.

And please make sure all the required services are running in Exchange and try to ping server IP address from client side to check the connection.

Best Regards.

Free Windows Admin Tool Kit Click here and download it now
May 29th, 2015 4:48am

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

Other recent topics Other recent topics