I have tried to upgrade helm3 to helm4. There was only 1300 domains under one Helm control server and another 2 remote server.
I have installed the helm4.1.1 control server in same Helm 3.2 server. Helm 4.1.1 installed in another 2 helm 3.2 remote server. We can install the helm3.2 and Helm 4.1.1 in same server.
According to the different blog discussion , I have updated helm 4.1.1 with the latest version.
After that I have executed the helm4upgradetool.exe in parellel helm installation folder.
I could see it is migrating all plans, packages and domains one by one. Within one hour this tool migrated around 300 domains and its packages to helm 4.1.1
But after one hour helmupgradetool was taking 5- 10 minutes for each account. After each account the migration time for account migration was keep on increasing.
After 500 domain migration the tool started to migrate the next reseller account. But while it creating the package it has give the following error
Creating New Package [Source: ImportAccount]
ERROR: System.Exception: Can not create package due to error "Unable to create a Package as the Plan r10mb has not had any Limits configured."
at WHA.Helm.UpgradeTool.Helm4Importer.ImportPackages(XmlElement PackagesNode, Account Account, GlobalDNS GlobalDNS) [Source: ImportPackages]
After this it failed to migrate any single domain.
While I enter to the HELM panel I could not see the message of the each plan - plan limit not configured.
According to the suggestion in the different blog, I deleted the helm4.1.1 db and given the migration process again.
Each migration I waited around 30 hours to finish. But always I was getting the same error in the log file more over in the helm 4.1.1 panel
So I have stopped the usage of migration tool and created each accounts manually. While I move the account some time helm4.1.1 was giving me the error plan limit not configured.
I have wasted another 2 days to resolve the issue. Several reboot of all servers couldn’t resolve the issue. At last I have reinstalled all helm components , all modules and updated helm 4.1.1 in all servers even if it was latest version. This step resolved helm 4.1.1 plan limit issue.
By
Lijo Peter
Adsin Technologies
http://www.adsinmedia.com