Not sure if anyone else has run into that before:

Running the agCleanup agent in the domlog.nsf is raising the following error:

Memory allocation request exceeded 65,000 bytes

While the message is a bit misleading, the cause is quite reasonable once discovered.

In this particular case the entity running the agent did not have access to delete document in the domlog.nsf. This is inherited from the domlog.ntf template for LocalDomainAdmins.
Domino is writing an error line into the agent log for each document it  is attempting to delete.
With the vast number of documents that are to be deleted from the database on a daily basis, the logging field of the agent is reaching the 64K limit.

The solution: Grant deletion rights to the entity running the agent.

One of my previous posts describes that there are two different ways policies are applied to traveler users.

When Traveler policies are applied, the content of the settings document is being copied over into a profile document of the user’s mail file.

The Traveler server is using the Traveler’s Cluster Cache database (ntsclcache.nsf) to look-up the location of the user’s mail file.

The following error could be raised when policies can not be applied:

Notes Traveler: SEVERE [SYSADMIN] Internal Error: Debug Data: Error on UpdateProfileFromPolicyError: Database ‘mail/mdemo2.nsf’ on ‘CN=MAIL/O=Organisation’. Error(227 )=Invalid or nonexistent document

There might be an issue with the ntsclcache.nsf. Just open the database, remove the entries for the affected user. Restart the Traveler task and try applying the policies again manually.

In my case the mail file was located on a 7.0.3 server in a different domain, hence I had to issue ‘Tell Traveler Policy Update MDemo2‘

The command syntax for the deletion of users has been extended for version 8.5 of Lotus Traveler.

Use
‘Tell Traveler Delete <Device> <User>‘
instead of using
‘Tell Traveler Delete <User>‘,
whereas Device refers back to the Device ID of the mobile phone. It can be replaced by a * wild card, indicating all devices.

When using the delete command, bear in mind that the name of the user or device must not contain white spaces. Hence the short name of the user has to be used.

It is also important to note that the user to be manually removed from the Traveler database must exist in one of the directories of the Traveler server in order to resolve the short name.

My head is buzzing around Lotus Travler, Windows Mobile and Nokia S60 devices. If I would have known how cool this stuff can be I would have started looking into it much earlier!

Anyhow, my recent adventure into setting up IBM Lotus Traveler for a corporate taught me more tricks of the trade than I am able to put into one individual blog entry due to limited amount of time. That’s because there is much more to be discovered!

Tip #1: Install Domino x.509 root certificates for S60 devices:

IBM provides us with the option of secure (HTTPS) communication between the Lotus Traveler client and the Domino Server. No problemo I though, just create a key ring with the root certificate using the Domino Certification authority and issue a certificate for the domino server, import the root certificate to the mobile device and …

But wait, how do I get the certificate to the device? Just moving it over via Bluetooth or file transfer brings up an error: “Messaging: Feature not supported” or “Unable to open. File type not supported”.

Once the solution to this little annoyance has been found it seems to be so easy.  Kaz 911 is explaining how to install (Microsoft) Exchange certificates on S60 devices. The same procedure applies to Domino issued certificates - looks like there is commonality between the two products.

In a Nutshell:

1. Place the certificate file on a web server than can be accessed from the phone browser
2. Define the mime type for the .der extension on your web server as application/x-509-ca-cert
   If you don’t happen to have access to the mime.types file on the Apache server and you are not using Domino you could also just amend the .htaccess file adding  AddType application/x-x509-ca-cert .cer
3. Browse to the file with the phone browser and accept the certificate

There seems to be a common moaning about Nokia PC Suite not being able to replicate room information with Lotus Notes. 

Wait! There is an easy solution for that. Instead of using the full edition of PC Suite you can switch over to the Nokia PC Suite Enterprise Edition.

An added bonus for system administrators is the ability to customise the package in order to enable/disable individual replication features or to pre-define one- or two way replication.

While I struggled to set-up the application on my PC using the exe installer (don’t ask, weird things happened), it is working brilliant when unpacking the msi first and running the setup via msiexec.

How to install:

Unpack package to your hard drive:

nokia_pc_suite_ee.exe /U=”C:\”

Run set-up using the LNROOMS=”1″ switch to enable room replication:

 msiexec /I “nokia_pc_suite_ee.msi” LNROOMS=”1″