During the configuration of BlackBerry Enterprise Server (BES) version 12 with ActiveSync monitoring in a Traveler environment, you may see an "access" or "cannot parse" error.
This can mean the URL constructed by GSX Monitor is invalid and does not redirect to the correct path for the ActiveSync commands.
- Error in ScanActiveSync URIs: The hostname could not be parsed.
- Cannot access http://server.domain.com/servlet/traveler...
How to Solve the Issue
GSX Monitor retrieves the BES 12 hostname from the email profile. If the hostname in the email profile contains additional parameters such as /servlet/traveler or a port number, then GSX Monitor will not be able to construct a valid ActiveSync URL as it is adding this information by default.
Below we show how to check the BES 12 hostname configured in the email profile.
Checking the ActiveSync URL from BES12 email profile:
- Open a web browser.
- Log into the BES Administration Console by entering the following URL:
- Change the port from the default 8008 if required.
- Log in using valid credentials.
- Locate the Email profiles on the left, and expand this section:
- Ensure the Host name or IP address field does not contain any additional parameter.
With the hostname correctly configured in the BES 12 email profile document, GSX Monitor is able to create a BES12 ActiveSync scenario successfully.
According to BlackBerry's BES12 documentation, step 6 of "creating an email profile", the server name should only contain a hostname or IP address.
The suffix /servlet/traveler should be a transparent redirection to Microsoft-Server-ActiveSync to follow BlackBerry and IBM guidelines.
- Manually configuring the HTTP server for Traveler redirection
- BES12 email profile creation
- BlackBerry UEM online help