Category Archives: Administration

Misleading error message at ST Meeting Server installation

Posted on by
Reply

This week I was challenged with a completely deceptive error message during the installation of the Sametime Meeting Server. The error message claimed that

System Clocks are not synchronized within 5 minutes of one another, Please synchronize for federation.

IBM Installation manager error message

Since I was working in a somewhat unreliable test environment I obviously believed in the message and dutifully compared the system times between the Sametime Systems Console server and the Sametime Meeting server. Without a lot of surprise the times were synchronised and the time zone settings didn’t cause any trouble either. This obviously didn’t help me in any shape or form hence I started to investigate the various log files created by the system.

Looking at the Deployment Manager’s System log I discovered an error, which was logged every time I tried to confirm the deployment plan for the Sametime Meeting Server:

[20/04/12 16:21:13:150 NZST] 00000065 exception     W com.ibm.ws.wim.adapter.file.was.FileAdapter login CWWIM4512E The password match failed.
[20/04/12 16:21:13:151 NZST] 00000065 exception     W com.ibm.ws.wim.adapter.file.was.FileAdapter login
                                com.ibm.websphere.wim.exception.PasswordCheckFailedException: CWWIM4512E The password match failed.
at com.ibm.ws.wim.adapter.file.was.FileAdapter.login(FileAdapter.java:2025)
at com.ibm.ws.wim.ProfileManager.loginImpl(ProfileManager.java:3519)
…
[20/04/12 16:21:13:153 NZST] 00000065 LTPAServerObj E   SECJ0369E: Authentication failed when using LTPA. The exception is <null>.

This triggered my memory. We recently had to change the password for the local Websphere administrative user. Researching above error message I learned from Dave (Thanks!) that the local file registry could still hold the wrong password. The link in Dave’s post pointed me to the instructions on how to How to reset the administrator’s password in the file registry. While those instructions obviously aim for Websphere Portal they still helped me solve my issues with the Sametime Systems Console deployment manager.

After synchronising all the nodes and restarting the application servers, node agents and the deployment manager I managed to successfully deploy the Sametime Meeting Server.

 

How to reset the administrator’s password in the file registry

IBM Connections Documentation HTML wrapper

Posted on by
Reply

If you are like me and constantly being frustrated about the performance of the IBM Connections wiki you can try those two HTML wrapper documents for a more instant experience:

HTML wrapper

HTML wrapper accessible

Just note the comment on the top of each document “This draft is refreshed quarterly, as necessary, but does not contain all of the latest updates and fixes made to the community-owned version of the wiki articles.”

AusLUG12 presentation

Posted on by
1

Thanks to everyone who attended my session on Lotus Notes package customisation and the positive feedback I have received so far.

Don’t hesitate to drop me a line if you need to know more details on any of the topics covered.

Streamline client deployments with customised installation packages

Feel free to download the presentation from here. Most presentations should also be made available in the AusLUG community after the event.

Principal field invalidates RFC 5322 compliance

Posted on by
Reply

Due to lack of time, another post in ‘shorthand’:

Issue:
Outgoing SMTP messages are rejected by ISP or Gateway appliance with error “Invalid sender address”

Investigation:
RFC 5322 requires a from field in the header of every email. Emails that were sent from LotusScript specifying an invalid entry for the Principal field caused Domino to create invalid message headers. The mandatory From field was missing.

Solution:
When using Principal fields, ensure to use valid names. This are full names or abbreviated names as listed in the Domino Directory but not email addresses. Using email addresses in the principal field causes above issue even if the address is listed as an additional entry in the User Name field.

Lotus Traveler: 403 FORBIDDEN

Posted on by
2

Just a quick note on an issue we discovered lately.

Issue:
An Apple iPhone was unable to synchronise with the Traveler server. The only error message we got was 403 FORBIDDEN (Access not allowed even with authorization) in the Domlog.nsf.

Investigation:
Issue tell traveler security status username on the domino console. This will result with a listing of all devices registered to a user and their security status. In this particular case the security approval was pending for the iPhone but the device was not listed in the LotusTraveler.nsf.

Solution:
Issue tell traveler security approval approve deviceID username. This will approve the pending device approval and re-add the device to the LotusTraveler.nsf.