web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / The stored procedure s...
Microsoft Dynamics GP (Archived)

The stored procedure smGetNextNoteIndex retured the following result : DBMS : 2812, Dynamics dic : 0

(0) ShareShare
ReportReport
Posted on by GovindDevda 617

Hi All ,

Actually when i lost focus on vendor master's VendorID field  or other form then show a popup message

"The stored procedure smGetNextNoteIndex retured the following result : DBMS : 2812, Dynamics dic : 0"

please any one have a idea about this problem how we solve it.?

Thanks & Regards

Govind Devda

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Tim Foster Profile Picture
    Tim Foster 8,515 on at
    RE: The stored procedure smGetNextNoteIndex retured the following result : DBMS : 2812, Dynamics dic : 0

    According to the error message, the Stored Procedure smGetNextNoteIndex does not exist.

    From SQL BOL:

    Error 2812

    Severity Level 16

    Message Text

    Could not find stored procedure

    Check in SQL to see if it's still there.  If it is, check permissions and make sure [DYNGRP] has Execute permission.

  • Verified answer
    David Musgrave MVP GPUG All Star Legend Moderator Profile Picture
    David Musgrave MVP ... 14,069 Most Valuable Professional on at
    RE: The stored procedure smGetNextNoteIndex retured the following result : DBMS : 2812, Dynamics dic : 0

    Hi Govind

    Search SQL Error 2812 on the web gives:

    Error 2812

    Severity Level 16

    Message Text

    Could not find stored procedure '%.*ls'.

    technet.microsoft.com/.../aa258751%28v=sql.80%29.aspx;MSPPError=-2147217396

    Looking at the source for smGetNextNoteIndex in the system database, it only contains an update statement on the SY01500 table in a transaction.

    So... I suspect you have a trigger on the SY01500 table which is attempting to call a non-existent stored procedure.

    Using SQL Server Management Studio, find the SY01500 table in System database and expand it and look under Triggers.

    There are no triggers for that table by default. So if you have any, right click on them and disable them.

    If the error goes away, you have identified the cause. You will then need to contact whoever added the triggers and get them to fix their code.

    David

    PS: The reason I think it is this situation is because the error is returned by smGetNextNoteIndex which is different to not finding smGetNextNoteIndex. But do check if smGetNextNoteIndex is there under Programmability >> Stored Procedures. If it is missing run DBMaintenance.exe in the GP Application folder to fix.

  • GovindDevda Profile Picture
    GovindDevda 617 on at
    RE: The stored procedure smGetNextNoteIndex retured the following result : DBMS : 2812, Dynamics dic : 0

    Thanks David & Tim for guide me, problem is solve it.

    Thanks & Regards

    Govind Devda

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

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans