this works fine by converting the HTML produced by source_file.asp and saving it as a PDF file as long as the source file has no <img> tags in it. as soon as images are introduced in the source file the script errors with the following error message:
Active Server Pages error 'ASP 0115'
Unexpected error
/test.asp
A trappable error (C0000005) occurred in an external object. The script cannot continue running.
(also to note, none of the images referenced in the linked css file make it to the PDF either but this doesnt cause the script to error, they are just ignored)
i have scoured the component manual and many google searches with no result. if anyone can help with an explanation and a solution that would be great.
yes i have used the reference, samples and searched the persits component site extensivley but nothing of help.
the only thing i came across was related to correctly forming the image tag paths in the html code when passing a string of html to the ImportFomURL method. although this does appear to be related i formed all the img paths in all of the suggested ways in my source file just to be sure but with no success.
yes, thanks for pointing that out. as previoulsly mentioned... i have used the reference manual, samples and searched the persits component site extensivley.
i am also in conversation with persits but they are stuck for ideas. i assumed a post on a forum of this nature was a logical step in finding a solution but perhaps its not.
I don't think so. There's not enough information there. The Persits support folks are the only ones who know the internals of their component, and if anyone can tell you what specifically in your script is making it fail, it's going to be them.
For what it's worth, that error 0xC0000005 simply means that a memory fault occurred. Since the Persits code is almost surely compiled VB or compiled C++ code, we really don't have any hope of debugging to find out where that fault is. (A memory fault is when the CPU tries to read or write to memory that is not currently part of the process space or tried to write to memory that is in the process space but is not marked as writable.)
Without a *good* debugger and access to the source code, it would be nearly impossible to figure this out from that message.
Bookmarks