Problem

When I try to open my control panel, I get a Page Cannot Be Displayed error.
I’m trying to open it using localhost on port 8086.

Solution

1.) Check the configuration tool, under the Website tab. What have you chosen from the dropdown box? If there is an IP chosen, then localhost may not work – only http://SelectedIP:8086

2.) If this is not the issue, then check the Page Not Displayed error. Is it a 500 error? If so, in Internet Explorer go to Tools, Internet Options and choose the Advanced Tab. Scroll down and uncheck the Show Friendly HTTP Error Messages box. Click OK, then refresh the page. You may get a different error. If this is the case, make sure you have MS XML 4.0 SP2 installed as specified in the Pre-Install Guide.

3.) Make sure that the IIS site (Helm Control Panel) is running in IIS and is not stopped.

4.) If you are running IIS 6, also make sure that ASP pages are set to “Allowed”, not “Prohibited”. To check this, open IIS and choose Web Service Extensions. You’ll see a list of properties on the right. Active Server Pages should be set to “Allowed”. If they aren’t, highlight them and click “Allow”.

4.) Make sure that the database is set up correctly in the Configuration Tool. Click the Test Connection button to confirm this is successful.

5) If any of the above checks don’t work, raise a ticket with your Helm provider (if you have a valid support contract with them).

Helm keeps giving ’ ValidateLicenceEx Invalid licence key. Licence has expired. ’ errors in the log

Problem

On occasions, the licence updater stays in memory and doesn’t end properly if ran from a scheduled task (you can see it running in the Task Manager as HelmLicence.exe). This then causes you to not be able to login to Helm.

Solution

1.) The problem is actually to do with Internet Explorer settings.

Take a look at the Windows scheduled task that runs the licence updater. This can be found here:

Start > Programs > Accessories > System Tools > Scheduled Tasks

and is called Helm Licence Updater.

Right click it, choose “Properties” and make a note of the user that is set to run this. It is usually HELM_ADMIN, and the password is the password you chose when installing Helm.

Important Note:- If you changed the servername AFTER installing the control panel, you will need to alter it here. For instance if your server was called MYSERVER then the licence task would have been running under MYSERVERHELMADMIN. If you changed the servername to NEWSERVER then you need to make sure that the task also changed, so it is NEWSERVERHELMADMIN.

You can either keep this the same, or change it to Administrator or some other user you know the password of.

Next, login to the server as that user. So if the task was running under HELMADMIN, you need to login to the server as the HELMADMIN user. The password for this will be a) either known to you if you are running multiple servers because you will have needed to create this user on all of your remote servers or b) if you are running a single server, it’s the password you chose when installing Helm. If you forgot it, you can reset it in the System Identity tab of the Helm Configuration Tool (make sure that if you do this, you reset it on ALL remote servers that you have too!).

Now run the scheduled licence updater task (go to the task, right-click it and choose “Run”). You should find you get a internet explorer pop up box – click OK and tick don’t show this again. (if you have changed it to another user, you may not see this box as you may have already logged in some time ago and this pop up was clicked on before)

Now you can log out and back in as the normal user you log in as.

You can now see the problem – when the scheduled task ran as that user, the Internet Explorer pop up box was waiting for a confirmation click – however you never saw it and that task was held in memory. It must have been in memory and never ran again for more than 30 days – if it doesn’t run for 30 days, you get that licence error.

2.) In the rare event that this doesn’t solve your problem – check the system date of the server. It should be today’s date. If it is set in the past or the future, it may cause issues with the licencing. Set it to today’s date, then try and log in.

—Alex

When I try to add a server to Helm, I get the error ’ Unable to add server. Can not obtain Licence From Server ‘.
Problem

When I try to add a server to Helm, I get an error saying:

Unable to add server. Can not obtain licence from server.

and I cannot add the server.

Solution

Ensure the following:

1.) The HELM_ADMIN user is on all machines that you are trying to add into Helm, with Administrator permissions.

2.) MS XML 4.0 is installed on all machines.

3.) File and Print Sharing is enabled on all machines (refer to the Helm Pre-Installation Guide on how to do this).

4.) The Remote Registry service is started on all machines (refer to the Helm Pre-Installation Guide on how to do this).

5.) Every machine can access every other machine’s C drive. You can test this by doing the following: – Go to Start > Run – Type RemoteServerIPC$
The remote server’s C drive should open on the server. If this isn’t the case, then there is a communication issue between the two servers which you will need to resolve.

6.) If all of this is correct, please follow this article to reset and then update your licence key:

http://support.webhostautomation.com…details&_i=148

7.) Also try rebooting the two machines in question.

—Alex

If you are using MSDE for the Helm system database, it can be backed up using the backup tool which is available for download here at:

http://www.webhostautomation.com/members/download_redirect.aspx?id=19

You can use other methods such as IIS Metabase backup to backup IIS and other data, and for domains you can use a simple copy/ftp backup process using MS Backup/Veritas or whatever you use to do backups normally.

—Alex

Suspending user accounts doesn’t disable DNS, FTP or email
Problem

When I go into a User account and choose Suspended then save it, it only stops that user’s website in IIS. It doesn’t pause/suspend DNS, Email accounts or FTP accounts.

Solution

This is because some of the software products supported by Helm don’t offer the ability to suspend accounts. Therefore offering the generic ability to each of these under a user account isn’t possible at this time.

—Alex

Helm keeps giving ’ ValidateLicenceEx Invalid licence key. Licence has expired. ’ errors in the log

Problem

On occasions, the licence updater stays in memory and doesn’t end properly if ran from a scheduled task (you can see it running in the Task Manager as HelmLicence.exe). This then causes you to not be able to login to Helm.

Solution

1.) The problem is actually to do with Internet Explorer settings.

Take a look at the Windows scheduled task that runs the licence updater. This can be found here:

Start > Programs > Accessories > System Tools > Scheduled Tasks

and is called Helm Licence Updater.

Right click it, choose “Properties” and make a note of the user that is set to run this. It is usually HELM_ADMIN, and the password is the password you chose when installing Helm.

Important Note:- If you changed the servername AFTER installing the control panel, you will need to alter it here. For instance if your server was called MYSERVER then the licence task would have been running under MYSERVERHELMADMIN. If you changed the servername to NEWSERVER then you need to make sure that the task also changed, so it is NEWSERVERHELMADMIN.

You can either keep this the same, or change it to Administrator or some other user you know the password of.

Next, login to the server as that user. So if the task was running under HELMADMIN, you need to login to the server as the HELMADMIN user. The password for this will be a) either known to you if you are running multiple servers because you will have needed to create this user on all of your remote servers or b) if you are running a single server, it’s the password you chose when installing Helm. If you forgot it, you can reset it in the System Identity tab of the Helm Configuration Tool (make sure that if you do this, you reset it on ALL remote servers that you have too!).

Now run the scheduled licence updater task (go to the task, right-click it and choose “Run”). You should find you get a internet explorer pop up box – click OK and tick don’t show this again. (if you have changed it to another user, you may not see this box as you may have already logged in some time ago and this pop up was clicked on before)

Now you can log out and back in as the normal user you log in as.

You can now see the problem – when the scheduled task ran as that user, the Internet Explorer pop up box was waiting for a confirmation click – however you never saw it and that task was held in memory. It must have been in memory and never ran again for more than 30 days – if it doesn’t run for 30 days, you get that licence error.

2.) In the rare event that this doesn’t solve your problem – check the system date of the server. It should be today’s date. If it is set in the past or the future, it may cause issues with the licencing. Set it to today’s date, then try and log in.

—Alex

Step 1) Edit the /etc/resolv.conf file
Check if the IP addresses for nameservers are as follows.
nameserver 127.0.0.1
nameserver 192.168.1.1
nameserver 192.168.1.2

If not please change it. Webalizer checks resolve.conf file before generating the webstats.

Step 2) Go to the path /usr/local/cpanel/src/3rdparty/gpl/webalizer-2.01-10
Then run the following command
./configure—enable-dns—with-dblib=/lib

Step 3) Then run /scripts/runweblogs to see if the changes are updated.

You need to make one change to your httpd.conf file in the /etc/httpd/conf directory. (It is advised that you make a backup of the file BEFORE making any changes.)

Edit the file, look for HostnameLookups and change the value to On. Save the file and restart the web server i.e.
/etc/rc.d/init.d/httpd restart

If exim is running but still cpanel emails about exim fails then do following….:

pico /etc/chkserv.d/exim
<supportLineBreakNewLine]—>

service[exim]=25,QUIT,554,/etc/rc.d/init.d/exim stop;/etc/rc.d/init.d/exim stop;/etc/rc.d/init.d/exim stop;/etc/rc.d/init.d/exim start

to:

service[exim]=25,QUIT,220,/etc/rc.d/init.d/exim stop;/etc/rc.d/init.d/exim stop;/etc/rc.d/init.d/exim stop;/etc/rc.d/init.d/exim start

Note: 554 -> 220 is the difference. Then run:
/etc/init.d/chkservd stop
/etc/init.d/chkservd start

Hello Everyone,

If you are getting following error while installing phpbb from Fantastico

Warning: fileperms(): Stat failed for /home/qededu/.fantasticodata/temporary/phpBB2 (errno=2 – No such file or directory) in /usr/local/cpanel/3rdparty/fantastico//includes/enc_functions.php on line 287

Warning: isfile(): Stat failed for /home/qededu/publichtml/test/config.php (errno=13 – Permission denied) in /tmp/cpanelphpengine.1146740152.297467947.16752673597 on line 1147
1) File: /home/qededu/publichtml/test/config.php [ERROR! ]

Warning: isfile(): Stat failed for /home/qededu/publichtml/test/data.sql (errno=13 – Permission denied) in /tmp/cpanel_phpengine.1146740152.297467947.16752673597 on line 1147

2) File: /home/qededu/public_html/test/data.sql [ERROR! ]

Just check the permission of tar file. Try to run following commands:

root@venus [~]# whereis tar
root@venus [~]# ls -al /bin/tar

If permission of /bin/tar is not 755 just change it to 755.
root@venus [~]#ls -al /bin/tar
rwx——- 1 root root 149484 Mar 13 10:57 /bin/tar*
root@venus [~]#chmod 755 /bin/tar*
root@venus [~]# ls -al /bin/tar
rwxrxr-x 1 root root 149484 Mar 13 10:57 /bin/tar*

That’s all.
Shane Bewick

Following is a snapshot of Enterprise Linux :

—> What is it?

Red Hat Enterprise Linux is the premier operating system for open source computing. It’s sold by annual subscription, runs on seven system architectures, and is certified by top enterprise software and hardware vendors. It’s backed by a Red Hat Network subscription up to 24×7 support with one-hour response, and the Red Hat Open Source Assurance program.

—>What does it do?

Red Hat Enterprise Linux creates a reliable, secure, high performance platform designed for today’s commercial environments—with capabilities that match or surpass those of proprietary operating systems. Sold in three products that span client systems to the largest servers, Red Hat Enterprise Linux delivers a consistent application, management, and user environment.

—>Why should I care?

Red Hat Enterprise Linux is the corporate Linux standard. It’s already at work running some of the world’s largest commercial, government, and academic institutions. For any deployment—from the desktop to the datacenter-Red Hat Enterprise Linux delivers unmatched performance and cost savings, and the freedom of open source technology.

—>Red Hat Enterprise Linux Features and Benefits

All products in the Red Hat Enterprise Linux family are based on a common software core—kernel, libraries, development toolchain, and utilities. This provides a homogeneous environment ideal for simplifying multi-system and desktop-to-datacenter configurations. The immediate benefit: simplified deployment of distributed applications, and a consistent environment for users and system administrators across the entire family.

—>New in Red Hat Enterprise Linux, Version 3

Introduced in September 2003, Red Hat Enterprise Linux, version 3, includes a broad range of new features:

1) Support for seven architectures:
Intel X86, Intel Itanium, AMD AMD64 and IBM zSeries, iSeries, pSeries, and S/390.

2) 4-4 memory split:
Increased kernel & user address space for X86 systems, allowing support for 64GB of main memory and larger user applications.

3) Native Posix Thread Library:
A new high-performance multi-threading capability provides improved performance for multi-threaded applications.

4) Based on Linux 2.4.21 kernel:
Red Hat Enterprise Linux uses the latest stable Linux kernel with numerous additions from the Linux 2.5/2.6 kernels.

5) Improved scalability:
Support for larger SMP, memory and I/O systems allows version 3 to support servers approximately twice the size of version 2.1.

6) Forward compatibility:
Version 3 includes compatibility libraries so it can run version 2.1 applications without modification.

7) Standards support:
LSB 1.3 compliant and undergoing NIAP CC EAL2 evaluation.

Improved desktop:
Includes Red Hat’s Bluecurve graphical user interface, and a comprehensive set of personal productivity applications.

9) Enhanced security:
Includes several new security features, including support for file system ACLs.

10) Bundled Stronghold:
Red Hat’s secure web server solution, previously available as a separate layered product for Enterprise Linux AS, has been updated to Apache version 2 and included as part of the base Red Hat Enterprise Linux product set.

11) Improved compiler/tools:
Includes GCC 3.2 and debugging/profiling tools.

12) Logical Volume Manager:
Provides enterprise-strength storage management.

13) Diskless systems:
Supports deployment of diskless clients.

14) Enhanced Java:
Java implementations from BEA and IBM.

15) Enhanced networking:
Includes numerous features to improve stability & performance.

16) Support for Samba 3 provides numerous new features:

Greatly improved interoperability with Microsoft Active Directory. Samba 3.0 is able to join an ADS realm as a member server and authenticate users using LDAP/Kerberos
Improved Windows 2000/XP/2003 printing support including publishing printer attributes in active directory
Support for migrating from a Windows NT 4.0 domain to a Samba domain and maintaining user, group and domain SIDs
Support for establishing trust relationships with Windows NT 4.0 domain controllers
Support for client and server SMB signing to ensure compatibility with default Windows 2003 security settings
Improved ACL mapping

—>For more information on these and other new features, please refer to the Red Hat Enterprise Linux Feature-Function-Benefit analysis.

Regards,

Alex