Traveler 8.5 - Parsing Error

HCL Domino Domino Forum
1

I upgraded to Traveler 8.5 (from 8.0.1.2 which worked great).Server run’s domino 8.5.

When trying to register a mobile device i get an error:

“Parsing error reading the configuration file at line 10 position 29”

“Failed to read the configuration file”

Hard reset of the mobile and reinstall client didn’t help.

Users that are running Traveler 8.0.1.2 still working.

I’ll appreciate any help.

Thanks.

2

Subject: Traveler parsing error

This sounds familiar. Please try latest maintenance for 8.5 and see if it resolves the problem. If not let us know and will investigate further.

http://www.ibm.com/support/docview.wss?uid=swg24019529

3

Subject: I installed Traveler 8.5.0.1

Thanks for your reply.I installed Traveler 8.5.0.1.

I don’t see any improvement.

I still get exactly the same error.

4

Subject: Did you also install Interim Fix LO37251

The interim fixes are cumulative, I belive there was a fix for parsing errors allong the way. If still having the issue after upgrading both server and client then probably need to see the logs from the device. Logs can be submitted by openning a Problem Report through either Passport Advantage or Partner World:

Passport Advantage: Hybrid cloud software for a smarter business | IBM

Partner World: http://www.ibm.com/partnerworld/pwhome.nsf/weblook/index.html

5

Subject: LO37251 was installed on Traveler 8.5.0

As mentioned, I don’t see any improvement to the “Parsing Error” issue.I sent a PR directly from the device.

Thanks for your help.

It’s a bit urgent by now…

Considering downgrading to 8.0.1.3.

6

Subject: I Found the problem but no solution yet

The error was “Parsing error at line 10 Position 29”.That position at the WM’s configuration file has the Traveler server name at the format “cn=Server/o=Org”.

Our org name is in Hebrew letters and that’s exactly position 29 (after the “/o=”).

It doesn’t seem to bother version 8.012 which worked great or any other Domino product that we used since version 4.

Now i have two options:

  1. Wait for a fix.

  2. Install the Traveler server in a new Org. the problem is that i don’t know what I’m going to loose from that.

I’ll appreciate any feedback.

Thanks.