If you are seeing some old and invalid objects in the “lotustraveler.nsf”, on the HCL Traveler server, try running “tell traveler cleanup show” command. It will show you which entries are obsolete and could be deleted.
Provided that you are OK with the result, run the “cleanup” command without the “show” option, this command will delete the entries previously shown.
To find out more about the HCL Traveler “cleanup” command, take a look at the official documentation.
In the HCL Sametime version 11 there is no System Console, which means that the Name Change tasks have to be created directly in the “stnamechange.nsf” database.
This process is not documented. After trying to reinvent the wheel and failing gloriously, I decided to write a blog post about it. 🙂
Just open the “stnamechange.nsf”, with a user which has manager access on the database, click on “Create” and create a new “Name Change” document.
After that just choose the name of the document, “Description” is optional. Under “Location” enter the DN of your Sametime Community Server, “CN=<server_name>/O=<organisation_name>”. “File” is a richtext field, and here you have to upload the CSV file you want to use. You can read the details about creating the CSV file in the official documentation.
In the end the document should look like the following:
After that just run the stnamechange.cmd/.sh as you normally would with HCL Sametime version 10 or earlier.
If you are on Windows OS, open CMD as administrator, navigate to the Domino program directory and start stnamechange.cmd or stnamechange.sh respectively with the following parameters:
stnamechange.cmd <domino_program_directory> <domino_data_directory>
For example:
stnamechange.cmd c:\HCL\Domino c:\HCL\Domino\Data
That should be it. If you run into any problems, you can take a look at the log, every time you run the command, a log file is created in the “Trace” directory of the Sametime server. You can even set verbose logging.
I hope this helps and saves you some time.
Recently I had a problem with Verse On-Premises and Connections Files integration. Integration with Connections Profiles was working fine, but uploading an attachment to a new mail and Files application or attaching a file directly from Files App was just not working. After a bit of troubleshooting I opened a PMR.
After a little while I got an information that Verse On-Premises and Connections Files integration is officially not supported. It will be supported in future, it just isn´t supported in the current release.
Shortly after that I managed to solve the problem with the help of Roberto Boccadoro. Check out his post about this issue.
The integration with Connections Files works, you just may not get help from the IBM Support if you run into a serious problem.
Since a few days Docs 2.0 CR1 iFix 001 is available for download from the Fix Central, it includes the following Fixes:
Prior to installing this iFix you need to install CR1 for IBM Docs 2.0.
Official Release Notes to IBM Docs 2.0 CR1 iFix001.
Recently, new Versions of Connections plug-ins were released in IBM Greenhouse.
IBM Connections Desktop Plug-in for Windows & IBM Connections for MAC, Version 16.8
The new Version adds a new feature:
(BETA) – a new authentication method called “Web Forms Authentication”
IBM Connections Plug-in for Microsoft Outlook, Version 16.8
Adds miscellaneous defect fixes.
IBM Connections Plug-ins for IBM Notes, Version 5.5
Supports the ability to work with both personal and community owned files organized in multi-level nested folders.
I tried to install Docs 2.0 CR1 but when I ran the command to perform the upgrade the task failed, specifically when updating the Conversion server, with the error “Target with name ic55.eld.it was not found.”
I quickly found out that two other esteemed friends, Christoph Stoettner and Milan Matejic, had encountered the same issue and were able to solve it.
The problem is in the file config.py that is in the patch installation directory. At the bottom of the file there the line “self.me_hostname = socket.gethostname()”. The solution is to change that to “self.me_hostname = socket.getfqdn()”.
Once I did that, CR1 installed flawlessly. Thanks a lot to Christian and Milan!
After an OS restart we encountered a problem with the Traveler Server, the local Derby database became corrupt, and therefore Traveler clients could not sync the enterprise data.
After starting the Traveler task the following errors were logged in the console:
[09C4:000C-0B5C] <Timestamp>Â Â Traveler: WARNING <Username> Session ID d082448615552a82da8175a9ea5d071a309 could not be associated with any existing PS threads.
[09C4:000C-0B5C] <Timestamp>  Traveler: SEVERE <Username> Exception Thrown: com.lotus.sync.db.PersistenceException: java.sql.SQLSyntaxErrorException: Invalid Properties list in FROM list. There is no index ‘IDX_GUIDNEXT_1’ on table ‘GU
[09C4:000C-0B5C] <Timestamp>Â Â Traveler: WARNING <Username> Sync exception being treated as a backend failure. Exception Thrown: com.lotus.sync.db.PersistenceException: java.sql.SQLSyntaxErrorException: Invalid Properties list in FROM list.
Next course of action was to try to defrag the Database which solved the problem. I simply removed the Traveler task from the “notes.ini” file and started it with “Load Traveler -defrag” command. The defragmentation Process took about 10 Minutes after which the Traveler task was started and the mobile devices could sync the PIM Data without any problems.
The following article from IBM also describes a similar behavior:
http://www-01.ibm.com/support/docview.wss?uid=swg21608001
After WAS Update from 8.5.5.6 to 8.5.5.8 I could login only into “Profiles” Connections Application, all other Connections Applications were not “reachable”. After digging little further I found the following Errors in the “AppsCluster” Logs:
0000016f LotusConnecti E com.ibm.openactivities.exception.OpenActivitiesException: com.ibm.connections.directory.services.exception.DSException: com.ibm.connections.directory.services.exception.DSOutOfServiceException: com.ibm.connections.directory.services.exception.DSOutOfServiceException: CLFRK0004E: Directory Service Extension(DSX) received a HTTP response from URL ‘https://social-d.bat-groupware.at/profiles/dsx/instance.do?login=WBTSTT’ expected XML, received unexpected content-type ‘text/html;charset=UTF-8’!
javax.servlet.ServletException: com.ibm.openactivities.exception.OpenActivitiesException: com.ibm.connections.directory.services.exception.DSException: com.ibm.connections.directory.services.exception.DSOutOfServiceException: com.ibm.connections.directory.services.exception.DSOutOfServiceException: CLFRK0004E: Directory Service Extension(DSX) received a HTTP response from URL ‘https://social-d.bat-groupware.at/profiles/dsx/instance.do?login=WBTSTT’ expected XML, received unexpected content-type ‘text/html;charset=UTF-8’!
E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[action]: com.ibm.openactivities.exception.OpenActivitiesException: com.ibm.connections.directory.services.exception.DSException: com.ibm.connections.directory.services.exception.DSOutOfServiceException: com.ibm.connections.directory.services.exception.DSOutOfServiceException: CLFRK0004E: Directory Service Extension(DSX) received a HTTP response from URL ‘https://social-d.bat-groupware.at/profiles/dsx/instance.do?login=WBTSTT’ expected XML, received unexpected content-type ‘text/html;charset=UTF-8’!
After that I found out that the “Domain Name” setting for the Single sign-on (SSO) Configuration has changed after the update. You can get to this setting by logging into ISC Console and navigating to: “Security Ă Global security Ă Web and SIP security Ă Single sign-on (SSO)”.
This may be specific to our environment, usually all our Windows Servers use “bat.dir” Domain, after a service is installed on them which is going to be used in the production we create a “Alias (CNAME)” entry in the DNS for it in the “.bat-groupware.at” Domain.
Connections Applications on this server are configured to use “.bat-groupware.at”, so after I changed the “Domain name” setting to the correct value, all Applications were working fine.
The IBM Connections 5.5 CR1 and IBM Docs 2.0 iFix 005 are available for download on FixCentral.
IBM Connections 5.5 CR1 Fix List.
IBM Connections 5.5 CR1 Download.
Cumulative Refresh 1 requires a Homepage Database Schema update which can be found here.
IBM Docs 2.0 iFix 005 Release Notes.
IBM Docs 2.0 iFix 005 Download.
It is recommended to update to the latest software release, so happy downloading… 🙂
There are a few things to consider before changing the IP-Address of a DMGR or a WAS node where Connections applications are running.
It is important to make sure that you have used a DNS record instead of the IP-Address you wish to change in course of the installation and configuration of IBM Connections. This way you can be sure that there are no other changes you have to apply in order to successfully change the IP, assumed you do not change the name of the DNS record.
This is where a good documentation matters, the easiest way to check if IP-Addresses were used in course of the configuration would be to check the documentation of the Connections environment.
The other way is to search for the IP-Address you want to change in the XML configuration files of the WAS cell, if you don´t find it there than you can be pretty sure that you are good to go. Since undocumented configuration changes are frequent this should be a recommended course of action.
The XML files mentioned above are located under:
<WAS_Installation_Root>\AppServer\profiles\<DMGR_Profile>\config\cells\<Cell_Name>\LotusConnections-config\
It is also important to check the other possible consequences in your network environment.
After that you can continue with the following steps:
Thoughts about HCL Connections, Domino and Sametime 