Prestashop 1.6.13 exception on modules_access after migrate to final domain

[franco.aquini]

i've builth a new site with Prestashop 1.6.13. when i've tried to migrate to the final domain, an exception appear:

 

[PrestaShopException]

 

No access reference in table module_access for id_module 67.

at line 2538 in file classes/module/Module.php

 

2533.                 self::$cache_permissions[$employee->id_profile][$row['id_module']]['uninstall'] = $row['uninstall'];

2534.             }

2535.         }

2536. 

2537.         if (!isset(self::$cache_permissions[$employee->id_profile][$id_module])) {

2538.             throw new PrestaShopException('No access reference in table module_access for id_module '.$id_module.'.');

2539.         }

2540. 

2541.         return (bool)self::$cache_permissions[$employee->id_profile][$id_module][$variable];

2542.     }

2543. 

ModuleCore::getPermissionStatic - [line 3283 - classes/controller/AdminController.php] - [2 Arguments]

AdminControllerCore->getModulesList - [line 2329 - classes/controller/AdminController.php] - [1 Arguments]

AdminControllerCore->renderModulesList - [line 2063 - classes/controller/AdminController.php]

AdminControllerCore->initContent - [line 136 - controllers/admin/AdminLoginController.php]

AdminLoginControllerCore->initContent - [line 189 - classes/controller/Controller.php]

ControllerCore->run - [line 367 - classes/Dispatcher.php]

DispatcherCore->dispatch - [line 58 - admin/index.php]

 

I've done many tests on ps_module_access table and on the users profiles, but i've not find a solution. 

 

Can you help me? 

 

Thank you very much.

 

[musicmaster]

look in the ps_module table which module has number 67. Then delete (or rename) it from the modules directory. Then reinstall that module.

 

Alternatively you might decide to add an entry for this module in the ps_module_access table.

[franco.aquini]

look in the ps_module table which module has number 67. Then delete (or rename) it from the modules directory. Then reinstall that module.

 

Alternatively you might decide to add an entry for this module in the ps_module_access table.

Thank you @musicmaster. If i delete module with id 67, than the error appear for another module. And in the ps_module_access table already exist a correct entry for that module. 

 

I don't understand where is the problem.

[musicmaster]

If it isn't the module then it should be the employee. So you might try to add some diagnostic code to see for which employee id it is looking in the ps_module_access table.