After my previous post I am now back with a more appealing issue. Not a show stopper but still annoying, considering the possibilities if the automated client update is truly going to work.
The issue I am facing is an error message on our Nokia mobile phones on checking for new updates using the update installer:
“The response indicates that the server does not support Lotus Installer”
Strangely enough I have been able to upgrade one phoneÂ using this method without any issues, all subsequent attempts from there onwards failedÂ and I am a bit stuck due to the lack of detail of information on this feature on the web. Did anyone else run into this issue today or during the beta phase? I have also opened a PMR with IBM. I will update this post as I am receivingÂ updates.
Just figured out the main cause of the issue. The domlog.nsf records the URL request of the Update Installer application from the mobile phone, which looks similar to that:
You can open this url in the browser of your PC and will receive a response similar to this:
As always, the devilÂ lies is inÂ the detail. Before getting to the response I had to enter my username and password in the browser, which made me think that this could be the actual issue.
Again, checking the domlog.nsf, I realised that the request from theÂ Update InstallerÂ is an unauthenticated one, hence making it impossible for the application to receive the response.
The possible workaround is also explaining why I had been able to run the update once. The phone still had an open connection to the server in the browser session, which made the Lotus Installer request an authenticated one as well. Guess that’s the workaround for now until IBM comes back with a permanent fix on this as I don’t fancy allowing anonymous access to the Traveler servlet itself.