Lotus Quickr Connectors: Location of the system-wide settings of the connector registry keys

Please be aware that the location of the system wide registry keys for the Lotus Quickr Connector are different if you are using Windows 32-Bit or Windows 64-Bit:

Location of the system-wide settings of the connector registry keys:

Windows 32-Bit:

HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Lotus Quickr

Windows 64-Bit:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\Lotus Quickr

The user-specific settings are the same for both 32-bit and 64-bit and are located in:

HKEY_CURRENT_USER\SOFTWARE\IBM\Lotus Quickr

IBM Sametime 8.5.2: Some things I learned during installation

Just for my reminder for the next time here are two things I learned today during a Sametime 8.5.2 installation. I did a test installation following the instructions in Frank’s presentation.

However the installation of the Meeting Server failed with the following error:

ADMA0158I: [EJBDeploy] Error executing deployment: java.lang.RuntimeException. Error is Application “com.ibm.etools.ejbdeploy.batch_extension” could not be found in the registry.

To solve this error I  deleted the contents of the following directory EXCEPT for the ‘config.ini’ file (there is a technote describing a similar issue while upgrading to Sametime 8.5.2 IFR1):

$WASHOME/deploytool/itp/configuration

I also had also to delete the reference to the Meeting Server in the Websphere profile registry. Just delete the line referencing your meeting server installation (something like “<profile isAReservationTicket=”false” isDefault=”false” name=”meetingSTMPNProfile1″ path=”C:\IBM\WebSphere\AppServer\profiles\meetingSTMPNProfile1″ template=”C:\IBM\WebSphere\AppServer\profileTemplates\default”/>) in the file

$WASHOME/properties/profileRegistry.xml

After I did that, I restarted the installation of the meeting Server and everything went fine then.

Later I had also a problem while installing the Media Manager. As soon as I started the installation manager on the machine it failed without an error message (no splash screen apeared at all). You just saw a java dump appearing but with no real information about the crash reason.

I think that the issue might have been related to my specific environment. I installed the servers in a Virtualbox environment and I solved the issue by decreasing the RAM for the machine temporarily to 3048 MB and adding a second virtual processor. I have no idea why this might have been an effect but afterwards the installation manager could be started without problems again and the Media Manager installation went fine.

Lotus Quickr (Domino): Increase number of feed entries

By default RSS feeds in Lotus Quickr (Domino) display only the last 10 entries. If you would like to see more entries in your feed reader, you need to modify the feed URL. Just add the keyword “pageSize=NN” to the URL where “NN” is the number of entries you would like to see.

E.g. if you want to see the last 50 entries instead of the last 10 entries for the following feed:

http://quickr.acme.com/dm/atom/library/_Ptestplace_RMain.nsf/view/_Ptestplace_RMain.nsf_FCD0EF97D625305B90525670800167213/feed?sK=modified&sO=desc

you need to modify the URL like

http://quickr.acme.com/dm/atom/library/_Ptestplace_RMain.nsf/view/_Ptestplace_RMain.nsf_FCD0EF97D625305B90525670800167213/feed?sK=modified&sO=desc&pageSize=50

Lotus Quickr Connector: Re-Enable Bubble Notifications

The Quickr connector displays a notification if a document has been successfully uploaded or if an error occured. However it could be that these notifications suddenly  no longer appear. This could be e.g. if another program disables notifications completely.

You can re-enable these notifications by setting the following registry key:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]
“EnableBalloonTips”=dword:00000001

After a restart of the PC (or the Windows explorer) the Quickr connector should display the bubble notifications again.

If you want you can configure the connector so that you will only be notified if an error occurs. For this go to the Connector preferences “Place Monitor -> Display only error is bubble notifications”.

If you want to set that preference automatically for all users you can set the following registry key on the machine:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Lotus Quickr\Desktop Integration\Monitor]
“NoShowInfoBubbles”=”1”

Lotus Quickr (Domino): Create a new SEARCH.NSF

It is not really new but just to make sure anybody is aware of it:

In earlier versions of Quickr, creating a new SEARCH.NSF for a  Quickr place was a manual process. With Quickr 8.5.1 and a current fixpack level (not sure which fixpack exactly introduced it…) you do have a QPTOOL command available to do the job.

Just run delete the existing SEARCH.NSF of a Quickr place and create it by running the following command on the Domino console:

load qptool createsearch -p <placename>

I recommend to do that every time you e.g. move a place from one server to another. In case you do have a Domino cluster, be also aware of the fact that the SEARCH.NSF is not a replica and needs to be created on all cluster members seperately (The QPTOOL REPLICAMAKER command will take care of that automatically).

Lotus Quickr (Domino): Do NOT use “/QP” as certifier

I think it is somewhere documented but just to make sure everybody is aware of it:

Do never use a certifier for organizational unit or organization for Quickr (Domino) users (also valid if using LDAP!) which is named “/QP”. “/QP” is used internally by Quickr and you will get into trouble in this case. E.g. if you will register a place with the command “qptool register -install” all directory users with such a certifier will no longer be able to access their places as they will be converted to local place users.

You will need to manually correct all these users by using “qptool changehierarchy” after each register command.

I am quite sure there might be other problems as well so the best would be not to use such a certifier at all.

Lotus Quickr (Domino): Maximum Size of Lists

There was a question regarding the maximum size of lists in Quickr (Domino) and the related parameters in QPCONFIG.XML. Here are the answers from support:

  • There is no enforced limit on the number of rows, if the “lists/sizeOfList” element is commented out in qpconfig.xml.  If that line is not commented out, then the maximum number of rows is the value of the “lists/sizeOflList” element in qpconfig.xml.
  • The maximum number of columns allowed in a list is 64.
  • The qpconfig parameter “lists/sizeOfSpreadsheet” means: maximum number of rows that can be in a spreadsheet that is used to import data into a list and the parameter “lists/sizeOfList” means the maximum number of items (aka rows) that a list may have.

Lotus Sametime: People Search not working

At a customer we did have the problem that the people search within the Lotus Sametime client was no longer working.

The users did get the message “Required directory or configuration information is missing” and in SAMETIME.LOG you could see the error “Open directory has failed – internal error (0x3)”.

The customer was using Lotus Domino as LDAP server. The problem could be solved by setting the LDAP timeout value back to 0 seconds (which is also the default). They set the value to “15” before.

You can change this in the Domino default configuration document under “LDAP -> Timout”.

After restarting the LDAP task the people search did work as expected again.

Lotus Domino: Change NIC Sequence Windows 2008 Server to be able to run server controller

If you do have multiple network interfaces (e.g. one for user, one for cluster, one for backup etc.) in a server with Windows 2008 you need to make sure that your main network interface is the first one in the sequence. Otherwise you might not be to connect to the Domino server controller. You will get the message “Either the Server Controller is not running on host <server name> or is not listening on port 2050” although the server and controller are running

To change the sequence of the network cards do the following:

  • Click on “Network and Internet” -> “View Network Status and Tasks (Network sharing Center)” -> Change Adapter Settings
  • Press “Alt-N”
  • Click on “Advanced” -> “Advanced Settings” -> “Connections: Change NIC Sequence”
  • Now put your the main network interface card on top of the list and save the configuration.