This past spring I upgraded our IDM implementation to v 4.0.1.

We had an issue where upon User creation the GroupWise accounts were
not always created. We found they would create if the User was in a
remote container but not a local container. It was suggested we take
the addition of the Post Office out of the User Template. We did and
thought that solved the problem. It did not. If the remote link is
slow the account will create. If it is fast it will not create.

A Consultant said that IDM 4.0.1 was faster than 3.5 and the creation
of the GW account could not complete as some attributes got over before
others thus giving the impression the User already existed. Here is a
snippet from the log:

OK dumb question but can you do any throttling to slow this big boy
down??

<nds dtdversion="2.0" ndsversion="8.x">
<source>
<product build="20090305_0422" instance="GroupWise" version="3.5.3
(linux)">DirXML Driver for GroupWise</product>
<contact>Novell, Inc.</contact>
</source>
<output>
<status code="javax.naming.NameAlreadyBoundException: The context
already exists. DOAA-ATL.DOAA-POATL..; remaining name
'DOAA-ATL.DOAA-POATL.'"
event-id="JDBCOracleHRToDOAA#Publisher#42476:4cab3876-45bb-4a21-9ff2-5415089b3ca7"
level="error" type="app-general">
<code>javax.naming.NameAlreadyBoundException: The context already
exists. DOAA-ATL.DOAA-POATL..; remaining name
'DOAA-ATL.DOAA-POATL.'</code>
<description>Name already exists in GroupWise:
\DOAA_TREE\DOAA\AUD-AUG\Matthews</description>
<object-dn>\DOAA_TREE\DOAA\AUD-AUG\Matthews</object-dn>
</status>
</output>
</nds>
[06/27/12 16:35:30.839]:GroupWise ST:Resolving association references.
[06/27/12 16:35:30.839]:GroupWise ST:Processing returned document.
[06/27/12 16:35:30.839]:GroupWise ST:Processing operation <status> for