I did check and there is a trigger called ifty_ilm_onNewModule. I looked at the code for that module and it references the ifinity url master.

I did make a backup prior to upgrading, so I can revert back, delete the trigger and try the upgrade again.

However, is there any way to determine which scripts are run during a specific phase of an upgrade and possible run them manually or do you think that could break some other update that was made after that one was origianlly supposed to be run?

Restored to 4.9.5, deleted the trigger, upgraded DNN to 5.5.1. No errors, everything seems to be running fine now.

Thanks for your help with this.

Just to follow up on this one: the ifty_ilm_onNewModule trigger is created when installing the Inline Link Master module.    The reason this trigger looks similar (and may even mention) the Url Master module is because it's a copy of the same trigger in that module (which is just called ifty_OnNewModule).

These triggers automatically create a new copy of the relevant module page in the Admin menu, either at the first install of the module, or when subsequent portals are created, also create the page for that portal.

The problems are twofold:
1) earlier versions of the module(s) did not uninstall these triggers correctly due to a bug.  This can mean you can get the problem even if you don't have the module currently installed - it's possible to have installed/uninstall the module and have the trigger 'left over'.
2) in DotNetNuke 5.5 (and later) the ModuleTitle column was removed from the TabMouldes table.  Thus the Sql within the trigger is no longer valid, which causes the syntax error shown.  This might show up in an unexpected place, or, commonly, during a DNN upgrade.  This versions of the module not specifically compatible with DNN 5.5.

The solution is to upgrade to the latest, DNN 5.5 compatible version of the module before attempting a DNN upgrade.  These can be found here:
http://www.ifinity.com.au/Products/Ur...
and
http://www.ifinity.com.au/Products/In...

There is no immediate effect from deleting the trigger (either module will continue to work), however, if you do delete the trigger, the respective module admin pages will not be automatically created if you add a new portal in the future.