Attempting to Browse asmx page yields "This type of page is not served"


When attempting to access several .asmx pages from within virtual folders within IIS, I receive the following errors;

This type of page is not served.
Description: The type of page you have requested is not served because it has been explicitly forbidden.  The extension '.asmx' may be incorrect.   Please review the URL below and make sure that it is spelled correctly.

This occurs when attrempting to access several differnt .asmx pages.  

Can anyone provide detail as to what may be at root cause for these errors?

Thank You,


500 pts due to urgency

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

.asmx files are not served to web browsers because they are ASP.NET web service files. This means that said web services can only be accessed by remote procedure calls. There is no actual content for you to view there.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Charlie_MelegaAuthor Commented:
Thanks for the reply.  I am not quite sure I understand as from an entirely different server instance I can successfully browse this particular .asmx page.  On the problem server in question, I receive the error posted.
Web Service Extension - ASP.NET v2.0.50727 is Allowed in both instances.

What is the result you get when browsing such files? Could you post the contents of one of these files? It may be that the extension is incorrect and the other server is configured to handle these files differently.
Charlie_MelegaAuthor Commented:
Attached is the actual error with additional debug trace output below the server error.
Yes, I believe you assessment is on the correct track. I believe the server in question may be not configured properly to handle .asmx files. Where could I validate this on the problem server?
Many thanks for your feedback.


Check your ISAPI filters. It is impossible for me to determine what the behaviour should be because I don't know what that file actually contains. I would recommend contacting the developers who created the .asmx file.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.