tag:blogger.com,1999:blog-5787751540548761056.post8605709602819741954..comments2011-09-07T11:14:53.392+01:00Muhimbihttp://www.blogger.com/profile/00157302110307291964noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5787751540548761056.post-14694927433767564172011-09-07T11:14:53.392+01:002011-09-07T11:14:53.392+01:00It is good to hear you have managed to resolve the problem, but the link provided in our blog post should work correctly, see http://blog.muhimbi.com/2010/08/using-sharepoint-forms-services-to.htmlMuhimbihttp://www.blogger.com/profile/00157302110307291964noreply@blogger.comtag:blogger.com,1999:blog-5787751540548761056.post-50927207434244749422011-09-02T16:00:57.903+01:002011-09-02T16:00:57.903+01:00I tried the sample code on this page and had problems getting Infopath forms to render using Forms Server. Just running the URL path to the XML file through the Muhimbi Convert function did not work for me. The PDF files were blank. After some trial and error I found that Sharepoint normally redirects calls to an Infopath XML file to the forms server so that the final URL is something like http://www.myserver.com/sites/thissite/_layouts/FormServer.aspx?XmlLocation=/sites/thissite/MyFormsLibrary/MyInfoPathFile.xml@DefaultItemOpen=1 . When sending that URL to the Muhimbi Convert function rather than a direct call to http://www.myserver.com/sites/thissite/MyFormsLibrary/MyInfoPathFile.xml the InfoPath form was successfully rendered and converted to PDF.Anonymousnoreply@blogger.com