Home | Login

Development-Blog

Hier schreibe ich meine Erfahrungen und Recherchen zu verschiedenen Problemen nieder. Es dient lediglich zum Nachschlagen, weiter nichts!!! Ich erhebe hier keinen Anspruch auf Richtigkeit oder Alleinstellung.

  • Impressum
  • Kalender

    August 2009
    M D M D F S S
    « Jul   Sep »
     12
    3456789
    10111213141516
    17181920212223
    24252627282930
    31  
  • Pages

    • Impressum
  • Catagories

    • Allgemeines (7)
    • Apache (1)
    • Aptana (2)
    • Carminat TomTom (1)
    • Citrix (1)
    • CSS (8)
    • Firefox (4)
    • Fritz!Box (2)
    • HTML (2)
    • Internet Explorer (4)
    • JavaScript (14)
    • jQuery (1)
    • Linux (1)
    • Magento (4)
    • mySQL (4)
    • Outlook (2)
    • PHP (7)
    • Programmierung (1)
    • QNAP TS-239 Pro (1)
    • Samsung (1)
    • SharePoint (3)
    • Skype (2)
    • Software (3)
    • SSDs (1)
    • TomTom Home (1)
    • USV (1)
    • USV (1)
    • Windows 7 (12)
    • Windows Vista (3)
    • Windows XP (11)
    • Wordpress (1)
    • XML (1)
  • Archive

    • April 2012
    • März 2012
    • Januar 2012
    • Oktober 2011
    • April 2011
    • Februar 2011
    • Januar 2011
    • November 2010
    • September 2010
    • August 2010
    • Juli 2010
    • Juni 2010
    • Mai 2010
    • März 2010
    • Februar 2010
    • Januar 2010
    • November 2009
    • Oktober 2009
    • September 2009
    • August 2009
    • Juli 2009
    • Juni 2009
    • Mai 2009
    • April 2009
    • März 2009
    • Februar 2009
  • Linkliste

    • Development Blog
    • Documentation
    • Plugins
    • Suggest Ideas
    • Support Forum
    • Themes
    • WordPress Planet
  • Meta

    • Registrieren
    • Anmelden

[SharePoint] Troubleshooting the SharePoint “File not found” Error

Posted by skoch on 17. August 2009

Have you ever come across a “File Not Found” error when accessing some part of your WSS 3.0 or MOSS 2007 portal? So have I. There are some modifications that the farm administrator can make to the web application’s web.config file to show more information about the error.

Follow these steps:

  1. Navigate Here:
    C:\inetpub\wwroot\wss\Virtual Directories\<your web app’s virtual directory>

    1. You can also open IIS
    2. Expand Sites
    3. Right click on your SharePoint site
    4. Choose explore
    5. proceed to step 2
  2. Copy and paste the web.config file (making a backup)
  3. Open web.config using notepad
  4. Search for “CallStack” , set this equal to true
  5. Search for “Custom”, set the customerrors = “Off”
  6. Save the web.config file and refresh your page in the browser

You should now see what the error actually is. Many times it is a web part assembly reference missing from the web.config or something similar.

This should at least give you a more precise troubleshooting starting point. Remember to turn CustomErrors back “On” in the web.config after fixing the issue so that your end users won’t see an ugly Asp.Net error if this happens again.

Filed under: SharePoint

Leave a Reply

You must be logged in to post a comment.

«[SharePoint] Externe URL zuordnen [SharePoint] zwei Server Synchronisieren »

Copyright © 2008 Development-Blog | XHTML 1.1 | CSS 2.1 | Design by Fernbap | WordPress Theme by DesertWolf