Could you try and save the PDF and the associated FDF file on your local system. Now, try double clicking on the FDF and see the behavior of the application.
Do you see the same behavior now as well, or is the behavior different from what you had mentioned earlier.
i get the same result after i save the file to the desktop or if i try to open the form in internet explorer.
Could you please try the following:
1. Generate a new PDF and a FDF file. Try opening the same and see if it behaves the same way.
2. Check if you have access to the PDF that is being used by the particular FDF.
3. If possible, please send me the FDF and the associated PDF that is behaving in this way on your system.
sorry i didn't see a notification that you replied to this discussion.
"1. Generate a new PDF and a FDF file. Try opening the same and see if it behaves the same way."
yes, it does behave the same way, it's just a continuous loop until i have to kill the process.
"2. Check if you have access to the PDF that is being used by the particular FDF."
by this do you mean the correct permissions? if that is what you mean, then yes, the permissions are set correctly.
"3. If possible, please send me the FDF and the associated PDF that is behaving in this way on your system."
i really wish i could but the information in the form is sensitive and cannot be sent.
as an update though, i reimaged the customer's workstation, installed Adobe Reader 10.1.1 and it worked perfectly (finally). HOWEVER, after about two weeks the same symptoms returned!
McAfee's Host Intrustion Prevention system (HIPS) was blocking the event from occurring. Disabled the HIPS to verify and once I got the information, I added the exception.
everything works fine now.