Forum Discussion
Mike_Aracic
Employee
14 years agoThe issue was resolved once the user uninstalled the security patch described here. Its not clear whether running without said patch in place represents a significant risk. It may be possible to further patch SQL Server or change the JVM to avoid this issue. See article )