RnRMgr: Error processing reservation document <noteid>

It was found that when rooms are being invited, they are not responding to invites even though they are being delivered into the rooms & resources database (rnrdb) It was found that the notice documents in the ($Nlookup) in the rnrdb are not being processed, which is why not responses are being sent. The RNRMGR task was found to be running correctly, but that it would give random errors “RnRMgr: Error processing reservation document <noteid>”. These note ids were tracked and found that they correlate to the notice documents in the ($NLookup) view in the rnrdb. A list of these were created and it was found that this is not happening to all rooms’ invites. The affected rooms were investigated and certain fields were found to be not on the documents. The resource documents in rnrdb were resaved and the the invites retested which worked. The rnrmgr was restarted to force it to reprocess the historic invites.

This is useful for environments where you want the user to be able to travel with his IBM Notes installation and plug it into any computer in order to gain access to his\her IBM Domino environment.

Extract the IBM Notes installation files into a temp directory (not on the flash drive). Fom dos prompt in the temp directory where the setup file is located, issue this command where f:\ is the drive letter of the flash drive or external hard drive.   setup /a /v”NOMAD=1 TARGETDIR=F:\ /qb+”

This will install notes onto the flashdrive. To configure the notes on the flash drive, open the FlasDrive and click on the autorun.exe file.

It was found if the Notes Gateway is stopped, and instead of starting it normally, right click on it in the Rightfax admin window and click on Debug. This enables a prompt that shows each step the gateway processes while starting up. This prompt would show that the password has not been entered, which would explain why the api could not connect to the Notes client.

If was found that the notes id password stored in the Notes gateway config was not being used, so the API could not start. We manually set the following key to be the clear password which resolved the problem.

HKEY_LOCAL_MACHINE\SOFTWARE\RightFax\Gateway\Gateway\Password

This could be a security concerns in some environments, and should only be used for troubleshooting purposes.

FIELD UnreadMarksCacheTime:=”"

There are some articles indicating that your server is running out of memory, which was not the cause in my situation. I then found that the traveller server has not yet replicated the NAB  with the R85 template. This caused the server doc to lack certain important fields for traveller settings.

To resolve this, update the design of the NAB (or replicate with the admin server after refreshing the design, as in my case), and edit the server document for the new traveller related fields to be saved.

The following entries were found in the notes.ini, ConstrainedSHM and ConstrainedSHMSizeMB, which caused the
Domino server to ‘hog’ the shared memory at startup. I removed these and the
servers have been up for more than 8 days now.

The following article was found on these ini settings. These setting seemed to have ‘creeped in’ with previous versions and administrators of the server.

http://www-10.lotus.com/ldd/dominowiki.nsf/dx/constrainedshmsizemb

We found the problem to be Domino counting it’s chickens by scanning for nsf files in the domino\html directory, which happens to contain more than 3 000 000 html and xml files (spread through 25 000 sub directories for this specific server. A nice workaround was found in which you set the folder attribute for the large directory to ‘hidden’ on OS level. This prevents Domino from scanning the directories for nsf’s on startup, but still serves the files through the http task.

Now for some coffee!

PS: This process will not cause you to loose any data.