asklijo.com

  • Increase font size
  • Default font size
  • Decrease font size

ftpgene is not taking the update which we have changed in HELM 4.1.1

Recently I have migrated the HELM 3.2 to Helm4.1.1 . The upgrade was manual and all email ids from smarter mail and ftp accout id  was showing in each domain.
While we change the quota limit of the ftp under package, that was not affecting in ftp server. still it was telling max quota limit is exceeded

I could solve the issue through the following method.

I have logged into the domain, and clicked on the ftp accounts.

I have just deleted the ftp account id and created again. Now it is affected in geneftp and I could upload more files to ftp server.

 

By

Lijo Peter

Last Updated on Saturday, 06 February 2010 17:15
 

How to install php pear mail in IIS under windows 2003 server

If you want to disable default smtp server in IIS and use the mail through any remote mail server you can use the pear package. To activate the pear mail service in your php kindly go through the following steps

According to my guide , I guess you have already installed php under your IIS

Open the command prompt in your server go to the php installed folder

eg : cd c:\php

execute the following command to install pear

c:\php\go-pear

give all those default

that will install pear

 

now if you try to send the mail through pear it may generate the following error

Fatal error: require_once() [function.require]: Failed opening required 'Mail.php' (include_path='.;c:\php\pear') in

 

This message indicate you have to install the pear mail package, you can install pear mail package by giving the following command in command prompt

c:\php\pear install mail

this will install the pear mail package

 

If you try to send the mail again you may get the following error

Warning: Mail_smtp::include_once(Net/SMTP.php) [function.Mail-smtp-include-once]: failed to open stream: No such file or directory in C:\php\PEAR\Mail\smtp.php on line 206

Warning: Mail_smtp::include_once() [function.include]: Failed opening 'Net/SMTP.php' for inclusion (include_path='.;c:\php\pear') in C:\php\PEAR\Mail\smtp.php on line 206

Fatal error: Class 'Net_SMTP' not found in C:\php\PEAR\Mail\smtp.php on line 210

 

This error indicate you have to install Pear Net_SMTP package , you can install that through the following command in command prompt

c:\php\pear install Net_SMTP

Now you have installed PEAR packages to send the email with SMTp authentication.

If you need the php code to send the mail with SMTP authentication, kindly click on the link given below

http://asklijo.com/component/content/article/38-web-hosting/65-how-to-send-mail-through-php-with-smtp-authentication


By

Lijo Peter

Adsin Technologies

Last Updated on Friday, 12 February 2010 14:41
 

Helm4upgradetool experience

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

 


Page 3 of 3