I guess there is nothing more to add to this than BRILLIANT! Sure, I’ve seen those DXL files before in the IBM_TECHNICAL_SUPPORT directory but never actually bothered opening them. What a mistake.

Thanks for sharing this really valuable topic Vlad!

You may have read or heard about the new feature that allows for the auto-population of groups in Domino 8.5. Since I have first learned of it I got quite excited, until I got hold of the new version to discover that IBM spoilt the community with the vast amount of 2 options: None and Home Server

 

Unfortunately the documentation confirmed my suspicion that this was about it: “Note For IBM Lotus Domino 8.5, Home Servers is the only auto-populate method available.”

While I see a reason for having a list of people populated by the home/mail server they are working on, there must be more to come to please today’s administrators. (more…)

I have always been against using the nlnotes.exe to launch the ‘Server-Client’ of a Lotus Domino installation but having a sepearate client-installation on the Windows box instead. This is a common requirement for environments with locally encrypted databases on the server in order to allow restoring data on the document level.

IBM has now published (or updated?) a technote outlining the reason for a dedicated client environment on the server.

Today was head scratching day again. Lotus Notes 8 was raising an error message that sounds so unusual for a Lotusscript developer:

Type mismatch in method CoerStrToNum: STRING found, double expected.

The only change to the environment has been the upgrade from Notes 7 to version 8. As it turns out, there are also a few notes about this message on Google, including a rather dubvious technote from IBM.

As it turns out, the source of the issue can be found in these two lines of code.

myDate$="17/01/2008 7:17"
var=CDat(myDate$)

Interstingly enough is the error message new to version 8 of Lotus Notes, obviously raised itself by the underlaying C++/Java code. All previous code streams, including the 8 debugger are raising the familar “type mismatch” error. This might create the impression that a regression bug has been introduced in Notes 8 – which is completely false.

Anyhow, who would have expected that the whole issue has been caused by a wrong regional setting on the underlaying operating system? In this case it has been set to US (American), with a date format of mm/dd/yyyy. As there isn’t a 17th month in a year the code fails.

I guess I would leave it open for discussion whether this has been an oversight by the developer, who couldn’t imagine that his/her code would ever been run in different region or a mistake by the persons setting up the laptop to not configure the (for New Zealand) proper date format dd/mm/yyyy.

Usually I don’t make a fuss about putting stuff on the web as it appears to be too straight forward. Until someone is going to ask you the exact same topic and you are reconising that it would have been word to share this tiny little bit of knowledge.

When working with partitioned servers there is the possibility (and probably best practice) to equip the physical (or virtual box, as it is going to turn out these days) with multiple network interface cards or at least multiple ip-addresses and configure the Domino servers to listen and response only to the address dedicated to the particular instance. This is achieved in utilising the TCPIP_TCPIPAddress=xxx.xxx.xxx.xxx:port parameter in the notes.ini.

The same can be done for the web interface in selecting the Internet Protocols -> HTTP tab of the server document. Look out for the Basics section right in the top left corner. In here you enable the web service to be bound to the host name and specify the Host name(s) the port is responding to.

Please note that the host name binding is done in the web site document when Internet Site documents are enabled in the Basics tab of the server document.