If we are running the latest released version and have made some modifications to the web files, will we have to redo those modifications after upgrading to the RC's? Or are the fixes in some other areas?
Thanks, Grant Griffith Web Application Developer Enhanced Telecommunications http://www.etczone.com 812-932-1000 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of tnichols Sent: Thursday, June 21, 2007 2:49 PM To: [email protected] Subject: RE: [IMail Forum] 2006.2 web messaging nightmare Regarding IIS crashes and 4005 and 3005 errors (event id 1309's and 1315's): I think it would be helpful to run down what we (Ipswitch) know so far about these issues. 1) The are several different issues here a) There was a problem with COM interop which was causing a severe Handle leak in IIS. This issue appeared only to happen on Multi processor machines under moderate to heavy loads (~50 or more simultaneous active web users). It would cause IIS to crash/and or worker process recycle events. This issue is fixed. b) 4005 invalid ticket information messages and 3005 invalid ticket warnings with cryptographic errors. Number of processors does affect this issue, but it is not exclusive to them. First the presence of 4005 invalid ticket errors does not necessarily indicate anything is wrong. Normal operation of a web site using windows forms authentication can periodically see this. The reason for this is that there is a known issue with the encryption keys used being regenerated each time the worker processes recycle. This happens, by default every 29 hours. If you see a few 4005 right after a worker process recycle event, then this is normal and expected. If that bothers you see: http://technet2.microsoft.com/windowsserver/en/library/8f4c0184-3793-496 6-9e 29-1314b94cb23d1033.mspx?mfr=true This will start you out in setting encryption and validation key that don't change and eliminate those types of errors. For experiencing the 4005s it is possible that these are due to worker process recycle events and not the cause. We believe that that is why some of the people with issue a) were seeing the 4005 errors. 4005 errors not associated with a worker process recycle are a potentially different matter, and there a number of different causes. We believe that our old email compose editor was causing some of these issue. As this control has been replaced, some of these issues have disappeared. c) 4005 expired tickets are likely due to exactly what it says. The users session expire due to inactivity. We have seen no evidence that expired tickets are causing problem, but we are also not sure why only some expired ticket events are logged. 2) The 4005s are informational messages, not errors, not warnings. They may indicate a problem, or they may just be Forms authentication doing its job. The mere presence of a 4005 is not indicative of a problem. Unexpected worker process recycles, IIS crashes, users being unexpectedly logged out of the system; these are the signs that there is a problem. 3) The login.apsx now has code in it to clear authCookies(put there to fix a bug). Please do not redirect to login.aspx. If you must redirect, redirect to default.aspx. That way authenticated users will not be logged out. However redirection is unnecessary. This functionality is already built into the web client. We believe we have address most of the issues associated with these problems. If you have any issues with these problem which appear to fall outside what is listed above, please contact us so we can address those cases as well. Thank you -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam Campbell Sent: Thursday, June 21, 2007 8:45 AM To: [email protected] Subject: RE: [IMail Forum] 2006.2 web messaging nightmare "The worker process does crash every now and again" That's the w3wp process, right? Our server, running IMail and WSUS, displays a crash message a few times a week regarding w3wp. adamc -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Keith Johnson Sent: Wednesday, June 20, 2007 22:32 To: [email protected] Subject: RE: [IMail Forum] 2006.2 web messaging nightmare Tripp, Thanks for the email. I have been posting up the forum as well as been running Preview 3 since it came out. However, I still get 4005 events just about every 30 min. We have over a 1000 users, about 3/4 active on web mail. This server takes in about 80K inbound emails and about 10 outbound. I haven't really had to restart IIS. The worker process does crash every now and again. Unfortunately, when the worker process goes down, IISAdmin and WWW is usually still up thus ASP is hung and there really is no monitoring for that. We have monitors on the outside ensuring the web site is up via keywords on the screen as well as triggers on key services to alert us of issues. We are rolling to RC1. However, I have adjusted some files since Preview 3 to address some minor issues reported on the forum, thus I am running most of the fixes. I was hoping the 4005's would be gone between Preview 3 and RC1. I know the editor was re-written to deal with 'snail' typing. I plan on rolling it up this weekend. Keith _____ From: [EMAIL PROTECTED] on behalf of Tripp Allen Sent: Wed 6/20/2007 9:57 PM To: [email protected] Subject: Re: [IMail Forum] 2006.2 web messaging nightmare The 4005 events were the primary focus for Dev over the past several weeks. For .21 we changed the architecture so we are no longer using a COM object from .NET (which appears to have caused many of the problems) and we dropped the FTB edit control which appeared to be causing issues as well. We have people running the technical preview that previously were having to restart IIS frequently (large, high web user installations) that have been running preview 3 for a couple of weeks and have not had to restart IIS since loading. Note that the new edit control now supports HTML messages in Safari as well. Tripp ----- Original Message ----- From: "Keith Johnson" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, June 20, 2007 9:46 PM Subject: RE: [IMail Forum] 2006.2 web messaging nightmare John, I have scheduled to rollup to RC1 this weekend, just wondering if you are still seeing those event id 1309's and 1315's. Most read: Event code: 4005 Event message: Forms authentication failed for the request. Reason: The ticket supplied has expired. Thanks for the update. Keith _____ From: [EMAIL PROTECTED] on behalf of John T (lists) Sent: Wed 6/20/2007 4:02 PM To: [email protected] Subject: RE: [IMail Forum] 2006.2 web messaging nightmare Yes, when Imail 2006.2 was released and many started to use it, including installations on high volume or heavily used servers, the webmail bugs started to show themselves. As an example, I was running the preview for Imail 2006.2 on my server and had no errors or problems whatsoever. However my server is low volume. After its release, when I installed it on a high volume client server with users all over the place the problems arose. As of right now, Imail 2006.21 RC1 is installed on my server and on my client's high volume server and so far no errors have been seen or reported. The preferences.config file is in each users file directory and is used by webmail to set how the user wants certain things. If it does not exist, that means the user has never changed anything from default and that is fine, although in some cases having a preferences.config file even if everything is default settings has helped. John T From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Spaminator Sent: Wednesday, June 20, 2007 12:25 PM To: [email protected]; [email protected] Subject: Re: [IMail Forum] 2006.2 web messaging nightmare This is a HUGE problem. I have a client with 800 accounts saying they're going to leave the platform because they're constantly getting logged out. I can't actually reproduce the probem here and am having a hard time tracking down their browser settings because they're across the country. Are there any temporary workarounds? What's the preferences.config fix? What is the ETA on 2006.21? I know it's in RC1 status, but we need it FAST FAST FAST! I really think Ipswitch should start publishing a KNOWN ISSUES list with every release, and constantly keep it updated as things arise. Forget scaring off potential customers, they WANT to see this stuff. Be more concerned with taking care of the many customers you already have! I looked through the forums and boards before upgrading to this version, which was released on March 6th I think, before upgrading our system. I saw a reference here and there, but it didn't sound like the widespread revolt that I'm experiencing! Thanks, One bloody and bruised IT guy -----Original Message----- From: "John T (lists)" <[EMAIL PROTECTED]> Sent 6/18/2007 5:16:49 PM To: [email protected] Subject: RE: [IMail Forum] 2006.2 web messaging nightmare Bill, resolution of these problems and development of 2006.21 is almost complete. I and others have been testing with beta 3 (oops, meant preview 3) and so far things are looking to be fixed. The couple of issues I saw were either quickly resolved by simple code changes or by updating the preferences.config file or by having the user update their browser. John T From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matrosity Hosting Sent: Monday, June 18, 2007 12:33 PM To: 'Tripp Allen' Cc: [email protected] Subject: [IMail Forum] 2006.2 web messaging nightmare Tripp, You have helped me in the past with web messaging issues and now that you are the product manager for Imail I am hoping you can once again fix a VERY big problem with web messaging. Many of our users are being logged out of web messaging when they send an email. I've waited a week for some solution from tech support/development with a final answer of downgrade to 2006.1 or await a new release. Neither of those are solutions because downgrading doesn't give me much confidence to upgrade and awaiting a new release will likely cost us business. I've searched the forums and we are not the only ones experiencing this problem and I hope that you can step in and get development to fix this ASAP. Thanks, Bill Foresman Matrosity Hosting www.matrosity.com<file:///\\www.matrosity.com> 850.656.2644 To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/ To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/ To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/ To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/ To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/ To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
