Re: SBS2003R2 Sharepoint Web Part Error (new post)

Tech-Archive recommends: Fix windows errors by optimizing your registry

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@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <F8173690-A39E-437D-BC0B-2F9F649D93DF@xxxxxxxxxxxxx>
<ebX1CNDuHHA.4572@xxxxxxxxxxxxxxxxxxxx>
<A22EEFDA-BAF1-4ED4-8915-0A940198703A@xxxxxxxxxxxxx>
<n10ki0KuHHA.2148@xxxxxxxxxxxxxxxxxxxxxx>
| 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@xxxxxxxxxxxxx>
| 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
.

Quantcast