Unanswered Issue with Web Application

  • Saturday, April 14, 2012 9:24 PM
     
     

    We have a web application and we have hosted a single sharepoint site in it. The problem is whenever we access the Sharepoint site in Internet Explorer, it works for the first time, whenwe close the IE and try again. it displays the below error message.

    server error

    404 file or directory not found

    the resource you are looking have been moved, had its name changed or its temporarily unavailable


    Initially i executed the following command in Web front ends , still the issue persists

    aspnet_regiis -i

    Still issue persist.

    The ULS log dosen't have any information to fix this issue, Any solution would be highly appreciated.

    NOTE: Except this Web application the rest of the web applications are working fine.

    ~Palanee


All Replies

  • Sunday, April 15, 2012 1:30 AM
     
     

    Hi Palanee,

    How was this Web App instantiated? Was it via code, IIS, PowerShell or from within SharePoint?

    Also, do you have multiple Web Front Ends? If so, go into IIS and check that the Web App was built properly on each (assuming that you are load balancing requests). If Timer Jobs are having issues within your farm, it may be that the Web App is being built correctly on one WFE but not the other.

    One more thing, what level of verbosity is your ULS log set to? It may be that you are not seeing a message simply because SharePoint is suppressing it.

    Hope this helps


    Troy Lanphier -- MCT/MCSE/MCITP SharePoint Server 2010 Administration -- Author: Microsoft SharePoint Foundation 2010 Inside Out -- http://blog.sharepointcookbook.com

  • Sunday, April 15, 2012 1:50 AM
     
     

    Hi,

    Please check the application pool and see if it's still running after you encounter the error.


    Miguel Fra / Falcon IT Services
    Computer & Network Support, Miami, FL
    Visit our Knowledgebase and Support Sharepoint Site

  • Sunday, April 15, 2012 4:06 PM
     
     

    Hi,

    Which site template you use to create the site collection? or it is a site / subsite?

    and as Falcon It Services mentioned, check app pool is either running or not after hits the error.


    Jason

  • Sunday, April 15, 2012 4:48 PM
     
     

    Hi,

    Did you try from various places? Did you also try to access this site from one of the servers.

    Please look this site up under httpWatch or Fiddler for an httpTrace. Especially the second time when it is breaking.


    Thanks, Soumya | MCITP, SharePoint 2010

  • Monday, April 16, 2012 2:08 PM
     
     
    yes the application pool is running fine after i encounter the error.

    Thanks! Palani K

  • Monday, April 16, 2012 2:11 PM
     
     

    The web app is initiated within Sharepoint. Yes i do have 2 (total) WFE's. I compared both the IIS settings, the only thing i could find is in one WFE , under ISAPI and CGI , i can see .net 4 registered. however .net 4 is not available in the other WFE.

    Thanks for looking into this.

    Thanks!

    Palaniappan K


    Thanks! Palani K

  • Monday, April 16, 2012 2:11 PM
     
     
    Thanks for looking into this.

    Thanks! Palani K

  • Monday, April 16, 2012 2:12 PM
     
     

    There is no issue with the App pool

    Thanks for looking into this.

    Thanks!

    Palanee


    Thanks! Palani K

  • Monday, April 16, 2012 2:13 PM
     
     

    Accessing the site from server or other WFE gives the same error. Fiddler dosen't give any inputs.

    Thanks for looking into this.

    Thanks!

    Palanee.


    Thanks! Palani K

  • Monday, April 16, 2012 2:59 PM
     
     
    Have you tried to access the site locally on the server which does not has .NET 4.0, also have you checked the IIS Logs , you should enable Failed Request Tracing in IIS to trace the 404 error.

    Rahul Gupta, MCITP, MCPD - SharePoint 2010

  • Monday, April 16, 2012 3:50 PM
     
     

    Hi,

    Since you have two WFEs, please access the other WFE's site from each other.

    To be clear:

    From WFE1, access WFE2's site

    From WFE2, access WFE1's site

    This can be done by hard coding entries in the local host files of each server.

    Looks like this may need additional long hours of troubeshooting. Since you have multiple WFEs, there must be load balancer in front of them. Are the sticky sessions enabled in the load balancer.

    Seems like you may need to troubleshoot many options to pin point errrors. Please start with my accessing each WFE's site. That way load balanacer and client issues are not in picture.


    Thanks, Soumya | MCITP, SharePoint 2010

  • Tuesday, April 17, 2012 2:32 PM
     
     

    Hi soumya,

     The MS foundation Web Application Service is not started in Central Admin. Could you let me know whether that service need to be started in CA.

    Thanks!

    Palanee


    Thanks! Palani K

  • Tuesday, April 17, 2012 3:50 PM
     
     
    MS foundation Web Application Service should be started on the Web Front Ends and it should be stopped on the application server.

    Rahul Gupta, MCITP, MCPD - SharePoint 2010