Page Comparison

...

There will normally be a delay between clicking the connect button and receiving the error message if it is connectivity issue rather than an authentication issue. This is because in the case of an authentication issue, the connection is made immediately but the server refuses login, whilst in the case of a connectivity issue the SQL Management Studio will try over and over to connect for around 15-30 seconds before giving up and reporting the error.

...

Anchor
SQLNativeClient SQLNativeClient

SQL Native Client Version

If you are able to connect using the credentials with SQL Management Studio, and Jiwa the application is able to connect but generating reports produces the "Logon Failed" error - then the problem is the SQL Native Client has been removed from the machine, or the SQL Native client version is no longer the version Jiwa expects.

Jiwa installs with the SQL Native Client 11 and when generating crystal reports Jiwa will force the database provider to be "SQLNCLI11" - SQL Native Client 11 - so if a user or other software has removed or change the version of SQL Native Client then crystal reports will generate this error.

To rectify this, either re-instate the correct version of SQL Native Client, or use one of the following plugins to modify Jiwa's behaviour to force Crystal Reports to instead use the OLEDB provider - making report generation in Jiwa no longer dependent on the SQL Native Client.

07.01.00.00

07.00.175.00

Connectivity Error

In the case of a connectivity error (unable to connect using the credentials with SQL Management Studio ), then there are 3 troubleshooting steps we can take in the case of a connectivity error.

...