When you make a mistake you have to apologize. VoP 1.0.5 and Traveler

Apologies to whoever read my previous blog post about issues with VoP 1.0.5 and Traveler. It is not a bug, it was a mistake on my part.
When I went into the <dominodata>/domino/workspace/applications/eclipse/plugins directory I inadvertently deleted all the jar files: “del *.jar” instead of using the correct wildcard syntax specified in the instructions “*-1.0.*-0.0-*.jar”, core-1.0.*.*.jar and servlet-1.0.*.*.jar .
Doing so I deleted the file com.lotus.sync.traveler.admin.jar and that is why Traveler stopped working. That file is placed there by the Traveler installation process, and that’s why after I reinstalled Traveler on top of VoP 1.0.5 it worked again.

I am very sorry of having created a false alert, but unfortunately mistakes happen…. apologies again to my readers and most of all to the Verse development team.

Problems with Verse on Premises 1.0.5 and Traveler

On my server I upgraded VoP to 1.0.5 and Traveler stopped working.
Looking at the console there were no errors but the devices could not connect to the server anymore; opening https://server/traveler gave a 404 error.

In order to test I reverted back to VoP 1.0.4 and Traveler started working again, then I upgraded to VoP 1.0.5 again and Traveler stopped working again.

The solution I found is to install first VoP 1.0.5 and then reinstall Traveler, when I did that everything worked again, now I have VoP 1.0.5 and Traveler both up and running.

Solved – Problems with IBM Client Application Access and ODS 53

I upgraded my databases to ODS 53, and ICAA 1.0.2 stopped working.

When I launch it I get those errors

Solution: I had to upgrade to ICAA 2.0 and then everything worked.