Will license support for this be added so that those of us with monthly Helm rentals can upgrade?

I want to upgrade so I can have support for MySQL 4.1 which Helm 3.1 does not currently support, not just because "I feel like it" :-(




(Matt-12/15/04-01:00):
I have some monthly HELM licenses through servermatrix. It is my understanding that the monthly licenses from webhostautomation include the maintenance contract to upgrade from Helm 3.1 to Helm 3.2. Is this correct, and if so, how can I take advantage of this?


(rbriggs-12/15/04-00:52):
I'm checking into this now!


(rbriggs-12/15/04-01:00):
While any application will recommend upgrading to the latest and greatest we do not currently support HELM 3.2

This is very interesting.

Is this "non-support" because of licensing (no license for 3.2 for SM/TP customers) or because of risky upgrade (stability, incompatibility, etc), or because of something else (example: SM/TP staff is not ready)?

my helm installation says "Software Version: 3.2" and when I click on "Software Updates" I see an update named "Helm 3.1.8+ To Helm 3.2.0 (Stable)*"

Haven't updated yet. I will do it over the weekend just in case something goes wrong.

All customers who have a Helm licence from ServerMatrix are entitled to a free upgrade. You can update Helm from the Helm Configuration Tool which you should find on the desktop of your server.

That is great to know. I can confirm that it is possible to upgrade to version 3.2 with the Servermatrix license. We have not done it however -- will schedule to do that soon. It looks like the answer from the SM tech means just that SM is not ready to provide support for Helm 3.2, and not because of the license restrictions.

Anyone step off this edge yet?

EDIT: I think what SM is trying to say is that they don't support Helm 3.2 yet as they haven't trained their techs on it. I'm not sure how good SM is on helm to begin with as I've never used them except for a really big problem that had me stumped.

Yeah. That is what I think too. We have never ask SM for support on Helm, so it a non-issue for us really. As long as we can upgrade, that is fine with us. In any case, the sure sign that they will have support for Helm 3.2 is when the new Helm/Windows servers are coming out with version 3.2 installed.

Since I have an owned license from WHA, I get my support from them (haven't had to use it though) so SM's stance atm didn't affect me.

If you were wondering how stability, performance, etc.. was, I'll just tell you I've experienced no problems since the upgrade. While it may be a paid upgrade to 3.2, it certainly doesn't feel like it (yet). The biggest thing they've added is support for application pools and virtual directories. I'll just tell you straight up to avoid those. Sometimes creating a new app pool works, sometimes it doesn't, though it's way too often a newly created app pool displays "Service Unavailable" and you have to log in via RDC and fix it. From there on out, they're fine, but it's a weird little niggle a bunch of people are experiencing atm.

I know some of our customer have had some odd problems with Application Pools including the "Service Unavailable" issue you've mentioned below. As always we'll be working to get any crinkles ironed out and will release patches as needed.

If you're interested in keeping up to date on any Helm news and issues the best think would be to pop over to our forums when you have a chance. I'll also be around here on this forum as much as possible.

Well, I stepped off the edge and did the update. Nothing broke, nothing really changed and I was disappointed I didn't get my subdomain hosting. (well I know a work around)

Hi,
Just signed up for a new server last week. It still comes with 3.1.16 installed. Tried to upgrade but got "The upgrade service does not recognize this product. Error 130001: Product not registered with the update service"

Anybody know how I register it?

cheers,
Robert

http://www.webhostautomation.com/downloads.aspx



Download that.

I'll try to get in touch with the right people to see why you got a server with 3.1.16 installed. You should have got 3.2.3 from the beginning.

Can other people confirm that this is what happened for them also?

I had the same problem back in march. Version 3.1.16 was installed and I couldn't run the update. The current version at that time was 3.1.19. I think this was about the time you changed the update method in Helm. Ticket 630171PLNT.

just open a ticket and sm will apply the needed patch for you . then you will be able to update