Tag: domino_v7

Funky replication message that might be an error message

One of our customers are experiencing some problems with some databases not replicating correctly. It might be connected to a recent upgrade to Domino 7.0.1 from 6.5.4 but we’re not sure. The problems can some times be fixed by clearing the replication history and manually replicating but that’s not really a long term solution.

To further troubleshoot I enabled the console log (set config console_log_enabled=1) and summary replication logging (set config log_replication=5) in the notes.ini via the Domino console. At the next scheduled replication I observed the strange messages (in bold below):

06-09-2006 10:49:35   Pushing dbname.nsf to servername/Organization dbname.nsf
06-09-2006 10:49:35   0 Bytes Saved from Field Level Replication
06-09-2006 10:49:35   0 Bytes Saved from Field Level Replication
06-09-2006 10:49:35   0 Bytes Saved from Field Level Replication
Unambiguous Note
NO Place Holders
Unambiguous Note
NO Place Holders
Unambiguous Note
NO Place Holders
Unambiguous Note
NO Place Holders
Unambiguous Note
NO Place Holders
06-09-2006 10:49:36   0 Bytes Saved from Field Level Replication
06-09-2006 10:49:36   0 Bytes Saved from Field Level Replication
06-09-2006 10:49:36   0 Bytes Saved from Field Level Replication
06-09-2006 10:49:36   0 Bytes Saved from Field Level Replication

I have never seen these messages before and it seems like they only appear with the databases we are having problems with.

If anyone has any information about these messages that they would be willing to share I would be a happy camper. I guess it’s also one of those times to be grateful that one can call Lotus Support!

Change to LDAP Directory Assistance (in Domino 7)

Or at least I think the change was in Domino 7… I never noticed it before since we have been using a custom DSAPI authentication module to work around the shortcoming in previous Domino releases.

The change is that the @Username function now returns the distinguished name of the authenticated user separated with slashes (/) even though it is a LDAP name and hence really separated by commas. This is über nice since it means we can scrap the custom DSAPI module and move the application from a Domino 5.x server to a Domino 7 server (we are having big issues deploying the DSAPI filter on Domino 7).

Sweet!

(For the record – my custom DSAPI filter does more than convert LDAP names separated by commas to names separated by slashes. It also handles dynamic LDAP groups composed on the groupOfUrls objectClass. If you need something like that let me know.)