I've been running IDM 3.0.1 for about a year now.
I have fairly stock driver policies, nothing too exotic, but please
let me know any details you need.

Last week, I upgraded to 3.5.1.
AFAIK, I followed the entire upgrade procedure correctly and it seemed
to work just fine.

However, I'm now having problems with both new and existing user
entries. Specifically associations, I think.

I initially migrated my AD driver to 3.5.1, but then saw these errors,
so built a new 3.5.1 AD driver from scratch and am seeing the same

Basically, for a new user on the publisher channel, it fails due to:
[03/03/08 10:36:33.386]:AD-Corp PT:
<nds dtdversion="3.5" ndsversion="8.x">
<product version=" ">DirXML</product>
<contact>Novell, Inc.</contact>
<status event-id="AD-Corp##11875ee4827##0" level="warning">Code
(-8019) Operation vetoed on unassociated object.<application>DirXML</

It can't possibly already have an association, it's a completely new

For existing users, it's finding an association, but for the other AD
driver, and also failing:
<nds dtdversion="2.2">
<product version=" ">DirXML</product>
<contact>Novell, Inc.</contact>
<modify-password class-name="User" event-id="AD-
Corp##11875d68b33##0" src-
<password><!-- content suppressed --></password>

If I remove the association, it fails again, but without the
<association> tag.

I don't have a lot of in depth experience with troubleshooting these
drivers, they just tend to work, so any help would be greatly appreciated.

Thanks much!