On Demand report fails with 404 not found

[malcolmg]

Reports that were working fine are suddenly failing with 404 errors.  Although on a stand alone they still work fine, once running from an external connection all of my generated reports fail.  Static pdf reports are not affected.

As far as I can tell nothing has changed on the server. 

Any advice or clue as to where I should be looking

Malcolm

[Bruce]

start by looking at the log to see the exact text of the incoming request.

then, taking the exact incoming name from the log, trace through the
webhandler CallForm method to see if it matches anything there.

Cheers
Bruce

[malcolmg]

Thanks Bruce.

I know the names are and this was confirmed in the log.  The form is called, the report generates but I get 2 different results
(1) Using Localhost - report is shown in browser - (using Tracker PDF)
(2) Internet Access - Page load error - Page not found.

I am of the opinion that it is a security issue but cannot prove it and the system administrator refuses to believe it.  The old "I did nothing" routine.  In my case "I did do nothing" but it broke anyway.

I am stumped and being month-end, the guys are screaming.

Malcolm

[Bruce]

Hi Malcolm,

Turn the NetShowSend=>1 define in the server (project defines) on.

Run Debugview on the server.

Start by seeing what is sent back to the browser after the request. Is it the PDF or is it a "Page not found"? If the former then there's a problem between the server and the client. If the latter then there's a problem on the server.

Cheers
Bruce

[malcolmg]

Well that was fun, but it proved that there is a problem on the server. 

It is not a Nettalk problem as it still runs perfectly on my standalone.

I am going to change the reports to write to disk and then open the pdf in another window.

Thanks for the help

Malcolm

 

[malcolmg]

It is a authority problem.

I found that the webserver works fine while I am running it under my profile, but fails as a service, which was run as Local System account.  I have now changed this to my account and we are back up and running like before.

This means that recently a security change must have been made to the Local System Account. 

Malcolm