Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

A save operation on table 'PM_Vendor_MSTR' (45)

(0) ShareShare
ReportReport
Posted on by Microsoft Employee

Hello All! when I alter a record for a vendor and hit save, I get the following message. I dug around and it seems like it has something to do with the "taVendorInsert" trigger. when I disable the trigger it runs fine, but when I enable the trigger I get the message. any ideas? the KB article said that it was an PSTL issue and I should hit the "register" button on PSTL, but I don't have a PSTL button.  I have a "rebuild proc" but I don't want to randomly hit that button. any help would be appreciated. Thank you. i'm using GP 2013 just did the R2 update as well!

*This post is locked for comments

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: A save operation on table 'PM_Vendor_MSTR' (45)

    if you have the PSTL tool, it's an option from that tool. few things to keep in mind before doing it. make sure you have a solid backup incase you need to revert and also make sure no on is using GP at that time. good luck! you can always google "how to rebuild procs using pstl"

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: A save operation on table 'PM_Vendor_MSTR' (45)

    Hi. Please tell us with more detail how you fix it. I am facing the same error message. How do I rebuild proc?

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: A save operation on table 'PM_Vendor_MSTR' (45)

    i had to rebuild the procs for all the companies that rigger was connected to and it worked!! i followed herry's advice!

  • RE: A save operation on table 'PM_Vendor_MSTR' (45)

    Hello Adal,

    This is mentioned in KB 2564866 and is sometimes caused by a trigger on the PM00200 table that is damaged or outdated.

    It can also be caused by this 'taVendorInsert' trigger, which is a part of the Professional Services Tools Library (PSTL), which you may just need to trigger PSTL to re-create its procedures.

    Thanks,

  • Verified answer
    Redbeard Profile Picture
    Redbeard 12,931 on at
    RE: A save operation on table 'PM_Vendor_MSTR' (45)

    Adal,

    Installing PSTL (Professional Service Tools Library) at any workstation would have updated the database, which is likely what caused this error.  Rebuilding the Procs should fix the error.  Make a back up, prior to running this process.  

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Vahid Ghafarpour – Community Spotlight

We are excited to recognize Vahid Ghafarpour as our February 2025 Community…

Tip: Become a User Group leader!

Join the ranks of valued community UG leaders

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,516 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,399 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans