Cookies are being expired after application pool is recycled

I have an .NET 1.1 application running under an IIS 6.0.  This application makes use of  "Remember Me" option to save a persistant cookie so that the user doesn't need to login all the time.  This works completly fine and has been for many years on many differernt servers, but I just deployed this application to one client's computer and now, whenever the application pool recycles, the user's cookie isn't being used to log them in again, in essence, the cookie acts like it's expired or non-existent.  The IIS settings on this server and another server which works fine are completly the same and the web.config files are exactly the same.  I know the cookie still exists, and I can test that by closing my browser and going back to the site where I am logged back in automatically again using the cookie.  The only time that the cookie is not being accepted is if the application pool is recycled, even if I am in mid-session.  What would cause this one server to not accept valid cookies for logging in users after the session expires?  Any help is appreciated.
bmcclearyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

craskinCommented:
you need to compare the machine.config files. if you're encrypting your cookies, the keys are refreshed when the app pool recycles. my guess is your old machine had static keys for the decryption.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bmcclearyAuthor Commented:
Thanks Caskin, we figured out that Windows Server 2003 SP2 was the culprit.  All the other servers were SP1.  With SP2, it causes the encryption key to be changed with each recycle.  We added a value to the web.config to make the keys static.  Thanks.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Editors IDEs

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.