exchange 2003 activesync goes down every day or so
after a reload of exchange 2003, long process, new server, repaired databases, BES server, etc... everything appears to be back to normal except EAS thru IIS6
i've been thru alanhardisty's article and all the settings/permissions appear to be ok.
the problem is, EAS works great for about a day, and then it just times out from the devices. while in this state, IIS works fine, all services are started, OWA works fine, just EAS doesn't
i'm able to get it working again 100% of the time by reinstalling dot net 1.1 and restarting iis:
"%windir%\Microsoft.NET\Fr
iisreset /restart
should i just script that to happen every few hours, or what's the better fix here?
i've been thru alanhardisty's article and all the settings/permissions appear to be ok.
the problem is, EAS works great for about a day, and then it just times out from the devices. while in this state, IIS works fine, all services are started, OWA works fine, just EAS doesn't
i'm able to get it working again 100% of the time by reinstalling dot net 1.1 and restarting iis:
"%windir%\Microsoft.NET\Fr
iisreset /restart
should i just script that to happen every few hours, or what's the better fix here?
ASKER
hi there, thanks for the comment
it appears that the time-out value in your link is for internet explorer, which is not used for activesync
i should mention that once IIS\microsoft-server-activ
this does relate to how IIS and ASP interact with each other though, so, very interested in seeing more thoughts/comments even if they're off the wall at this point
it appears that the time-out value in your link is for internet explorer, which is not used for activesync
i should mention that once IIS\microsoft-server-activ
this does relate to how IIS and ASP interact with each other though, so, very interested in seeing more thoughts/comments even if they're off the wall at this point
Hello,
It's not only for Internet Explorer but it makes changes on how HTTP.sys driver handle request with IIS.
From Microsoft KB:
There is no setting in Microsoft Internet Information Services (IIS) to control the keep-alive timeout other than the Windows registry KeepAliveTime value. But with some Web servers and some proxy servers, you can specify a connection expiration time. If you can specify a connection expiration time in the Web server or the proxy server, increase the keep-alive timeout interval. See your Web server documentation for the correct setting name and value. The default keep-alive timeout value for Internet Explorer is one minute (60 seconds). Therefore, you must use an HTTP keep-alive timeout interval on the Web server or the proxy server that is greater than one minute.
Also, here is a good ressources for troubleshooting Server ActiveSync: http://support.microsoft.com/kb/330461/en-us
It's not only for Internet Explorer but it makes changes on how HTTP.sys driver handle request with IIS.
From Microsoft KB:
There is no setting in Microsoft Internet Information Services (IIS) to control the keep-alive timeout other than the Windows registry KeepAliveTime value. But with some Web servers and some proxy servers, you can specify a connection expiration time. If you can specify a connection expiration time in the Web server or the proxy server, increase the keep-alive timeout interval. See your Web server documentation for the correct setting name and value. The default keep-alive timeout value for Internet Explorer is one minute (60 seconds). Therefore, you must use an HTTP keep-alive timeout interval on the Web server or the proxy server that is greater than one minute.
Also, here is a good ressources for troubleshooting Server ActiveSync: http://support.microsoft.com/kb/330461/en-us
ASKER
i have this tracked down so far, to a user with a corrupt calendar. everytime he syncs, EAS drops out - 100% reproducible. in the process of nuking that user now
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
yep, this is left over from a crash about 2 weeks ago - i'd love to isinteg it but as for now the client won't let me take it offline long enough to eseutil it. isinteg ran for about 45 minutes each time and as many times as i ran it, the test called "folders" won't go under 150 errors. at that point our MS call-in case ($250) representative gave up and said that's that. then we went with some 3rd party program to recover this user and a few others - but the few others are mostly ok.
Don't forget to close the question down if you don't need any further assistance.
Alan
Alan
ASKER
yep, got this finalized yesterday just didnt have a chance to make it back
wish i had more time in the day, shree is pulling away from me in the RoY race :/
while i didn't actually use eseutil/isinteg (i did it by hand instead) the accepted answer would have worked. the problem was for sure one user with corrupt data, whenever he synced asp.net would crash out. after removing the corruption on that user, everyone could sync again and it hasn't crashed out since
thanks for the attention, alan and tomex
wish i had more time in the day, shree is pulling away from me in the RoY race :/
while i didn't actually use eseutil/isinteg (i did it by hand instead) the accepted answer would have worked. the problem was for sure one user with corrupt data, whenever he synced asp.net would crash out. after removing the corruption on that user, everyone could sync again and it hasn't crashed out since
thanks for the attention, alan and tomex
See http://support.microsoft.com/kb/813827/en-us for the server.