Error Detected by export DLL for pdf

Post Author: netonomous
CA Forum: Exporting
We have a Win 2000 box with this feature working with no problem.
I am getting an error exporting to .PDF when using .NET 2 Business Objects. Quite the opposite of your situation. Any ideas? My temp folder is under C:\Windows\Temp and the error I receive is
Error in File C:\WINDOWS\TEMP\TSRDetail {F7EAB0D7-408F-4787-A1FE-5086F7199CB9}.rpt: Error detected by export DLL: This is on a Win 2003 box Service Pack 1 with IIS 6.0 with ASP.NET Framework for Crystal using an Oracle Database. Excel exports work ok.
Thanks much in advance.

Similar Messages

Error detected by export DLL. Microsoft Windows Small Business Server 2003 SP 1

Post Author: craig.engelbrecht
CA Forum: .NET
I have an Excel report that stopped working on a live environment a couple months ago.When I run the report I get the error 'Error detected by export DLL'.The server is running Microsoft Windows Small Business Server, Service Pack 1 and is using Crystal Reports 9.I am unable to replicate this error on other environments running the same configuration.I tried installing 'crnet11win_en.exe', even though this was a fix for Windows Server 2003 SP2, still no luck. Does anyone have any ideas on what is causing this and how it can be fixed?? Thanks,Craig

Thanks Ludek
We found the issue after doing control tests, here.
We found that our crystal viewer, developed in .NET 2003, does not work with XP SP3, even with the fix crnet11win_en.exe.
Our control test, was:
Ran report with XP SP2, exported ok
Upgraded pc to XP SP3, then ran report again, Report failed to export, with error message as described.
Had a crystal viewer set for using .NET 2005 files, but not yet ready for deployment to users, tested and was able to export to excel using .NET 2005 with XP SP3.
The issue seems to relate to exportmodeller.dll, which was the issue in the past when XP was upgraded and stopped the export function from working before.

Error detected by Export DLL, when trying to export to excel

Hi All
We are having an issue that has occured recently where some of our user's are unable to export to excel. They were working ok.
The crystal viewer was originally designed using Framework 1.1 (vs.net 2003) and we have applied the hotfix to the user's pc called:
crnet11win_en.exe
Which fixed the issue originally, by upgrading the ExportModeller.dll to 9.1.1.528.
However in this case, even after running the patch, the user's pc is still unable to export to "excel", works ok for PDF and WORD, just not excel.
Tested the report on 2 other pc's and the report is able to export to excel.
Just not on that user's pc, is anyone able to give advice of what could be stopping the user from running the report.
The user is on Windows XP SP3, but we been informed that other user's with XP SP3 are able to export to excel with no problem.
Thanks in advance for any help or advice that you can give.
Regards
Chris
Edited by: CMThompson on Feb 22, 2010 11:52 AM

Thanks Ludek
We found the issue after doing control tests, here.
We found that our crystal viewer, developed in .NET 2003, does not work with XP SP3, even with the fix crnet11win_en.exe.
Our control test, was:
Ran report with XP SP2, exported ok
Upgraded pc to XP SP3, then ran report again, Report failed to export, with error message as described.
Had a crystal viewer set for using .NET 2005 files, but not yet ready for deployment to users, tested and was able to export to excel using .NET 2005 with XP SP3.
The issue seems to relate to exportmodeller.dll, which was the issue in the past when XP was upgraded and stopped the export function from working before.

Crystal Report Export To Excel Error: "Error detected by Export DDL"

I have a windows application in .Net 2003, whenever i export the crystal report on my development machine or other windows xp machines it runs smoothly, but when i deploy the application on client's machine having windows vista installed, it displays error of "Error in file........., Error detected by export DLL"
pls help me.

First thing to look at is the wiki [What versions of Crystal Reports are supported on Windows Vista in VS .NET?|https://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=64259646].
Note that CR 9.1 is not supported on Vista. And if CR 9.1 is not supported on Vista, any earlier version of CR will also not be supported on Vista. That is not to say the app(s) will not work, they may - or not. You never know... and we have no experience with these types of installs as we don't need to have it.
Next, have a look at KBase [1205312 - "Error detected by export DLL" while exporting to Excel after applying SP2 on Windows 2003 Server|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333233303335333333313332%7D.do]. Not exactly the same OS, but I'd follow through on the suggestions in that KB anyhow.
Finally, If this app works on a Vista box when a VB 6 app is not installed, compare the dlls loaded between that box and the one that has both apps. Use [Modules|https://smpdl.sap-ag.de/~sapidp/012002523100006252802008E/modules.zip] to do that.
Other than that, only suggestion I have is to upgrade to a version of CR that does support Vista.
- Ludek

Error detected by database DLL. [On Page Server: server_name]

We have a web app that launches Crystal Reports (version 8) in the crystal reports viewer that plugs into IE (version 6.0 & 7.0). The reports connect to SQL Server 2005. We have some reports that work but we have 2 reports that used to work but stopped working since we made the change. Whenever we launch the report from the browser we get
u2018Error detected by database DLL. [On Page Server: server_name]u2019
This is very frustrating as we have
1.
Recreated the reports from scratch
2.
Checked the connection to the database
3.
We connect to the live server using Terminal Server and we installed Crystal on the terminal server and the reports run fine there.
4.
We had the report s working after the modification but for some strange reason they stop working and we start getting the above error
5.
Also we have noticed that sometimes when we remove the query string (?sf=...) to the report it works (actually we get the login screen - but it works fine after that).
6.
Please note that the reports with the query string work fine on our test server and on my local machine connecting to a local copy of the database.
I am now very confused and would be very grateful for any help on this issue.
Best regards
Jose

Well, after much search I found and fixed the problem.
The problem was that I connect to two databases as part of a general view and our live server did not have the 'Crystal' user defined for the second (and less used) database. Once we defined the user on this second database it worked.
One comment I would like to make is that the friendly error message 'Error detected by database DLL. [On Page Server: server_name]' is not as good as the 'raw' message that we get when we finally connected Crystal to the live server database and try to run the report - it went something like 'you are missing a connection to the database database_name' - I wished I had this error from the start.

Error in Pre- Export methods for a request

Hi All,
I am getting an error while releasing a request, its giving
"Error in Pre- Export methods for a request DM0k.....". Could you please tell me why and how can I rectify that?
Thanks.
NA

Please go through as per the link
[SAP Transport Request |http://www.sap-basis-abap.com/sapbs008.htm]
thanks
G. Lakshmipathi

Error in pre-export methods for request

hi...
while releasing the TR we are facing this error msg..." Error in pre-export methods for request" it is showing lock in fornt of the TR.neither be able to delete the TR ....
do reply as soon as possible..

Hi,
I had the same error PU238.
What I did was:
Execute SE03 to unlock the object.
Then execute the program 'RS_STREE_OBJECTS_TO_REQ_GET', not sure what it does.
Afterwards, it worked perfectly.
Hope that information helps you.
Regards,

Setting default export quality for PDFs in Pages 5.0

Hi,
Anyone know if it is possible to set a default export quality for PDFs in Pages 5.0. Even if it remembered the last used setting that would be helpful.
Thanks,
Nick

OK, I have managed to get higher quality images from the PDF renderer. Here is what I have found:
1) The PDF renderer in Reporting Services 2005 will size all images that it is given at 96 DPI no matter what DPI the image is when you pass it to the renderer. That means that a 300 DPI image or even a 600 DPI image will be sized in the PDF as if it is only 96 DPI. That means your high DPI image will render much larger than you expect.
So you might expect a 300 DPI image that is 6.5 inches wide to render properly at 1950 pixels. Yet, the PDF renderer will size it as it were 96 DPI which would make the image 20.3 inches long!
2) There is good news though. Despite sizing the images as if they were 96 DPI, the PDF renderer appears to render higher DPI images at a higher quality than 96 DPI. So despite the sizing being wrong, the image actually is rendering at a higher quality.
This means that you should size the image to the proper number of inches based on 96 DPI calculations. Then you can use Bitmap.SetResolution to set your images to at least 300 DPI. That should give you a higher quality image that is the proper number of pixels to fit properly in your report.
I am able to do all of this sizing dynamically because I am using objects as my data sources, but I am sure there are VB functions you could use in the report itself to accomplish the same task.
It is late, and I've been at this project all day long, so forgive me if I have explained anything poorly or gotten any concepts long. Yet, at this late hour, I believe this is what the renderer is doing.
I hope this helps someone else in the future, or at least points them in the right direction.

I receive error message when exporting or converting pdf to word

i receive error message when exporting or converting pdf to word

Me too and I cannot find online support of any kind. It was hard enough to get to find this forum. Is there a tech support chat or phone number anyone can provide? Thanks!

String or binary Data would be truncated. Error detected by database DLL

Having problems generating two reports in Crystal Reports v8.5. I can run it on my machine and one on one of my Terminal Server(TermA). However when I tried to generate the same two reports on my second terminal server(TermB), it crashed and I get the following error messages: ODBC error: String or binary data would be truncated and Error detected by database DLL We have one set user ID and password to generate all of our Crystal Reports.
Steps taken:
Reinstall Crystal on TermB server and did a fresh installation of Crystal 8.5 on another workstation. Ran the reports and the result were the same (unable to generate the report) same errors messages.
Please HELP...
Thanks.

Terminal Server was not supported in CR 8.5

Is there something new about the U3D. Could we export 3D for PDF efficiently?

Is there something new about the U3D. Could we export 3D for PDF efficiently?
Thx

What are you asking?
Adobe's software range doesn't create U3D files anymore. You have to use third-party applications.

Error 109 when Exporting as a PDF... please help!

I have an InDesign file that I want to export as a PDF.
I've done this MANY times before; however, now the PDF that is generated from within InDesign that says, "The document could not be saved. There was a problem reading this document (109)".
How can I resolve this? The file is only 1.5 Mb (2 pages)... a simple newsletter (mostly text... no bizarre graphics).
I'm on a 2 Ghz MacBook Pro running CS2 (with all patches & updates applied) on OS X v10.5.8.
Also: any idea how to actually send an email to Adobe support? My account information needs updated, but the fields will not allow me edit or select the content. (Tried both Safari and Firefox with the same results... figured it was a web site issue.)
Thanks for any help!
Kind regards,
Jeff

2 suggestions:
move job to local computer not network drive
copy all objects and paste into new doc and retry (may need to restart in between to keep system tidy)
I presume you are saving resulting file to easy local location where you are not likely to get permissions errors etc.

Error message when combining files for pdf conversion

I have been combing several files into a single pdf with ease. Then today I try to do what I have been doing all along and I get a message that says an unknow error has occured and to try again later. Well I have tried again later several times and hours apart. Please help me to combine my files again.
Thank you,
Lisa

Hi lisalisame,
I am sorry for the trouble with Combine tools.
Please send us your files so that I can help you. If your files are too big, then just send us small one and I will share how to shre your big files with us using https://files.acrobat.com (clicking "Share Files" icon).
https://adobeformscentral.com/?f=qJiclooYWGGNFtWfj8g3wg#
Thank you.
Hisami

Error -108 while exporting video for Apple TV

Anyone have a clue why I would be getting at error -108 in QuickTime Pro while converting an MPEG-4 file to Apple TV format? I was just doing File/Export and selecting "Movie to Apple TV" as the export format.
I'm using QT Pro on Vista. The full error message is "Error -108: An unknown error has occured." It came up (probably) at the very end of the export. (The export seemed to running fine, and it was past 50% when I left to go out for awhile. The error was up on the screen when I came back.) The source video is about 2.5 GB, and should be a fairly normal MPEG-4 video, 30fps, 720x480. The error message itself isn't very helpful, obviously.

sorry, are you sure?
when I bought my ATV I compared ATV1 and ATV2 and the video performances are the same, infact I play my video in 1280x720 with my ATV but it is convert with toast.
I compared the same video in ATV (720p) and in mpeg 2 (1920x1080 25 Mb/sec) with my medley 4geek and the quality is the same.
Sorry, am I sure about what ?
Apple TV 1 will only play 720p movies at 24 or 25 fps up to 5 Mbps or 960 x 540 at 30 fps, the Apple TV will play video at all frame rates at 720p and around about double the data rate.
Are you sure your camera produces mpeg2 files. If so you might not see an awful lot of difference between the original and the converted videos because h264 is significantly more efficient than mpeg2, although I'd expect you to see some. If your files from your camera are actually h264 wrapped in an mpeg2 container then I'd expect you to see more difference.
another problem, is impossible to create a video .mpe2(fullhd) with imovie, for that I bought ATV.
I don't fully understand what you are asking here.
why toast convert correct to ATV and apple software no?
Possibly because when you are using toast you are choosing a datarate that is compatible with the Apple TV (ie 5 Mbps or less), whereas if you are using (for example) quicktime preset for the Apple TV, you might be making files that are compatible with the Apple TV 2 but not the Apple TV 2, but it's difficult to say without knowing what settings you are using.

Is the Export Quality for PDFs in Reporting Services 2005 only 96DPI?

I have been fighting with Reporting Services all day, and despite setting the PDF output quality to 300DPI, I have noticed that the image quality appears to be only 96DPI. I've noticed this because images with a size set for 300DPI are too large for the page, and images set for 96DPI fit just right.
Could someone please tell me if this is a limitation of Reporting Services 2005, or am I just doing something wrong?
I need to know this because I am up against a deadline with this project. I had ran several tests with Reporting Services but had never had assumed there would be problems with image quality.
Is there any other product that offers similar features to Microsoft Reporting Services that you could recommend?
My luck has not been very good with this project, and I'm assuming the response is going to be 96DPI is all that is supported...

OK, I have managed to get higher quality images from the PDF renderer. Here is what I have found:
1) The PDF renderer in Reporting Services 2005 will size all images that it is given at 96 DPI no matter what DPI the image is when you pass it to the renderer. That means that a 300 DPI image or even a 600 DPI image will be sized in the PDF as if it is only 96 DPI. That means your high DPI image will render much larger than you expect.
So you might expect a 300 DPI image that is 6.5 inches wide to render properly at 1950 pixels. Yet, the PDF renderer will size it as it were 96 DPI which would make the image 20.3 inches long!
2) There is good news though. Despite sizing the images as if they were 96 DPI, the PDF renderer appears to render higher DPI images at a higher quality than 96 DPI. So despite the sizing being wrong, the image actually is rendering at a higher quality.
This means that you should size the image to the proper number of inches based on 96 DPI calculations. Then you can use Bitmap.SetResolution to set your images to at least 300 DPI. That should give you a higher quality image that is the proper number of pixels to fit properly in your report.
I am able to do all of this sizing dynamically because I am using objects as my data sources, but I am sure there are VB functions you could use in the report itself to accomplish the same task.
It is late, and I've been at this project all day long, so forgive me if I have explained anything poorly or gotten any concepts long. Yet, at this late hour, I believe this is what the renderer is doing.
I hope this helps someone else in the future, or at least points them in the right direction.

Error Detected by export DLL for pdf

Similar Messages

Maybe you are looking for