> > I'm in the process of setting up a new web server. I know just enough > > about this to get things up & running. Or so I thought. My old server is > > running IIS 5, which I'm reasonably comfortable messing with. The new > > server is running IIS 6 which I've barely touched. For some reason, ASP > > files will not render in my test setup. I get 404 errors. If I change > > the extension to aspx or htm, the code runs fine. Anyone out there > > taking a break from the heated "life after VFP" discussion have any > > clues for me? <g>
> As usual, after I post a question I figure out the answer... Well, for the archives, if anyone's reading this and actually wants the answer, I believe the solution was to enable 'Active Server pages' in the 'Web Service Extensions' section of the IIS admin... W2K3 throws 404 errors when it should be throwing 500 errors for things like this, in the name of 'security'... FYI, if you're trying to run SOAP with WSDL files, you need to enable 'All Unknown ISAPI Extensions'. There may be a less inclusive way to do this, but enabling that basically makes it operate like IIS5, and the security in regards to that was suitable for me, so that's what I've done. -- Derek _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
