Working during this large migration we discovered that a bug exists on 6.5.6 and Fix Pack 2 has a problem with Unique Organizational Unit Names. In a previous post (link.) I mentioned how to move away from Unique organizational units. Well it seems that Lotus has resolved this problem but unexpectedly.
I'm on an engagement where every user has a unique ou. This is a requirement for this particular customer and I won't go into details. Well, when utilizing a C++ API call as a part of the rename process, we have determined that the end users name changes but the AdminP rename process would drop the Unique OU value. Well if we find any strange things with the rename we try to do the same thing manually. Well this was not successful either. When we manually rename a user we saw an error in the Admin4.nsf after attempting to complete the move request. This error is "The new name in the supplied Name Change Request does not match the subject name in the supplied certificate".
Well this is something that we found in Domino 6.5.6 Fix Pack 2. We attempted to upgrade to 6.5.6 Fix Pack 3 and it did not matter. The problem still existed. Next, we went to 7.0.3. In this case, we discovered the problem still existed. We engaged support from IBM and discovered that this is a bug. The following is a quote from IBM
"This technote and your test prove that there is a Domino issue going on with these servers. It is not related to the OS. According to the documentation the problem is fixed in Domino 702. We also know that it was a regression in 703 that is scheduled to be fixed in Domino 7.0.4.( SPR# WMUH77GJ8E). For now, I would suggest upgrading to Domino 7.0.2."
We have tested this on 7.0.2 and it is working fine.
Comments (0)Perry Hiltz June 20 2008 03:09:11 PM