Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have a client who setup SiteMinder on our server and I need to add a web app to the website directory that is the root of the domain. When they browse login.url.com it redirects them to their server, authenticates user, comes back and lands on a 404 page in my IIS. I put the Default.aspx and application files at the Default Website as well as the siteminderagent virtual directory, but they still are getting a 404 error.

enter image description here

How can I figure out where this application is landing them with a 404?

Also, I installed .NET 3.5 on the server and the app is .NET 3.5, however even after installing it only shows 2.0xx inside the properties window of the default website... do I need to change this?

enter image description here

share|improve this question
1  
The ASP.NET version is fine as 2.0. I believe this is because .NET 3.5 did not include an update to ASP.NET –  Somantra Sep 23 '11 at 18:30

2 Answers 2

up vote 2 down vote accepted

You might find what you are looking for in the W3SVC logs. You can see the request as it came in and I would think that should be enlightening. http://support.microsoft.com/kb/313437

In the logs, check the substatus code for the 404 responses.

404 Substatus 2 in IIS means: Web service extension lockdown policy prevents this request.

If this is the case, you probably just need to enable the ASP.NET web service extensions. See here: 404 when page exists - IIS 5, ASP.NET 4.0

share|improve this answer
    
No, the URL is actually the same currently. If you have the cookie you get the 404, if not you go to the client server and get the cookie. If I already know the URL, how can I reverse figure out which place in IIS the URL points to? –  ioSamurai Sep 23 '11 at 18:47
    
You might find what you are looking for in the W3SVC logs. You can see the request as it came in and I would think that should be enlightening. support.microsoft.com/kb/313437 –  Somantra Sep 23 '11 at 18:49
    
All I see is the requests that came in on port 80 to root '/' but no hints as to why the page installed at this location is not loading. Default.aspx is there with all the required files deployed from VS2010, but I have no idea why I am getting a 404. –  ioSamurai Sep 26 '11 at 17:26
1  
What is the substatus code for the 404 responses? 404 Substatus 2 in IIS means: "Web service extension lockdown policy prevents this request.". If this is the case, you probably just need to enable the ASP.NET web service extensions. See here: serverfault.com/questions/29487/… –  Somantra Sep 26 '11 at 18:36
    
I think this might be the problem, ASP.NET 2 was marked as PROHIBITED! Shit I feel really dumb. Just gotta remind myself that my mom doesn't even know the difference between a web page and a PDF so I'm doing pretty good still... hopefully this is the solution, I am waiting to test, then I can award you the answer. Thanks again. –  ioSamurai Sep 26 '11 at 19:01

Is default.aspx set as a default document for the sites in question? It sounds like it probably isn't assuming everything else is configured correctly.

share|improve this answer
    
yeah it is, thanks –  ioSamurai Sep 23 '11 at 18:40

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.