Common Troubleshooting
If you haven't already, check whether an Exchange Connection can be established, click the Test Connection button in Configuration->Connections->Exchange Connection.
Resolutions to common errors outputted by Exchange Connection Tests include:
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.
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:
Further Troubleshooting
Run the Test-WebServicesConnectivity Cmdlet From the Exchange Shell
The command will output the following:
[PS] C:\Program Files\Microsoft\Exchange Server\V15\Scripts>Test-WebServicesConnectivity
Source ServiceEndpoint Scenario Result Latency (MS)
------ --------------- -------- ------ -------
mailarchiva.stimulussoft.local mailarchiva.stimulussoft.local Autodiscover: SOAP Provider Success
35
mailarchiva.stimulussoft.local mailarchiva.stimulussoft.local EWS: GetFolder Success
53
- 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.
Internal Server Error
Service unavailable
If you get "service unavailable", you may have IIS connection limits defined which are preventing Архива from completing the import. To remove these limits, follow the below steps:
Open IIS7 and navigate to SERVERNAME\Sites\SBS Web Applications Under Actions/Configure click Limits. Untick “Limit Number of connections”. |