SecuritySuite - SuiteCRM and CE Teams

Wow, you're fast. Are you using Module Installer or a different install process? SuiteCRM shouldn't be executing that table creation sense the module is already installed. We may need to force a bypass here if you are using Module Installer.

I am using the module loader / installer

Digging into that message more in the Suite code, it looks like that is just an informational message. Do you see any other messages? How about in your suitecrm.log or PHP/Apache logs?

I wonder if this could be a file permissions/ownership issue that is preventing copying the files over after doing the database structure installation. This appears to be the order that SuiteCRM installs.

That's perfectly normal as well. What does Module Installer show as installed? Seems like there are no errors. Maybe a browser console error is being thrown?

That usually means that SuiteCRM couldn't back up files due to permissions during that original install so uninstalling can't be done anymore. I recommend reassessing file permissions. Even considering temporarily opening up permissions to install and then immediately reverting permissions back to what it was.

Another idea is to open up the debug level in your php.ini, restarting Apache, and trying again. Some important errors may be getting suppressed.

Did you receive my reply to your email? It looks like there is a fatal PHP error pertaining to a custom module that you have. For whatever reason, it is causing the installer to not work. Addressing that will make the installer work correctly.

I don't know, this error is for a submodule that I can't find so I can't remove it either. I don't think it's connected.

That's a good clue right there. That would explain why SuiteCRM is running into that error if the module isn't there. I suggest doing a search/grep on all of your SuiteCRM files and find where that module name is referenced. Then remove as appropriate. Even commenting out any references should be good enough to make this work.

You will need to log into the server (not the CRM) and do a search on all files in your SuiteCRM directory for "msims_shipping_". Then comment out each reference to it in the code. For whatever reason, this module left some orphaned references to it in the code base.

It could also be in the database in a table such as "relationships". If you find anything in that table go ahead and delete that row only.

The cron thing shouldn't be an issue. The fatal error was around that orphaned module. Any luck finding that in the relationships table? Could be either on the lhs or rhs side.

Try this query:

select * from relationships
where relationship_name like '%msims_shipping%' 
  or lhs_module like '%msims_shipping%' or rhs_module like '%msims_shipping%'
  or lhs_table like '%msims_shipping%' or rhs_table like '%msims_shipping%'
  or join_table like '%msims_shipping%';

I got your reply that this came up with nothing. Going back to the original stack trace, there has to be something in the code base with "msims_shipping" in it. Usually that would be in /custom/metadata or in /custom/Extension somewhere. I would focus back at searching the entire code base to get this found and cleaned up.