Fix for Mail Enable – %1 is not a valid Win32 application.

As mentioned in a previous post, I am in the middle of changing my hosting, from a reseller account, to my own VPS.

After working closely with eHosting support, I’ve managed to beat into submission the large majority of the features required.
One thing however, was the installation of MailEnable Standard (the free one)
It didn’t come with any form of web mail client.

Some emailing, and googling later, I discovered the latest version of MailEnable standard (v 3.6)  includes webmail

After installing this on my VPS, and trying it out on a test domain, it threw an error in the web browser:

%1 is not a valid Win32 application.

This caused me quite a lot of trouble to figure out, but the solution – ASP.Net needed re-registering with IIS.
(I had recently installed .net 3.5 – not sure if this had anyrthing to do with it)
To do this, click Start, Run, then type "CMD"

At the command prompt, type (or cut paste, like most people)

C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i -enable

Hit enter.

That fixed it for me, hopefully it will for anyone else.

2 responses to “Fix for Mail Enable – %1 is not a valid Win32 application.”

  1. Mark avatar
    Mark

    I was having same issue on W3K 64bit (VPS solution). When I installed MailEnable (free edition) it auto installed the 64bit version (initially ME complained that I didn’t have DotNet 3.5 installed so I installed that 1st then retried ME install which worked).

    ME WebMail worked just fine. But then I needed to install some 32bit ActiveX DLLs for my website (ASPUpload was one of them), and to get these working I had to run c:\inetpub\adminscripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1

    This got my 32bit DLLs working fine but WebMail stopped with an error like “%1 not 32bit Win app” (or something like that).

    So I ran your solution (C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i -enable) and hey presto, WebMail worked again *and* my 32bit DLLs kept on working.

    IIS6 added (and enabled) the entry “ASP.NET v2.0.50727 (32 bit)” to the Web Service Extensions list. “ASP.NET v2.0.5072” was already in the list (I suspect from the DotNet 3.5 install). I think I also ended up with 2 Default.aspx entries in the Document list for all my websites (I just went and deleted one or both Default.aspx entires from all my websites that didn’t use aspx).

    This took me several days to resolve. I hope my experience (and Alex’s) helps others.

    Cheers Alex.

    Regards, Mark. Sydney, Australia.

  2. Tom avatar
    Tom

    Thank you!

Leave a Reply

Your email address will not be published. Required fields are marked *