Dib clone causes -1418 errors in IDM when creating a new driver set or adding a server to an existing driver set

These errors are reported if the DirXML-ServerKeys attribute value on the pseudoServer object is invalid. This attribute is new to Identity Manager 3.5.

• The assumption is that under some circumstances the attribute is invalid due to the DIBClone process
  
• The problem will occur when using NICI files which do not belong to the DIB
  

Use of the incorrect NICI key files could occur when building a temporary tree on a server, copying the DIB from a different server to the server where the temporary tree is installed. Then starting eDirectory. The NICI files on the destination server do not belong to the DIB which was opened. Replacing the NICI files with the correct ones will not work after the above errors have been observed.

When the DIRXML-ServerKeys attribute is invalid IDM can not function.

When moving a DIB or DIBClone between servers the NICI files which belong to the source server must accompany the DIB. (Netware: sys:\system\nici; Windows: windows\system32\novell\nici; Linux: /var/novell/nici)

To solve the problem, contact Novell Customer support so that they can use the utility DSDump to remove thehidden attribute (the attribute value on the pseudoServer cannot be seen using iMonitor). IDM will then regenerate the key. Also, do not try to use DXCMD to regenerate the DirXML keys because this will core eDirectory.

In the case of a DIBClone, ensure the NICI files from the source server are copied to the destination server before starting eDirectory on the destination server. If practical in terms of time and DIB size, redo the DIBClone process; delete the NCP Server object for the DIBCloned server and create a new DIBClone.

This problem has been reported to development.