Crystal Reports No Export Dll Found
Tanja Freeze
we have a software that we provide to customers that includes Crystal Reports as a feature to generate and export reports. All is working as expected. Recently, 1 user was able to generate the reports, but was unable to export the reports in any format.
I'm not sure which question I didn't answer. The exact version of .NET SDK Runtimes is 4.0.30319. It's already installed on the user machine and he is the administrator. CR is running well, the Export of the report inside of CR is what's throwing the error above.
if it is from the .rpt file then it is just a crystal report. if it is from a vendor menu it may trigger a stored procedure or program as I mentioned then the crystal report. Just about every one of our 800+ crystal reports integral to our erp system ran this way, with the system prepping the data.
Thanks for signing up! Keep an eye out for a confirmation email from our team. To ensure any newsletters you subscribed to hit your inbox, make sure to add newsl...@nl.technologyadvice.com to your contacts list.
Recently installed Dynamics SL SP3 client on new Win 7 workstations with Office 2007. Unable to export reports to Excel or PDF. Seems to hang, then get "Crystal Helper Executable Not Responding" error, followed by a couple ROI errors.
So glad I found Adam's suggestion above. Adding the Crpehlpr.exe fixed my issue. We were trying to print checks from Dynamics through a Crystal Report and we just started receiving a "Crystal Helper Not Responding" error and the checks would not print. I added this file to the Data Executive Prevention and it solved the problem. Thanks!
5. Browse to the Microsoft Dynamics SL program installation directory or the Microsoft Business Solutions - Solomon program installation directory. If you have an additional drive that is a mapped drive to this installation directory, you must add the file through both paths.
Two new OEM Windows 7 workstations. Having the same issue with MS Dynamics SL 7.0 on both. Process will hang, I go into Task Manager and see the report "not responding". I end the task, then "Crystal Helper Executable Not Responding" error appears.
Crystal Reports (Dynamics) was originally installed on the workstations. I uninstalled Crystal Reports and attempted to export, same errors appeared. I uninstalled Dynamics and re-installed Dynamics, same result. Then re-installed Crystal Reports, same result.
Can they print to file using a different format? There are different .dll files that handle printing to file for different file types. This would be a good test to help us to see if perhaps there is something wrong with the .dll file that handles the printing to excel file.
I inherited an application running crystal reports under VS2008, vb.net and Crystal worked just fine. When I compiled it under Windows 10 would work in development environment, but when published would fail at "SetDataSource()" - there were no errors at all; it would just hang there forever. I spun my wheels until I decided to compile it under 2017. Under VS 2017 I actually got errors which enabled me to get past it and eventually get them to work. So I ran a few reports and all seemed to work well. I compiled and released to Production.
When released, several users had reports fail. Not all were failing; just some. After investigating I noticed the repors with "subreports" were failing. The simple ones worked. So I go back to the drawing board and find that those reports were failing at "Report.Export()" which is where I exported them to PDF. I also tried using Report.ExportToDisk() but same result. It will just hang there.
Hi, Shannon. I posted that on every forum I could find. I was a banging my head on the wall for a while. To answer your question it is not particular to Atlassian. It was about a Crystal Report being run on Visual Studio 2017.
Thank you for letting us know! We don't tend to get a lot of users asking about Crystal Reports here, since our forum is dedicated solely to Atlassian software, but glad to hear you were able to resolve it.
I recently found myself needing to do some Crystal Reports testing on a virtual machine. The tests were successful on my laptop but we use a virtual machine running Windows Server 2008 R2 and IIS7 as a clean environment for testing. With these tests we were using both ODBC and SQL OLE DB connections to our database. The OLE DB connections were easy enough to replicate but we wanted to make sure our ODBC settings matched my laptop environment. To do this we used the Export feature in the system registry of my Windows 7 laptop.
Before I demonstrate this though I should explain what ODBC is. Open Database Connectivity (ODBC) is a standard way for connecting to databases. ODBC and the associated driver can connect to a database regardless of the database manufacturer or the operating system on which it runs.
3. You should now be within the Registry Editor. ODBC Data Sources are stored as keys within the Windows registry. Fortunately they are easy to retrieve. Your DSNs will be housed in two separate spots on Windows 7. (Other operating systems tend to place these in different files so you may need to hunt around.)
4. Once you have found the correct folder you can now export the desired connection(s). Right click the ODBC.INI folder and select Export to copy every ODBC key in the folder. You can also choose a more granular level of exporting by selecting one DSN within the folder at a time. Unfortunately the CTRL key cannot be used to select multiple files for one export.
Once the Export is saved to disk it will create a .reg file. This file can be opened and examined with a text editor like Notepad. Within the file you will see the various properties of a DSN like server and database names, as well as the selected database driver.
With the .reg file open you will now need to modify the file. As you have seen above when you export the ODBC Data Source you only get the DSN properties. However, when you insert this code into the registry on the target machine the DSN will be inserted into the registry but will unavailable elsewhere. To ensure you will have access to the DSN within your Crystal Report file, the ODBC Data Source Administrator and other places you are using ODBC Data Sources you will need to prepend the following code to the file:
5. You can now copy the .reg file to the destination computer for installation. Before you install though you might want to open the file and compare the DSN properties. It might be possible the target computer contains different settings than the export file. You can edit the .reg file to match before deploying the file.
7. The last step is to verify the install. Open the Registry Editor on the destination computer and navigate to the correct DSN folder path. Confirm that your ODBC Data Source is listed in the folder. Close the ODBC Data Source Administrator and re-open it to confirm they are accessible there as well. You can then tweak the DSN further by using the Configure button if need be.
That is it in a nutshell. In this tutorial we have exported ODBC Data Source connections between two computers running different Microsoft operating systems. We saved ourselves time and headaches by ensuring our connections are identical between the two machines.
About Ken Cenerelli
I am a technical writer/programmer writer/content developer, .NET developer, Microsoft MVP, public speaker, blogger, and Microsoft Azure nerd. I blog about technology at kencenerelli.wordpress.com and am on Twitter via @KenCenerelli.
I know this is an older thread but I was wondering if the export process takes into consideration an assigned static TCP\IP port rather than the typical 1433. The Registry Key contains does contain a number of accurate string values for the existing connector(DB, Description, Driver, Last User and Server).
So looks like the issue is only when I exported directly from crystal. When I scheduled the report it was exported to PDF and sent out with no formatting issues.
Not sure what the difference would be.
If you have access to SAP Support, you can look for SAP Note 2165260, which is the master list of all of the registry settings available to control aspects of Crystal. There are a number of them that work with PDF exports.
Definitely a web app. But in this case it looks like I just need to make a change to text boxes that have the issue of no wrapping the text correctly (text gets cut off on the right side when exported to PDF).
Thank Mike, I have seen that but it doesn't solve the issue of wanting to get the formatted survey submission. I want to send the pdf file on to someone who doesn't have immediate access to the database and just needs something simple and easy to read.
So, if we think about the option of the Blog, then could you have a hidden field; that worked behind that scenes, which contains the person's email that you want to send the "simple" PDF to. Maybe edit the python script to look for the field that contains the email address you want to send the PDF form to?
Even though this person does not have direct access, the PDF could still be created by the process/script and then emailed over to them; since you would hard code in the email address within the hidden field.
However, if the "person" you are sending the PDFs to could change to a list of multiple different people, then you would need to have some sort of trigger; if() function, that would allow the form to determine which individual would receive the PDF file through email based on answer to a question within the form.
There might also be another method you could use, if you trust the person filling out the survey, and that would be to use this post below to create an email that contains the information the end user needs to review within it that could be sent prior to submitting the form?
We frequently run into this requirement, client wants to see the "field datasheet" submitted with the project deliverable, usually as an appendix of the report. Some client's accept a feat. class/table dump into a single excel table, some don't. In reality, a compiled single table that's produced by dumping the feat. classes and tables in the service is MUCH more useful, but none-the-less some people still like to see the raw "field datasheet".
7fc3f7cf58