tags:

views:

143

answers:

0

We have a third party application that ends up generating and opening an InfoPath 2003 form from a Web page. This is NOT a SharePoint forms issue - it is a plain old Web app that upon a button click generates some InfoPath XML with the appropriate mso-infoPathSolution and mso-application elements in it and sets the appropriate content type on the HTTP response to cause InfoPath to open and display the form. Anyway, there are two embedded images in the .xsn file that are shown as signatures on the bottom of the form. Everything was working until about two weeks ago, but now on our Terminal Servers we are getting behavior where most of the time, for most users, the divs where those two images should show up are rending the red-X missing image icon instead. There is also a linked image in the form and that is rendering correctly.

The application has NOT changed. While I can crack open the .xsn and look inside it, it is a signed form and I don't want to change it because it's not my application. We went to IE 7 about the same time this started occurring, but given that the images are broken inside InfoPath itself, I think that's a red herring (and to repeat, it is NOT a SharePoint form, so the whole "no embedded images in SharePoint forms" issue doesn't apply). There were also some Office 2003 patches applied around the same time frame - I am more suspicious of those.

My question is simple - has anyone seen this type of behavior before? What else should we be looking at to resolve this? Like I said, altering the form is a non-option, and considering that it does work on some machines but not others it HAS to be something environmental.

Thanks,

Jim