Crystal Closing without Crash Message in Database Expert when browsing connected database tables

[former_member1115203]

Recently changes were made to allow us to run Crystal against a specific database through eVPN from home.

Prior to the change everything worked perfectly from virtual machines or on site but not through the eVPN.

Post change we can now run reports and even modify them using existing tables from virtual machines, on site, or through the eVPN.

However if we try to use the Database Expert to view new tables to pull into reports Crystal closes without any message from virtual machines, onsite or the eVPN.

Crystal still works properly when connecting to other data sources.

Can anyone tell me what might be causing this behavior difference now?

What does Crystal do differently when browsing with the Databse Expert than connecting to run a report?

What might the connection teams have configured incorrectly when modifying the tunnel connecting us to this database.

I am running Crystal Reports 11.5.8.826

[mynynachau]

Thank you for visiting SAP Community to get answers to your questions. Since you're new in asking questions here, I recommend that you familiarize yourself with https://community.sap.com/resources/questions-and-answers (if you haven't already), as it provides tips for preparing questions that draw responses from our members.

Should you wish, you can revise your question by selecting Actions, then Edit (although once someone answers your question, you'll lose the ability to edit the question -- but if that happens, you can leave more details in a comment).

Finally, if you're hoping to connect with readers, please consider adding a picture to your profile. Here's how you do it: https://www.youtube.com/watch?v=F5JdUbyjfMA&list=PLpQebylHrdh5s3gwy-h6RtymfDpoz3vDS . By personalizing your profile with a photo of you, you encourage readers to respond.

Best regards

Mynyna

SAP Community moderator

[former_member1115203]

Unfortunately that is not the current situation. It is not the act of adding tables that causes issues. It is the act of attempting to view the tables in the first place. It is also something that was working prior to tunnel changes and stopped working after though the firewall team cannot determine the cause.

[vitaly_izmaylov]

You may wanna try CRLogger:

https://apps.support.sap.com/sap/support/knowledge/public/1603398 - How to perform a trace in Crystal Reports and in .NET SDK's application using crlogger? [Video]

It captures communication between CR and Datasources and you may find more details.

ODBC trace is another option

[vitaly_izmaylov]

We used to have similar problem with IBM DB2 ODBC driver:

https://apps.support.sap.com/sap/support/knowledge/public/en/1621593

it required Write Access permission.

Note: look for registry keys

• For Crystal Reports XI R2:
  • HKEY_LOCAL_MACHINE\Software\Wow6432Node\Business Objects\Suite 11.5\ (on 64 bit OS)
  • HKEY_LOCAL_MACHINE\Software\Business Objects\Suite 11.5\ (on 32 bit OS)
  • HKEY_CURRENT_USER\Software\ Business Objects\Suite 11.5\