Troubleshooting free/busy issues in Exchange hybrid environment

What does this guide do?

Describes how to troubleshoot free/busy issues that may occur in a hybrid deployment of an on-premises Microsoft Exchange Server and Microsoft Exchange Online in Office 365

Who is it for?

Tenant administrators. Elevated access will be required for many of the steps.

How does it work?

We’ll begin by asking you the issue you are facing. Then we’ll take you through a series of troubleshooting steps that are specific to your situation.

Estimated time of completion:

30-60 minutes.

Welcome to the hybrid environment free/busy troubleshooter

Select the option that best describes the issue that you are facing:

Note: If you want to review how free/busy works in a hybrid deployment, click the "I want to better understand how Hybrid Free/Busy is supposed to work" option.

Welcome to the hybrid environment free/busy troubleshooter

Select the option that best describes the issue that you are facing:

Note: If you want to review how free/busy works in a hybrid deployment, click the "I want to better understand how Hybrid Free/Busy is supposed to work" option.

On-premises Exchange server version in your environment

To better understand how Hybrid Free/Busy is supposed to work, review the following flowcharts. Select the version of the on-premises Exchange server that matches your environment:

The Exchange 2010/2013 free/busy workflow

The following diagram shows the Exchange 2010/2013 free/busy workflow:

P3_ExchangeWorkFlow
 


Did this solve your issue?

The Exchange 2007 free/busy workflow

The following diagram shows the Exchange 2007 free/busy workflow:

P4_ExchangeWorkFlow
 


Did this solve your issue?

Exchange 2003 free/busy workflow

The following diagram shows the Exchange 2003 free/busy workflow:

P5_ExchangeWorkFlow
 


Did this solve your issue?

Does Free/busy work on-premises?

Log on to an on-premises user's mailbox and then try to view the Free/Busy for another on-premises user. This test is to verify that you do not have any issues with availability information retrieval within your on-premises environment.


Were you able to see the Free/busy information?

You have an on-premises free/busy issue

This troubleshooter is used to diagnose free/busy issues in a hybrid environment. This does not seem to be your immediate issue. After the on-premises free/busy issues are addressed, restart this troubleshooter.

For information about how to troubleshoot some common on-premises free/busy issues, see Troubleshooting Free/Busy Information for Outlook 2007.

Cloud user cannot see free/busy for on-premises user

To determine what error message you are receiving from OWA, follow these steps:

  1. Use the account of the affected cloud user to log on to the Portal at http://portal.MicrosoftOnline.com
  2. Click Outlook at the top of the page. The Outlook Web App opens.
  3. Create a new meeting request, and then add the on-premises user to the meeting.
  4. When the Hash marks are returned, rest the pointer over them to display the error message. Note the error message error code number.

P8_FreeBusyStutas
 


Select the appropriate error code in the following list to narrow the troubleshooting steps that you must follow:

Cloud user cannot see On-premises user’s Free/Busy

Use the following methods to verify that Autodiscover can be resolved from an external source and that the Firewall is open.

Method one: Verify that Autodiscover is resolving to the on-premises Exchange CAS server

  1. From an external computer, open Command Prompt and type the following commands and press ENTER after each command:
    • NSLookup
    • autodiscover.<Your_Domain.com>
  2. In the response to the command, the "Address"value should be the external IP of the on-premises Exchange CAS server. For example: Name: autodiscover.contoso.com Address: 38.96.29.10

Method two: Verify that you can send an Autodiscover POST request to potential Autodiscover URLs

  1. Go to https://www.testexchangeconnectivity.com
  2. On Microsoft Office Outlook Connectivity Tests select Outlook Autodiscover, and then click Next.
  3. Complete the Outlook Autodiscover form (Email address, User Name and password), then click Perform Test.

If the Exchange connectivity tests fail for autodiscover, check the on-premises Autodiscover Internet Access configuration. For more information about how to do this, see the Microsoft TechNet topic Configure the Autodiscover Service for Internet Access.


Did this solve your issue?

Cloud user cannot see On-premises user’s Free/Busy

Verify that the autodiscover endpoint is pointing to the on-premises Exchange Hybrid Server(s).

Check the IIS logs on the Exchange Hybrid server to verify that the Autodiscover POST request is being received by this server:

  1. On the Exchange Hybrid Server, click Start, click Run, type %SystemDrive%\inetpub\logs\LogFiles, and then press ENTER.
  2. Open the W3SVC1 folder, then open the most recent IIS log file
  3. Search for "Autodiscover"
  4. The following screen shot shows an example of the Autodiscover POST request on IIS log: 

P10_error5039
 


If you do not see any entry for Autodiscover in your on-premises Exchange hybrid deployment server, the firewall may be pointing to a wrong CAS server.


Did this solve your issue?

Cloud user cannot see On-premises user’s Free/Busy

Is the domain name present in the org relationship?

To verify the domain name value in the Organization Relationship, follow these steps:

  1. Connect to Exchange Online by using Windows PowerShell. For more information about how to do this, see Connect to Exchange Online using remote PowerShell.
  2. In Windows PowerShell , run the following command: Get-OrganizationRelationship -Identity "Exchange Online to On Premises Organization Relationship" | FL
  3. Check DomainName value. The vanity domain (yourdomain.com) should be present.
  4. If the DomainName value is missing your vanity domain, run the following command: Set-OrganizationRelationship -Identity "Exchange Online to On Premises Organization Relationship" –DomainName yourdomain.com

Did this solve your issue?

Cloud user cannot see On-premises user’s Free/Busy

Is IIS handler Mapping missing?

Determine whether Internet Information Services (IIS) configuration is missing the svc-Integrated handler mapping for the Autodiscover endpoint.

  1. On the on-premises Exchange 2010 hybrid deployment server, open Internet Information Services (IIS) Manager
  2. Expand ServerName -- > Site -- > Default Web Site, and then click Autodiscover
  3. On IIS section, open Handler Mappings. The following screen shot shows an example of the svc-Integrated handler mapping in IIS:
    P12_HandlerMapping
     

If the IIS is missing the svc-Integrated handler mapping, see the topic "Exception has been thrown by the target" error in a hybrid deployment of Office 365 and your on-premises environment.


Did this solve your issue?

Cloud user cannot see On-premises user’s Free/Busy

Follow these steps to verify if EWS has External URL set:

  1. On the on-premises Exchange hybrid deployment server, open Exchange Management Shell, and then run the following cmdlet: Get-WebServicesVirtualDirectory | FL Name,Server,externalURL
  2. If the ExternalURL is missing on the Exchange hybrid deployment server, run the following cmdlet: Set-WebServicesVirtualDirectory -Identity "ServerName\EWS (Default Web Site)" -ExternalUrl https://mail.contoso.com/ews/exchange.asmx

Did this solve your issue?

Cloud user cannot see On-premises user’s Free/Busy

Verify that the Microsoft Exchange Web Services (EWS) are resolvable and there are no firewall issues.

Check IIS logs on the Exchange 2010/2013 CAS server(s) to confirm that Web Services request is being received by this server. To do this, follow these steps:

  1. On the Exchange 2010/2013 CAS server, click Start, click Run, type %SystemDrive%\inetpub\logs\LogFiles, and then press ENTER.
  2. Open the W3SVC1 folder, and then open the latest IIS log file.
  3. In the latest IIS log file, search for "exchange.asmx/wssecurity”. The following screen shot shows an example of the request in the IIS log:
    P15_error5016
     
  4. If you do not see any entry for "exchange.asmx/wssecurity"in your on-premises Exchange 2010/2013 hybrid deployment server, the firewall may be pointing to a wrong CAS server, or you may have pre-authentication configured on the firewall. For information about how to bypass firewall pre-authentication, see How to Configure TMG for Office 365 (Exchange) Hybrid deployments.

Did this solve your issue?

Cloud user cannot see On-premises user’s Free/Busy

Is IIS handler mapping missing on EWS?

Determine whether Internet Information Services (IIS) configuration is missing the svc-Integrated handler mapping for the EWS endpoint

  1. On the on-premises Exchange hybrid deployment server, open Internet Information Services (IIS) Manager.
  2. Expand ServerName -- > Site -- > Default Web Site, and then click EWS.
  3. In the IIS area, open Handler Mappings. The following screen shot shows an example of the svc-Integrated handler mapping in IIS:
    P17_HandlerMapping
     
  4. If the IIS is missing the svc-Integrated handler mapping, see the support article "Exception has been thrown by the target" error in a hybrid deployment of Office 365 and your on-premises environment.

Did this solve your issue?

Cloud user cannot see On-premises user’s Free/Busy

Is WSSecurity enabled as an authentication method?

On the on-premises Exchange hybrid deployment server, run the following command in Exchange Management Shell: Get-WebServicesVirtualDirectory | fl name,server,externalURL,ExternalAuthenticationMethods

If the WSSecurity is missing for ExternalAuthenticationMethods is missing on Exchange hybrid deployment server run the following command: Set-WebServicesVirtualDirectory -Identity "ServerName\EWS (Default Web Site)" –WSSecurityAuthentication $true


Did this solve your issue?

Cloud user cannot see On-premises user’s Free/Busy

Verify Org Relationship settings are configured correctly to enable Free/busy for the users.

For Online Settings

  1. Connect to Exchange Online by using Windows PowerShell. For more information about how to do this, see Connect to Exchange Online using remote PowerShell.
  2. In Windows PowerShell, run the following command: Get-OrganizationRelationship -Identity "Exchange Online to On Premises Organization Relationship" | FL

The output should resemble the following:

  • TargetApplicatioURI: FYDIBOHF25SPDLT.Contoso.com
  • TargetAutodiscoverURI: https://autodiscover.contoso.com/autodiscover/autodiscover.svc/wssecurity
  • DomainNames: {Contoso.com}
  • FreeBusyAccessEnabled : True
  • FreeBusyAccessLevel: LimitedDetails

If a value must be changed, use the "set-OrganizationRelationship"cmdlet to fix the property. For more information about syntax and options, see Set-OrganizationRelationship.

For On-Premises settings

  1. On the Exchange 2010/2013 CAS, run the following command in the Exchange Management Shell: Get-OrganizationReationship -Identity "On Premises to Exchange Online Organization Relationship”

The output should resemble the following:

  • TargetApplicatioURI: outlook.com
  • TargetAutodiscoverURI: https://podxxx.outlook.com/autodiscover/autodiscover.svc/wssecurity
  • DomainNames: {xxxx.mail.onmicrosoft.com,contoso.com}
  • FreeBusyAccessEnabled : True
  • FreeBusyAccessLevel : LimitedDetails

If a value must be changed, use the "set-OrganizationRelationship"cmdlet to fix the property. For more information about syntax and options, see Set-OrganizationRelationship.


Did this solve your issue?

On-Premises user cannot see cloud user's Free/busy

On which version of Exchange is the on-premises users' mailbox located?

Your Exchange 2003 user cannot see cloud user's free/busy

Can you reproduce the issue by using an on-premises Exchange 2010 mailbox?

  1. Log on to Outlook or an OWA client as a user who has an Exchange 2010 on-premises mailbox.
  2. Create a new meeting request and add a cloud user to the meeting request.
  3. When you view the scheduling assistant do you see hash marks for the cloud user?
Your Exchange 2003 user cannot see cloud user's free/busy

Verify that there is no hard-coded Public folder routing that would prevent the legacy Free/busy request from succeeding.

Note: This is not a common issue.

Verify that the ms-Exch-Folder-Affinity-List attribute on the Exchange Server 2003 properties has Exchange 2010 ObjectGUID with the lowest cost (The format of this property is as follows: {guid of server},cost).

  1. On a Domain Controller click Start, click Run, type adsiedit.msc, and then click OK.
  2. Right-click ADSI Edit, and then click Connect to.
  3. On Select a well known Naming Context, select Configuration, and then click OK.
  4. Expand Configuration -- > Services -- > Microsoft Exchange -- > First Organization -- > Exchange Administrative Group (FYDIBOHF23SPDLT)-- > Servers.
  5. Right-click Exchange 2010 server, and then click Properties.
  6. Copy the objectGUID value and then paste it in a notepad text file.
  7. Move to Configuration -- > Services -- > Microsoft Exchange -- > First Organization -- > First Administrative Group -- > Servers.
  8. Right-click Exchange Server 2003, and then select Properties.
  9. Verify that ms-Exch-Folder-Affinity-List value is set with Exchange 2010 objectGUID. If the Exchange 2010 objectGUID is not listed on ms-Exch-Folder-Affinity-List, you can add it by using the format: {guid of server},cost.

Did this solve your issue?

Your Exchange 2003 user cannot see cloud user's free/busy

Is the External Free/busy present and replicated correctly?

Add the OU=EXTERNAL (FYDIBOHF25SPDLT) public folder. To do this, follow these steps:

  1. Connect to the on-premises Exchange 2010 SP1 or later public folder server.
  2. Open Windows PowerShell.
  3. Run the following cmdlet: Add-PsSnapin Microsoft.Exchange.Management.Powershell.Setup
  4. Run the following cmdlet: Install-FreeBusyFolder

Note: The OU=EXTERNAL (FYDIBOHF25SPDLT) public folder should only be present on Exchange 2010 servers and NOT replicated to Exchange 2003 or Exchange 2007.


Did this solve your issue?

Your Exchange 2003 user cannot see cloud user's free/busy

Verify that the recipient object on the on-premises server has the correct LegacyExchangeDN configured.

  1. Every cloud mailbox will have a corresponding on-premises Mail enabled object. For this kind of Free/busy query we use the LegacyExchangeDN to route our request to the Proper Public folder server. To make sure that this value is accurate, follow these steps:
  2. On the Exchange 2010 server, run the following command in the Exchange Management Shell: Get-RemoteMailbox Username |fl LegacyExchangeDN where username is the name of the cloud user that you are trying to see free/busy information for.
  3. In the results, verify that the External (FYDIBOHF25SPDLT) is in the path. For example, the results should show the path as follows: 
    P24_CannotSeeBusyFree
     

Did this solve your issue?

Your Exchange 2003 user cannot see cloud user's free/busy

Verify Permissions on Public folder.

To use the Exchange 2010 Public Folder Management Console to change the client permissions for the External (FYDIBOHF25SPDLT) free/busy replica, follow these steps:

  1. Start the Exchange 2010 Exchange Management Console.
  2. In the console tree, click Toolbox.
  3. In the result pane, click Public Folder Management Console, and then in the action pane, click Open Tool. The Public Folder Management Console appears.
  4. In the Public Folder Management Console, in the action pane, click Connect to Server.
  5. In Connect to server, click Browse to view a list of the available Mailbox servers that contain a public folder database.
  6. In Select Public Folder Servers, select the Exchange 2010 server. Click OK, and then click OK.
  7. In the Public Folder tree, move to System Public Folder -- > SCHEDULE+ FREE/BUSY
  8. In the Result pane, right-click EX:/O=FIRST ORGANIZATION/OU=EXTERNAL (FYDIBOHF25SPDLT), and then click Properties.
  9. On the Permissions tab, confirm that Edit all permission level is selected for the Default user
    P25_CannotSeeBusyFree
     

Did this solve your issue?

Your Exchange 2003 user cannot see cloud user's free/busy

Is the arbitration mailbox missing or corrupted?

The Arbitration mailbox can be edited by using ADSIEdit. The federated.email account should be located in the default users container of Active Directory for the Exchange 2010 domain.

Use one of the following options:

  1. Use adsiedit.
    1. Connect to the default naming context in Active Directory.
    2. Browse to the Users container and view the properties of the federatedemail account.
    3. Change the proxyaddress attributes of the account to either have ONE of the SMTP addresses already federated, or add the already existing proxy address namespace present into the federation trust.
  2. From the Exchange Server 2003 open "Active Directory Users and Computers."
    1. Move to the Users container and right-click the FederatedEmail account - then click Properties.
    2. If you go to the email addresses tab that you can add another proxy address to match the federation namespaces already configured, or add the pre-existing primary SMTP namespace to the federation trust.

Did this solve your issue?

Your Exchange 2007 user cannot access cloud user's free/busy

Can you repro with an on-premises Exchange 2010 or 2013 mailbox?

  1. Log on to your Outlook or OWA client as a user who has an Exchange 2010 or 2013 on-premises mailbox.
  2. Create a new meeting request and add a cloud user to the meeting request.
  3. When you view the scheduling assistant do you see hash marks for the cloud user?
Your Exchange 2007 user cannot access cloud user's free/busy

Check the availability address space to make sure that it has the correct settings. This might be a misconfiguration of the AvailabilityAddressSpace. Check that ProxyURL value on AvailabilityAddressSpace configuration match the InternalURL of the Exchange 2010/2013 CAS Web Service virtual directory. To do this, follow these steps:

  1. On the on-premises server, run the following commands in Exchange Management Shell:
    Get-AvailabilityAddressSpace | FL ProxyUrl
    Get-WebServicesVirtualDirectory | FL Server,InternalUrl
  2. If the ProxyURL and InternalURL values do not match, run the following commands:
    Remove-AvailabilityAddressSpace -Identity ‘contoso.mail.onmicrosoft.com'
    Add-AvailabilityAddressSpace -ForestName contoso.mail.onmicrosoft.com' -AccessMethod 'InternalProxy' -UseServiceAccount
    'True' -ProxyUrl https://cas2010.contoso.com/ews/exchange.asmx
  3. If the ProxyURL and InternalURL values do match, make sure that you can access the URL from the Exchange 2007 CAS server. To do this, move to ProxyURL of the AvailabilityAddressSpace from CAS 2007. Authenticate with the Exchange 2007 source mailbox credential. The expected result is as follows: 
    P28_CannotAccessBusyFree
     

Note: The InternalURL of the Exchange 2010/2013 CAS Web Service virtual directory should differ from Exchange 2007 CAS Web Service virtual directory.


Did this solve your issue?

Exchange 2010/2013 user cannot see cloud user's free/busy

Log on to an on-premises user's mailbox and then try to view the Free/Busy for another on-premises user. This test is to verify that you do not have any issues with availability information retrieval within your on-premises environment. 


Were you able to see the Free/busy information?

On-premises user cannot see cloud user's Free/busy

Determine what error message you are receiving from OWA.

  1. Use the affected user's account to log on to the on-premises OWA.
  2. Create a new meeting request, and then add the on-premises user to the meeting.
  3. When the Hash marks are returned rest the pointer over them to display the error message. Note the error code number in the error message.
    P30_OnPremisesCannotSeeBusyFree
     

Select the appropriate error message in the following list to help narrow the troubleshooting steps that you must follow:

Exchange 2010/2013 user cannot see cloud user's free/busy

If you must have web proxy settings in your environment, verify that the on-premises Exchange 2010 and Exchange 2013 servers are set to use it.

On the on-premises Exchange 2010 and Exchange 2013 server(s) run the following command in the Exchange Management Shell: "Get-ExchangeServer | fl InternetWebProxy."

In most environments the results will be blank. However, if you have an outgoing proxy in your on-premises environment you may have to configure the correct proxy settings.

To resolve this issue, run the following command, where the address and port number http://192.168.5.56:8080 is replaced with your server address and port number:

Set-ExchangeServer -InternetWebProxy http://192.168.5.56:8080


Did this solve your issue?

Exchange 2010/2013 user cannot see cloud user's free/busy

Verify Org Relationship settings are configured correctly to allow for Free/busy for the users.

For Online Settings

  1. Connect to Exchange Online by using Windows PowerShell. For more information about how to do this, see Connect to Exchange Online using remote PowerShell.
  2. In Windows PowerShell, run the following command: Get-OrganizationRelationship -Identity "Exchange Online to On Premises Organization Relationship" | FL

The output should resemble the following:

  • TargetApplicatioURI: FYDIBOHF25SPDLT.Contoso.com
  • TargetAutodiscoverURI: https://autodiscover.contoso.com/autodiscover/autodiscover.svc/wssecurity
  • DomainNames: {Contoso.com}
  • FreeBusyAccessEnabled : True
  • FreeBusyAccessLevel: LimitedDetails

If a value must be changed, use the "set-OrganizationRelationship"cmdlet to fix the property. For more information about the syntax and options to do this, see Set-OrganizationRelationship.

For On-Premises settings

From the Exchange 2010/2013 CAS, run the following command in the Exchange Management Shell:

Get-OrganizationReationship -Identity "On Premises to Exchange Online Organization Relationship”

The output should resemble the following:

  • TargetApplicatioURI: outlook.com
  • TargetAutodiscoverURI: https://podxxx.outlook.com/autodiscover/autodiscover.svc/wssecurity
  • DomainNames: {xxxx.mail.onmicrosoft.com,contoso.com}
  • FreeBusyAccessEnabled : True
  • FreeBusyAccessLevel : LimitedDetails

If a value must be changed, use the "set-OrganizationRelationship"cmdlet to fix the property, For more information about the syntax and options to do this, see Set-OrganizationRelationship.


Did this solve your issue?

Exchange 2010/2013 user cannot see cloud user's free/busy

Make sure that the time set on your server is not inaccurate by more than 5 minutes. If the server time is more than 5 minutes difference from real time, the communications with the federation gateway become invalid. This causes free/busy to fail.

For information about how to fix server time issues, see How to configure an authoritative time server in Windows Server.


Did this solve your issue?

Exchange 2010/2013 user cannot see cloud user's free/busy

Determine whether the correct target address is specified on the MEU on-premises. Every Cloud Mailbox will have a corresponding on-premises object. This object must have the correct remote routing address (also known as the target address) specified. The remote routing address should contain a domain name similar to TenantName.Mail.OnMicrosoft.com.

To verify that the remote routing address is set, follow these steps:

  1. On the Exchange 2010 server or Exchange 2013 server, run the following command in the Exchange Management Shell: Get-RemoteMailbox Username |fl RemoteRoutingAddress, where username is the name of the cloud user that you are trying to see free/busy information for.
  2. Verify that the address contains TenantName.Mail.OnMicrosoft.com
    P34_CannotSeeBusyFree
     

Note: If you did not use the Hybrid configuration wizard, the domain name should reflect the remote routing domain that you have selected.


Did this solve your issue?

Exchange 2010/2013 user cannot see cloud user's free/busy

Verify that the Org Relationship settings are configured correctly to enable Free/busy for the users.

For Online Settings

Connect to Exchange Online by using Windows PowerShell. For more information about how to do this, see Connect Windows PowerShell to the Service.

In Windows PowerShell, run the following command: Get-OrganizationRelationship -Identity "Exchange Online to On Premises Organization Relationship" | FL

The output should resemble the following:

  • TargetApplicatioURI: FYDIBOHF25SPDLT.Contoso.com
  • TargetAutodiscoverURI: https://autodiscover.contoso.com/autodiscover/autodiscover.svc/wssecurity
  • DomainNames: {Contoso.com}
  • FreeBusyAccessEnabled : True
  • FreeBusyAccessLevel: LimitedDetails

If a value must be changed, use the "set-OrganizationRelationship"cmdlet to fix the property. For more information about syntax and options to do this, see Set-OrganizationRelationship.

For On-Premises settings

From the Exchange 2010/2013 CAS, run the following command in Exchange Management Shell: Get-OrganizationReationship -Identity "On Premises to Exchange Online Organization Relationship”

The output should resemble the following:

  • TargetApplicatioURI: outlook.com
  • TargetAutodiscoverURI: https://podxxx.outlook.com/autodiscover/autodiscover.svc/wssecurity
  • DomainNames: {xxxx.mail.onmicrosoft.com,contoso.com}
  • FreeBusyAccessEnabled : True
  • FreeBusyAccessLevel : LimitedDetails

If a value must be changed, use the "set-OrganizationRelationship"cmdlet to fix the property. For more information about syntax and options to do this, see Set-OrganizationRelationship.


Did this solve your issue?

Exchange 2010/2013 user cannot see cloud user's free/busy

Verify that a token can be created that has test-federation trust.

From the on-premises environment, verify that you can retrieve a delegation token that will be used for Free/busy authorization. To do this, follow these steps:

  1. Open the Exchange Management Shell from the on-premises Exchange 2010 or 2013 server.
  2. Run the following command: Test-FederationTrust –UserIdentity User@company.com –verbose where User is the on-premises user who has issues viewing the cloud user's free/busy information.
  3. The output should show success for every test. If there is a failure, use the Hybrid Configuration Wizard again to try to reset the federation trust.
    P36_CannotSeeBusyFree
     

Did this solve your issue?

Exchange 2010/2013 user cannot see cloud user's free/busy

If the server time is more than 5 minutes difference from real time, communications with the federation gateway become invalid. This causes you free/busy to fail.

For information about how to fix server time issues, see How to configure an authoritative time server in Windows Server.


Did this solve your issue?

On-premises Free/busy is not working for 2010/2013

This walkthrough is used to troubleshoot Hybrid free/busy issues. Based on you answers, you have on-premises issues. For information about how to troubleshoot common on-premises free/busy issues, see Troubleshooting Free/Busy Information for Outlook 2007.

Troubleshooting general Public folder issues

The Free/busy guided walk though is not meant to troubleshoot Public folder issues. For information about how to troubleshoot Public Folder issues, see How to troubleshoot public folder replication problems in Exchange 2000 Server and in Exchange Server 2003.

Congratulations, your issue is resolved!

Thank you for using the Free/busy guide.

Still having problems?

Sorry, we cannot resolve this issue by using this guide.

Właściwości

Identyfikator artykułu: 10092 — ostatni przegląd: 04.05.2016 — zmiana: 84

Opinia
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)