Make sure you run "Quick Repair and Rebuild" from Admin -> Repair. Hopefully you will see a sql query to be executed in order to create such a table.

Andre,

Wow, I think you've got it.  I ran the repair and it did see that the table was missing and it did generate some creation SQL.  Before I go further, let me ask a question:

When I import a module like that, is the table not automatically generated in the database?  Is it just metadata that is imported that describes the table/fields and the table must be created separately?  Or was their some sort of error during import?

In any case, unfortunately the sql execution failed with a Database failure. Please refer to sugarcrm.log for details message.  I don't see any entries in the log about the failure.  What should I try next?

Thanks much for the assist.

Bryan Hunt

It should, but sometimes extended metadata are not compiled at time, so I ALWAYS run the repair actions after a deploy, in order to make sure nothing is missing.

Andre,

Thanks again for the information.

Any ideas on how I can proceed with the failed sql code?  Is there a place where I can execute the sql code a bit at a time until I determine where the error is?

Bryan

Remove all the comments from the SQL code and check that the same table is not changed twice (for index settings e.g.). Double check the syntax and remove any not necessary SQL code, even duplicate semicolons. If you want post the code here and I'll have a look on it.

Andre,

I ended up having Sugar Support pull everything out, then redeployed.  Worked fine the second time.

Thanks.

Bryan