1
'Aw, Snap!' Error in Chrome with SmarterMail Enterprise 7.6
Problem reported by Katherine Huddle - August 28, 2014 at 7:22 AM
Submitted
Hi,
 
Has anyone else been receiving the 'Aw, Snap!' error message in Chrome while running SmarterMail Enterprise 7.6? This seems to be occurring when new messages are being created. 
 
Thanks!
 
 

5 Replies

Reply to Thread
0
Steve Reid Replied
August 28, 2014 at 8:42 AM
Your version is quite old. You should consider upgrading, it may just fix your issue.
1
Bruce Barnes Replied
August 29, 2014 at 2:46 AM
Only the most current, and two prior versions of SmarterMail are supported. You'll have to ulgrade your SmarterMail software.
Bruce Barnes
ChicagoNetTech Inc

Phone: (224) 444-0169

E-Mail and DNS Security Specialist
Network Security Specialist

Customer Service Portal: https://portal.chicagonettech.com
Website: https://www.ChicagoNetTech.com
Security Blog: http://networkbastion.blogspot.com/

Web and E-Mail Hosting, E-Mail Security and Consulting
1
Richard Davies Replied
September 9, 2014 at 3:25 AM
Hi, 
 
  We are also experiencing this issue with 10.7.4842 . It only occurs with Google Chrome, and happens when composing or replying to an email. 
  I tried this on the server itself connecting to localhost and the error occurred, but still with the default Aw Snap error message in Chrome. All tabs from Smartermail change to this error. 
  We have no extensions installed, happens with an existing install of Chrome and new installs. Chrome version that was just installed on the server is Version 37.0.2062.103 m. I tried changing the setting as described on http://www.ghacks.net/2013/05/23/how-to-fix-google-chromes-aw-snap-error-message-when-loading-websites/  but this had no effect. 
1
Bruce Barnes Replied
September 11, 2014 at 10:24 AM
Unless there's a major issue with SmarterMail 10.X it will not be upgraded with patches.
 
You have no problem in SmarterMail 12.X, but should consider upgrading to the most recent version of 12.X, which is 12.4.5364, released on 8 September, 2014. 
 
 
The more recent releases cover several very important issues.  The release notes are here: SmarterMail 12.x Release Notes
 
Here's the instructions for doing a Major Upgrade of SmarterMail - SmarterTools
 
Here's the instructions for doing a Minor Upgrade of SmarterMail - SmarterTools
 
EDIT:  Just checked Chrome Version "37.0.2062.103 m" using SmarterMail 12.4.5364, and have no issues.
 
Bruce Barnes
ChicagoNetTech Inc

Phone: (224) 444-0169

E-Mail and DNS Security Specialist
Network Security Specialist

Customer Service Portal: https://portal.chicagonettech.com
Website: https://www.ChicagoNetTech.com
Security Blog: http://networkbastion.blogspot.com/

Web and E-Mail Hosting, E-Mail Security and Consulting
1
secretwep Replied
September 11, 2014 at 2:23 PM
Katherine,
 
I am running SmarterMail Enterprise 7.6 as well and have also been getting the "Aw Snap!" crashes.  The started about 2 weeks ago with Chrome 37.0.2062.103 m and subsequently 37.0.2062.120 m.  A Flash update also occurred recently and that may also be involved in some way.  There are more than a few reports out there that seem to implicate Flash as an issue, but I'm now thinking it really is more related to Chrome itself.  As you may be aware, Flash is utilized as part of the HTML5 file uploader in SM Ent. 7.6 when you are composing a message ("Attach Files").
 
I threw about 4 hours of IT time at it today and ran through many permutations and did some Flash unloading and reloading, applied a series of recent (just today) Windows 7 updates.  I unchecked Use Hardware Acceleration in Chrome.  I also loaded the EMET tool (Microsoft's Enhanced Mitigation Experience Toolkit) and applied it to Chrome.  I still got the "Aww Snap" messages in all cases.  Incidently, when EMET was applied the "Attach Files" button turned into an error and became non-functional.
 
My current solution (and the only one that prevented the error) is to install Google Chrome Beta (38).  Please note, if you do install it, it may appear to be installed, but you need to go over to "About Chrome" and finish up the installation where it says "almost finished".  Then you should be good to go.
 
This may or may not be a viable solution for you, depending on the number of users you support and your willingness to utilize Chrome Beta.  It is a stop-gap measure.  For me 4 hours of IT is nothing compared to the upgrade cost (well over $1000 in true costs).  I'd like to upgrade SM, but it's just not in the budget at the moment.
 
I hope it helps,
John
 

Reply to Thread