www.gsx.com | log in | register

Last update: . Author: Cyril LEROY .

BlackBerry Enterprise Server 12 ActiveSync - "The Hostname Could not be Parsed" Error

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. 

BlackBerry UEM | IBM Traveler

Symptoms

  • 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:

  1. Open a web browser.
  2. Log into the BES Administration Console by entering the following URL:
  3. Log in using valid credentials.
  4. Locate the Email profiles on the left, and expand this section:
  5. 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.

Related articles



Not finding what you are looking for?

Have more questions? Submit a request


Was this article helpful?

0 out of 0 found this helpful