Bulk pdf file creation generate Failed To Create PDF Documents with below message. This error never generate for one or two pdf file creation. I am using this command to create PDF documents.
Conditional expression :
Please look this issue .
This is not a known issue. I quick run of pdf creation did not show the error.
Please provide a testcase to proceed further.
you might want to change the pdf creator driver. I used the one from pdf forge to run my quick test.
The problem here is, I understand that you have a problem but we need to be able to reproduce the problem to take this further.
The problem could be in the driver we use but we have to log a bug with the provider - we need to submit a valid testcase to them.
You may want to use pdf forge and try to print to it using SalReportPrint() for such bulk report to work around the problem.
However, happy to take on board if you could submit a test case.
I understand , but how can i generate test case where as problem is in bulk pdf generation. can you provide pdf forge driver which can be used using SalPrintFile , i can try with that one also.
if you can arrange any real time session that i can show you live.
PDF Failed after create 2155 or more records in TD 6.2 sp3r with the following message.
Please look this issue again and provide us solutions as this is pending since 2013.
I've been experiencing this same problem for about a year and a half now. It's happened on all kinds of different Windows versions. I think there are a couple of key subjects here:
1) The problem probably arises after some sort of update, and I very much suspect it's a Windows update, not an Acrobat update. I say this because it happens that one day a user is working just fine and next day he calls me saying that he's got the problem, with no intervention on our side and no known intervention on his side.
2) The problem is machine-dependant. I work with municipal offices, where I usually have users accessing the application from many different machines. At a given moment, it's possible to create a PDF of one report from machine A and it's NOT possible to create a PDF of THE SAME report from machine B.
To make it even more bizarre: I have both 6.0 and 6.2 versions installed in my computer. Up until last friday I was able to work just fine with both versions. As of last monday now it works fine on version 6.2, but it doesn't work on version 6.0. I do change my machine path every time I work with a different TD version.
I attach screenshots. Fisrt I get "Failed to create PDF document" and then I get "Error... Cannot open printer".
While trying to find out what's going on, I have been able to fire the first message by using SalReportPrintToFileEx deliberately providing a path with no file name. In this case, I get the first error message but not the second one. However, I'm getting both error messages from my application, where I'm positive I'm using a correct path + file name for the function parameter. What's most significant to me is that the same executable works OK in one machine and doesn't work on the machine that's on the table beside
Any know fixes yet? Using external tools like PDF Creator and such is factible, but we find it's slower, it's also OS version-dependant, and it greatly complicates installations.
Thanks for the help.
"Can not open printer" error initially came after installed TD62Sp4 on win7 framework 4.5 but removed after printer installed.
Exception error now resolved , i had tried on appx 4000 PDF mails .
You can try this
I hope this will help.
I replaced my RepPdfLib60.dll with the version that came along with TD60 SP5 deploy, and bingo! Even though my SP is 8, and even though the deploy we've installed in our customers is also 8, reports continue to work normally and the problem with the generation of PDF files is gone. I never knew why it happened, but this simple step seems to solve the problem. I've tried it on our development environment, and I've also tried it in one of our customers. just one thing: since DLLs are loaded in memory the first time you use them, make sure to restart the machine (or flush your memory if you have an alternative way to do it) where you try this after you've replaced the file, or else you'll end up thinking it continues to work wrong.
Good luck. Thanks Miquel!
Who is online
Users browsing this forum: [Ccbot] and 3 guests