Hello Perry,
As you mentioned, everything I can find on these messages, references some type of modification or customization, whether it is something in Dexterity, third-party products and/or modified forms/reports:
>Procedure trigger registration for IV_Post_Line_Item failed
>Procedure trigger registration for ICTR_ReportList_EmailReport failed
>Outsourcing function trigger registration for function SetAcctID of form POP_POLine failed
When you mention you removed all ISV and customizations, did you try installing a brand, new instance of Dynamics GP at the same version/build and with Manufacturing installed but with no third party products, customizations and/or any modified forms or reports dictionary files added in order to launch Dynamics GP and see if these error messages still show? I ask because in most cases, removing third-party products and customizations from the Dynamics.set file isn't a valid test.
If you have tested with a 'clean' install with any of the items I mentioned and still get these messages, then we'd probably need a case opened for the 'Manufacturing' team to look at anything data related which may be causing the errors to occur.
The only other items I could think of checking, that we've seen cause odd errors and performance are:
>Verify whether or not there are any DDL triggers setup in SQL and/or database triggers on SQL or GP databases.
community.dynamics.com/.../microsoft-dynamics-gp-upgrades-failing-on-concat-null-yields-null-error-message
This blog goes over verifying whether any DDL triggers, database triggers and/or custom triggers exist, which could be causing this type of error to occur.
>The POP_POLine object is the POP10110 table, verify we don't have any custom triggers or anything on that table that isn't default to Dynamics GP.
> You can use the following script to look for any third-party objects such as triggers or functions in GP databases by using these script examples:
>Triggers: Select * from sysobjects where xtype = 'TR' order by name
>Functions: Select * from sysobjects where xtype = 'FN' order by name
>The following logs may also give more information as to what is causing these errors, such as a script or object being run:
KB 850996 - How to create a Dexsql.log file to troubleshoot error messages in Microsoft Dynamics GP
support.microsoft.com/.../how-to-create-a-dexsql-log-file-to-troubleshoot-error-messages-in-micr
How to gather a Dexterity Scriptlog in Microsoft Dynamics GP
support.microsoft.com/.../how-to-gather-a-dexterity-scriptlog-in-microsoft-dynamics-gp
Let us know if you have any questions.
Thanks,
