Post 3.0.1.0 upgrade problem

[Paul]

Try this: Stop your Mezzmo server and exit Mezzmo. Using Windows Explorer, go to your Mezzmo program folder and delete the 'auTemp' and 'auLogs' folders if they are present. Now try to start Mezzmo and see how you go.

[splittingdistant]

Hi Paul,

I could only find a "auTemp" folder, which I deleted. Unfortunately, the pesky message still appears after I restarted Mezzmo.

I also tried repairing the installation with a redownloaded package but still no luck I'm afraid.

I'm not sure if this will help but, the message appears after the Mezzmo GUI has appeared but before the Windows "User Account Control" message which pops up when the Mezzmo server initiates.

Regards,

Kevin.

[Paul]

Hi Kevin,

We reproduced your problem. Here's the fix:

• Stop your Mezzmo server and exit Mezzmo if running.
• Use Windows Start menu to run "regedit.exe". This is the Windows Registry Editor.
• If you have not used Windows Registry Editor before, be careful as it contains settings for Windows and your programs. I'd suggest you make a backup of the registry before making any changes. To do this, click the top icon in the tree (Computer) and click File -> Export to save a backup.
• In Windows Registry Editor, go to HKEY_LOCAL_MACHINE -> SOFTWARE -> Conceiva -> Mezzmo -> AutoUpdate -> Settings (or if you are running Windows 64 go to HKEY_LOCAL_MACHINE -> SOFTWARE -> Wow6432Node -> Conceiva -> Mezzmo -> AutoUpdate -> Settings).
• You should see "busy" attribute listed there. If this value is set to "1", then double-click it and change it to "0".
• Exit Windows Registry Editor.
• Run Mezzmo and see how you go now.

[splittingdistant]

Paul,

We'll start with the bad news!

The main Mezzmo system registry entries on my Win7 Home Premium system were not under HKEY_LOCAL_MACHINE, but I managed to find something close under HKEY_CURRENT_USER -> SOFTWARE -> Conceiva -> Mezzmo -> AutoUpdate -> Settings.

But there was no "busy" attribute, just attributes called "(default)", "ask", and "err".

However, when I did a full search of the registry for the "busy" attribute, I found this: "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Conceiva\ Mezzmo\AutoUpdate\Settings" which DID include a "busy" attribute which was set to "1".

And now the good news!

On changing this to "0", I can confirm that the pesky message no longer appears when Mezzmo starts. So we can consider this problem well and truly fixed.

It might be the case that the location of the registry entry "busy" will depend on which one of the numerous versions of Windows is used, and as I forgot to tell you which version of Windows I was on when I first posted it didn't help the resolution process, so sorry about that.

In fact it would be great if Conceiva would port Mezzmo to Linux so I could ditch Windows, and the mess that is the System Registry for once and for all.

Regards & Thanks,

Kevin.

[Rich]

Hi if it helps,

64 bit machines use a different node in the Windows registry which is why it can be located at : HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Conceiva\ Mezzmo\AutoUpdate\Settings (with the Wow6432Node being the difference) otherwise use
HKEY_LOCAL_MACHINE -> SOFTWARE -> Conceiva -> Mezzmo -> AutoUpdate -> Settings

Thanks for the help - I had the same problem.

If it helps also - I noted the help about was still showing 3.0.1.0 after the upgrade failed and you got the message : "A previous package installation has not been completed.

Please restart Windows to complete the package installation before
running Auto Update again."

Thanks

Rich

[Nyarlathotep]

In fact it would be great if Conceiva would port Mezzmo to Linux so I could ditch Windows, and the mess that is the System Registry for once and for all.

Though it still requires a Windows installation, Mezzmo does work using VirtualBox...

[Paul]

Glad you are up and running now.

Thanks for the heads-up on the Windows 64 registry path. I have edited my post to include both Win 32 and Win 64.