Showing posts with label lotus_notes_traveler. Show all posts
Showing posts with label lotus_notes_traveler. Show all posts

Wednesday, January 14, 2009

It happens again, BES Knocks off Traveler

When last we left it in my post a few months back, we had found the 4.1.6 version of BES added a cute little line that disables Traveler. Of course this presumes both run on the same server.

So it is also with MR3, the latest update which I installed in an attempt to resolve a dropping of BES from our Lotus 8.5 Domino server.

Now can anyone tell me how to update the dll for the security patch? I presume I need to copy them over, but the readme was not readable for me.

And why can't I access my server NAB in Traveler when emailing staff? My phone is on its last legs, just has to get through Lotusphere 2009, so am not worrying too much.

So onward to Lotusphere now that everyone has Blackberries buzzing and Traveler's traveling.

And yet another day delay in the website for this:
Domcubus from Mycubus, portable servers for SMB, Home or all things Lotus

Tuesday, July 29, 2008

Lotus Notes Traveler and BES 4.1.6 Resolution

After some discussions with RIM and IBM, the good people at IBM support, thanks to Steven Kyle who handled my PMR, were able to recreate the problem on a test server.

It seems the installation of BES 4.1.6 alters the notes.ini file

Lotus Notes Traveler has two components, a Server and an HTTP Servlet. The Server communicates with the users mail servers, stores history information etc and the HTTP Servlet communicates with the devices. When I installed the BES 4.1.6 Server it added this parameter to the notes.ini file which basically disables any Java based HTTP Servlet:
HTTPDisableJVM=1

They removed this field from the notes.ini file and restarted the Domino Server and the Lotus Notes Traveler servlet started without problem and the device began syncing again. If the Lotus Notes Traveler Servlet starts successfully you will see a message similar to this on the Domino Console when the HTTP Server is starting:

HTTP JVM: com.lotus.sync.servlet.TravelerServlet: init
HTTP JVM: Traveler 8.0.1.2.200807181242: debug = false

So the questions for Blackberry and us in production are:

1) Why do they add HTTPDisableJVM=1 to the notes.ini file?
2) Will BES break if this parameter is removed?

Haven't tested it yet, harwdare failure this morning, but if it resolves it for you. Great.

PS - Don't forget IBM released a hotfix on the 24th for Lotus Traveler. Go get it, read the instructions first and then upgrade it.

Friday, July 25, 2008

BES 4.1.6 upgrade may break Lotus Notes Traveler

Lotus Notes Traveler servlet reply
A technical posting, ask for help and others who have this setup and it works or doesn't work.
If like many small companies you run a Domino server and it also hosts BES and traveler, you may have a problem.

We upgraded a BES to 416 from 415 this morning and since then Traveler has stopped. It is running on the server fine, but the clients can't connect, error 36 usually.

Something has affected the servlet engine and Traveler clients can not connect to the server.

You can test it by going to your server from a browser and typing servername.com/servlet/traveler

You should then see something that looks like this picture.
If you get a 404 error, you have problems.

Perhaps this is the issue: Default port number is 50125 for IPC (Inter process socket connection between Lotus Notes Traveler Server and its HTTP server servlet).

All feedback is appreciated. My phone thanks you.

Thursday, February 28, 2008

Lotus Notes Traveler, still AWOL

Sadly, IBM has not replied to my request for a download of it.
And it is still not available for Business Partners to download.
I have customers that want it as part of their 8.01 upgrade, but we can't get it?
This is getting frustrating.