Can not Access Sharepoint Central Administrator after Microsoft Updates

I tried that once.  It did not give me any options, it only said, "countinue to repair sharepoint."  Should I delete the Sharepoint Central Administration from the IIS first and delete the contents in "C:\inetpub\wwwrooot\wws\VirtualDirectories\28151" first and then run the Configuration Wizard?  

I have the same problem on my WSS 3.0 site. The admin gets an error 403 Forbidden. A normal domain user gets the sharepoint  'permisison denied, you are logged in as domain\user, 'log in as another user'

I tried what Robbie suggest above. I removed Central Administrator with the wizard and re-installed it. No change. I noticed that the administration port doesn't match the virtual directory folder in /inetpub/wwwroot/wss/VirtualDirectories/. So I removed it again and specified a port number. still the same problem and it still installs under the same old directory (10516).

So I removed it a 3rd time and installed it again and told it to use port 10516, but that didn't make any difference either.

I'm stumped.

Dave

p.s. I think that if you have all the services on one server, it may not offer the options Robbie suggested. I have a separate host for the SQL Server.

Change the app pool for central admin to the default app pool. Please post the results.

:-)

same results but I still have numerous Warnings and Error Events:

Event Type:      Error
Event Source:      Windows SharePoint Services 3 Search
Event Category:      Gatherer
Event ID:      2424
Date:            10/26/2007
Time:            7:55:07 AM
User:            N/A
Computer:      FCHRINTRA2
Description:
The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

Context: Application 'Search', Catalog 'index file on the search server Search'

Event Type:      Warning
Event Source:      ASP.NET 2.0.50727.0
Event Category:      Web Event
Event ID:      1310
Date:            10/26/2007
Time:            7:58:23 AM
User:            N/A
Computer:      FCHRINTRA2
Description:
Event code: 3006
Event message: A parser error has occurred.
Event time: 10/26/2007 7:58:22 AM
Event time (UTC): 10/26/2007 11:58:22 AM
Event ID: 4d590c08ab314cd7940e61c14537dea4
Event sequence: 1
Event occurrence: 1
Event detail code: 0
 
Application information:
    Application domain: /LM/W3SVC/560870771/Root-1-128378734992892910
    Trust level: WSS_Minimal
    Application Virtual Path: /
    Application Path: C:\Inetpub\wwwroot\wss\VirtualDirectories\28185\
    Machine name: FCHRINTRA2
 
Process information:
    Process ID: 3608
    Process name: w3wp.exe
    Account name: NT AUTHORITY\NETWORK SERVICE
 
Exception information:
    Exception type: HttpException
    Exception message: Data at the root level is invalid. Line 1, position 1.
 
Request information:
    Request URL: http://fchrintra2:28185/
    Request path: /
    User host address: 164.51.33.216
    User:  
    Is authenticated: False
    Authentication Type:  
    Thread account name: NT AUTHORITY\NETWORK SERVICE
 
Thread information:
    Thread ID: 1
    Thread account name: NT AUTHORITY\NETWORK SERVICE
    Is impersonating: False
    Stack trace:    at System.Web.Compilation.BuildManager.ReportTopLevelCompilationException()
   at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled()
   at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters)

Make the search and content accounts on the Search Config page the
same account (search account)

:-)

I think you are referring to a feature that is under the Sharepoint Central Administrator which I cannot access.  If there is another way to access it, please let me know

Any resolution to this?

Nope.  Are you having the same problem?

Yep. I called Microsoft. They said the support is free but they would have to call me back. Typical call back time was 24 hours. I am still waiting.

I have been thinking of backing it up, uninstalling it and restoring it.  I have been dealing with this for some time now, but no one seems to have a solution.  That is my last resort and I think it is about time :)

I have installed Sharepoint v3 on a different server.

I have restored the SQl databases from the old server to the new. Going to see if it will allow me to add a content database and then go on from there. will let you know what happens.

PS: Never done this before...

OK.. This worked...

stsadm (in c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\bin) allows you to import the database and do an upgrade.

The process is:

1. Create a new application in SharePoint (do not create the site collection)
2. Attach the database to your SQL Server if it's not already attached
3. Go to the command prompt and type: stsadm -o addcontentdb -url http://myapplicationpath -database <mydatabasename>
4. Check that the application now has the database attached and there are sites in it (in Central Admin -> Applications -> Manage Content Datbases)
5. Browse to the site to check it
6. <optional> go back to central admin and delete the empty database that was created as part of step 1

At that point, you may bask in the glory of a restored SharePoint site.  :)

Note you can do it all from the web interface, as long as the version of SharePoint installed matches the database version.

Yes, that is the method I have used, but I am looking for a solution to fix the database rather then restore it to a new one.  I have successfully restored it to another Sharepoint site a few times, but certain features get lost in the transfer.  For that reason, I wanted to see if I can repair it if I can, but it I have no choice.......I will be force to do that.  

Well, As I said ealier.. I have a call open with Microsoft. I chased them this morning...Someone will call me back soon... appaently.

I restored my sites with no problem and everyone seems to be happy (at the moment)

If MS do call me back i'll let you know what happens. Good Luck!

HI

try to give write access\ to the logged in user to the following folder C:\windows\Microsoft.NET\Framework\v2.0.50727.