Crystal report version 2020 - SQL always on failover

[Keerthir]

Hi Everyone,

We are using Crystal reports version 2020 with MS OLE DB driver version 18.4.

SQL is always on with failover database (multisubnetfailover set as true).

This is sporadically throwing error in Crystal reports alone as below. All other applications connected with same always on is working fine in the same environment.

Appreciate your help on this.

Thanks

[DonWilliams]

Have a look at the Database support Excel file here:

https://www.sap.com/documents/2020/06/b2ec5eaa-9d7d-0010-87a3-c30de2ffd8ff.html

Be sure to use the one supported for your MS SQL Server.

CR keeps the log on info in memory according to whats saved in the RPT file, when the report is idle it caches the connect info to release the connection. MS Caches the connection info also so if one is idle it releases the connection and puts it into a pool to be used by another request to connect. CR doesn't support this feature.

So if your connection is redirected to another fail over server only way is to refresh the report by setting location using the same log on info, the client will redirect accordingly.

CR has no option to do it automatically, it assumes the connection info doesn't change.

[Keerthir]

Thanks for your reply.

Whether Crystal reports supports listener name to connect to database with Multisubnetfailover is set as true?

Appreciate your response on this. Thank you

[JWiseman]

Hi Don, would using the ODBC SQL Server Wire Protocol be a solution given its pooling options?