Fatal error in custom module when install

Question

Hi, We have created a custom basic module in SugarCRM pro v7.9.01. When we install it getting fatal error. PHP Fatal error: Uncaught exception 'SugarApiExceptionInvalidParameter' with message 'Invalid link created_by_link' in /var/www/html/include/SugarQuery/SugarQuery.php:941
Stack trace:
#0 /var/www/html/include/SugarQuery/SugarQuery.php(371): SugarQuery->loadBeans('created_by_link', Array)
#1 /var/www/html/data/SugarBean.php(3084): SugarQuery->join('created_by_link', Array)
#2 /var/www/html/include/SugarObjects/templates/person/Person.php(37): SugarBean->retrieve(1, false, true)
#3 /var/www/html/modules/Users/User.php(781): Person->retrieve(1, false, true)
#4 /var/www/html/data/BeanFactory.php(90): User->retrieve(1, false, true)
#5 /var/www/html/modules/ProjectTask/ProjectTask.php(75): BeanFactory::getBean('Users', 1)
#6 /var/www/html/data/BeanFactory.php(238): ProjectTask->__construct()
#7 /var/www/html/include/SugarObjects/VardefManager.php(769): BeanFactory::newBean('Project in /var/www/html/include/SugarQuery/SugarQuery.php on line 941 How to fix it? Thanks!

pavan agrawal · Accepted Answer

Hi pavan agrawal , I have heard of this before. The issue turned out to be that reminents of a previous attempt to deploy a module with that same name were in the file system of the instance, and had to be manually cleaned out before Module Builder could deploy a new module of that same name. If you are going to try the following, I recommend doing it in a test environment copy of your instance, as it involves deleting files. Diagnostically, please be aware that at the time Module Builder would deploy new modules/packages with other module names. Is that true in your case? After deleting the original module and package and rebuilding it from scratch using only the user interface, attempts to redeploy it still generated the error. Remnants of the module were left over in the file system. Searching the file system for any files referencing the name of the deleted module revealed the exact remnants. Deleting those files and starting completely over resulted in the module deploying properly. Link to SugarCRM's published best practices regarding Module Builder: http://support.sugarcrm.com/Documentation/Sugar_Developer/Sugar_Developer_Guide_7.9/Architecture/Module_Builder/Best_Practices_When_Building_Custom_Modules/