Web Wiz Forums - IIS6 "native mode"???

Print Page | Close Window

IIS6 "native mode"???

Printed From: Web Wiz Forums
Category: Web Wiz Web App Support Forums
Forum Name: Web Wiz Forums
Forum Description: Support forum for Web Wiz Forums application.
URL: https://forums.webwiz.net/forum_posts.asp?TID=4014
Printed Date: 02 April 2026 at 12:52am
Software Version: Web Wiz Forums 12.08 - https://www.webwizforums.com

Topic: IIS6 "native mode"???

Posted By: drjamez
Subject: IIS6 "native mode"???
Date Posted: 02 July 2003 at 4:00pm

Hello.

I have found the forum works on Windows Server 2003 in IIS5 Isolation Mode, but (at least for me) it seems to have problems authenticating users if i go into the worker process mode - the native IIS6 one that launches discrete sessions, etc.

If I am in IIS6 Worker Process Mode, I get the only members with sufficient permission log-in errors. I am sure this has to do with the ASP session ID being reset. Anyone know if it's possible to use IIS6 Worker Process mode, or must I run the new IIS under an IIS5 compatibility mode?

I'm hoping it's a setting I can adjust. Thank you for your help.

- James -

Replies:

Posted By: drjamez
Date Posted: 02 July 2003 at 8:58pm

A little more...

I'm running 7.01 SQLServer edition. I need IIS6 Process Mode because OWA for Exchange 2003 RC1 demands it.

I found a temporary solution - I made the DefaultAppPool settings the same as the Exchange web app settings are... and now I've got it working again.

Is there a better solution?

- James -

Posted By: WebWiz-Bruce
Date Posted: 03 July 2003 at 1:22am

It will run under IIS6, but you need to keep the session ID's and not set them to be reset all the time.

-------------
https://www.webwiz.net/web-wiz-forums/forum-hosting.htm" rel="nofollow - Web Wiz Forums Hosting
https://www.webwiz.net/web-hosting/windows-web-hosting.htm" rel="nofollow - ASP.NET Web Hosting

Posted By: drjamez
Date Posted: 03 July 2003 at 7:57am

That's pretty much what Microsoft did with their OWA interface, too. Mirroring the settings from OWA's pool to the DefaultAppPool seemed to fix it.

What an annoying little problem. Thanks for confirming the solution and keep up the excellent work!

- James -