« Previous Next »

Thread: HTTP Error 404.17 - Not Found

Last post 05-19-2009 10:40 AM by sasikantt_24. 2 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (3 items)

Sort Posts:

  • 05-18-2009, 8:20 AM

    HTTP Error 404.17 - Not Found

    Hi

     

    HTTP Error 404.17 - Not Found

    The requested content appears to be script and will not be served by the static file handler.

     

    I migrated my web service from IIS 6.0 to IIS 7.0 successfully with following steps.

      

    1. I check for dependencies for my web service. I found that web service is dependant on “MyAppPool “

    I migrated application using manifest. In manifest I write following things.

     <MyApplication><metaKey path="lm/w3svc/apppools/ MyAppPool" /><metaKey path="lm/w3svc/1/Root/ MyApplication " />

    </ MyApplication >

     

    2. I use following command to migrate web service.

     

    msdeploy -verb:migrate -source:manifest=D:\ MyApplication.xml -dest:auto,computerName=IIS7.0ServerName

     

    I successfully migrate web service with above steps.

     

    3. When I browse web service I get Http error 404.17 as mentioned above.

     

    Application pool for “MyApplication” is “MyAppPool” after migration. When I change it manually to “DefaultAppPool” everything works fine. But I don’t want to change application pool.

     

    I also tried with changing “Enable 32-Bit Applications” in advanced settings for “MyAppPool” to True.  But no luck.

     

    Please help me out, Let me know work around or please guide me if I am doing anything wrong.

     

    Thanks

     

  • 05-19-2009, 5:50 AM In reply to

    • WWWWeb
    • Top 100 Contributor
    • Joined on 04-30-2009, 5:42 AM
    • Posts 52

    Re: HTTP Error 404.17 - Not Found

    404.17 - Dynamic content mapped to the static file handler via a wildcard MIME mapping.

     

    Do you have a wildcard mapping?

  • 05-19-2009, 10:40 AM In reply to

    Re: HTTP Error 404.17 - Not Found

    Hi,

    I just migrate web service with its app pool from IIS 6.0 to IIS 7.0 using MS Deploy as mentioned above.

    Can any one please let me know the work around for this error?

    Thanks

     

Page 1 of 1 (3 items)
Microsoft Communities