Upgrade to Hoster 4.06 fails - "Serial Number does not match registration"
 

I am getting this error "Serial Number does not match registration" after upgrading from Hoster 3.31.

I did everything on the website - Windows XP Pro, updated to all the latest patches using IE6. Uninstalled and re-installed many times. When installing, the installation program connects to MTU and "approves" the email and registration code (I get the "Thank you" message), then as soon as I go to launch the program I get the error every time.

What do I need to do to make this work?

sorry to asked this and i am not implying anything,but did you buy the upgrade?, if not you have to buy the new upgrade since version 4.xxxx has a diff. registration # than 3.31xxx, that's probably why youre getting that error msg.

Yes, I upgraded to 4.06.

When I install 3.31 using the 3.31 code, it says "Thank you", then I get the "Serial Number does not match Registration" when I launch the program. (In other words, installing 4.06 has destroyed the 3.31 registration).
When I install 3.31 using the 4.06 code, it says "The code you entered is for a different product".
When I install 4.06 using the 4.06 code, it says "Thank you", then I get the "Serial Number does not match Registration" when I launch the program.
When I install 4.06 using the 3.31 code, it says "The code you entered is for a different product".

So, nothing works in any combination of registration codes and versions.

Here's how it's setup to work. First you have to be online. Install 3.XX using your old Hoster code then upgrade to Hoster4.XX using your upgrade code. Login to your account at:

https://www.mtu.com/catalog/login.php


This is where all of your RegCodes are located.

Since there has been some confusion with your codes, I would unistall Hoster, restart the computer, install 3.XX (using the old RegCode) then upgrade to Hoster 4 (using the upgrade RegCode).

If this is not working, go to:

http://www.mtu.com/support/customer-...m#WebEmailForm

and submit a support ticket.

Be sure to always use (logging in to your account & when you enter your information into Hoster for setup.) the email address you gave MTU when you purchased Hoster.

I hope this helps. :w

Jim :g

[quote=musictraining;84840]Yes, I upgraded to 4.06.

When I install 3.31 using the 3.31 code, it says "Thank you", then I get the "Serial Number does not match Registration" when I launch the program. (In other words, installing 4.06 has destroyed the 3.31 registration).
yes you will get that error msg, since 4.xxx uses a diff. reg. #

you might wanna double check when putting in the reg. # manually, i did that last night when i upgraded my back-up laptop i kinda transpose the #0 to a letter o

like i said the first time3.xxx has a totally diff. reg. # than version 4.xxx

so if nothing works you're best bet is to log in support and submit a ticket

I don't have a machine in front of me right now but....didn't the location of the Hoster.exe file change from 3.xx to 4.xx? Could musictraining just have a problem with the shortcut on the desktop? Remind me the directory of the .exe file for 3.xx and 4.xx.

Is 3.4 working?

It's actually 3.31 that I upgraded from, and no, it is not working now.

Even if I uninstall 4.06 and reinstall 3.31, 3.31 now gives the same error.

Folks, this has been resolved by phone between Musictraining and MTUSUPPORT.

The problem turned out to be something we have never seen before.

Musictraining installed under one user (Admin probably), and then tried to run under a different user.

The "Serial Number mismatch..." error appears when you do this.

This is the first time we have seen this, but it is not unreasonable for any number of our users to try and/or do this.

We will look and see if there is something we can do so Hoster will run, even if Windows doesn't want to allow it... or at least not say "SN mismatch" which implies the installation was done wrong on MTU's part. :e

Another BITE from Microsoft.... :m :t

Also just to add - I solved the problem by:

1) Uninstall Hoster

2) Running regedit, and identifying Hoster keys that could not be accessed due to permissions.

3) Right-click on those keys and select Permissions

4) Select Advanced, then the Owner tab

5) See which user account is the owner

6) Log into that account, and delete all hoster keys

7) Reinstall from the intended user account

Ideally, the keys should have their Owner set to the "Adminstrators" group, not one single administrative user.

Hopefully there's some light at the end of the tunnel.

http://application-programming.busin...ents.com/?p=40