Re: SBS2003R2 Sharepoint Web Part Error (new post)

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I've been getting the kind assistance of Terence Liu. What we are seeing is
when we set the ASP.NET tab to V1.1.xxxx VPN access to the Companyweb ceases
and we get "Service Unavailable" errors.

Mr. Liu offline (sorry)
1. Click Start - Administrative Tools - Microsoft.Net Framework 1.1 Wizards
2. Click Adjust .NET Security
3. Select "Make changes to this computer" and click Next.
4. Set all levels back to default. To do this, select My Computer and then
click the Default level button.
5. Repeat for "Local Intranet', 'Internet', 'Trusted Sites', and 'Untrusted
Sites'.
6. Click Next and Finish
7. Run iisreset

If this issue persists, please also help to gather the metabase on SBS. He
now has the metabase information. I'll keep you posted.

Thanks for the post, I just saw another SBS 2003 (release 1) server loose a
basic Webpart Calendar suddenly. The error message is "Web Parts and Web
Part Zone controls must live in a runat='Server' HtmlForm." This is a topic
for a different post.

Paul

"bass_player [SBS-MVP]" wrote:

Check the ASP.NET tab in your companyweb properties and make sure it is
using v1.1.xxxx instead of v2.0.xxxx if this is Windows Sharepoint Services
v2

"Paul Wolfson" <PaulWolfson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F8173690-A39E-437D-BC0B-2F9F649D93DF@xxxxxxxxxxxxxxxx
Out of the box I am encountering the Companyweb Webparts giving the
following
error. (Using ASP.NET 2.0)

Web Part Error: This page has encountered a critical error. Contact your
system administrator if this problem persists.

Posts on the Web say use IIS Manager to use ASP.NET 1.1. This fixes the
Web
Part Error. But then I get service unavailble errors and cannot get
beyond
the default page on VPN login. Or worse get Service Unavailable errors
from
IIS hours later. IIS logs cannot mix .NET 1.1 and .NET 2.0 errors.

This problem has persisted across complete server rebuilds. I have done
complete hardware change outs. The only other clue is it seems to be
related
to Dual Core AMD processors. These processors also produce negative ping
times on the network which AMD acknowleges but hasn't a good fix for yet.
Fortunately the negative ping time seems harmless unless there is a
relationship here.

Any ideas? I don't know where to start hunting down a solution. I can't
take down single production SBS servers - but this is a very visible
error.
I've not seen it in SBS 2003 only in R2.



.

Quantcast