Невозможно установить соединение с Exchange

Решение обычных проблем

Если вы ещё этого не сделали, проверьте, может ли быть установлено соединение с Exchange, нажмите на кнопку "Проверить соединение" во вкладке Настройка -> Соединения -> Exchange клиент.

Решения обычных ошибок, выдаваемых при создании тестового соединения с Exchange Connection Tests, вы можете увидеть ниже:

Error #1: failed to connect to mailbox daisy@stimulussoft.local:Unable to access mailbox daisy@stimulussoft.local:Unauthorized
Resolution: Ensure Windows Authentication is enabled in IIS->Default Web Site->EWS->Authentication Method on Exchange Server. Ensure that full qualified user principal name (not an email address) is entered in the Exchange Connection.Ensure that the corresponding account password entered in the Exchange Connection is correct.

Error #2: failed to connect to mailbox daisy@stimulussoft.local:Unable to access mailbox daisy@stimulussoft.local:Unexpected EOF in prolog at [row,col {unknown-source}]: [1,0]
Resolution: Disable ASP.Net Impersonation in IIS->Default Web Site->EWS->Authentication Method on Exchange Server

Error #3: test exchange connection using mailbox daisy@stimulussoft.local.. failed to connect to mailbox daisy@stimulussoft.local:Unable to access mailbox daisy@stimulussoft.local:Forbidden
Resolution: Change SSL settings to match IIS->Default Web Site->EWS->SSL Settings the Connection Mode specified in Exchange Connection. Also, set EWS SSL Settings to Ignore Client Certificates.

Error #4: could not retrieve list of users from server 192.168.0.250:failed to locate users in the directory:Failed to locate authority for name: mailarchiva.stimulussoft.local
Resolution: Either DNS is not setup correctly on the Архива server or there is no connectivity to the Exchange server from the Архива server

Error #5: failed to connect to mailbox extest_1ea06f331e634@stimulussoft.local:Unable to access mailboxextest_1ea06f331e634@stimulussoft.local:The account does not have permission to impersonate the requested user.
Resolution: Impersonation rights were not assigned to the user specified in the Exchange Connection. Please refer to Exchange Impersonation to assign impersonation rights to the user.

Error #6: The primary SMTP address must be specified when referencing a mailbox.
Resolution: Upgrade to very latest version. This issue was fixed by introducing primary mailbox attribute name and field in Configuration->Logins.

Icon

Note: It typically takes ten minutes or so for an impersonation command to take effect. Thus, after assigning Exchange Impersonation rights, it is prudent to wait a few minutes before running Test Exchange Connection again.

Error #6: Internal server error.
Resolution: This error is returned from Microsoft Exchange. Try renaming C:\Inetpub\wwwroot\web.config to C:\Inetpub\wwwroot\web.config.bak on the Windows server, and run the command iisreset from the commandline. Also, verify that the url https://[exchange_ip_address]/ews/Exchange.asmx can be accessed from a web browser on the machine running Архива.

Resolution Walk Through

Ensure that Windows Authentication is enabled on EWS Site in IIS
a) Open the Microsoft IIS on the Exchange server
b) Expand Sites->EWS in the tree view on the left.
c) Double-click Authentication
d) Ensure that ASP.NET Impersonation is disabled and Windows Authentication is enabled
Ensure that EWS SSL Settings are set to not require a certificate
a) Open the Microsoft IIS on the Exchange server
b) Expand Sites->EWS in the tree view on the left
c) Double click SSL Settings
d) Check Require SSL and set client certificates to Ignore
Configure the Exchange Connector on the Архива server.

a) Make sure the correct version of Microsoft Exchange is selected
b) The impersonation account must be in the form journal@stimulussoft.com (enter user principal name of impersonation account, not email address)
c) Connection Mode should be set to match the EWS Site SSL settings set earlier
Click the Test Connection button. If successful, the output will be displayed as follows:

Решение дальнейших проблем

Run the Test-WebServicesConnectivity Cmdlet From the Exchange Shell

Icon
The Test-WebServicesConnectivity command may require a preparation script called C:\Program Files\Microsoft\Exchange Server\V15\Scripts\new-TestCasConnectivityUser.ps1 to be executed prior.
The command will output the following:
If EWS:GetFolder returns Failure.. Try renaming C:\Inetpub\wwwroot\web.config to C:\Inetpub\wwwroot\web.config.bak, thereafter from the command prompt on the Windows server, type iisreset
Verify that the Exchange server web services interface can be accessed from the machine running Архива.
a) On the Архива server, open a web browser
b) Enter url https://[exchange_ip_address]/ews/Exchange.asmx.
c) Authenticate with the same user and password entered into the Exchange Connection.
d) You should be able to get a valid response (i.e. not 500 or 404 errors). On Exchange 2013, it outputs "You have created a service...". On Exchange 2010, it displayed the WSDL definition for the Exchange web service interface.

Внутренняя ошибка сервера

This is a general error reported by Microsoft Exchange. It is often caused by a communication error between Microsoft Exchange and IIS. Common causes include incorrect/missing permissions in MS Exchange, problemtic Exchange upgrades from earlier version and/or corrupted Exchange objects. To resolve, please follow the Further Troubleshooting steps above. Failing that, it is helpful to examine both IIS and Exchange server event viewer logs. See: http://msexchangeguru.com/2013/09/24/e2013remote-server500internalservererror/. IIS logs normally located at C:\Windows\System32\LogFiles\W3SVC1. More detailed logging of HTTP 500 errors can be found under http://learn.iis.net/page.aspx/772/troubleshoot-with-failed-request-tracing/.

Сервис недоступен

Если вы получаете ошибку "Сервис недоступен" (англ. "service unavailable"), возможно, у вас установлены ограничения на IIS соединения, которые не позволяют Архива завершить импортt. Чтобы убрать эти ограничения, сделайте следующее: