Use the appropriate method below, depending on which trigger is causing the issue:
METHOD 1: If the taVendorInsert trigger is causing the issue, follow these steps to refresh this trigger:
1. In Microsoft Dynamics GP, click the shortcut to open Professional Services Tools Library (PSTL).
2. Click the Register button in the lower left corner of the window.
3. A window will pop up prompting you to enter the registration code. Just click OK, as you do not need to change the keys.
4. This will trigger PSTL to recreate its procedures.
5. When completed, test the issue again to see if the error message still happens.
Note: If the issue persists, repeat the steps above to refresh PSTL a second time. Sometimes it works the second time. If the issue still persists, then you may want to look at reinstalling a newer version of PSTL.
METHOD 2: If any of the ep_Audit triggers are causing the issue, follow these steps to recreate these triggers:
1. Make a current backup of the Dynamics database, company database and also the Audit database before following these steps.
2. In Microsoft Dynamics GP, click Microsoft Dynamics GP, point to Tools, point to Setup, point to Company, point to Audit Trails and click on Audit Trail Maintenance.
3. In the Audit Trail Maintenance window, in the Audited Tables section in the lower right corner, review to see any audits for the PM00200 table and click to select it.
4. Click Stop Auditing.
5. If this is the only company database that writes to the Audit Trail database for this PM00200 table, then click the Remove button to remove the audit and the trigger will be removed from the table. IMPORTANT NOTE: Clicking Remove will also completely remove the PM00200_Audit 'table' in the Audit database, so all the history that has been tracked to date will also be removed. Therefore, make sure to have a current backup of the Audit database before doing this step.
6. Test to make sure the error message no longer occurs.
7. Now go back into the Audit Trail Maintenance window and re-setup the audit on the PM00200 table if needed.
METHOD 3: If you have a custom trigger, you can use these steps to script out the trigger details so you can review:
1. Open SQL Server Management Studio.
2. In the Object Explorer section in the left-hand margin, click to expand the SQL instance.
3. Click to expand Databases.
4. Click to expand the appropriate company database.
5. Click to expand Tables.
6. Click to expand the dbo.PM00200 table.
7. Click to expand Triggers.
8. Right-click on the custom trigger and select Script Trigger As and Create To and New Query Editor Window (or File).
9. Review the details of the trigger. You will need to consult whoever created the trigger to have them update it as needed. Microsoft Support is unable to support any custom triggers.