Showing posts with label upgraded. Show all posts
Showing posts with label upgraded. Show all posts

Thursday, March 22, 2012

Serious Warning about upgrading to 2.0 -- ccokieless sessions

We upgraded this wend and are now getting call after call on our tech
support line. It appears that 2.0 handles the cookieless sessionID
differently than 1.X. Now every one of our customers that had our site
bookmarked with their sessionID in the URL is getting a server error (404)
when they try to open it. And I can't even trap the error and give them a
nice explanation since they aren't even getting into the app.
Good job Microsoft! Very smooth upgrade path.Hello,
you really should present this feedback on ASP.NET Forums's as that's where
MS's Web Platform & Tools team listens
Migrating from ASP.NET 1.x to ASP.NET 2.0
Discuss issues about compatibility with and migration from previous versions
of ASP.NET.
http://forums.asp.net/180/ShowForum.aspx
Teemu Keiski
ASP.NET MVP, AspInsider
Finland, EU
http://blogs.aspadvice.com/joteke
"Chip" <chip@.intradata.com> wrote in message
news:%23Y3Szz7OGHA.1180@.TK2MSFTNGP09.phx.gbl...
> We upgraded this wend and are now getting call after call on our tech
> support line. It appears that 2.0 handles the cookieless sessionID
> differently than 1.X. Now every one of our customers that had our site
> bookmarked with their sessionID in the URL is getting a server error (404)
> when they try to open it. And I can't even trap the error and give them a
> nice explanation since they aren't even getting into the app.
> Good job Microsoft! Very smooth upgrade path.
>

Serious Warning about upgrading to 2.0 -- ccokieless sessions

We upgraded this weekend and are now getting call after call on our tech
support line. It appears that 2.0 handles the cookieless sessionID
differently than 1.X. Now every one of our customers that had our site
bookmarked with their sessionID in the URL is getting a server error (404)
when they try to open it. And I can't even trap the error and give them a
nice explanation since they aren't even getting into the app.

Good job Microsoft! Very smooth upgrade path.Hello,

you really should present this feedback on ASP.NET Forums's as that's where
MS's Web Platform & Tools team listens

Migrating from ASP.NET 1.x to ASP.NET 2.0
Discuss issues about compatibility with and migration from previous versions
of ASP.NET.
http://forums.asp.net/180/ShowForum.aspx

--
Teemu Keiski
ASP.NET MVP, AspInsider
Finland, EU
http://blogs.aspadvice.com/joteke

"Chip" <chip@.intradata.com> wrote in message
news:%23Y3Szz7OGHA.1180@.TK2MSFTNGP09.phx.gbl...
> We upgraded this weekend and are now getting call after call on our tech
> support line. It appears that 2.0 handles the cookieless sessionID
> differently than 1.X. Now every one of our customers that had our site
> bookmarked with their sessionID in the URL is getting a server error (404)
> when they try to open it. And I can't even trap the error and give them a
> nice explanation since they aren't even getting into the app.
> Good job Microsoft! Very smooth upgrade path.

Tuesday, March 13, 2012

server application not available

After I upgraded to .NET 2.0, every a few days, our sites will stop and I
get an error message of "server application not available". I tried the
event viewer but did not find any information related to this.

I am using Windows 2003 standard, any idea where to look for the error? It
sounds like a DotNet run time error?

regards,

Guoqi Zheng
http://www.ureader.comPossibly it could be due to process recycling but then again it could be a
dozen other things. IIS settings, whether in IIS 5.0 compatibility mode,
various IIS settings that you may or may not have set, and half a dozen other
things.
First step, check the Application Event log to see if there are any clues.
Check connections being properly closed, download the Best Practices
Whitepapers from MSDN and "Get under the hood".
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com

"guoqi zheng" wrote:

> After I upgraded to .NET 2.0, every a few days, our sites will stop and I
> get an error message of "server application not available". I tried the
> event viewer but did not find any information related to this.
> I am using Windows 2003 standard, any idea where to look for the error? It
> sounds like a DotNet run time error?
>
> regards,
> Guoqi Zheng
> http://www.ureader.com
We saw the same thing in a server that we recently upgraded to .net 2.0.
There were a few different applications running, one in 2.0, the rest
in 1.1.

Turns out you can't have different versions of .net running in the same
app pool. As soon as we moved the 2.0 stuff to a new app pool, the
problem went away.

I don't know if this is your problem, but it seems likely. As Peter in
the previous post said: it could be half a dozen other things.

guoqi zheng wrote:
> After I upgraded to .NET 2.0, every a few days, our sites will stop and I
> get an error message of "server application not available". I tried the
> event viewer but did not find any information related to this.
> I am using Windows 2003 standard, any idea where to look for the error? It
> sounds like a DotNet run time error?
>
> regards,
> Guoqi Zheng
> http://www.ureader.com

--
David Hogue

server application not available

After I upgraded to .NET 2.0, every a few days, our sites will stop and I
get an error message of "server application not available". I tried the
event viewer but did not find any information related to this.
I am using Windows 2003 standard, any idea where to look for the error? It
sounds like a DotNet run time error?
regards,
Guoqi Zheng
http://www.ureader.comPossibly it could be due to process recycling but then again it could be a
dozen other things. IIS settings, whether in IIS 5.0 compatibility mode,
various IIS settings that you may or may not have set, and half a dozen othe
r
things.
First step, check the Application Event log to see if there are any clues.
Check connections being properly closed, download the Best Practices
Whitepapers from MSDN and "Get under the hood".
Peter
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
"guoqi zheng" wrote:

> After I upgraded to .NET 2.0, every a few days, our sites will stop and I
> get an error message of "server application not available". I tried the
> event viewer but did not find any information related to this.
> I am using Windows 2003 standard, any idea where to look for the error? It
> sounds like a DotNet run time error?
>
> regards,
> Guoqi Zheng
> http://www.ureader.com
>
We saw the same thing in a server that we recently upgraded to .net 2.0.
There were a few different applications running, one in 2.0, the rest
in 1.1.
Turns out you can't have different versions of .net running in the same
app pool. As soon as we moved the 2.0 stuff to a new app pool, the
problem went away.
I don't know if this is your problem, but it seems likely. As Peter in
the previous post said: it could be half a dozen other things.
guoqi zheng wrote:
> After I upgraded to .NET 2.0, every a few days, our sites will stop and I
> get an error message of "server application not available". I tried the
> event viewer but did not find any information related to this.
> I am using Windows 2003 standard, any idea where to look for the error? It
> sounds like a DotNet run time error?
>
> regards,
> Guoqi Zheng
> http://www.ureader.com
David Hogue