SEE relies on driver and DLL changes in order to give it access to Windows auth, and these are likely to be the same changes any other auth-based applications make, in order to perform their tasks (like messing with the msgina.dll IIRC).
Have you tried swapping the order of install?
I've not installed both, so would recommend you log a case with both vendors to further your investigation.