Traveler error about incorrect server version

As a follow up to my post about the traveler fix we received.

Do not fat finger your typing, as I did.

I included an extra = sign in the xml file and that presented the following challenges:

1) new installations would fail with an error that says:
"The Server you have contacted must be upgraded to support this version of Lotus notes Traveler"
2) Devices would repeatedly get asked to download the updated or newer client

While these were my instructions:
\traveler\cfg\client\VersionInfo.txt

#Lotus Notes Traveler - Android
Lotus\ Traveler.Android.version=8.5.3.2 201207031233

If Linux OS - be sure the file pemissions/ownership is not changed.

I somehow added an extra = sign before the version number.

The IBM team sent me this URL to test the server which I provide in case anyone else sees these errors.

http://www.yourdomain.com/servlet/traveler?action=checkForUpdate&deviceType=Android&Version=0

You should get in return a message that looks like this(your verssion number may be different):

AppName=Lotus Traveler
DownloadLink=http://www.yourdomain.com/traveler/LotusTraveler/android/LotusTraveler.apk
Version=8.5.3.2 201207031233
LMIAppConfigFile=traveler.properties

In the incorrect xml file, the version line showed version== and thus the two sides could not communicate properly.

Live and learn.

Q-SnTT - Quickr Qpconfig.xml Errors

All together now, repeat after me, I will NOT edit the qpconfig.xml while sleep deprived or during the night while attending Lotusphere. I will not...

If you like the above graphic, go make one here.

Here is why:

12/09/2009 07:25:48 PM JVM: Java Virtual Machine initialized.
12/09/2009 07:25:49 PM Agent error: [Fatal Error] :69:5: The element type "user" must be terminated by the matching end-tag "</user>".
12/09/2009 07:25:52 PM org.xml.sax.SAXParseException: The element type "user" must be terminated by the matching end-tag "</user>".

What is this error in my server console telling me?

I have an agent run amok? A java agent at that.

And some org.xml.sax whatever? Come on guys, I'm an admin not a miracle java debugger.

But that /user thing rings a bell....

So here is what happened. It seems in my over zealous creative way, I had edited the qpconfig.xml and misplaced a reference. Who knew HTML was so unforgiving, or in this case XML. Raise your hands, me too, yes I know, my bad.

But in any event, here is what it looked like:


and what it should look like:


Mote the juxtaposition of the /user field.

So if you get odd java/xml errors in your server console after editing your Qpconfig.xml file, guess you know where to start now don't you.

Q-SnTT - Domain name doesn't compute

Q stands for Quickr.
I don't do many SnTT but seeing as this one bugged me, I will let you all know about it.

So Abbott & Costello(not client's real name) have a Domino network which will now be using Lotus Quickr. Their domain is of course called Abbott & Costello because someone a decade ago set them up that way.
I Love my job.

What's so unusual? SPACES
Usually Domino Domains are listed in concatenated ways, like abbott&costello.

Now those admins out there probably now this technote VERY Well, if not, now you do.

The highlight is:

Domino domain names should be a single word or string (maximum of 31 characters). Do not use periods (.) in the Domino domain name as they are reserved characters.

AND

Domino server names can consist of one or more words (a maximum of 79 characters) and can consist of any characters except: parentheses, at (@), slash and backslash (/ and \), equal (=), and plus (+). Using spaces or periods is not recommended.

If you use spaces, you must enter that server name in quotes ("") when entering a command at the server console. As the Domino server name is also used within the given protocols name to address resolve process the use of underscores and periods can create lookup failures within different protocols. As such they are strongly not recommended.

Great! I tried that in my QPCONFIG.XML but no luck. You see XML works in a different way.

Your QPCONFIG.XML file may require the Domain name of Abbott & Costello but if you put it in this way you will see an error which looks like this:

10/10/2008 10:16:26 HTTP JVM: [Fatal Error] :43:41: The entity name must immediately follow the '&' in the entity reference.

I tried the quotation marks no luck, and IBM support came back and told me to try swapping the & sign for & amp ; (as one word) and that worked.

For more substitutes for XML characters you may have in your domain name, check this page.