MailEnable 8.x upgrade

Because our MailEnable webclient stopped working in IE 11 (thanks again schizo Internet Explorer identifying yourself as a Gecko browser) we decided to migrate MailEnable to the latest release 8.x. We planned an upgrade this weekend and installed MailEnable without any problems.

Clients started using the MailEnable webclient but noticed that it wasn't possible to add attachments. The error "The license for this software prevents access to webmail attachments" was shown:

Via diagnostics we checked the state of the MailEnable server. This has to be a license problem caused by the migration:

So the license key is valid but we are getting license errors? Let's hit the internet and see if any resources are available. Other people have experienced the same problem and are talking about re-installing the software. Before we'll get into that we'll do a bit more digging around. Re-installing is the last thing on our mind.

This forum post talks about an installation error concerning the registry key "Install Key":

http://forum.mailenable.com/viewtopic.php?f=2&t=26241

We check the key but it seems that MailEnable has fixed this problem in the installer. However, it must have something to do with this key because the problem matches ours exactly. We decide to do a clean install on an available dev server. As expected the install works out of the box and webmail is up and running.

The next step is to break the install on the dev server just like on our production environment. We start by checking the "Install Key" in the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Mail Enable\Mail Enable\Registration

The key is the same on both machines. However, the value is different (as expected). We back-up the values on both machines and update the dev machine with the production value.

Bingo: dev webmail also stops working. With this in mind we update our production key with the original value from our dev server. Webmail immediately starts working again.

Problem solved.

Update: the same problem returned after a couple of months. I found out that removing the RAW: from the Install Key fixed the problem.

Terug naar het overzicht