Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We have a legacy setup that creates pdf’s on the fly based on client info. I can follow everything through where the process gathers the info and everything runs normally, until it gets to the doc.Form.FlattenFormFields then it goes in to limbo. I’ve captured the base64binary string and it tried to use that to convert to a pdf with no luck also.
Anyone have any ideas or tips on pdf4net. I know this is a vague question but a lot of the system is a black box so we aren’t even sure where to start.
OK figured out that the problem was corruption in the memory stream of the pdf. The process is using Strata frames (a black box) and passing in a doc ID and session parameters which are stored in a cookie. We had to change the cookie a week or so back because some clients session cookie was getting too big (he was storing a butt load of data in the cookie). We bypassed the Strata frames call that created the memory stream and are creating our own in .net and it is working in the test environment now.