Setting up a 64-bit Crystal Web Service on a new/cloned server, every configuration step appears correct (TNS entry created, Java/environment variables set, IIS configured, 64-bit CWS and runtime installed), but requesting a saved report still fails with an HTTP 500 error or 'failed to load database information' — what's worth double-checking when everything looks right on paper?

Q: Setting up a 64-bit Crystal Web Service on a new/cloned server, every configuration step appears correct (TNS entry created, Java/environment variables set, IIS configured, 64-bit CWS and runtime installed), but requesting a saved report still fails with an HTTP 500 error or 'failed to load database information' — what's worth double-checking when everything looks right on paper?

Validate the actual TNS entry with a real tnsping test, not just by confirming it works through a GUI tool like SQL Developer — a malformed or incorrectly structured TNS entry can still work fine through SQL Developer's own connection handling while failing for CWS, and tnsping is a more reliable way to catch a genuinely broken TNS configuration than testing exclusively through a database IDE. Fixing the TNS entry's structure to pass a plain tnsping test resolved this exact HTTP 500 / 'failed to load database information' combination in practice.

Answer

Validate the actual TNS entry with a real tnsping <alias> test, not just by confirming it works through a GUI tool like SQL Developer — a malformed or incorrectly structured TNS entry can still work fine through SQL Developer's own connection handling while failing for CWS, and tnsping is a more reliable way to catch a genuinely broken TNS configuration than testing exclusively through a database IDE. Fixing the TNS entry's structure to pass a plain tnsping test resolved this exact HTTP 500 / 'failed to load database information' combination in practice.

← Browse Reporting and analytics questions