Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Database Expert Crashes when Pressing Links

I have Crystal 2013 installed and it crashes when I go to Database Expert and press links on any report that has multiple tables or commands.  I have searched the web and tried many of the suggestions that sound similar.  The only thing that comes to mind is the laptop I am using did have Crystal 2008 installed and it was then uninstalled and 2013 was installed on it.  Maybe the original 2008 is causing a conflict but I cannot confirm what the conflict might be.

Former Member
replied

Eric,

We recently identified the crash on Table Linking could be caused by unregistered .dll. I've created SAP KBA https://service.sap.com/sap/support/notes/2221121

Here is the solution:

Cause


Visual Link Editor engine - vle.dll is not registered.

Resolution


Verify if the vle.dll binary exists in:

(for 32 bit platform)

C:\Program Files\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86

(for 64 bit platform)

C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86

If the dll exists, try to register it. Here are the steps:

  1. Start > Run
  2. Type the following command:

(for 32 bit platform)

regsvr32 "C:\Program Files\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\vle.dll"

(for 64 bit platform)

regsvr32 "C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\vle.dll"

If you get a Success message then restart Crystal Reports again and test the table linking.

If the registration fails with an error then try to run the Command as Administrator:

  1. Navigate to C:\Windows\System32
  2. Right click cmd.exe and select Run as Administrator
  3. In the command line copy the

(for 32 bit platform)

regsvr32 "C:\Program Files\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\vle.dll"

(for 64 bit platform)

regsvr32 "C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\vle.dll"

If the registration still fails try to register it using Dependency Walker http://www.dependencywalker.com/faq.html

"The best way to debug a module that fails to register is by opening REGSVR32.EXE in Dependency Walker rather than your DLL. Then choose to start profiling (F7). In the profiling dialog, enter the full path to your DLL in the "Program arguments" field. For "Starting directory", you may wish to enter the directory that the DLL resides in. Check the options you wish to use and press Ok. This will run REGSVR32.EXE and attempt to register your DLL. By actually running REGSVR32.EXE, you can see more types of runtime errors."

Hope it helps,

Vitaly

0 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question