Many warning messages like the one below are being written to the DWP logs:
U0003592 Status: '01S02' Native error: '0' Msg: 'Cursor type changed'.
This message is occurring in the DWP logs because the SQL Server Native Client is being used for the DB connection and not the 'SQLSRV32.DLL' ODBC driver. The message has no impact on Automic system processing.
Automic does not recommend using the Mars_Connection with Microsoft SQL Server is currently not recommended (Reason: in very rare instances, database deadlocks are not reported to the calling application causing the effect during Automic processing that activities can be started twice).
SQL Server Native Client 10.0 (sqlncli10.dll) fully supports connectivity to and the functionality of these versions of SQL Server: 2000, 2005, and 2008 (Microsoft recommends using it for all three platforms).
SQL Server Native Client (sqlncli.dll) and the "SQL Server" driver (sqlsrv32.dll) also supports connectivity to SQL Server 2008 and SQL Server 2005; however, you are not be able to access some of the new functionality of SQL Server 2008 using "sqlncli.dll" or "sqlsrv32.dll", nor are you able to access some functionality of SQL Server 2005 when using "sqlsrv32.dll".
This message is only a warning. It appears when 'S'(static cursor) is defined in the connect string in the first position.
It does not appear when 'N'(the cursor only scrolls forward) is defined in the connect string in the first place and Mars_Connection=Yes.