Mobility Experts: WorxMail Troubleshooting - lessons from the field

12:43 PM
Mobility Experts: WorxMail Troubleshooting - lessons from the field -

In this blog we are three WorxMail problems through the configuration problems caused coverage to Lotus Traveler, and Exchange Server mailbox user accounts in connection with configurations AD that fails WorxMail synchronization. While there could be many possible causes for these problems to be, but in this blog, we cover only a few possible cases that may result in synchronization problems WorxMail

Problem 1 :.

WorxMail sync fails with the Lotus Traveler server with the error message "to negotiate version error on a common ActiveSync protocol negotiation ActiveSync protocol. Error Folder Sync :. Not done"

WorxMail error

to negotiate error on a common ActiveSync protocol. Negotiating ActiveSync protocol: Error Folder Sync :. Not performed

Error Description:

WorxMail synchronization fails with the Lotus Traveler server. Lotus Traveler server will not send the response to the HTTP Options command. The possible control points and in our case Traveler server is not configured with the path / traveler / Microsoft-Server-ActiveSync so that commands Activesync has sent / Microsoft-Server-ActiveSync as a path. The Post http command should be possible in the format /traveler/Microsoft-Server-ActiveSync.

CheckPoints:

1) Please check Lotus Notes Traveler is configured as follows:

the following corresponds to the configuration pages in the Traveler server Domino Administration

  • Domino Directory configuration - web Internet sites .. Internet sites, the following rules configured.
    1. Override Session Authentication / traveler forms-based authentication. disable
    2. Change Web Site rule for / servlet / traveler to /traveler.
    3. Rule Change for site / Microsoft-Server-ActiveSync to / traveler / Microsoft-Server-ActiveSync.

2) ensure that Domino blocking options not

There are two ways in which the Domino HTTP server options could block which in generally a "405 method not allowed" resulting response from the server. Consult this technote for more information to verify that options is not blocked by the Domino HTTP server:

https://www.ibm.com/support/docview.wss?uid=swg2002

[1945001überprüfen] 3) that other network applications not oPTIONS block (This needs to check now)

If Domino is not blocking oPTIONS, make sure that the options allowed by a firewall, VPN, reverse proxy or other network device / software What to find between the device and the Traveler server

could intervene in the protocols WorxMail .:

WorxMail tracks report " No Reported VERSIONS - IS LOCKED HTTP OPTIONS" server

"10-Oct-2014. 11: 05: 49: 486 (-0500 ) ", WorxMail, INFO (4)" ActiveSync protocol versions of Exchange Server supports: NO REPORTS vERSIONS - IS HTTP OPTIONS BLOCKED?”,-,com.citrix.workmail.provisiondispatchqueue,9e1f,WorxMail,/Users/test/Slave/workspace/WorxMail_Release_Artemis_9.0/develop/MobileMail/iOS/Release/9.0-artemis/ExchangeMail/activesync/libiosactivesync/engine/ActiveSyncEngine.m,-[ActiveSyncEngine validateAccount:error:],561

"10-Oct-2014 11: 05: 49: 486 (-0500)" , WorxMail, ERROR (2), "Negotiating ActiveSync protocol failed.”,,com.citrix.workmail.provisiondispatchqueue,9e1f,WorxMail,/Users/test/Slave/workspace/WorxMail_Release_Artemis_9.0/develop/MobileMail/iOS/Release/9.0-artemis/ExchangeMail/activesync/libiosactivesync/engine/ActiveSyncEngine.m,-[ActiveSyncEngine setServerCapabilitiesAndProtocolVersion:],393

"10-Oct-2014 11: 05: 49: 486 (-0500)", WorxMail, INFO (4), "Server responds without Version with status code 0 information”,-,com.citrix.workmail.provisiondispatchqueue,9e1f,WorxMail,/Users/test/Slave/workspace/WorxMail_Release_Artemis_9.0/develop/MobileMail/iOS/Release/9.0-artemis/ExchangeMail/activesync/libiosactivesync/engine/ActiveSyncEngine.m,-[ActiveSyncEngine validateAccount:error:],565

"10-Oct-2014 11: 05: 49: 487 (-0500)", WorxMail, ERROR (2) "WorxMail could not determine the server version - HTTP OPTIONS is blocked perhaps?“,Active,com.apple.main-thread,707,WorxMail,/Users/test/Slave/workspace/WorxMail_Release_Artemis_9.0/develop/MobileMail/iOS/Release/9.0-artemis/ExchangeMail/ExchangeAccountViewController.m,__80-[ExchangeAccountViewController observeValueForKeyPath:ofObject:change:context:]_block_invoke,1042

Problem 2 :.

The access to the corporate network is not currently available during WorxMail introduction available

Few users are confronted with the error "Access to the corporate network is currently unavailable"

What to find in WorxMail logs .:

in WorxMail protocols we can see the status code 111 for FolderSync. Answer

FolderSync operational status code 0. Now parsing reply ..
Parsing FolderSync response failed with status code: 111
FolderSync caught parser except

status code 111 means :.

This is a server-side configuration error. Check out the following link for the error codes. Status Code 111 translated:

111 ServerErrorRetryLater The server encountered an unknown error has occurred, the device should try again later Supported by :. 14.0, 14.1When protocol, version 2.5, 12.0 or 12.1 is used, an HTTP 503 response is returned instead of Status value

Please see MS link for the HTTP status codes and their meanings.

https://msdn.microsoft.com/en-us/library/ee218647 (v = EXCHG.80) .aspx

Solution:

in Exchange Server 2010, this problem can occur if the Exchange servers group does not have the appropriate permissions in Active Directory in the mailbox object. The most common cause for this is broken inheritance in Active Directory Access Control List (ACL).

Make sure that the user you are trying to check on the Active Directory user permissions "Include inheritable permissions from the parent object" to be used, has.

  1. Open Active Directory Users and Computers.
  2. in the console at the top, click Advanced Features View> Menu.
  3. Search and right ~~ POS = TRUNC mailbox account (user object) in the console and click Properties.
  4. Click on the Security tab.
  5. click Advanced.
  6. Make sure that the check box is selected for "Include inheritable permissions from this parent object"

Problem 3 :.

WorxMail error message "your mailbox is full, your message can not until you delete messages sent from your mailbox. WorxMail is this message when more space is available Send"

WorxMail error message :.

What to see in the logs:

status code 115 means:

from the above screenshot we can see the status code returned 115th Status code 115 is: (reference: https://msdn.microsoft.com/en-us/library/ee218647%28v=exchg.80%29.aspx)

value member name meaning Protocol version
115 SendQuotaExceeded The application would transmit rate exceed Supported by :. 14.0, 14.1

Possible Fix:

, since the quota is exceeded, has the news from the folders are deleted, which consumes a lot of space.

Previous
Next Post »
0 Komentar