An error occured with module license. Please contact support.

[DJFireCFH]

The title is what one of our clients is getting from clicking on " Install Applications!" button from with-in their Client area, under their web hosting. When they click the button it just gives an error message "An error occured with module license. Please contact support."

 

What license is it talking about? or what is it referring to ?

[brian!]

you might want to try looking in the activity log or module log to see if more detail is provided there...

 

utilities -> logs -> activity log

utilities -> logs -> module log

[DJFireCFH]

Ive checked those logs, its not showing anything about that.

[brian!]

I can only suggest to go through your addons one by one and work out which it could be...

 

if you have the "cPanel Extended For WHMCS" module from ModulesGarden, I think that uses the phrase "Install Applications!" within it.

 

http://www.modulesgarden.com/products/whmcs/cpanel_extended/features

 

if so, then you should probably contact ModulesGarden directly for support.

[vdavid23]

I know if it helps but in my case the problem was that the account had the wrong reseller account owner

 

This is my opinion:

 

I have searched many blogs and threats concerning the setup of this package and I have seen many generic responses from staff. Like:"Open a trouble ticket." which seems to be the easy answer to all the bugs or poor documented solutions to the setup and configuration of this product.

 

I feel that if those supporting the product were required to setup their own hosting server they would have a better grasp on the functionality of the package and less shifting of responsibility to the advanced technicians. I am assuming by their generic responses this is not happening. I feel requiring the advance developers to answer the most rudimentary questions, that staff, who support this product, should have a firm grasp on before supporting the product, is only taking away good time and energy from the developers who could be spending more time on the feature requests to make this a better product.

 

Some of the most basic questions should be asked before even making an attempt to correct or support many of the questions being posted, such as:

 

1. Are you using the default configuration when you first install?

 

I am assuming, before any product release, that the developers ran many tests before releasing any version. I am sure some will be missed, but the most basic of these I am sure are caught in the R&D process. I am sure the hours of testing proved the most basic setup will function in many setups, with the features list provided, but we are human, and there are those variables we cannot account for that could pose a problem in the future, but the reason I state all of this, is because that first question should be the baseline of the following questions.

 

1. Did you alter the most basic configuration in anyway?

 

By asking this question you have a baseline to work from, and if the support staff has been allowed to configure their own servers they will get a better grasp on the functionality of the software, but I see a lot of shade tree programmers answering the most basic questions, and yet they lack the most basic of skills to be answering them. Their qualifications are exposed by the limited scope of capability to respond in an appropriate manner, and shifting the responsibility to either the developers or buggy code.

 

 

Buggy code, or user error are not answers, they only give a level of unprofessionalism to the software that can and should be avoid through proper training. I know we get busy and do not have a proper plan in place for training of support staff, but a better answer would be "I don't know because I am only a few months in training." We cannot see the "In training button" in the threads so we feel those answering the questions are fully qualified to be answering these questions.

 

I will get off my soap box and answer some very basic questions to help new comers to the software, if you follow these simple and proven steps you will have a fully operational server in no time, but bear in mind, you must have some degree of knowledge in Linux and also Cpanel or other control panels that integrate with this software. If you feel you have a firm grasp on this, then what I am about to share will make sense, otherwise it will continue being a hit and miss, trial and error approach.

 

If I have learned anything in all the years supporting products and hardware this one key point should be remembered. In algebra you do not work both side of the equation at the same time. You work one, then the other, you can't not do both. In our excitement of opening a powerful package like this (which I am guilty of) I go to all the menu options and turn on and turn off features, not realizing I am creating my own problem.

 

I would say this again, the first question should always be this:

 

1. Is this a fresh install and did you change anything?

 

Then the next question should be:

 

1. Have you setup the General settings using the classic view?

 

The reason this one is important is because this theme I found has all the required features needed to host a self running hosting server. The most common theme in all the questions, including mine were, how to I get the server to automatically setup accounts after payment or an order is placed?"

 

I found this template is easier to navigate and will help troubleshoot most of the common problems with this software.

 

Then I feel the next question should be:

 

2. Did you add any custom software or hosting templates?

 

If you are excited and want a server running quick, and I am guilty of this too, we get head of the problem and add more problems to the mix. Again, start with the most basic of setups first, and then add your modules later. Too many times in my excitement of running new software I add modules before I have the most basic of setups running first. Get the system running in the basic setup and then begin your tweaking, this allows you to know which added module is causing the problem, but many of the problems are because we get in a hurry, and now we are troubleshooting issues that were never the problem to begin with.

 

Start with a base: I am sure the developers did this before releasing any version, and why support is not recommending this first I don't know. If customers whine because they have to do a fresh install, that is not your issue, you are there to trouble shoot the issue, and if the customer was too excited or in a hurry to do the most basic of configurations first, you could be troubleshooting a "core" issue not related to a module at all.

 

The next question should be:

 

3. Have you setup the server to configure using "root?'

 

I know setting up any server this way is dangerous, but when you are setting up a server you have to determine where the issue is first. In my discovery of "gateway modules", and the automated setup feature, where the account is not sitting in a "Pending status" when I used my "root" access to cpanel my features worked correctly. Now I have a base to work from and I can begin troubleshooting why my reseller accounts does not create the accounts automatically after purchase and I can begin asking the right questions, but until this is done you will continue asking questions from support who are not fully trained in the processes themselves.

 

The point is this: "When I got a base, which was functioning the way it was intended to, then I could turn on, turn off modules, add new templates, customize my login screens and be confident that it was not a "buggy" version or release, but to many times it is easier to blame the developers than to do our own research.

 

Again, the software works great out of the box. I found when I found a couple simple steps listed above in my setup before adding all my modules and ticking all the features, I found I spent less time reading blogs and spending more time tweaking the software.

 

I hope this response helps "everyone" and not a select few.

 

- - - Updated - - -

 

I know if it helps but in my case the problem was that the account had the wrong reseller account owner

 

This is my opinion:

 

I have searched many blogs and threads concerning the setup of this package and I have seen many generic responses from staff. Like:"Open a trouble ticket." which seems to be the easy answer to all the bugs or poor documented solutions to the setup and configuration of this product.

 

I feel that if those supporting the product were required to setup their own hosting server they would have a better grasp on the functionality of the package and less shifting of responsibility to the advanced technicians. I am assuming by their generic responses this is not happening. I feel requiring the advance developers to answer the most rudimentary questions, that staff, who support this product, should have a firm grasp on before supporting the product, is only taking away good time and energy from the developers who could be spending more time on the feature requests to make this a better product.

 

Some of the most basic questions should be asked before even making an attempt to correct or support many of the questions being posted, such as:

 

1. Are you using the default configuration when you first install?

 

I am assuming, before any product release, that the developers ran many tests before releasing any version. I am sure some will be missed, but the most basic of these I am sure are caught in the R&D process. I am sure the hours of testing proved the most basic setup will function in many setups, with the features list provided, but we are human, and there are those variables we cannot account for that could pose a problem in the future, but the reason I state all of this, is because that first question should be the baseline of the following questions.

 

1. Did you alter the most basic configuration in anyway?

 

By asking this question you have a baseline to work from, and if the support staff has been allowed to configure their own servers they will get a better grasp on the functionality of the software, but I see a lot of shade tree programmers answering the most basic questions, and yet they lack the most basic of skills to be answering them. Their qualifications are exposed by the limited scope of capability to respond in an appropriate manner, and shifting the responsibility to either the developers or buggy code.

 

 

Buggy code, or user error are not answers, they only give a level of unprofessionalism to the software that can and should be avoid through proper training. I know we get busy and do not have a proper plan in place for training of support staff, but a better answer would be "I don't know because I am only a few months in training." We cannot see the "In training button" in the threads so we feel those answering the questions are fully qualified to be answering these questions.

 

I will get off my soap box and answer some very basic questions to help new comers to the software, if you follow these simple and proven steps you will have a fully operational server in no time, but bear in mind, you must have some degree of knowledge in Linux and also Cpanel or other control panels that integrate with this software. If you feel you have a firm grasp on this, then what I am about to share will make sense, otherwise it will continue being a hit and miss, trial and error approach.

 

If I have learned anything in all the years supporting products and hardware this one key point should be remembered. In algebra you do not work both side of the equation at the same time. You work one, then the other, you can't not do both. In our excitement of opening a powerful package like this (which I am guilty of) I go to all the menu options and turn on and turn off features, not realizing I am creating my own problem.

 

I would say this again, the first question should always be this:

 

1. Is this a fresh install and did you change anything?

 

Then the next question should be:

 

1. Have you setup the General settings using the classic view?

 

The reason this one is important is because this theme I found has all the required features needed to host a self running hosting server. The most common theme in all the questions, including mine were, how to I get the server to automatically setup accounts after payment or an order is placed?"

 

I found this template is easier to navigate and will help troubleshoot most of the common problems with this software.

 

Then I feel the next question should be:

 

2. Did you add any custom software or hosting templates?

 

If you are excited and want a server running quick, and I am guilty of this too, we get head of the problem and add more problems to the mix. Again, start with the most basic of setups first, and then add your modules later. Too many times in my excitement of running new software I add modules before I have the most basic of setups running first. Get the system running in the basic setup and then begin your tweaking, this allows you to know which added module is causing the problem, but many of the problems are because we get in a hurry, and now we are troubleshooting issues that were never the problem to begin with.

 

Start with a base: I am sure the developers did this before releasing any version, and why support is not recommending this first I don't know. If customers whine because they have to do a fresh install, that is not your issue, you are there to trouble shoot the issue, and if the customer was too excited or in a hurry to do the most basic of configurations first, you could be troubleshooting a "core" issue not related to a module at all.

 

The next question should be:

 

3. Have you setup the server to configure using "root?'

 

I know setting up any server this way is dangerous, but when you are setting up a server you have to determine where the issue is first. In my discovery of "gateway modules", and the automated setup feature, where the account is not sitting in a "Pending status" when I used my "root" access to cpanel my features worked correctly. Now I have a base to work from and I can begin troubleshooting why my reseller accounts does not create the accounts automatically after purchase and I can begin asking the right questions, but until this is done you will continue asking questions from support who are not fully trained in the processes themselves.

 

The point is this: "When I got a base, which was functioning the way it was intended to, then I could turn on, turn off modules, add new templates, customize my login screens and be confident that it was not a "buggy" version or release, but to many times it is easier to blame the developers than to do our own research.

 

Again, the software works great out of the box. I found when I found a couple simple steps listed above in my setup before adding all my modules and ticking all the features, I found I spent less time reading blogs and spending more time tweaking the software.

 

I hope this response helps "everyone" and not a select few.