Group:  English: Windows Server ยป microsoft.public.windows.server.sbs
Thread: SBS2003R2 Sharepoint Web Part Error (new post)

DotNetBag
.NET Development Newsgroups

HTVi
TV Discussion Newsgroups

Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
Rising Antivirus 2006

SBS2003R2 Sharepoint Web Part Error (new post)
Paul Wolfson 24.06.2007 22:38:00
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.
RE: SBS2003R2 Sharepoint Web Part Error (new post)
v-terliu[ at ]online.microsoft.com (Terence Liu [MSFT]) 25.06.2007 06:37:32
Hello Paul,

Thank you for posting here.

Generally, we should set the ASP.NET to 1.1.xx on SBS 2003 R2 for web sites.

Before we go any further, please let me know the following information so
that we can understand your situation more clearly.

1. What do you mean by "out of the box"? Do you mean you cannot access the
companyweb from internal clients and external clients?

2. Where do you get "service unavailable errors"? Please capture
screenshots on the error messages and send the pictures to me at
v-terliu[ at ]microsoft.com

3. As you mentioned "cannot get beyond the default page on VPN login", does
this issue only happen with VPN client? How about internal non-VPN client
access? Does this issue occurs with every VPN users? Which's "default page"
you cannot get?

4. Can you access the companyweb from VPN client?

5. What do you mean by "Or Worse get service unavailable errors from IIS
hours later"?

6. Gather MPS report for further investigation

a. Visit
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_NETWORK.EXE. to download the file.

b. Run the MPSRPT_NETWORK.EXE on the server box.

c. Wait for 10~15 minutes.

d. Open Windows explorer, navigate to
%SYSTEMROOT%\MPSReports\Network\Reports\cab\

e. Send the .cab file directly to me at v-terliu[ at ]microsoft.com

I appreciate your time and look forward to hearing from you.

Thanks and have a nice day!

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: SBS2003R2 Sharepoint Web Part Error (new post)
| thread-index: Ace2sFHAZ9Enzae5So+WZYACZEHLVA==
| X-WBNR-Posting-Host: 207.46.193.207
| From: =?Utf-8?B?UGF1bCBXb2xmc29u?= <PaulWolfson[ at ]discussions.microsoft.com>
| Subject: SBS2003R2 Sharepoint Web Part Error (new post)
| Date: Sun, 24 Jun 2007 15:38:00 -0700
| Lines: 21
| Message-ID: <F8173690-A39E-437D-BC0B-2F9F649D93DF[ at ]microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:45953
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| 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.
|

Re: SBS2003R2 Sharepoint Web Part Error (new post)
"bass_player [SBS-MVP]" <bass_player[ at ]mvps.org> 26.06.2007 20:47:49
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[ at ]discussions.microsoft.com> wrote in message
news:F8173690-A39E-437D-BC0B-2F9F649D93DF[ at ]microsoft.com...
[Quoted Text]
> 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.


Re: SBS2003R2 Sharepoint Web Part Error (new post)
Paul Wolfson 26.06.2007 21:07:02
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:

[Quoted Text]
> 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[ at ]discussions.microsoft.com> wrote in message
> news:F8173690-A39E-437D-BC0B-2F9F649D93DF[ at ]microsoft.com...
> > 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.
>
>
>
Re: SBS2003R2 Sharepoint Web Part Error (new post)
v-terliu[ at ]online.microsoft.com (Terence Liu [MSFT]) 27.06.2007 11:20:12
Hello Paul,

Thank you for kind reply.

Based on my further research, I suggest we try the following steps:

1. Ran the following commands on SBS.

c:\windows\Microsoft.Net\Framework\v1.1.4322.0 > aspnet_regiis -i also
c:\windows\Microsoft.Net\Framework\v2.0.50727 > aspnet_regiis -i

2. Then ran command iisreset on SBS

Then test this issue.

From the metabase, I find the Application settings for companyweb is nor
correct, I suggest we try the following steps if the above steps have no
effect on this issue:

1. Open properties window of companyweb, select Home Directory tab,

2. The Application settings should be "Default Application" but not "root",
please click Remove button to remove root.

3. Click OK.

Note: Ensure select 1.1.xx under the asp.net tab.

If we cannot resolve the issue after we perform the above steps, please
kindly help me collect some information for further investigation:

1. Do you get same error when you access the companyweb from internal
client computer?

2. Do you get same error when you access the companyweb from SBS itself?

Hope these steps will give you some help.

Thanks and have a nice day!

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: SBS2003R2 Sharepoint Web Part Error (new post)
| thread-index: Ace4NfEJxrQXOFdgRha2UOQNnvrS0w==
| X-WBNR-Posting-Host: 207.46.192.207
| From: =?Utf-8?B?UGF1bCBXb2xmc29u?= <PaulWolfson[ at ]discussions.microsoft.com>
| References: <F8173690-A39E-437D-BC0B-2F9F649D93DF[ at ]microsoft.com>
<ebX1CNDuHHA.4572[ at ]TK2MSFTNGP02.phx.gbl>
| Subject: Re: SBS2003R2 Sharepoint Web Part Error (new post)
| Date: Tue, 26 Jun 2007 14:07:02 -0700
| Lines: 63
| Message-ID: <A22EEFDA-BAF1-4ED4-8915-0A940198703A[ at ]microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:46458
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| 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[ at ]discussions.microsoft.com> wrote in message
| > news:F8173690-A39E-437D-BC0B-2F9F649D93DF[ at ]microsoft.com...
| > > 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.
| >
| >
| >
|

Re: SBS2003R2 Sharepoint Web Part Error (new post)
GeraldF <me[ at ]somewhere.com> 29.06.2007 05:20:50
In article <n10ki0KuHHA.2148[ at ]TK2MSFTNGHUB02.phx.gbl>, v-
terliu[ at ]online.microsoft.com says...

[Quoted Text]
> 1. Ran the following commands on SBS.
>
> c:\windows\Microsoft.Net\Framework\v1.1.4322.0 > aspnet_regiis -i also
> c:\windows\Microsoft.Net\Framework\v2.0.50727 > aspnet_regiis -i
>
> 2. Then ran command iisreset on SBS
>
> Then test this issue.

When you do this all of the Web directories reset to
aspnet2 this includes all of the Default Web pages.
Re: SBS2003R2 Sharepoint Web Part Error (new post)
GeraldF <me[ at ]somewhere.com> 29.06.2007 05:36:17
In addition if you attempt to set the companyweb to
aspnet1 you get the following error when you open the
company web:

Server Error in '/' Application.
--------------------------------------------------------
------------------------

Runtime Error
Description: An application error occurred on the
server. The current custom error settings for this
application prevent the details of the application error
from being viewed remotely (for security reasons). It
could, however, be viewed by browsers running on the
local server machine.

Details: To enable the details of this specific error
message to be viewable on remote machines, please create
a <customErrors> tag within a "web.config" configuration
file located in the root directory of the current web
application. This <customErrors> tag should then have
its "mode" attribute set to "Off".


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

<configuration>
<system.web>
<customErrors mode="Off"/>
</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="RemoteOnly"
defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
Re: SBS2003R2 Sharepoint Web Part Error (new post)
Paul Wolfson 29.06.2007 21:46:02
Hello Terence,

We seem to have gone in circles here. To review:

Originally the server came up freshly loaded with Sharepoint 2.0 reporting
critical errors in WebParts,

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

Many suggestions here and elsewhere were to use ASP.NET 1.1.4322 rather than
ASP.NET v2.0.50727. That makes sense, coders can't always keep up with
deadlines.

However while that immediately fixed the Web Part Error within a little
while (say 15 minutes) RWW fails with the error saying Service Unavailable.
That is explainable by the error logged by IIS:

Event Type: Error
Event Source: ASP.NET 2.0.50727.0
Event Category: None
Event ID: 1062
Date: 6/29/2007
Time: 3:39:51 PM
User: N/A
Computer: NARWHALE
Description:
It is not possible to run two different versions of ASP.NET in the same IIS
process. Please use the IIS Administration Tool to reconfigure your server to
run the application in a separate process.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Then after much research it was determined that asp.net (both versions
should be reloaded from the directories:

c:\windows\Microsoft.Net\Framework\v1.1.4322.0 and
c:\windows\Microsoft.Net\Framework\v2.0.50727

using the command "aspnet_regiis -i" in each of the two.

Run iisreset and set companyweb back to ASP.NET 1.1.4322. That helps as
expected for a few minutes until IIS again complains as above:

Description:
It is not possible to run two different versions of ASP.NET in the same IIS
process. Please use the IIS Administration Tool to reconfigure your server to
run the application in a separate process.

Ok then Terence suggested looking at the Home Directory tab and reseting
"root" to
"Default Application" by removing root and using the pulldown to load
"Default Application", setting ASP.NET to 1.1.4322. This was done. But,
that causes RWW and other W3SVC processes to fail.

But then resetting the ASP.NET tab back to ASP.nET 2.0.50727 and using World
Wide Web Publishing Service to restart W3SVC because of the error message:

Event Type: Error
Event Source: ASP.NET 2.0.50727.0
Event Category: None
Event ID: 1024
Date: 6/29/2007
Time: 3:52:47 PM
User: N/A
Computer: NARWHALE
Description:
Failed while restarting W3SVC. Error code: 0x8007041d

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

We come around right back to Web Part Error in Companyweb.

At this point we've come full circle at least once. But the crux of the
issue is we have "Web Part Error: This page has encountered a critical error.
Contact your system administrator if this problem persists." It's a problem
in SBS 2003 R2 only.

I'm not really clear about Gerald's suggestions other than a way to coax
more debugging information either locally or over RWW. He may have been
suggesting more than I realize, but if so I wasn't clear what he was
suggesting.

Anyway, the question is that while I am very, very grateful for all the
suggestions, time and help, what is next?

So much is different in SBS 2003 R2 (starting with SQL Server 2005) that I
feel quite stuck in the mud.

Finally, here is Terence Liu's check list with my answers:

Note: Ensure select 1.1.xx under the asp.net tab.
Ans: Yes done.

If we cannot resolve the issue after we perform the above steps, please
kindly help me collect some information for further investigation:
Ans: OK.

1. Do you get same error when you access the companyweb from internal
client computer?

Ans: Not exactly, I seem to get two manifestations of the same thing: "It
is not possible to run two different versions of ASP.NET in the same IIS
process" W3SVC is down. Locally on a client I don't get any web, just a
time out.

2. Do you get same error when you access the companyweb from SBS itself?
Ans: I don't get anything in a browser window when I try to access
companyweb from SBS (console) itself, just a timeout. And finally, over RWW
I get Service Unavailable messages from IIS as before.

Hope these steps will give you some help.
Ans: Not so far we need to keep digging.

Best regards,
Paul Wolfson


"Terence Liu [MSFT]" wrote:

[Quoted Text]
> Hello Paul,
>
> Thank you for kind reply.
>
> Based on my further research, I suggest we try the following steps:
>
> 1. Ran the following commands on SBS.
>
> c:\windows\Microsoft.Net\Framework\v1.1.4322.0 > aspnet_regiis -i also
> c:\windows\Microsoft.Net\Framework\v2.0.50727 > aspnet_regiis -i
>
> 2. Then ran command iisreset on SBS
>
> Then test this issue.
>
> From the metabase, I find the Application settings for companyweb is nor
> correct, I suggest we try the following steps if the above steps have no
> effect on this issue:
>
> 1. Open properties window of companyweb, select Home Directory tab,
>
> 2. The Application settings should be "Default Application" but not "root",
> please click Remove button to remove root.
>
> 3. Click OK.
>
> Note: Ensure select 1.1.xx under the asp.net tab.
>
> If we cannot resolve the issue after we perform the above steps, please
> kindly help me collect some information for further investigation:
>
> 1. Do you get same error when you access the companyweb from internal
> client computer?
>
> 2. Do you get same error when you access the companyweb from SBS itself?
>
> Hope these steps will give you some help.
>
> Thanks and have a nice day!
>
> Best regards,
>
> Terence Liu(MSFT)
>
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> This newsgroup only focuses on SBS technical issues. If you have issues
> regarding other Microsoft products, you'd better post in the corresponding
> newsgroups so that they can be resolved in an efficient and timely manner.
> You can locate the newsgroup here:
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
> When opening a new thread via the web interface, we recommend you check the
> "Notify me of replies" box to receive e-mail notifications when there are
> any updates in your thread. When responding to posts via your newsreader,
> please "Reply to Group" so that others may learn and benefit from your
> issue.
>
> Microsoft engineers can only focus on one issue per thread. Although we
> provide other information for your reference, we recommend you post
> different incidents in different threads to keep the thread clean. In doing
> so, it will ensure your issues are resolved in a timely manner.
>
> For urgent issues, you may want to contact Microsoft CSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> Any input or comments in this thread are highly appreciated.
> =====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --------------------
> | Thread-Topic: SBS2003R2 Sharepoint Web Part Error (new post)
> | thread-index: Ace4NfEJxrQXOFdgRha2UOQNnvrS0w==
> | X-WBNR-Posting-Host: 207.46.192.207
> | From: =?Utf-8?B?UGF1bCBXb2xmc29u?= <PaulWolfson[ at ]discussions.microsoft.com>
> | References: <F8173690-A39E-437D-BC0B-2F9F649D93DF[ at ]microsoft.com>
> <ebX1CNDuHHA.4572[ at ]TK2MSFTNGP02.phx.gbl>
> | Subject: Re: SBS2003R2 Sharepoint Web Part Error (new post)
> | Date: Tue, 26 Jun 2007 14:07:02 -0700
> | Lines: 63
> | Message-ID: <A22EEFDA-BAF1-4ED4-8915-0A940198703A[ at ]microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
> | Newsgroups: microsoft.public.windows.server.sbs
> | Path: TK2MSFTNGHUB02.phx.gbl
> | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:46458
> | NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
> | X-Tomcat-NG: microsoft.public.windows.server.sbs
> |
> | 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[ at ]discussions.microsoft.com> wrote in message
> | > news:F8173690-A39E-437D-BC0B-2F9F649D93DF[ at ]microsoft.com...
> | > > 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.
> | >
> | >
> | >
> |
>
>
Re: SBS2003R2 Sharepoint Web Part Error (new post)
v-terliu[ at ]online.microsoft.com (Terence Liu [MSFT]) 02.07.2007 10:08:07
Hello Paul,

Thank you for kind reply back.

First I want to explain that since we have performed some troubleshooting
steps and the issue remains. I think this problem may be a little complex
and our troubleshooting maybe time-consuming. So if you would like to call
CSS for assistance, I would be appreciate and think it is a more effective
ways. To obtain the phone numbers for specific technology request please
take a look at the web site listed below.

http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.

However I will do my best to be of assistance if you still want to continue
here.

From the event error, we can see that the error 1024 and 1062 all about
asp.net 2.0. I think the installation of asp.net 2.0 may corrupted the
companyweb site, I suggest we perform the following steps one by one to
reinstall the companyweb on SBS to see if we can resolve this issue:

How to remove and how to install the Windows Small Business Server 2003
SharePoint Services companyweb Web site
http://support.microsoft.com/?id=829114

If we still cannot resolve this issue after reinstall the companyweb, we
may have to try full backup the SBS and uninstall the asp.net 2.0 from SBS
thru Control panel->Add or Remove Programs.

Hope these steps will give you some help.

Thanks and have a nice day!

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: SBS2003R2 Sharepoint Web Part Error (new post)
| thread-index: Ace6luNtZCtctrPISZCRmSMKUK9sEA==
| X-WBNR-Posting-Host: 207.46.193.207
| From: =?Utf-8?B?UGF1bCBXb2xmc29u?= <PaulWolfson[ at ]discussions.microsoft.com>
| References: <F8173690-A39E-437D-BC0B-2F9F649D93DF[ at ]microsoft.com>
<ebX1CNDuHHA.4572[ at ]TK2MSFTNGP02.phx.gbl>
<A22EEFDA-BAF1-4ED4-8915-0A940198703A[ at ]microsoft.com>
<n10ki0KuHHA.2148[ at ]TK2MSFTNGHUB02.phx.gbl>
| Subject: Re: SBS2003R2 Sharepoint Web Part Error (new post)
| Date: Fri, 29 Jun 2007 14:46:02 -0700
| Lines: 305
| Message-ID: <C4251CB8-FBEC-419F-81FC-12183391F210[ at ]microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:47348
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Hello Terence,
|
| We seem to have gone in circles here. To review:
|
| Originally the server came up freshly loaded with Sharepoint 2.0
reporting
| critical errors in WebParts,
|
| "Web Part Error: This page has encountered a critical error. Contact your
| system administrator if this problem persists."
|
| Many suggestions here and elsewhere were to use ASP.NET 1.1.4322 rather
than
| ASP.NET v2.0.50727. That makes sense, coders can't always keep up with
| deadlines.
|
| However while that immediately fixed the Web Part Error within a little
| while (say 15 minutes) RWW fails with the error saying Service
Unavailable.
| That is explainable by the error logged by IIS:
|
| Event Type: Error
| Event Source: ASP.NET 2.0.50727.0
| Event Category: None
| Event ID: 1062
| Date: 6/29/2007
| Time: 3:39:51 PM
| User: N/A
| Computer: NARWHALE
| Description:
| It is not possible to run two different versions of ASP.NET in the same
IIS
| process. Please use the IIS Administration Tool to reconfigure your
server to
| run the application in a separate process.
|
| For more information, see Help and Support Center at
| http://go.microsoft.com/fwlink/events.asp.
|
|
| Then after much research it was determined that asp.net (both versions
| should be reloaded from the directories:
|
| c:\windows\Microsoft.Net\Framework\v1.1.4322.0 and
| c:\windows\Microsoft.Net\Framework\v2.0.50727
|
| using the command "aspnet_regiis -i" in each of the two.
|
| Run iisreset and set companyweb back to ASP.NET 1.1.4322. That helps as
| expected for a few minutes until IIS again complains as above:
|
| Description:
| It is not possible to run two different versions of ASP.NET in the same
IIS
| process. Please use the IIS Administration Tool to reconfigure your
server to
| run the application in a separate process.
|
| Ok then Terence suggested looking at the Home Directory tab and reseting
| "root" to
| "Default Application" by removing root and using the pulldown to load
| "Default Application", setting ASP.NET to 1.1.4322. This was done.
But,
| that causes RWW and other W3SVC processes to fail.
|
| But then resetting the ASP.NET tab back to ASP.nET 2.0.50727 and using
World
| Wide Web Publishing Service to restart W3SVC because of the error message:
|
| Event Type: Error
| Event Source: ASP.NET 2.0.50727.0
| Event Category: None
| Event ID: 1024
| Date: 6/29/2007
| Time: 3:52:47 PM
| User: N/A
| Computer: NARWHALE
| Description:
| Failed while restarting W3SVC. Error code: 0x8007041d
|
| For more information, see Help and Support Center at
| http://go.microsoft.com/fwlink/events.asp.
|
| We come around right back to Web Part Error in Companyweb.
|
| At this point we've come full circle at least once. But the crux of the
| issue is we have "Web Part Error: This page has encountered a critical
error.
| Contact your system administrator if this problem persists." It's a
problem
| in SBS 2003 R2 only.
|
| I'm not really clear about Gerald's suggestions other than a way to coax
| more debugging information either locally or over RWW. He may have been
| suggesting more than I realize, but if so I wasn't clear what he was
| suggesting.
|
| Anyway, the question is that while I am very, very grateful for all the
| suggestions, time and help, what is next?
|
| So much is different in SBS 2003 R2 (starting with SQL Server 2005) that
I
| feel quite stuck in the mud.
|
| Finally, here is Terence Liu's check list with my answers:
|
| Note: Ensure select 1.1.xx under the asp.net tab.
| Ans: Yes done.
|
| If we cannot resolve the issue after we perform the above steps, please
| kindly help me collect some information for further investigation:
| Ans: OK.
|
| 1. Do you get same error when you access the companyweb from internal
| client computer?
|
| Ans: Not exactly, I seem to get two manifestations of the same thing:
"It
| is not possible to run two different versions of ASP.NET in the same IIS
| process" W3SVC is down. Locally on a client I don't get any web, just a
| time out.
|
| 2. Do you get same error when you access the companyweb from SBS itself?
| Ans: I don't get anything in a browser window when I try to access
| companyweb from SBS (console) itself, just a timeout. And finally, over
RWW
| I get Service Unavailable messages from IIS as before.
|
| Hope these steps will give you some help.
| Ans: Not so far we need to keep digging.
|
| Best regards,
| Paul Wolfson
|
|
| "Terence Liu [MSFT]" wrote:
|
| > Hello Paul,
| >
| > Thank you for kind reply.
| >
| > Based on my further research, I suggest we try the following steps:
| >
| > 1. Ran the following commands on SBS.
| >
| > c:\windows\Microsoft.Net\Framework\v1.1.4322.0 > aspnet_regiis -i also
| > c:\windows\Microsoft.Net\Framework\v2.0.50727 > aspnet_regiis -i
| >
| > 2. Then ran command iisreset on SBS
| >
| > Then test this issue.
| >
| > From the metabase, I find the Application settings for companyweb is
nor
| > correct, I suggest we try the following steps if the above steps have
no
| > effect on this issue:
| >
| > 1. Open properties window of companyweb, select Home Directory tab,
| >
| > 2. The Application settings should be "Default Application" but not
"root",
| > please click Remove button to remove root.
| >
| > 3. Click OK.
| >
| > Note: Ensure select 1.1.xx under the asp.net tab.
| >
| > If we cannot resolve the issue after we perform the above steps, please
| > kindly help me collect some information for further investigation:
| >
| > 1. Do you get same error when you access the companyweb from internal
| > client computer?
| >
| > 2. Do you get same error when you access the companyweb from SBS itself?
| >
| > Hope these steps will give you some help.
| >
| > Thanks and have a nice day!
| >
| > Best regards,
| >
| > Terence Liu(MSFT)
| >
| > Microsoft CSS Online Newsgroup Support
| >
| > Get Secure! - www.microsoft.com/security
| >
| > =====================================================
| > This newsgroup only focuses on SBS technical issues. If you have issues
| > regarding other Microsoft products, you'd better post in the
corresponding
| > newsgroups so that they can be resolved in an efficient and timely
manner.
| > You can locate the newsgroup here:
| > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
| >
| > When opening a new thread via the web interface, we recommend you check
the
| > "Notify me of replies" box to receive e-mail notifications when there
are
| > any updates in your thread. When responding to posts via your
newsreader,
| > please "Reply to Group" so that others may learn and benefit from your
| > issue.
| >
| > Microsoft engineers can only focus on one issue per thread. Although we
| > provide other information for your reference, we recommend you post
| > different incidents in different threads to keep the thread clean. In
doing
| > so, it will ensure your issues are resolved in a timely manner.
| >
| > For urgent issues, you may want to contact Microsoft CSS directly.
Please
| > check http://support.microsoft.com for regional support phone numbers.
| >
| > Any input or comments in this thread are highly appreciated.
| > =====================================================
| >
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| > --------------------
| > | Thread-Topic: SBS2003R2 Sharepoint Web Part Error (new post)
| > | thread-index: Ace4NfEJxrQXOFdgRha2UOQNnvrS0w==
| > | X-WBNR-Posting-Host: 207.46.192.207
| > | From: =?Utf-8?B?UGF1bCBXb2xmc29u?=
<PaulWolfson[ at ]discussions.microsoft.com>
| > | References: <F8173690-A39E-437D-BC0B-2F9F649D93DF[ at ]microsoft.com>
| > <ebX1CNDuHHA.4572[ at ]TK2MSFTNGP02.phx.gbl>
| > | Subject: Re: SBS2003R2 Sharepoint Web Part Error (new post)
| > | Date: Tue, 26 Jun 2007 14:07:02 -0700
| > | Lines: 63
| > | Message-ID: <A22EEFDA-BAF1-4ED4-8915-0A940198703A[ at ]microsoft.com>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | charset="Utf-8"
| > | Content-Transfer-Encoding: 7bit
| > | X-Newsreader: Microsoft CDO for Windows 2000
| > | Content-Class: urn:content-classes:message
| > | Importance: normal
| > | Priority: normal
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| > | Newsgroups: microsoft.public.windows.server.sbs
| > | Path: TK2MSFTNGHUB02.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:46458
| > | NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| > | X-Tomcat-NG: microsoft.public.windows.server.sbs
| > |
| > | 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[ at ]discussions.microsoft.com> wrote in
message
| > | > news:F8173690-A39E-437D-BC0B-2F9F649D93DF[ at ]microsoft.com...
| > | > > 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.
| > | >
| > | >
| > | >
| > |
| >
| >
|

Re: SBS2003R2 Sharepoint Web Part Error (new post)
Paul Wolfson 02.07.2007 19:30:02
Terence -

I agree with you that this is complex. I know this is tough - I'm about to
change out hardware and do a complete AD rebuild. The only other site using
SBS2003R2 is on a Core-Duo Intel CPU. Here because of parts availablity we
chose a Dual Core AMD Athalon 4800+. On an AM2 ASUS board we had BIOS
writing to protected memory error but Sharepoint worked even though the
server crashed every few hours (Lots of finger pointing but no solution). To
check components we shifted to an ECS AMD690 board and the server has run
stablely except for Sharepoint.

I have two options here, change out SBS2003R2 for a pair of Standard 2003R2
servers. 2nd server would run Exchange 2007 and be a redundant file server
(my orignal preference). Standard Server 2003R2 has run stablely on both
Intel and AM2 AMD dual core processors. Since the CPU load average is 6%
with peaks to 65% when huge print jobs hit the network this entry level
server ought work.

I'd appreciate your best guess here:

1. Blame AMD and use an Intel Duo-Core Pentium / Xeon only?
2. Abandon SBS 2003 R2 and go to more robust Standard Server 2003 R2?
3. Try your procedures to reload and hope AD survives?
4. Abandon AMD Athalon and use an Opteron based Board?

After mid-2004, SBS2003 just didn't have these problems. Only with the AM2
processor (Entry level AM2 Athalon Server) have we seen problems in in SBS
2003 R2. SBS has been an amazingly stable system for almost four years
now, what we are seeing looks like the orginal SBS2003 release which took a
while to stabilize and clean up.

Kindest regards,
Paul

"Terence Liu [MSFT]" wrote:

[Quoted Text]
> Hello Paul,
>
> Thank you for kind reply back.
>
> First I want to explain that since we have performed some troubleshooting
> steps and the issue remains. I think this problem may be a little complex
> and our troubleshooting maybe time-consuming. So if you would like to call
> CSS for assistance, I would be appreciate and think it is a more effective
> ways. To obtain the phone numbers for specific technology request please
> take a look at the web site listed below.
>
> http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
>
> If you are outside the US please see http://support.microsoft.com for
> regional support phone numbers.
>
> However I will do my best to be of assistance if you still want to continue
> here.
>
> From the event error, we can see that the error 1024 and 1062 all about
> asp.net 2.0. I think the installation of asp.net 2.0 may corrupted the
> companyweb site, I suggest we perform the following steps one by one to
> reinstall the companyweb on SBS to see if we can resolve this issue:
>
> How to remove and how to install the Windows Small Business Server 2003
> SharePoint Services companyweb Web site
> http://support.microsoft.com/?id=829114
>
> If we still cannot resolve this issue after reinstall the companyweb, we
> may have to try full backup the SBS and uninstall the asp.net 2.0 from SBS
> thru Control panel->Add or Remove Programs.
>
> Hope these steps will give you some help.
>
> Thanks and have a nice day!
>
> Best regards,
>
> Terence Liu(MSFT)
>
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> This newsgroup only focuses on SBS technical issues. If you have issues
> regarding other Microsoft products, you'd better post in the corresponding
> newsgroups so that they can be resolved in an efficient and timely manner.
> You can locate the newsgroup here:
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
> When opening a new thread via the web interface, we recommend you check the
> "Notify me of replies" box to receive e-mail notifications when there are
> any updates in your thread. When responding to posts via your newsreader,
> please "Reply to Group" so that others may learn and benefit from your
> issue.
>
> Microsoft engineers can only focus on one issue per thread. Although we
> provide other information for your reference, we recommend you post
> different incidents in different threads to keep the thread clean. In doing
> so, it will ensure your issues are resolved in a timely manner.
>
> For urgent issues, you may want to contact Microsoft CSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> Any input or comments in this thread are highly appreciated.
> =====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --------------------
> | Thread-Topic: SBS2003R2 Sharepoint Web Part Error (new post)
> | thread-index: Ace6luNtZCtctrPISZCRmSMKUK9sEA==
> | X-WBNR-Posting-Host: 207.46.193.207
> | From: =?Utf-8?B?UGF1bCBXb2xmc29u?= <PaulWolfson[ at ]discussions.microsoft.com>
> | References: <F8173690-A39E-437D-BC0B-2F9F649D93DF[ at ]microsoft.com>
> <ebX1CNDuHHA.4572[ at ]TK2MSFTNGP02.phx.gbl>
> <A22EEFDA-BAF1-4ED4-8915-0A940198703A[ at ]microsoft.com>
> <n10ki0KuHHA.2148[ at ]TK2MSFTNGHUB02.phx.gbl>
> | Subject: Re: SBS2003R2 Sharepoint Web Part Error (new post)
> | Date: Fri, 29 Jun 2007 14:46:02 -0700
> | Lines: 305
> | Message-ID: <C4251CB8-FBEC-419F-81FC-12183391F210[ at ]microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
> | Newsgroups: microsoft.public.windows.server.sbs
> | Path: TK2MSFTNGHUB02.phx.gbl
> | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:47348
> | NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
> | X-Tomcat-NG: microsoft.public.windows.server.sbs
> |
> | Hello Terence,
> |
> | We seem to have gone in circles here. To review:
> |
> | Originally the server came up freshly loaded with Sharepoint 2.0
> reporting
> | critical errors in WebParts,
> |
> | "Web Part Error: This page has encountered a critical error. Contact your
> | system administrator if this problem persists."
> |
> | Many suggestions here and elsewhere were to use ASP.NET 1.1.4322 rather
> than
> | ASP.NET v2.0.50727. That makes sense, coders can't always keep up with
> | deadlines.
> |
> | However while that immediately fixed the Web Part Error within a little
> | while (say 15 minutes) RWW fails with the error saying Service
> Unavailable.
> | That is explainable by the error logged by IIS:
> |
> | Event Type: Error
> | Event Source: ASP.NET 2.0.50727.0
> | Event Category: None
> | Event ID: 1062
> | Date: 6/29/2007
> | Time: 3:39:51 PM
> | User: N/A
> | Computer: NARWHALE
> | Description:
> | It is not possible to run two different versions of ASP.NET in the same
> IIS
> | process. Please use the IIS Administration Tool to reconfigure your
> server to
> | run the application in a separate process.
> |
> | For more information, see Help and Support Center at
> | http://go.microsoft.com/fwlink/events.asp.
> |
> |
> | Then after much research it was determined that asp.net (both versions
> | should be reloaded from the directories:
> |
> | c:\windows\Microsoft.Net\Framework\v1.1.4322.0 and
> | c:\windows\Microsoft.Net\Framework\v2.0.50727
> |
> | using the command "aspnet_regiis -i" in each of the two.
> |
> | Run iisreset and set companyweb back to ASP.NET 1.1.4322. That helps as
> | expected for a few minutes until IIS again complains as above:
> |
> | Description:
> | It is not possible to run two different versions of ASP.NET in the same
> IIS
> | process. Please use the IIS Administration Tool to reconfigure your
> server to
> | run the application in a separate process.
> |
> | Ok then Terence suggested looking at the Home Directory tab and reseting
> | "root" to
> | "Default Application" by removing root and using the pulldown to load
> | "Default Application", setting ASP.NET to 1.1.4322. This was done.
> But,
> | that causes RWW and other W3SVC processes to fail.
> |
> | But then resetting the ASP.NET tab back to ASP.nET 2.0.50727 and using
> World
> | Wide Web Publishing Service to restart W3SVC because of the error message:
> |
> | Event Type: Error
> | Event Source: ASP.NET 2.0.50727.0
> | Event Category: None
> | Event ID: 1024
> | Date: 6/29/2007
> | Time: 3:52:47 PM
> | User: N/A
> | Computer: NARWHALE
> | Description:
> | Failed while restarting W3SVC. Error code: 0x8007041d
> |
> | For more information, see Help and Support Center at
> | http://go.microsoft.com/fwlink/events.asp.
> |
> | We come around right back to Web Part Error in Companyweb.
> |
> | At this point we've come full circle at least once. But the crux of the
> | issue is we have "Web Part Error: This page has encountered a critical
> error.
> | Contact your system administrator if this problem persists." It's a
> problem
> | in SBS 2003 R2 only.
> |
> | I'm not really clear about Gerald's suggestions other than a way to coax
> | more debugging information either locally or over RWW. He may have been
> | suggesting more than I realize, but if so I wasn't clear what he was
> | suggesting.
> |
> | Anyway, the question is that while I am very, very grateful for all the
> | suggestions, time and help, what is next?
> |
> | So much is different in SBS 2003 R2 (starting with SQL Server 2005) that
> I
> | feel quite stuck in the mud.
> |
> | Finally, here is Terence Liu's check list with my answers:
> |
> | Note: Ensure select 1.1.xx under the asp.net tab.
> | Ans: Yes done.
> |
> | If we cannot resolve the issue after we perform the above steps, please
> | kindly help me collect some information for further investigation:
> | Ans: OK.
> |
> | 1. Do you get same error when you access the companyweb from internal
> | client computer?
> |
> | Ans: Not exactly, I seem to get two manifestations of the same thing:
> "It
> | is not possible to run two different versions of ASP.NET in the same IIS
> | process" W3SVC is down. Locally on a client I don't get any web, just a
> | time out.
> |
> | 2. Do you get same error when you access the companyweb from SBS itself?
> | Ans: I don't get anything in a browser window when I try to access
> | companyweb from SBS (console) itself, just a timeout. And finally, over
> RWW
> | I get Service Unavailable messages from IIS as before.
> |
> | Hope these steps will give you some help.
> | Ans: Not so far we need to keep digging.
> |
> | Best regards,
> | Paul Wolfson
> |
> |
> | "Terence Liu [MSFT]" wrote:
> |
> | > Hello Paul,
> | >
> | > Thank you for kind reply.
> | >
> | > Based on my further research, I suggest we try the following steps:
> | >
> | > 1. Ran the following commands on SBS.
> | >
> | > c:\windows\Microsoft.Net\Framework\v1.1.4322.0 > aspnet_regiis -i also
> | > c:\windows\Microsoft.Net\Framework\v2.0.50727 > aspnet_regiis -i
> | >
> | > 2. Then ran command iisreset on SBS
> | >
> | > Then test this issue.
> | >
> | > From the metabase, I find the Application settings for companyweb is
> nor
> | > correct, I suggest we try the following steps if the above steps have
> no
> | > effect on this issue:
> | >
> | > 1. Open properties window of companyweb, select Home Directory tab,
> | >
> | > 2. The Application settings should be "Default Application" but not
> "root",
> | > please click Remove button to remove root.
> | >
> | > 3. Click OK.
> | >
> | > Note: Ensure select 1.1.xx under the asp.net tab.
> | >
> | > If we cannot resolve the issue after we perform the above steps, please
> | > kindly help me collect some information for further investigation:
> | >
> | > 1. Do you get same error when you access the companyweb from internal
> | > client computer?
> | >
> | > 2. Do you get same error when you access the companyweb from SBS itself?
> | >
> | > Hope these steps will give you some help.
> | >
> | > Thanks and have a nice day!
> | >
> | > Best regards,
> | >
> | > Terence Liu(MSFT)
> | >
> | > Microsoft CSS Online Newsgroup Support
> | >
> | > Get Secure! - www.microsoft.com/security
> | >
> | > =====================================================
> | > This newsgroup only focuses on SBS technical issues. If you have issues
> | > regarding other Microsoft products, you'd better post in the
> corresponding
> | > newsgroups so that they can be resolved in an efficient and timely
> manner.
> | > You can locate the newsgroup here:
> | > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
> | >
> | > When opening a new thread via the web interface, we recommend you check
> the
> | > "Notify me of replies" box to receive e-mail notifications when there
> are
> | > any updates in your thread. When responding to posts via your
Re: SBS2003R2 Sharepoint Web Part Error (new post)
v-terliu[ at ]online.microsoft.com (Terence Liu [MSFT]) 03.07.2007 06:03:03
Hello Paul,

Thank you for kind update.

Since I'm not familiar with hardware of server, I cannot give you some
further advice on it. However, you can check all the hardware with our HCL:
http://www.microsoft.com/whdc/hcl/default.mspx
Ensure that the server's CPU and board and other components are all in our
HCL.

Another easy way, please try to buy popular model server from famous
manufacturer, like IBM, HP or DELL. The server come from the manufacturer
pass through compatibility test.

Of course, you can contact your hardware vendor for further investigation.

If you still want to do troubleshooting on this thread with me, I suggest
you try to do reinstall the companyweb thru the KB829114 and let me know
the result.
If you want to do this issue with our CSS or with your hardware vendor,
please also let me know, I will close this thread.

If there's anything else I can do for you, please do not hesitate to let me
know.

Thank you and have a nice day,

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: SBS2003R2 Sharepoint Web Part Error (new post)
| thread-index: Ace832KexPNj5luKSmCKQWKRub0W+Q==
| X-WBNR-Posting-Host: 207.46.193.207
| From: =?Utf-8?B?UGF1bCBXb2xmc29u?= <PaulWolfson[ at ]discussions.microsoft.com>
| References: <F8173690-A39E-437D-BC0B-2F9F649D93DF[ at ]microsoft.com>
<ebX1CNDuHHA.4572[ at ]TK2MSFTNGP02.phx.gbl>
<A22EEFDA-BAF1-4ED4-8915-0A940198703A[ at ]microsoft.com>
<n10ki0KuHHA.2148[ at ]TK2MSFTNGHUB02.phx.gbl>
<C4251CB8-FBEC-419F-81FC-12183391F210[ at ]microsoft.com>
<cnUTkDJvHHA.3972[ at ]TK2MSFTNGHUB02.phx.gbl>
| Subject: Re: SBS2003R2 Sharepoint Web Part Error (new post)
| Date: Mon, 2 Jul 2007 12:30:02 -0700
| Lines: 336
| Message-ID: <FFB1792B-8099-4BBF-A23F-A15E5B110B13[ at ]microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:47706
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Terence -
|
| I agree with you that this is complex. I know this is tough - I'm about
to
| change out hardware and do a complete AD rebuild. The only other site
using
| SBS2003R2 is on a Core-Duo Intel CPU. Here because of parts availablity
we
| chose a Dual Core AMD Athalon 4800+. On an AM2 ASUS board we had BIOS
| writing to protected memory error but Sharepoint worked even though the
| server crashed every few hours (Lots of finger pointing but no solution).
To
| check components we shifted to an ECS AMD690 board and the server has run
| stablely except for Sharepoint.
|
| I have two options here, change out SBS2003R2 for a pair of Standard
2003R2
| servers. 2nd server would run Exchange 2007 and be a redundant file
server
| (my orignal preference). Standard Server 2003R2 has run stablely on both
| Intel and AM2 AMD dual core processors. Since the CPU load average is 6%
| with peaks to 65% when huge print jobs hit the network this entry level
| server ought work.
|
| I'd appreciate your best guess here:
|
| 1. Blame AMD and use an Intel Duo-Core Pentium / Xeon only?
| 2. Abandon SBS 2003 R2 and go to more robust Standard Server 2003 R2?
| 3. Try your procedures to reload and hope AD survives?
| 4. Abandon AMD Athalon and use an Opteron based Board?
|
| After mid-2004, SBS2003 just didn't have these problems. Only with the
AM2
| processor (Entry level AM2 Athalon Server) have we seen problems in in
SBS
| 2003 R2. SBS has been an amazingly stable system for almost four years
| now, what we are seeing looks like the orginal SBS2003 release which took
a
| while to stabilize and clean up.
|
| Kindest regards,
| Paul
|
| "Terence Liu [MSFT]" wrote:
|
| > Hello Paul,
| >
| > Thank you for kind reply back.
| >
| > First I want to explain that since we have performed some
troubleshooting
| > steps and the issue remains. I think this problem may be a little
complex
| > and our troubleshooting maybe time-consuming. So if you would like to
call
| > CSS for assistance, I would be appreciate and think it is a more
effective
| > ways. To obtain the phone numbers for specific technology request
please
| > take a look at the web site listed below.
| >
| > http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
| >
| > If you are outside the US please see http://support.microsoft.com for
| > regional support phone numbers.
| >
| > However I will do my best to be of assistance if you still want to
continue
| > here.
| >
| > From the event error, we can see that the error 1024 and 1062 all about
| > asp.net 2.0. I think the installation of asp.net 2.0 may corrupted the
| > companyweb site, I suggest we perform the following steps one by one to
| > reinstall the companyweb on SBS to see if we can resolve this issue:
| >
| > How to remove and how to install the Windows Small Business Server 2003
| > SharePoint Services companyweb Web site
| > http://support.microsoft.com/?id=829114
| >
| > If we still cannot resolve this issue after reinstall the companyweb,
we
| > may have to try full backup the SBS and uninstall the asp.net 2.0 from
SBS
| > thru Control panel->Add or Remove Programs.
| >
| > Hope these steps will give you some help.
| >
| > Thanks and have a nice day!
| >
| > Best regards,
| >
| > Terence Liu(MSFT)
| >
| > Microsoft CSS Online Newsgroup Support
| >
| > Get Secure! - www.microsoft.com/security
| >
| > =====================================================
| > This newsgroup only focuses on SBS technical issues. If you have issues
| > regarding other Microsoft products, you'd better post in the
corresponding
| > newsgroups so that they can be resolved in an efficient and timely
manner.
| > You can locate the newsgroup here:
| > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
| >
| > When opening a new thread via the web interface, we recommend you check
the
| > "Notify me of replies" box to receive e-mail notifications when there
are
| > any updates in your thread. When responding to posts via your
newsreader,
| > please "Reply to Group" so that others may learn and benefit from your
| > issue.
| >
| > Microsoft engineers can only focus on one issue per thread. Although we
| > provide other information for your reference, we recommend you post
| > different incidents in different threads to keep the thread clean. In
doing
| > so, it will ensure your issues are resolved in a timely manner.
| >
| > For urgent issues, you may want to contact Microsoft CSS directly.
Please
| > check http://support.microsoft.com for regional support phone numbers.
| >
| > Any input or comments in this thread are highly appreciated.
| > =====================================================
| >
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| > --------------------
| > | Thread-Topic: SBS2003R2 Sharepoint Web Part Error (new post)
| > | thread-index: Ace6luNtZCtctrPISZCRmSMKUK9sEA==
| > | X-WBNR-Posting-Host: 207.46.193.207
| > | From: =?Utf-8?B?UGF1bCBXb2xmc29u?=
<PaulWolfson[ at ]discussions.microsoft.com>
| > | References: <F8173690-A39E-437D-BC0B-2F9F649D93DF[ at ]microsoft.com>
| > <ebX1CNDuHHA.4572[ at ]TK2MSFTNGP02.phx.gbl>
| > <A22EEFDA-BAF1-4ED4-8915-0A940198703A[ at ]microsoft.com>
| > <n10ki0KuHHA.2148[ at ]TK2MSFTNGHUB02.phx.gbl>
| > | Subject: Re: SBS2003R2 Sharepoint Web Part Error (new post)
| > | Date: Fri, 29 Jun 2007 14:46:02 -0700
| > | Lines: 305
| > | Message-ID: <C4251CB8-FBEC-419F-81FC-12183391F210[ at ]microsoft.com>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | charset="Utf-8"
| > | Content-Transfer-Encoding: 7bit
| > | X-Newsreader: Microsoft CDO for Windows 2000
| > | Content-Class: urn:content-classes:message
| > | Importance: normal
| > | Priority: normal
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| > | Newsgroups: microsoft.public.windows.server.sbs
| > | Path: TK2MSFTNGHUB02.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:47348
| > | NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| > | X-Tomcat-NG: microsoft.public.windows.server.sbs
| > |
| > | Hello Terence,
| > |
| > | We seem to have gone in circles here. To review:
| > |
| > | Originally the server came up freshly loaded with Sharepoint 2.0
| > reporting
| > | critical errors in WebParts,
| > |
| > | "Web Part Error: This page has encountered a critical error. Contact
your
| > | system administrator if this problem persists."
| > |
| > | Many suggestions here and elsewhere were to use ASP.NET 1.1.4322
rather
| > than
| > | ASP.NET v2.0.50727. That makes sense, coders can't always keep up
with
| > | deadlines.
| > |
| > | However while that immediately fixed the Web Part Error within a
little
| > | while (say 15 minutes) RWW fails with the error saying Service
| > Unavailable.
| > | That is explainable by the error logged by IIS:
| > |
| > | Event Type: Error
| > | Event Source: ASP.NET 2.0.50727.0
| > | Event Category: None
| > | Event ID: 1062
| > | Date: 6/29/2007
| > | Time: 3:39:51 PM
| > | User: N/A
| > | Computer: NARWHALE
| > | Description:
| > | It is not possible to run two different versions of ASP.NET in the
same
| > IIS
| > | process. Please use the IIS Administration Tool to reconfigure your
| > server to
| > | run the application in a separate process.
| > |
| > | For more information, see Help and Support Center at
| > | http://go.microsoft.com/fwlink/events.asp.
| > |
| > |
| > | Then after much research it was determined that asp.net (both
versions
| > | should be reloaded from the directories:
| > |
| > | c:\windows\Microsoft.Net\Framework\v1.1.4322.0 and
| > | c:\windows\Microsoft.Net\Framework\v2.0.50727
| > |
| > | using the command "aspnet_regiis -i" in each of the two.
| > |
| > | Run iisreset and set companyweb back to ASP.NET 1.1.4322. That helps
as
| > | expected for a few minutes until IIS again complains as above:
| > |
| > | Description:
| > | It is not possible to run two different versions of ASP.NET in the
same
| > IIS
| > | process. Please use the IIS Administration Tool to reconfigure your
| > server to
| > | run the application in a separate process.
| > |
| > | Ok then Terence suggested looking at the Home Directory tab and
reseting
| > | "root" to
| > | "Default Application" by removing root and using the pulldown to load
| > | "Default Application", setting ASP.NET to 1.1.4322. This was done.
| > But,
| > | that causes RWW and other W3SVC processes to fail.
| > |
| > | But then resetting the ASP.NET tab back to ASP.nET 2.0.50727 and
using
| > World
| > | Wide Web Publishing Service to restart W3SVC because of the error
message:
| > |
| > | Event Type: Error
| > | Event Source: ASP.NET 2.0.50727.0
| > | Event Category: None
| > | Event ID: 1024
| > | Date: 6/29/2007
| > | Time: 3:52:47 PM
| > | User: N/A
| > | Computer: NARWHALE
| > | Description:
| > | Failed while restarting W3SVC. Error code: 0x8007041d
| > |
| > | For more information, see Help and Support Center at
| > | http://go.microsoft.com/fwlink/events.asp.
| > |
| > | We come around right back to Web Part Error in Companyweb.
| > |
| > | At this point we've come full circle at least once. But the crux of
the
| > | issue is we have "Web Part Error: This page has encountered a
critical
| > error.
| > | Contact your system administrator if this problem persists." It's a
| > problem
| > | in SBS 2003 R2 only.
| > |
| > | I'm not really clear about Gerald's suggestions other than a way to
coax
| > | more debugging information either locally or over RWW. He may have
been
| > | suggesting more than I realize, but if so I wasn't clear what he was
| > | suggesting.
| > |
| > | Anyway, the question is that while I am very, very grateful for all
the
| > | suggestions, time and help, what is next?
| > |
| > | So much is different in SBS 2003 R2 (starting with SQL Server 2005)
that
| > I
| > | feel quite stuck in the mud.
| > |
| > | Finally, here is Terence Liu's check list with my answers:
| > |
| > | Note: Ensure select 1.1.xx under the asp.net tab.
| > | Ans: Yes done.
| > |
| > | If we cannot resolve the issue after we perform the above steps,
please
| > | kindly help me collect some information for further investigation:
| > | Ans: OK.
| > |
| > | 1. Do you get same error when you access the companyweb from
internal
| > | client computer?
| > |
| > | Ans: Not exactly, I seem to get two manifestations of the same
thing:
| > "It
| > | is not possible to run two different versions of ASP.NET in the same
IIS
| > | process" W3SVC is down. Locally on a client I don't get any web,
just a
| > | time out.
| > |
| > | 2. Do you get same error when you access the companyweb from SBS
itself?
| > | Ans: I don't get anything in a browser window when I try to access
| > | companyweb from SBS (console) itself, just a timeout. And finally,
over
| > RWW
| > | I get Service Unavailable messages from IIS as before.
| > |
| > | Hope these steps will give you some help.
| > | Ans: Not so far we need to keep digging.
| > |
| > | Best regards,
| > | Paul Wolfson
| > |
| > |
| > | "Terence Liu [MSFT]" wrote:
| > |
| > | > Hello Paul,
| > | >
| > | > Thank you for kind reply.
| > | >
| > | > Based on my further research, I suggest we try the following steps:
| > | >
| > | > 1. Ran the following commands on SBS.
| > | >
| > | > c:\windows\Microsoft.Net\Framework\v1.1.4322.0 > aspnet_regiis -i
also
| > | > c:\windows\Microsoft.Net\Framework\v2.0.50727 > aspnet_regiis -i
| > | >
| > | > 2. Then ran command iisreset on SBS
| > | >
| > | > Then test this issue.
| > | >
| > | > From the metabase, I find the Application settings for companyweb
is
| > nor
| > | > correct, I suggest we try the following steps if the above steps
have
| > no
| > | > effect on this issue:
| > | >
| > | > 1. Open properties window of companyweb, select Home Directory tab,
| > | >
| > | > 2. The Application settings should be "Default Application" but not
| > "root",
| > | > please click Remove button to remove root.
| > | >
| > | > 3. Click OK.
| > | >
| > | > Note: Ensure select 1.1.xx under the asp.net tab.
| > | >
| > | > If we cannot resolve the issue after we perform the above steps,
please
| > | > kindly help me collect some information for further investigation:
| > | >
| > | > 1. Do you get same error when you access the companyweb from
internal
| > | > client computer?
| > | >
| > | > 2. Do you get same error when you access the companyweb from SBS
itself?
| > | >
| > | > Hope these steps will give you some help.
| > | >
| > | > Thanks and have a nice day!
| > | >
| > | > Best regards,
| > | >
| > | > Terence Liu(MSFT)
| > | >
| > | > Microsoft CSS Online Newsgroup Support
| > | >
| > | > Get Secure! - www.microsoft.com/security
| > | >
| > | > =====================================================
| > | > This newsgroup only focuses on SBS technical issues. If you have
issues
| > | > regarding other Microsoft products, you'd better post in the
| > corresponding
| > | > newsgroups so that they can be resolved in an efficient and timely
| > manner.
| > | > You can locate the newsgroup here:
| > | > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
| > | >
| > | > When opening a new thread via the web interface, we recommend you
check
| > the
| > | > "Notify me of replies" box to receive e-mail notifications when
there
| > are
| > | > any updates in your thread. When responding to posts via your
|

Re: SBS2003R2 Sharepoint Web Part Error (new post)
Paul Wolfson 03.07.2007 14:42:00
Terence,

I'll opt to close this thread with a few comments:

The original server built on an ASUS M2N with an Adaptec RAID controller is
now running Windows Standard 2003 R2 server on the customer's site, after a
stint running XP, as a test, in the managing partner's office. It has now
been joined by a second. All but AD management is now running on those
servers rather than SBS. SBS really crams a lot into a single box and this
kind of problem though rare does occur. The biggest problem with SBS is on a
25 node network, you cannot just dump and reload the server without heavy
penalties. We've just reached the point of AD reload.

As to hardware, check Microsoft's hardware acceptance list: you will find
ASUS M2N and Adaptec as certified for Windows 2003 servers.

As to IBM, HP and Dell, all I can say is with the problems of OEM preloads
of SBS as well as occasional hardware problems; they can cause more
headaches than they solve. The hardware choice is always at the customer's
pleasure.

It may be that SBS R2 is just too immature at this point to use in
production. Some clients will continue to opt for SBS, but as with this
client we will continue to recommend a dual redundant server solution with
SBS as a fall back solution where the cost of hardware outweighs the risk of
SBS versus standard Server(s).

Anyway, on that note, it has truely been a pleasure corresponding with you.
I know this has been a very taxing thread to deal with. You have put a lot
of time and effort into working it.

Thanks for your efforts and best regards,

Paul Wolfson



"Terence Liu [MSFT]" wrote:

[Quoted Text]
> Hello Paul,
>
> Thank you for kind update.
>
> Since I'm not familiar with hardware of server, I cannot give you some
> further advice on it. However, you can check all the hardware with our HCL:
> http://www.microsoft.com/whdc/hcl/default.mspx
> Ensure that the server's CPU and board and other components are all in our
> HCL.
>
> Another easy way, please try to buy popular model server from famous
> manufacturer, like IBM, HP or DELL. The server come from the manufacturer
> pass through compatibility test.
>
> Of course, you can contact your hardware vendor for further investigation.
>
> If you still want to do troubleshooting on this thread with me, I suggest
> you try to do reinstall the companyweb thru the KB829114 and let me know
> the result.
> If you want to do this issue with our CSS or with your hardware vendor,
> please also let me know, I will close this thread.
>
> If there's anything else I can do for you, please do not hesitate to let me
> know.
>
> Thank you and have a nice day,
>
> Best regards,
>
> Terence Liu(MSFT)
>
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> This newsgroup only focuses on SBS technical issues. If you have issues
> regarding other Microsoft products, you'd better post in the corresponding
> newsgroups so that they can be resolved in an efficient and timely manner.
> You can locate the newsgroup here:
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
> When opening a new thread via the web interface, we recommend you check the
> "Notify me of replies" box to receive e-mail notifications when there are
> any updates in your thread. When responding to posts via your newsreader,
> please "Reply to Group" so that others may learn and benefit from your
> issue.
>
> Microsoft engineers can only focus on one issue per thread. Although we
> provide other information for your reference, we recommend you post
> different incidents in different threads to keep the thread clean. In doing
> so, it will ensure your issues are resolved in a timely manner.
>
> For urgent issues, you may want to contact Microsoft CSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> Any input or comments in this thread are highly appreciated.
> =====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --------------------
> | Thread-Topic: SBS2003R2 Sharepoint Web Part Error (new post)
> | thread-index: Ace832KexPNj5luKSmCKQWKRub0W+Q==
> | X-WBNR-Posting-Host: 207.46.193.207
> | From: =?Utf-8?B?UGF1bCBXb2xmc29u?= <PaulWolfson[ at ]discussions.microsoft.com>
> | References: <F8173690-A39E-437D-BC0B-2F9F649D93DF[ at ]microsoft.com>
> <ebX1CNDuHHA.4572[ at ]TK2MSFTNGP02.phx.gbl>
> <A22EEFDA-BAF1-4ED4-8915-0A940198703A[ at ]microsoft.com>
> <n10ki0KuHHA.2148[ at ]TK2MSFTNGHUB02.phx.gbl>
> <C4251CB8-FBEC-419F-81FC-12183391F210[ at ]microsoft.com>
> <cnUTkDJvHHA.3972[ at ]TK2MSFTNGHUB02.phx.gbl>
> | Subject: Re: SBS2003R2 Sharepoint Web Part Error (new post)
> | Date: Mon, 2 Jul 2007 12:30:02 -0700
> | Lines: 336
> | Message-ID: <FFB1792B-8099-4BBF-A23F-A15E5B110B13[ at ]microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
> | Newsgroups: microsoft.public.windows.server.sbs
> | Path: TK2MSFTNGHUB02.phx.gbl
> | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:47706
> | NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
> | X-Tomcat-NG: microsoft.public.windows.server.sbs
> |
> | Terence -
> |
> | I agree with you that this is complex. I know this is tough - I'm about
> to
> | change out hardware and do a complete AD rebuild. The only other site
> using
> | SBS2003R2 is on a Core-Duo Intel CPU. Here because of parts availablity
> we
> | chose a Dual Core AMD Athalon 4800+. On an AM2 ASUS board we had BIOS
> | writing to protected memory error but Sharepoint worked even though the
> | server crashed every few hours (Lots of finger pointing but no solution).
> To
> | check components we shifted to an ECS AMD690 board and the server has run
> | stablely except for Sharepoint.
> |
> | I have two options here, change out SBS2003R2 for a pair of Standard
> 2003R2
> | servers. 2nd server would run Exchange 2007 and be a redundant file
> server
> | (my orignal preference). Standard Server 2003R2 has run stablely on both
> | Intel and AM2 AMD dual core processors. Since the CPU load average is 6%
> | with peaks to 65% when huge print jobs hit the network this entry level
> | server ought work.
> |
> | I'd appreciate your best guess here:
> |
> | 1. Blame AMD and use an Intel Duo-Core Pentium / Xeon only?
> | 2. Abandon SBS 2003 R2 and go to more robust Standard Server 2003 R2?
> | 3. Try your procedures to reload and hope AD survives?
> | 4. Abandon AMD Athalon and use an Opteron based Board?
> |
> | After mid-2004, SBS2003 just didn't have these problems. Only with the
> AM2
> | processor (Entry level AM2 Athalon Server) have we seen problems in in
> SBS
> | 2003 R2. SBS has been an amazingly stable system for almost four years
> | now, what we are seeing looks like the orginal SBS2003 release which took
> a
> | while to stabilize and clean up.
> |
> | Kindest regards,
> | Paul
> |
> | "Terence Liu [MSFT]" wrote:
> |
> | > Hello Paul,
> | >
> | > Thank you for kind reply back.
> | >
> | > First I want to explain that since we have performed some
> troubleshooting
> | > steps and the issue remains. I think this problem may be a little
> complex
> | > and our troubleshooting maybe time-consuming. So if you would like to
> call
> | > CSS for assistance, I would be appreciate and think it is a more
> effective
> | > ways. To obtain the phone numbers for specific technology request
> please
> | > take a look at the web site listed below.
> | >
> | > http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
> | >
> | > If you are outside the US please see http://support.microsoft.com for
> | > regional support phone numbers.
> | >
> | > However I will do my best to be of assistance if you still want to
> continue
> | > here.
> | >
> | > From the event error, we can see that the error 1024 and 1062 all about
> | > asp.net 2.0. I think the installation of asp.net 2.0 may corrupted the
> | > companyweb site, I suggest we perform the following steps one by one to
> | > reinstall the companyweb on SBS to see if we can resolve this issue:
> | >
> | > How to remove and how to install the Windows Small Business Server 2003
> | > SharePoint Services companyweb Web site
> | > http://support.microsoft.com/?id=829114
> | >
> | > If we still cannot resolve this issue after reinstall the companyweb,
> we
> | > may have to try full backup the SBS and uninstall the asp.net 2.0 from
> SBS
> | > thru Control panel->Add or Remove Programs.
> | >
> | > Hope these steps will give you some help.
> | >
> | > Thanks and have a nice day!
> | >
> | > Best regards,
> | >
> | > Terence Liu(MSFT)
> | >
> | > Microsoft CSS Online Newsgroup Support
> | >
> | > Get Secure! - www.microsoft.com/security
> | >
> | > =====================================================
> | > This newsgroup only focuses on SBS technical issues. If you have issues
> | > regarding other Microsoft products, you'd better post in the
> corresponding
> | > newsgroups so that they can be resolved in an efficient and timely
> manner.
> | > You can locate the newsgroup here:
> | > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
> | >
> | > When opening a new thread via the web interface, we recommend you check
> the
> | > "Notify me of replies" box to receive e-mail notifications when there
> are
> | > any updates in your thread. When responding to posts via your
> newsreader,
> | > please "Reply to Group" so that others may learn and benefit from your
> | > issue.
> | >
> | > Microsoft engineers can only focus on one issue per thread. Although we
> | > provide other information for your reference, we recommend you post
> | > different incidents in different threads to keep the thread clean. In
> doing
> | > so, it will ensure your issues are resolved in a timely manner.
> | >
> | > For urgent issues, you may want to contact Microsoft CSS directly.
> Please
> | > check http://support.microsoft.com for regional support phone numbers.
> | >
> | > Any input or comments in this thread are highly appreciated.
> | > =====================================================
> | >
> | > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> | >
> | > --------------------
> | > | Thread-Topic: SBS2003R2 Sharepoint Web Part Error (new post)
> | > | thread-index: Ace6luNtZCtctrPISZCRmSMKUK9sEA==
> | > | X-WBNR-Posting-Host: 207.46.193.207
> | > | From: =?Utf-8?B?UGF1bCBXb2xmc29u?=
> <PaulWolfson[ at ]discussions.microsoft.com>
> | > | References: <F8173690-A39E-437D-BC0B-2F9F649D93DF[ at ]microsoft.com>
> | > <ebX1CNDuHHA.4572[ at ]TK2MSFTNGP02.phx.gbl>
> | > <A22EEFDA-BAF1-4ED4-8915-0A940198703A[ at ]microsoft.com>
> | > <n10ki0KuHHA.2148[ at ]TK2MSFTNGHUB02.phx.gbl>
> | > | Subject: Re: SBS2003R2 Sharepoint Web Part Error (new post)
> | > | Date: Fri, 29 Jun 2007 14:46:02 -0700
> | > | Lines: 305
> | > | Message-ID: <C4251CB8-FBEC-419F-81FC-12183391F210[ at ]microsoft.com>
> | > | MIME-Version: 1.0
> | > | Content-Type: text/plain;
> | > | charset="Utf-8"
> | > | Content-Transfer-Encoding: 7bit
> | > | X-Newsreader: Microsoft CDO for Windows 2000
> | > | Content-Class: urn:content-classes:message
> | > | Importance: normal
> | > | Priority: normal
> | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
> | > | Newsgroups: microsoft.public.windows.server.sbs
> | > | Path: TK2MSFTNGHUB02.phx.gbl
> | > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:47348
> | > | NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
> | > | X-Tomcat-NG: microsoft.public.windows.server.sbs
> | > |
> | > | Hello Terence,
> | > |
> | > | We seem to have gone in circles here. To review:
> | > |
> | > | Originally the server came up freshly loaded with Sharepoint 2.0
> | > reporting
> | > | critical errors in WebParts,
> | > |
> | > | "Web Part Error: This page has encountered a critical error. Contact
> your
> | > | system administrator if this problem persists."
> | > |
> | > | Many suggestions here and elsewhere were to use ASP.NET 1.1.4322
> rather
> | > than
> | > | ASP.NET v2.0.50727. That makes sense, coders can't always keep up
> with
> | > | deadlines.
> | > |
> | > | However while that immediately fixed the Web Part Error within a
> little
> | > | while (say 15 minutes) RWW fails with the error saying Service
> | > Unavailable.
> | > | That is explainable by the error logged by IIS:
> | > |
> | > | Event Type: Error
> | > | Event Source: ASP.NET 2.0.50727.0
> | > | Event Category: None
> | > | Event ID: 1062
> | > | Date: 6/29/2007
> | > | Time: 3:39:51 PM
> | > | User: N/A
> | > | Computer: NARWHALE
> | > | Description:
> | > | It is not possible to run two different versions of ASP.NET in the
> same
> | > IIS
> | > | process. Please use the IIS Administration Tool to reconfigure your
> | > server to
> | > | run the application in a separate process.
> | > |
> | > | For more information, see Help and Support Center at
> | > | http://go.microsoft.com/fwlink/events.asp.
> | > |
> | > |
> | > | Then after much research it was determined that asp.net (both
> versions
> | > | should be reloaded from the directories:
> | > |
Re: SBS2003R2 Sharepoint Web Part Error (new post)
v-terliu[ at ]online.microsoft.com (Terence Liu [MSFT]) 04.07.2007 07:17:40
Hello Paul,

Thank you for your comments.

I'm sorry for that I do not help you to find the root cause of this issue.
And I appreciate your time on this post.

I understand that this limitation may inconvenience our users and we
apologize for the inconvenience you faced. In our efforts to continue to
improve our products, you are welcome to add your suggestions in
Partnerfeedback newsgroup to make Microsoft products easier and more
powerful to use. Thanks for your understanding.

Submitting suggestions for product enhancement:

Legitimate Wishes fit into the following guidelines:

Enhancement or feature addition to existing Microsoft products
Reproducible problem or bug with current version that needs resolution
Cannot find documentation of feature within the help files
Difficulty using the product
All beta products
Product packaging complaints
Added accessibility feature for a Microsoft product
These can be submitted here:

https://support.microsoft.com/common/survey.aspx?scid=sw;en;1214&showpage=1&
WS=Wish&url=http%3a%2f%2fwww.microsoft.com%2fireland%2fcontact%2f

I'm also very glad work in newsgroup with you. I look forward to working
with you again.

Thank you and have a nice day,

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: SBS2003R2 Sharepoint Web Part Error (new post)
| thread-index: Ace9gFCis/k3wvzkTV2Vz00ZLhbECA==
| X-WBNR-Posting-Host: 207.46.193.207
| From: =?Utf-8?B?UGF1bCBXb2xmc29u?= <PaulWolfson[ at ]discussions.microsoft.com>
| References: <F8173690-A39E-437D-BC0B-2F9F649D93DF[ at ]microsoft.com>
<ebX1CNDuHHA.4572[ at ]TK2MSFTNGP02.phx.gbl>
<A22EEFDA-BAF1-4ED4-8915-0A940198703A[ at ]microsoft.com>
<n10ki0KuHHA.2148[ at ]TK2MSFTNGHUB02.phx.gbl>
<C4251CB8-FBEC-419F-81FC-12183391F210[ at ]microsoft.com>
<cnUTkDJvHHA.3972[ at ]TK2MSFTNGHUB02.phx.gbl>
<FFB1792B-8099-4BBF-A23F-A15E5B110B13[ at ]microsoft.com>
<zyu9UfTvHHA.4612[ at ]TK2MSFTNGHUB02.phx.gbl>
| Subject: Re: SBS2003R2 Sharepoint Web Part Error (new post)
| Date: Tue, 3 Jul 2007 07:42:00 -0700
| Lines: 339
| Message-ID: <B4A75FD9-190E-4824-8A44-DAC082B68D1D[ at ]microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:47921
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Terence,
|
| I'll opt to close this thread with a few comments:
|
| The original server built on an ASUS M2N with an Adaptec RAID controller
is
| now running Windows Standard 2003 R2 server on the customer's site, after
a
| stint running XP, as a test, in the managing partner's office. It has
now
| been joined by a second. All but AD management is now running on those
| servers rather than SBS. SBS really crams a lot into a single box and
this
| kind of problem though rare does occur. The biggest problem with SBS is
on a
| 25 node network, you cannot just dump and reload the server without heavy
| penalties. We've just reached the point of AD reload.
|
| As to hardware, check Microsoft's hardware acceptance list: you will
find
| ASUS M2N and Adaptec as certified for Windows 2003 servers.
|
| As to IBM, HP and Dell, all I can say is with the problems of OEM
preloads
| of SBS as well as occasional hardware problems; they can cause more
| headaches than they solve. The hardware choice is always at the
customer's
| pleasure.
|
| It may be that SBS R2 is just too immature at this point to use in
| production. Some clients will continue to opt for SBS, but as with
this
| client we will continue to recommend a dual redundant server solution
with
| SBS as a fall back solution where the cost of hardware outweighs the risk
of
| SBS versus standard Server(s).
|
| Anyway, on that note, it has truely been a pleasure corresponding with
you.
| I know this has been a very taxing thread to deal with. You have put a
lot
| of time and effort into working it.
|
| Thanks for your efforts and best regards,
|
| Paul Wolfson
|
|
|
| "Terence Liu [MSFT]" wrote:
|
| > Hello Paul,
| >
| > Thank you for kind update.
| >
| > Since I'm not familiar with hardware of server, I cannot give you some
| > further advice on it. However, you can check all the hardware with our
HCL:
| > http://www.microsoft.com/whdc/hcl/default.mspx
| > Ensure that the server's CPU and board and other components are all in
our
| > HCL.
| >
| > Another easy way, please try to buy popular model server from famous
| > manufacturer, like IBM, HP or DELL. The server come from the
manufacturer
| > pass through compatibility test.
| >
| > Of course, you can contact your hardware vendor for further
investigation.
| >
| > If you still want to do troubleshooting on this thread with me, I
suggest
| > you try to do reinstall the companyweb thru the KB829114 and let me
know
| > the result.
| > If you want to do this issue with our CSS or with your hardware vendor,
| > please also let me know, I will close this thread.
| >
| > If there's anything else I can do for you, please do not hesitate to
let me
| > know.
| >
| > Thank you and have a nice day,
| >
| > Best regards,
| >
| > Terence Liu(MSFT)
| >
| > Microsoft CSS Online Newsgroup Support
| >
| > Get Secure! - www.microsoft.com/security
| >
| > =====================================================
| > This newsgroup only focuses on SBS technical issues. If you have issues
| > regarding other Microsoft products, you'd better post in the
corresponding
| > newsgroups so that they can be resolved in an efficient and timely
manner.
| > You can locate the newsgroup here:
| > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
| >
| > When opening a new thread via the web interface, we recommend you check
the
| > "Notify me of replies" box to receive e-mail notifications when there
are
| > any updates in your thread. When responding to posts via your
newsreader,
| > please "Reply to Group" so that others may learn and benefit from your
| > issue.
| >
| > Microsoft engineers can only focus on one issue per thread. Although we
| > provide other information for your reference, we recommend you post
| > different incidents in different threads to keep the thread clean. In
doing
| > so, it will ensure your issues are resolved in a timely manner.
| >
| > For urgent issues, you may want to contact Microsoft CSS directly.
Please
| > check http://support.microsoft.com for regional support phone numbers.
| >
| > Any input or comments in this thread are highly appreciated.
| > =====================================================
| >
| > Thi