Asp.NET 2.0 web service and Windows 2003 Server

[Bragadiru]

Hi,

I can publish My Asp.NET 2.0 web service, through a WebSetup project, on a
Windows XP Pro Sp2 and it works fine.

When I'm trying to publish it on a Windows 2003 Server IIS 6 => when I can
access the web service but it is closed after few seconds (I know 'cause I
have in global.asax.cs Application_Start/End
Trace.WriteLine(DateTime.Now());)

My pb is that I'm loosing my Application and Session globals objects data.

I saw that, by default, in Win2003 IIS 6->My Virtual
Directory ->DirectorySecurity tab->Anonymous acces and .. -> Authentication
method ONLY Integrated Authentication Mode is cheked. I enabled the
Anonymous access, too. In Win XP anonymous is enabled by default.

Client machine and server are part of the same Windows domain controller.

In windows form client code I have :

localhost.MywebService myWS = new localhost.MywebService();

....

myWS.Credentials = System.Net.CredentialCache.DefaultCredentials;

myWs.CookieContainer = new System.Net.CookieContainer();

....

What am I doing wrong ?

What else should I change in win2003 to work like in WinXp ?

How can I catch in Application_end which process is shutting down my asp.net
web service ?

In Win2003 Application log I found this warning :

The registry key for IIS subauthenticator is not configured correctly on
local machine, the anonymous password sync feature is disabled.
Thanks for any suggestion

[Luke Zhang [MSFT]]

Hello,

you may first check following options on the win 2003 server:

Win2003 IIS manager --> Application Pools,

You may expand each nodes under Application Pools to find the application
pool your web service is working in. Then right click the application pool
and select "Properties". On the "recycling" tab, check if there is a
recycling policy here is force your web applicaiton recycle in a short
while; On the "Performance" tab, check the Idle timeout's value, is it set
too short to perform a shutdown.
Hope this help,

Luke Zhang
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

[Bragadiru]

Thanks Luke.

I just checked :

On Recycling tab,

Recycle worker processes (in miunutes) = 21
Recycle worker process (number of requests = 20000
Recycle worker processes at the following times = 23:59

On Performance tab,

Shutdown worker processes after being idle for (time in minutes) = 20
Maximum number of worker processes = 2

Nothing seems wrong to me.

Also, there is no antivirus on Win 2003 Server Enterprise.

Thanks a lot

"Luke Zhang [MSFT]" <lu******@online.microsoft.com> wrote in message
news:F6**************@TK2MSFTNGXA01.phx.gbl...

Hello,

you may first check following options on the win 2003 server:

Win2003 IIS manager --> Application Pools,

You may expand each nodes under Application Pools to find the application
pool your web service is working in. Then right click the application pool
and select "Properties". On the "recycling" tab, check if there is a
recycling policy here is force your web applicaiton recycle in a short
while; On the "Performance" tab, check the Idle timeout's value, is it set
too short to perform a shutdown.
Hope this help,

Luke Zhang
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

[Luke Zhang [MSFT]]

For deeply trouble shoot this problem, you may create a new application
pool on the server, and add a simple web service to the new application
pool to see if it will generate the problem. If not, you may continue to
move your actual web service application to the new application pool.

Luke Zhang
(This posting is provided "AS IS", with no warranties, and confers no
rights.)