If I browse to http://myservername/default.aspx instead of http://myservername the 403 error is gone, instead I get this error in the web.config file. Still exploring, but anyone have any suggestions?: 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: Unrecognized attribute 'type'. Source Error: Line 14: </sectionGroup> Line 15: Line 16: <sectionGroup name="System.Workflow.ComponentModel.WorkflowCompiler" type="System.Workflow.ComponentModel.Compiler.WorkflowCompilerConfigurationSectionGroup, System.Workflow.ComponentModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"> Line 17: <section name="authorizedTypes" type="System.Workflow.ComponentModel.Compiler.AuthorizedTypesSectionHandler, System.Workflow.ComponentModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /> Line 18: </sectionGroup> Source File: C:\Inetpub\wwwroot\wss\VirtualDirectories\81\web.config Line: 16

simple assumption: base on the location of the web.config (C:\Inetpub\wwwroot\wss\VirtualDirectories\81\web.config) seems like you use 81 port. Do you access your server using http://myservername or http://myservername:81?Blog - http://sadomovalex.blogspot.com CAML via C# - http://camlex.codeplex.com

Had someone ask for help: they described having a registry issue, sounds like they ran the repair utility for windows (2003 server), and then SharePoint 2007 stopped working. Gives a 403 error when you browse to the site collection in the root directory. I am able to access CA however. Where would I start looking to correct this? It seems like a permission issue, but not sure where to begin. Any advice appreciated.

OK, what I've done is delete the default web application and create a new one. I created a new site collection as a placeholder, and now I can browse to http://myservername and I view the site fine. Now I want to restore the original site collection (they have a full farm backup). I have the original databases saved as well. What's the best method for restoring the site collection?

I used STSADM to restore the original content database, which brought the same old permissions issues back. So there is something in the db that is causing this apparently? If anyone has any suggestions I'd be most grateful. Looking into ASP.NET versions right now associated with the site in IIS...