by Michael Urspringer
If you are using Domino LDAP together with Quickr and you create new users by just manually creating new person documents, you have to make sure that you make the user names hierarchical. So e.g. add “Firstname Lastname/Acme” as the first line in the username field, and then “Firstname Lastname” as the second line.
As Quickr does not support flat names you will see strange things happening otherwise (e.g. in the member list “No Access” is displayed for members with a flat name etc.)
A customer today had the problem that he could not connect to the Quickr server via the MS Office connectors. He got an error 12029 from all Office products while the Explorer and Notes connectors just worked fine.
In this special case the local firewall on the client caused that issue. The firewall blocked all network connections from the Office suite. After allowing Office to establish a network connection everything worked fine again. So if you have connectivity problems don’t forget to check the firewall settings on the client.
To change the maximum file size limit for uploads in Lotus Quickr (Domino Services) you have to do this on several places:
Because of the default settings the maximum file size for uploading is limited to 10 MB if you do not change these settings.
I would recommend to leave the fields in the server document empty and only configure the maximum file size within Quickr.
[Thanks to my collegue Matt Newton]
For Quickr 8.1 you should make sure that you have set the option “Internet Protocols -> Domino Web Engine -> Use UTF-8 for output” to “Yes” in the server document of the Domino server.
Otherwise you might observe several issues e.g.
This might happen with special characters of other languages as well.
I recently ran into strange problems with response documents in the Quickr discussion folder. The main topics appeared correctly but all response documents did only appear in the index view and not in the discussion folder itself.
Every time I ran “load qptool -f -p placename” on the console all missing response documents magically appeared again.
The reason for that strange behaviour was the ODS 48 of the Quickr databases on this server. As soon as I switched back the ODS to 43 (“load compact -r”) and restarted the server new response documents were visible again.
You might need to run “load qptool -f -p placename” to make sure that older docuemnts will appear also.
SNAPPS has finally updated their templates for Quickr (Domino Services) to be compatible with Quickr 8.1.
While initiating a chat session in the embedded Sametime client of Lotus Notes 8.0.1 I got the message “A Runtime Error has occured. Do you wish to debug? Line: 0 Error: Object expected”.
This also happened when another person started a chat with me.
The solution was to check the following options in Internet Explorer (Tools -> Internet Options -> Advanced):
Disable Script Debugging (Internet Explorer)
Disable Script Debugging (Other)
I also unchecked the option “Display a notification about every script error”.
After that the embedded Sametime client worked as expected again.
Quickr 8.1 (Domino Sevices) in German (and other Tier 1 languages) has been released yesterday. You should be able to download them from Partnerworld now. The part number for German language is C1CF8DE. The code seems to be on hotfix level 3.
The other part numbers can be found in this document.
You can add Quickr places automatically to the Quickr connectors via an HTML link by using the following syntax for the link:
quickr://server.acme.com/library/[@P_PLACENAME_/@RMain.nsf]
where “_PLACENAME_” must be replaced by the URL and “server.acme.com” must be replaced by the full qualified name of your server (including port information if other than port 80 is used).
For SSL connections you can use “quickrs:” instead of “quickr:“.
If the server is not already known to your connectors you will be asked for the credentials.
This syntax is only valid for Quickr (Services for Domino). If anyone has a hint how to do this with Quickr places on Quickr (Portal Services) please leave a comment.
You can use such a link e.g. on the welcome page of your place to make it easier for your users to add the place to their connector.
Today I had to deal with some strange single-sign-on problems between Websphere Application Server 6.1 (underneath of Lotus Connections) and Quickr (Domino) and Sametime together with a Domino LDAP directory.
Although SSO between the Domino servers worked without a problem, I was logged out as soon as I switched between the Websphere and Domino world.
We already experienced some problems while configuring the federated repositories in WAS 6.1. as we were unable to enter “O=Acme” in the field “Distinguished name of a base entry in this repository” at the repository reference page although this was our base certifier.
The certifier was copied into the Domino directory of the LDAP server; we could see the organization and all underlying users in a LDAP browser and we were able to login with these users into Lots Connections. Only SSO to Domino was not working.
Enabling SSO debugging on the Domino server (adding “debug_sso_trace_level=2” and “websess_verbose_trace=1” to NOTES.INI) showed that the token generated by the WAS server has two times the organization in the user name (e.g. “CN=First Name/O=Acme/O=Acme”). In the LDAP browser you also could see that the entry “O=Acme” was listed below all other LDAP entries and not near the other organizational entries in the directory which also was very strange.
Looking at the certifier attributes in the LDAP browser then revealed that NO attributes existed (including the “O” attribute). So this was the explanation why you could not add “O=Acme” in the repository configuration.
Looking then at the (rather old, from 1995) certifier document in the Domino directory I realized that in the field “Issued to:” there was an entry like “/O=Acme”. Other (newer) certifiers showed something like “O=Test” in this field. I then re-saved the certifier document with a Notes 8 client without changing anything else.
And voila … the field “Issued to:” then showed the correct value “O=Acme”; in WAS you were able to set the parameter correctly and single-sign-on worked as it should.
So be aware if you are using Domino LDAP servers with old certifier documents (which you might have at most of our long-term Domino customers).