Thank you Matt, you have confirm my thoughts. From reading the forum, I see there are still issues with web frontend piece. We do not want to go through another upgrade only to downgrade. Like you said, it's a catch 22 as we really need to be at the latest version. We evaluated Zimbra as a replacement system and liked it, but our director shot it down, saying if we migrate off imail, it will be exchange. The state is an exchange shop and K12 larger schools have their own exchange servers and we have exchange servers on the core to distribute the mail internally. They are currently working with the budget office (no money last year), in the meantime I'm getting beat up. Hopefully, this summer we will be installing exchange servers.
I checked my IMAP settings and they are OK. The contact database I will visit. I was hoping the two errors may both be related to the database. I do reboot the server on a scheduled task at 0600 each day. I also have scheduled tasks to sync LDAP each night as we have multiple domains and OpenLDAP does not work well either. Tends to get to 30 domains and bomb. I worked with IpSwitch tech support on this probably a year ago. Originally I was told there was no issue, than told they couldn't duplicate, than they actually said they did duplicate it once they added enough domains. I was told I was on a list and would be provided a fix when it was resolved. I'm still waiting. Email is just so important now, stability is a must. Ipswitch needs to get cracking. James W. Herron Department of Technology and Information 801 Silver Lake Blvd. Dover, De 19904 [EMAIL PROTECTED] (P) 302-739-9657 (F) 302-739-7243 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Sent: Wednesday, September 26, 2007 5:26 PM To: [email protected] Subject: Re: [IMail Forum] Several issues with mail access Jim, 2006.21 has a webmail message parsing bug that will cause IIS to crash (and kick off all users). Before it finally crashes, it will frequently redline a single core. Restarting IIS once a day with a scheduled task will help the instability, but it won't fix it. Without restarts, the server can hang until there is manual intervention. This has been reported repeatedly to Ipswitch and they have reproduced at least some of the parsing errors that trigger this condition, however they have offered nothing at all in terms of providing a fix, or even that they are working on the issue. This problem makes 2006.21 a bad choice for a larger server with active webmail use, though smaller servers with less webmail use will see this issue much less frequently. I did not see these problems with 2006.1. The problem with not running the most recent version is that there are security issues that will almost definitely be exploited just like most of the past bugs that can give system privileges to an IMail attacker. It's a Catch 22, either have a stable server, or have one that can be hacked. For larger installations, there is no good solution. To fix your 2006.1 issues, you need to migrate to MS SQL Express to store your contacts in instead of using the default Access solution. Search the list for documentation on how to do this. You have too many users for webmail to handle contacts with an Access database. The IMAP issue is less clear to me, but you want to make sure that the IMAP service is not set to "force subscribe", otherwise users can't see their sub-folders and other related issues. 2006.1 also will not work appropriately with Safari. The real fix is to demand that Ipswitch fix the problems that cause IIS to crash. They can do that without making users wait another 6 months or so for an interim release like they did with 2006.21. I would like to see Ipswitch address this immediately. Matt Herron Jim W. (DTI) wrote: Hoping someone with more insight to IMail than I have could assist on my earlier post below. Thank you, Jim James W. Herron Department of Technology and Information 801 Silver Lake Blvd. Dover, De 19904 [EMAIL PROTECTED] (P) 302-739-9657 (F) 302-739-7243 From: [EMAIL PROTECTED] [ mailto:[EMAIL PROTECTED] On Behalf Of Herron Jim W. (DTI) Sent: Monday, September 24, 2007 2:23 PM To: [email protected] Subject: [IMail Forum] Several issues with mail access We are running Imail 2006.03, the last stable version we had success with. We have 8400+ users in 38 virtual domains, with probably 75% using browsers for access. We skipped 2006.04 and went to 2006.1, just as we finished testing 2006.2 came out. We upgraded from 2006.03 to 2006.2 and it was a disaster. Ipswitch recommended downgrading to 2006.1 which we never had in production, things were better but frontend still kept crashing. We went back to 2006.03, we have not gone to 2006.21 yet, this list forum had negative statements on browser access and the .net errors, we pulled out again right at the last minute. I say these things because I know ipswitch's answer is going to be upgrading to 2006.21. We are experiencing two errors listed below, this is displayed on the left panel of the browser, users cannot see their folders, just the error message. Other panels display properly. Does anyone have any insight to what is going on and/or recommendations for a fix. Another product is not a solution for this year anyway. Got to get through another year of IMail with possibilities of exchange next year. When these errors happen, I've been rebuilding the workshare DB for the one mentioning database (unknown). On the other restarting services or the server works. CPU is running 30 to 100 percent at the time, with more time on the 100% side. W3wp.exe is running 50+ % with IMAP4d32 running at another 30+ % and SMTPd32, POP3d32 and queue manager eating the rest. The w3wp using over a GB of memory. Server is a Compaq G3 with Intel(R) Xeon(TM) CPU 3.20GHz and 3 GB of RAM. Windows 2003 server Standard Edition Service Pack 2. First error, to do with the workshare database. An error was encountered while processing your request. (Return to previous page <javascript:history.go(-1)> ) If you encounter this error again, please provide the following information to your network administrator to assist in trouble-shooting. Message: ERROR [HY000] [Microsoft][ODBC Microsoft Access Driver] Cannot open database '(unknown)'. It may not be a database that your application recognizes, or the file may be corrupt. ERROR [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed ERROR [HY000] [Microsoft][ODBC Microsoft Access Driver] Cannot open database '(unknown)'. It may not be a database that your application recognizes, or the file may be corrupt. StackTrace: at System.Data.Odbc.OdbcConnection.Open() at Ipswitch.Web.Mail.WgsContactSource..ctor(IUser user) at Ipswitch.Web.Client.ContactTree.ProcessContactFolders(IUser user) at Ipswitch.Web.Client.ContactTree.Page_Load(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.AddedControl(Control control, Int32 index) at System.Web.UI.ControlCollection.Add(Control child) at Infragistics.WebUI.UltraWebListbar.UltraWebListbar.CreateChildControls() at System.Web.UI.Control.EnsureChildControls() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Page.ProcessRequestMain() Second error, Connection lost. An error was encountered while processing your request. (Return to previous page <javascript:history.go(-1)> ) If you encounter this error again, please provide the following information to your network administrator to assist in trouble-shooting. Message: Connection dropped StackTrace: at Hunny.Mail.Socket.Underflow() at Hunny.Mail.Socket.Read() at Hunny.Mail.Imap4Parser.Read(Socket socket) at Hunny.Mail.Imap4Parser.ParseTag(Socket socket) at Hunny.Mail.Imap4Parser.ParseOneResponse(Socket socket) at Hunny.Mail.Imap4Client.Connect(String address, Int32 port) at Ipswitch.Web.Mail.Imap4Connection..ctor(IUser user) at Ipswitch.Web.Mail.Imap4Folder.get_Count() at Ipswitch.Web.Client.FolderTree.ProcessMailFolderList(ArrayList folders, Nodes level) at Ipswitch.Web.Client.FolderTree.ProcessMailFolders(IUser user) at Ipswitch.Web.Client.FolderTree.Page_Load(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.AddedControl(Control control, Int32 index) at System.Web.UI.ControlCollection.Add(Control child) at Infragistics.WebUI.UltraWebListbar.UltraWebListbar.CreateChildControls() at System.Web.UI.Control.EnsureChildControls() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Page.ProcessRequestMain() Any help or insight is appreciated. James W. Herron Department of Technology and Information 801 Silver Lake Blvd. Dover, De 19904 [EMAIL PROTECTED] (P) 302-739-9657 (F) 302-739-7243
<<image001.gif>>
