Companyweb and Sharepoint Administration broken

Executed the command and restarted IIS and web services.

Still getting the 403 error.

I'm getting a runtime error when I try to browse Sharepoint Central Administration as well:


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly"/>
    </system.web>
</configuration>
 

Do you have .NET 2.0 installed?  Are the sites configured to use .NET 1.1?  (If 2.0 is installed there will be an ASP .NET tab in the site's properties display).

Jeff
TechSoEasy

Yes, both Sharepoint Central Admin and Companyweb are set to use 1.1

I can get to the FrontPage Extensions admin page.  The link off that page to admin companyweb iproduces a 404 error:
http://companyweb/_vti_bin/_vti_adm/fpadmdll.dll?page=webadmin.htm

Would it help at all to install Sharepoint 2.0 SP 3?    

"The link off that page to admin companyweb iproduces a 404 error:
http://companyweb/_vti_bin/_vti_adm/fpadmdll.dll?page=webadmin.htm"

As it should.  You shouldn't have FrontPage extensions on the companyweb site.

Installing a service pack won't necessarily help fix the availability of the site.

A 403 Error is actually a permissions problem.  Sorry that I didn't catch that right away.

So you have messed with permissions?  

Try just rerunning the Configure Email and Internet Connection Wizard (CEICW -- which is linked as Connect to the Internet in the Server Management Console > To-Do List) to see if that will set things right./

A visual how-to for the CEICW is here:  http://sbsurl.com/ceicw

Jeff
TechSoEasy

I re-ran the wizard but no apparent effect.  Still getting the 403 error.

I've changed some permissions in attempts to fix the problems, but nothing's worked so far and there don't seem to be any obvious system errors.  Could it be a database issue?

"Could it be a database issue?"

Not if you are getting a 403 for http://companyweb as well as an error for http://localhost:8081

If you monkeyed with the permissions on the C:\Inetpub folder that could cause both errors.

Check to be sure that all are correct per this KB article:  http://support.microsoft.com/kb/812614

Jeff
TechSoEasy

So I checked permissions and found / fixed some errors.  The most glaring however, is that ASPNET is indicated as needing permissions in many places but I don't have a user with ASPNET in the name.

Also, while editing Windows User Rights, using the Default Domain Controllers Policy, I found that there are no users configured in  Impersonate a cient after authentication.

Additionally, wherever Users was indicated in the KB, I found Authenticated Users instead.

Lastly, I"m getting the errors below when visiting http://localhost:8081

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly"/>
    </system.web>
</configuration>
 

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="On" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>
 

For some reason, changing IP restrictions to All Computers Granted Accesss worked,  per this article : http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/Q_23860753.html

However, when I check the SBS server of another client, the All computer was set to "denied access" with exceptions for the local subnet and localhost.

Which configuration is proper and why the existing configuration not have worked with "deny" set?

Thanks,
Fred

I spoke too soon!

The site came up for a minute, now I get the 403 regardelss of the IP restriction setting :(

"but I don't have a user with ASPNET in the name"

That's a problem.  You most likely don't have .NET 1.1 Framework installed correctly.  The easiest way to repair this would be to reinstall Windows Server 2003 Service Pack 2 (The full download version:  http://www.microsoft.com/downloads/details.aspx?FamilyId=95AC1610-C232-4644-B828-C55EEC605D55&displaylang=en )

Then reregister .NET 1.1 as I initially recommended.

Jeff
TechSoEasy

I've installed SP2 but no effect on Companyweb.  

I also looked at another working sbs server and don't see an aspnet account, though the service is configured to use the Network Service account in services.

Next thought?

Thanks,
Fred

Sorry, that was my mistake... you shouldn't have the ASPNET account listed in any permissions.  That is only for IIS 5.0.

Let's go back to your Directory Security issue... the proper configuration is to have "By default, all computers will be:  Granted Access".

Jeff
TechSoEasy

Still nothing but a 403 error on Companyweb.

Microsoft Sharepoint Administration (Front Page Extensions) is still there and works.  Should I remove it?

Both the above and the regular Sharepoint administration server now ask for credentials when I try to connect, though the regular admin site stil gives the runtime error.

Also worth noting is that the SBS Monitoring is not working either.  I get the following error:

Server Application Unavailable
The web application you are attempting to access on this web server is currently unavailable.  Please hit the "Refresh" button in your web browser to retry your request.

Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.

So how did all of this break?  It was working before, right?

Did you attempt to install WSUS already?

Jeff
TechSoEasy

I'm not positive as to how it broke, but there was a major crash that lead to an exchange db fix a couple months ago.  They have an existing vacation calendar in the db as well as some static docs.

I've not done the wsus yet,  .Net 2.0 is installed, but IIS is registered to 1.14 .

Hmmm... if Exchange was reinstalled it probably messed up IIS which is highly integrated into Exchange's configuration.

Does OWA work?

At this point it might be best to just reinstall the Companyweb.  To do that, follow http://support.microsoft.com/kb/829114

Jeff
TechSoEasy

Exchainge wasn't reinstalled, just the DB was repaired.

Currently:

Sharepoint Central Administration procuces a logon prompt  then displayes the runtime error:
<!-- Web.Config Configuration File -->

OWA Works

Microsoft Sharepoint Administration (Front Page Extensions) Works

Companyweb produces a logon box then displayes  the "Directory Listing Denied" page.

Still think a re-install is the way to go?.