Traveler capacity planning and NOTES.INI settings.

IBM have recently published a series of new articles on the Domino Wiki site.  Two articles that really caught my eye were on:-

Capacity Planning on Traveler - haven’t seen as detailed and specific guide as this before

and

Traveler notes.ini settings - it’s great that Traveler customisations are now published and this is a brilliant reference to bookmark.

(Note:  that we already published an example of how to manually change these settings via NTSConfig.xml here - but having these available via notes.ini settings is obviously more straight forward!)

Cormac McCarthy – Domino People Ltd

Posted in Capacity Planning, Lotus Traveler | Leave a comment

Domino Server – Java Security vulnerability fixes

Hot off the press.

IBM have issued a series of Interim fixes to plug four identified JVM vulnerabilities, details of which are here

and the fixes are available here (for all operating systems) ** IBM ID Required to download

Cormac McCarthy – Domino People

Posted in Domino Server, Fix, Lotus Notes Client, Security | Leave a comment

Two new interim fixes released for Traveler

Two new interim fixes were released for Traveler.

They’re both maintenance releases containing multiple fixes – APAR Listing

You can download both of them from Fix Central

A valid IBM ID is required.

Cormac McCarthy – Domino People

Posted in Fix Pack, Interim Fix, Lotus Traveler | Leave a comment

Useful view for Replication or Save conflicts

This is a quick tip that can be used to find Replication or Save Conflicts in any Notes application, but as an Admin I’ve found it most useful for a Domain’s NAB.

In a Notes application,  click Create -> View

  1. Change the view name to something appropriate.
  2. Change the “View type” to “Private” from the drop down menu.
  3. Change the “Selection conditions” box to SELECT @IsAvailable($Conflict)
  4. Click “Save and Customize”.

Right Click on the view as it appears and select “View Properties”.

Click on the second tab, and untick the box “Show response documents in a hierarchy”.

Click the “Esc” key twice and when prompted click “Save”.

You’ll now have a new private view that will show you all Replication or Save conflicts:

It’s really something that should be checked regularly anyway but this is a hassle free way!

Cormac McCarthy – Domino People Ltd

Posted in Domino Server, names.nsf | 2 Comments

Workaround for unread marks problem.

Scenario:  You’ve more than one Domino server, with more than one replica of a database (that’s everyone with Notes I think!) .  You’ve set unread marks to be maintained in Database properties BUT you notice at some stage (usually when a server crashes) that a replica that normally isn’t used has a completely different number of unread marks.  (it’s happened to us all!)

The usual lazy helpdesk solution to this is to select all, mark all as read and tell the end user “it shouldn’t happen again”.

However have you tried going to the workspace,  Click “View”, and then untick “Stack Replica Icons”.  (don’t panic it upsets your workspace layout, you can get it back!)

Then click on the two (or more) replica icons while holding ctrl and shift, and click “Edit”, “Unread marks”, and you’ll see another option “Exchange unread marks”.

It’s quite often overlooked but it usually fixes the problem!

Let us know if you found this useful!

Cormac McCarthy – Domino People Ltd

 

 

 

Posted in Lotus Notes Client, Uncategorized | 4 Comments

Traveler – Update on known device limitations

IBM have updated their documentation on known device limitations for Traveler.  Although issues/limitations are decreasing all the time,  if you deploy Traveler, this is a great reference to have and familiarise yourself with:

Please let us know if you experience any issues or limitations that haven’t been documented!

Cormac McCarthy – Domino People Ltd

Posted in Android, HTC, iPhone, Lotus Traveler, Windows Phone | Leave a comment

Domino Error – Unable to Bind port…..

Most Domino Admins will have seen this in a console from time to time.  It happens when a local OS application is using a port Domino wants to use.  So far, so simple.  But what’s the quickest way of finding out which application/service is using the port you want?  In windows it really is quite easy…

Open a command prompt and type:

netstat -an -o

This will give you a list of applications (and PIDs) that have ownership of ports. Look for the port, and associate the PID with a Process in task manager.

Let’s take a common example.  You enable HTTPS for web connections in the server document and restart http.   The Domino console tells you “HTTP Server: Error – Unable to Bind port 443, port may be in use or user needs net_privaddr privilege”.

Remote to the OS of the server.  Open a command prompt.  Type “netstat -an -o”.  You’ll get something like this:-

Look for the port in question, in this case it’s 443, and the associated PID is 1268.  Open windows task manager, click “View” and “Select Columns..

Make sure PID is selected as a column.

 

Sort by the “PID” column and look for the PID from earlier (1268 in this case), you’ll find the “offending” application under “Image Name”.

In this case it was TeamViewer as you can see.

I hope you found this useful.  It’s not that complex a problem, but often it takes few minutes to remember exactly what the best way of checking this is!

Cormac McCarthy – Domino People Ltd.

Posted in bind error, Domino Web Server, HTTP, HTTPS, netstat, SSL | 4 Comments

SSL breaks after upgrading to Traveler 8.5.3 UP 1

On a production upgrade of Traveler to 8.5.3 U.P. 1 yesterday we came across a problem.

The upgrade itself completed without issue but mobile clients couldn’t connect to the server automatically after the server was back up and running.

We could see the following in the log :-

“HTTP Server: SSL Error: Keyring file not found, key ring file [keyfile.kyr], [Default Server]”

So we did some digging.  Before the upgrade the “SSL key file name” field (Server Document -> Ports > Internet Ports- >  SSL key file name) was something other than default (say mobile.kyr for argument’s sake).

After the upgrade this field changed back to the default “keyfile.kyr” automatically!  It is quite an easy fix (either renaming the the .kyr file on the OS and restarting HTTP or renaming the field in the server document and restarting HTTP fixes the problem).

We’ve done a few tests and it doesn’t appear to be reproducible on demand, however it is worth noting in case the same thing happens to you!

Cormac McCarthy – Domino People Ltd.

Posted in Android, HTC, HTTP, HTTPS, iPhone, Lotus Traveler, Windows Phone | Leave a comment

Traveler 8.5.3.2 Interim Fix 1 released

Overview

Lotus Traveler 8.5.3.2 IF 1 is an Interim Fix release that contains APAR fixes for the Lotus Traveler server and clients. The information below outlines the changes included.

Fix List

See Lotus Traveler APAR Listing

Feature List – new in 8.5.3.2 IF 1

Please ensure to read the detailed instructions.

You can download the fix here. (requires a IBM ID).

Posted in Android, HTC, iPhone, Lotus Traveler, Windows Phone | Leave a comment

Lotus Domino R8.5.3 Interim Fix for Traveler (Win 64bit)

If you are running Lotus Traveler on Domino 8.5.3 FP1 (Windows 64 bit), there’s a new interim fix available that may avoid serious issues (such as server crashes).

Details are available at this IBM tech note - http://www-01.ibm.com/support/docview.wss?uid=swg21591859

(please note to download the fix requires an IBM log in)

Posted in Android, Domino Server, HTC, iPhone, Lotus Traveler, Uncategorized, Windows Phone | Leave a comment