Hello,
I just moved my CMS2002 Aspx Pages to the production
enviornment which is on a Windows 2003 Server. However I
get the following error mentioned below whenever I try to
Browse a aspx page. Any normal html or ASP page works just
fine. Has anyone faced this problem?

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

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


Regards,
Soni.

[ Post a follow-up to this message ]

Hi Soni,

this machine is most likely a multiproc or hyperthreaded machine.
There is a .NET framework 1.1 bug that can cause this:
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm#338EC18A-3FE8-4519-A002-CF711B17A5CF

Cheers,
Stefan

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


"Soni" <anonymous@discussions.microsoft.com> wrote in message
 news:11dca01c414b5$c8b0e9d0$a601280a@phx
.gbl...
> Hello,
> I just moved my CMS2002 Aspx Pages to the production
> enviornment which is on a Windows 2003 Server. However I
> get the following error mentioned below whenever I try to
> Browse a aspx page. Any normal html or ASP page works just
> fine. Has anyone faced this problem?
>
> Server Application Unavailable
> The web application you are attempting to access on this
> web server is
> currently unavailable.  Please hit the "Refresh" button in
> your web browser
> to retry your request.
>
> Administrator Note: An error message detailing the cause
> of this specific
> request failure can be found in the application event log
> of the web server.
> Please review this log entry to discover what caused this
> error to occur.
>
>
> Regards,
> Soni.
>

[ Post a follow-up to this message ]

Don't feel alone Soni on this one. We did a migration a few weeks ago and
burned away 8 hours of dev time along with an MS Premier call to only find
out that hyper threading is a MAJOR issue. This was a non dec call, so I
don't care about the cost, I care that we were stuck for so long in the
middle of a migration. Man I was extremely frustrated with this. It took one
of our  own systems engineers to remember that there might be an issue with
hyper threading (this is after blasting away the production server twice to
see if it was an issue with IIS). Needless to say, I am extremely
disappointed in that this issue is not well documented at all. I have
already explained this to my TAM, and hopefully MS will put up a much BIGGER
notice to this issue, rather than burying it in an FAQ. When we tested our
migration plan in the lab, we tested on non multi proc machines -- so we
never noticed this as an issue. Anyways, long story short, disable
hyperthreading and you will be fine as Stefan has pointed out below

- Nick
nfwilson@nospam.hotmail.com



"Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
news:uU9$RXOFEHA.3880@TK2MSFTNGP10.phx.gbl...
> Hi Soni,
>
> this machine is most likely a multiproc or hyperthreaded machine.
> There is a .NET framework 1.1 bug that can cause this:
> http://download.microsoft.com/downl...
a/MCMS+2002+-+(complete)+FAQ.htm#338EC18A-3FE8-4519-A002-CF711B17A5CF
>
> Cheers,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
> "Soni" <anonymous@discussions.microsoft.com> wrote in message
>  news:11dca01c414b5$c8b0e9d0$a601280a@phx
.gbl... 
>
>

[ Post a follow-up to this message ]

Hi,
Couple of questions,
1) Do I need to enable the Hyper-Threading after the patch
is applied or do i need to leave it disabled?
2) Any documentation on how to disable/enable the Hyper-
threading which I believe is in the BIOS. Am I right?

Regards,
Soni.

>-----Original Message-----
>Don't feel alone Soni on this one. We did a migration a
few weeks ago and
>burned away 8 hours of dev time along with an MS Premier
call to only find
>out that hyper threading is a MAJOR issue. This was a non
dec call, so I
>don't care about the cost, I care that we were stuck for
so long in the
>middle of a migration. Man I was extremely frustrated
with this. It took one
>of our  own systems engineers to remember that there
might be an issue with
>hyper threading (this is after blasting away the
production server twice to
>see if it was an issue with IIS). Needless to say, I am
extremely
>disappointed in that this issue is not well documented at
all. I have
>already explained this to my TAM, and hopefully MS will
put up a much BIGGER
>notice to this issue, rather than burying it in an FAQ.
When we tested our
>migration plan in the lab, we tested on non multi proc
machines -- so we
>never noticed this as an issue. Anyways, long story
short, disable
>hyperthreading and you will be fine as Stefan has pointed
out below
>
>- Nick
>nfwilson@nospam.hotmail.com
>
>
>
>"Stefan [MSFT]" <stefang@online.microsoft.com> wrote in
message
>news:uU9$RXOFEHA.3880@TK2MSFTNGP10.phx.gbl... 
hyperthreaded machine. 
c3a1-4003-9272-2404e92bb76a/MCMS+2002+-+(complete)
+FAQ.htm#338EC18A-3FE8-4519-A002-CF711B17A5CF 
and confers no 
message 
I 
to 
just 
this 
button in 
cause 
log 
this 
>
>
>.
>

[ Post a follow-up to this message ]

Hi Nick,

this is officially documented in the KB article which I'm refering to in my
FAQ.

Cheers,
Stefan.

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


"Nick Wilson" <nfwilson@nospam.hotmail.com> wrote in message
news:eW0ZU0TFEHA.1268@TK2MSFTNGP12.phx.gbl...
> Don't feel alone Soni on this one. We did a migration a few weeks ago and
> burned away 8 hours of dev time along with an MS Premier call to only find
> out that hyper threading is a MAJOR issue. This was a non dec call, so I
> don't care about the cost, I care that we were stuck for so long in the
> middle of a migration. Man I was extremely frustrated with this. It took
one
> of our  own systems engineers to remember that there might be an issue
with
> hyper threading (this is after blasting away the production server twice
to
> see if it was an issue with IIS). Needless to say, I am extremely
> disappointed in that this issue is not well documented at all. I have
> already explained this to my TAM, and hopefully MS will put up a much
BIGGER
> notice to this issue, rather than burying it in an FAQ. When we tested our
> migration plan in the lab, we tested on non multi proc machines -- so we
> never noticed this as an issue. Anyways, long story short, disable
> hyperthreading and you will be fine as Stefan has pointed out below
>
> - Nick
> nfwilson@nospam.hotmail.com
>
>
>
> "Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
> news:uU9$RXOFEHA.3880@TK2MSFTNGP10.phx.gbl... 
[url]http://download.microsoft.com/download/4/2/5/4250f79a-c3a1-4003-9272-2404e92bb76a/MCMS+2002+-+[/u
rl](complete)+FAQ.htm#338EC18A-3FE8-4519-A002-CF711B17A5CF 
>
>

[ Post a follow-up to this message ]

Hi Soni,

you only have to install the fix.

Cheers,
Stefan.

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


"soni" <anonymous@discussions.microsoft.com> wrote in message
 news:14e1201c41559$459a9dd0$a401280a@phx
.gbl...
> Hi,
> Couple of questions,
> 1) Do I need to enable the Hyper-Threading after the patch
> is applied or do i need to leave it disabled?
> 2) Any documentation on how to disable/enable the Hyper-
> threading which I believe is in the BIOS. Am I right?
>
> Regards,
> Soni.
> 
> few weeks ago and 
> call to only find 
> dec call, so I 
> so long in the 
> with this. It took one 
> might be an issue with 
> production server twice to 
> extremely 
> all. I have 
> put up a much BIGGER 
> When we tested our 
> machines -- so we 
> short, disable 
> out below 
> message 
> hyperthreaded machine. 
> c3a1-4003-9272-2404e92bb76a/MCMS+2002+-+(complete)
> +FAQ.htm#338EC18A-3FE8-4519-A002-CF711B17A5CF 
> and confers no 
> message 
> I 
> to 
> just 
> this 
> button in 
> cause 
> log 
> this 

[ Post a follow-up to this message ]

Stefan,
Do u mean i don't have to disable hyper-threading?
soni
>-----Original Message-----
>Hi Soni,
>
>you only have to install the fix.
>
>Cheers,
>Stefan.
>
>--
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>"soni" <anonymous@discussions.microsoft.com> wrote in
message
> news:14e1201c41559$459a9dd0$a401280a@phx
.gbl... 
patch 
Premier 
non 
for 
at 
pointed 
this: 
http://download.microsoft.com/download/4/2/5/4250f79a- 
However 
try 
works 
event 
>
>
>.
>

[ Post a follow-up to this message ]

Stefan
could you clarify please if I have to disable hyper-
threading before applying the fix?

thanx
Soni
>-----Original Message-----
>Stefan,
>Do u mean i don't have to disable hyper-threading?
>soni 
>confers no rights. 
>message 
>patch 
Hyper- 
a 
>Premier 
>non 
>for 
am 
documented
>at 
will 
FAQ. 
>pointed 
in 
>this: 
>http://download.microsoft.com/download/4/2/5/4250f79a- 
in 
production 
>However 
>try 
>works 
>event 
caused 
>.
>

[ Post a follow-up to this message ]

Hi Soni, we disabled hyper threading in the BIOS of the HP server and left
it off. I am not aware of any patch at all for the O/S or the application
itself which resolved this rather bizzare issue.

- Nick
nfwilson@nospam.hotmail.com
"soni" <anonymous@discussions.microsoft.com> wrote in message
 news:14d2c01c41565$f08eff40$a301280a@phx
.gbl...
> Stefan
> could you clarify please if I have to disable hyper-
> threading before applying the fix?
>
> thanx
> Soni 
> Hyper- 
> a 
> am 
> documented 
> will 
> FAQ. 
> in 
> in 
> production 
> caused 

[ Post a follow-up to this message ]

Hi Stefan, unfortuantely, the KB article that you listed is not intuitive at
all -- nor does it really get to the heart of the matter. I have already
worked with MS Premier on resolving this issue and hopefully a more clear
thought KB article will be published soon. Normally I have no issues with
working through problems and what not, but this issue really, really set our
timelines back during that weekend. Anyways, the point of the matter is that
we needed to disabled hyperthreading on the affected servers all together -
we could not use said hot fix at all. Once we disabled hyperthreading --
everything worked including the page, includine site manager ..

- Nick
nfwilson@nospam.hotmail.com

"Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
news:%23UKT5xVFEHA.696@TK2MSFTNGP12.phx.gbl...
> Hi Nick,
>
> this is officially documented in the KB article which I'm refering to in
> my
> FAQ.
>
> Cheers,
> Stefan.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
> "Nick Wilson" <nfwilson@nospam.hotmail.com> wrote in message
> news:eW0ZU0TFEHA.1268@TK2MSFTNGP12.phx.gbl... 
> one 
> with 
> to 
> BIGGER 
> http://download.microsoft.com/downl...
a/MCMS+2002+-+(complete)+FAQ.htm#338EC18A-3FE8-4519-A002-CF711B17A5CF 
>
>

[ Post a follow-up to this message ]