Central Admin not working. Error: File not found.

Have not made any changes to our environment for over a month now. No updates and no reboots. Starting this weekend whenever we try to access central administration it give us this error.

Have no idea what could have caused this or how to go about fixing it.

We are running Moss 2007 in a three server farm. WFE, APP server and SQL box.

Any ideas on how to get our central administration back or working?
Who is Participating?
CHEKM9Connect With a Mentor Author Commented:
Turns out the web.config file was corrupt.

Fixing the config file solved the issue.

have you changed your system password ?

first of all.

activate to detail error message:

Go to the Web.Config of your central Administration WebSite and change the following values to:

<customErrors mode="Off" />
<compilation debug="true">

Your Webconfig will look like:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
            <SafeMode MaxControls="200"
            <customErrors mode="Off" />
            <compilation debug="true">

post the detailed error message again.


Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

CHEKM9Author Commented:
No. All system accounts and passwords have been the same for over a year.
CHEKM9Author Commented:
Server Error in '/' Application.

Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Could not load file or assembly 'Microsoft.SharePoint, Version=, Culture=neutral' or one of its dependencies. The system cannot find the file specified.

Source Error:

Line 154:      <providers>
Line 155:        <add name="SPNavigationProvider" type="Microsoft.SharePoint.Navigation.SPNavigationProvider, Microsoft.SharePoint, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
Line 156:        <add name="SPSiteMapProvider" type="Microsoft.SharePoint.Navigation.SPSiteMapProvider, Microsoft.SharePoint, Version=, Culture=neutral, Pub?icKeyToken=71e9bce111e9429c" />
Line 157:        <add name="SPContentMapProvider" type="Microsoft.SharePoint.Navigation.SPContentMapProvider, Microsoft.SharePoint, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
Line 158:        <add name="SPXmlContentMapProvider" siteMapFile="_app_bin/layouts.sitemap" type="Microsoft.SharePoint.Navigation.SPXmlContentMapProvider, Microsoft.SharePoint, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />

Source File: C:\Inetpub\wwwroot\wss\VirtualDirectories\23512\web.config    Line: 156

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.SharePoint, Version=, Culture=neutral' could not be loaded.

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].


Version Information: Microsoft .NET Framework Version:2.0.50727.3603; ASP.NET Version:2.0.50727.3082
run the configration wizerd agian , then check the central admin site
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.