locked
Reoccuring Issue: EventID 8dzz System.Web.HttpException File does not Exist thrown when opening Site Settings page RRS feed

  • Question

  • I have a previous issue that keeps re-occuring:

    http://social.msdn.microsoft.com/Forums/en-US/sharepointadmin/thread/4748525f-27d9-4cd6-aecc-9d50aed0e7cc

    With the following error in the Diognostic logs:

    04/21/2010 08:40:11.00 	w3wp.exe (0x17A0)            	0x136C	Windows SharePoint Services  	General            	8dzz	High  	Exception Type: System.Web.HttpException Exception Message: The file '/_layouts/_controltemplates/TopNavBar.ascx' does not exist. 	 
    

    (The .resx issue has been resolved and have not seen it pop up again)

    I'll go for several weeks where everything works fine, then I start getting this error about TapNav.aspx. When it does start to occur, it happens when opening the "Site Settings", and also for some lists/librarie s(haven't determines what causes some lists to open and some not to, but it always happens on Site Settings).

    Re-running the seutp wizard on the servers seems to fix it, but it's rather annoying that it bombs out again every few weeks. Anyone have a clue why this might keep happening?

    Wednesday, April 21, 2010 1:48 PM

Answers

  • Hi,

     

    From the log in your post, actually the file “/_layouts/_controltemplates/TopNavBar.ascx” does not exist.

    As we know the file should be in “~/_controltemplates/TopNavBar.ascx”.

     

    Have you customized the “application.master” master page or other page in file system?

    When you open the page in file system by SPD, and the SPD will remove the parameter “~/” of the URL in this page automatically.

    The incorrect URL will be populated to the page without any prompt.

    (In my opinion, SPD think this value of the parameter “~/” is null or invalid when the page is not in the environment of a site)

     

    But this the parameter “~/” should be used in SharePoint sites,

     

    So you can check your application.master in File System, all of URLs should be included the parameter “~/” 

     

    In my local, the default URL of “TopNavBar.ascx” should be “~/_controltemplates/TopNavBar.ascx”.

     

    Why Re-running the setup wizard on the servers seems to fix it?

    That’s because you have replaced all customized page using the default pages in file system.

     

    Hope this helps

     

    Thanks!

    Stanfford

    • Marked as answer by Stanfford Liu Friday, April 30, 2010 7:59 AM
    Tuesday, April 27, 2010 8:32 AM

All replies

  • Hi,

     

    From the log in your post, actually the file “/_layouts/_controltemplates/TopNavBar.ascx” does not exist.

    As we know the file should be in “~/_controltemplates/TopNavBar.ascx”.

     

    Have you customized the “application.master” master page or other page in file system?

    When you open the page in file system by SPD, and the SPD will remove the parameter “~/” of the URL in this page automatically.

    The incorrect URL will be populated to the page without any prompt.

    (In my opinion, SPD think this value of the parameter “~/” is null or invalid when the page is not in the environment of a site)

     

    But this the parameter “~/” should be used in SharePoint sites,

     

    So you can check your application.master in File System, all of URLs should be included the parameter “~/” 

     

    In my local, the default URL of “TopNavBar.ascx” should be “~/_controltemplates/TopNavBar.ascx”.

     

    Why Re-running the setup wizard on the servers seems to fix it?

    That’s because you have replaced all customized page using the default pages in file system.

     

    Hope this helps

     

    Thanks!

    Stanfford

    • Marked as answer by Stanfford Liu Friday, April 30, 2010 7:59 AM
    Tuesday, April 27, 2010 8:32 AM
  • I checked the site this morning and got the same error.

    I re-ran the SP config wizard and restarted both servers in the farm. Checking again, still error. I guess the patch/fix didn't work this time. I haven't ever had to re-apply the master page or theme after re-running the setup, so I always assumed it left those setting alone.

    I just checked the Security event log on both servers, and I have no failure message from this morning - everything is success audit.
    I'll check the application.master shortly for "~/" and post the results...
    Thursday, May 6, 2010 4:06 PM