A certain database trigger in the Harvest database remained active after the last upgrade when it should have been deleted.
The solution to this problem is to delete a certain trigger in the Harvest database that is left-over from the previous version of Harvest and is obsolete.
In order to locate the trigger to be deleted, login to SQL Server Management Studio, navigate to the Harvest database, expand the list of tables, and locate the dbo.HARFORMATTACHMENT table. Click the “+” to expand the details of the HARFORMATTACHMENT table, and expand the “Triggers” folder to find a trigger named HARUSDDEPLOYINFO_ATTID_TRIGGER. Right click on the name of the trigger and select “Delete”.
<Please see attached file for image>src="/servlet/servlet.FileDownload?file=0150c000004AK7XAAW" alt="image001.jpg" width="545" height="654">
On the “Delete Object” dialog click “OK” to confirm.
<Please see attached file for image>src="/servlet/servlet.FileDownload?file=0150c000004AK7YAAW" alt="image002.jpg" width="624" height="560">
Once the trigger has been deleted, you can stop and restart the SCM Broker. After that you should be able to delete the package without any further trouble.
As always, it is best to make a backup of your Harvest database before giving this a try. Could you or your DBA follow these steps and let me know if this resolves the problem?