I’m experiencing a strange issue with PDF exports when running under IIS. My site is running Windows authentication on the application folders, but I have the /Scriptcase folders set for anonymous authentication so the PDF generation process can work.
When I access the application from from a browser on my local PC at http://myserver:iisport/app_name and export a PDF it works.
When I access the same application from a browser in a remote desktop session on the server itself at http://myserver:iisport/app_name and export a PDF it fails. I can see some files quickly being written and disappearing in Windows Explorer when I try the PDF export, but they disappear too fast for me to see what they are.
When I access the same application from either location using the Apache server the PDFs work normally. The behavior is consistent across Chrome and IE.
I expect this is more of a Windows and IIS issue than Scriptcase, but I’m hoping someone has seen it before or knows how to solve it. It isn’t a huge issue, but I do most of my development in the remote desktop session, and it would be easier if the PDF export worked the same there as on my local PC. I assume there is some identify or permissions difference between a browser accessing the IIS server from the remote desktop session vs. one accessing the same server across the network from another machine, but so far I’ve been unable to figure it out.