Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics GP (Archived)

The stored procedure rmHistoricalAgedTrialBalance returned the following results DBMS: 2627, Microsoft GP: 0.

Posted on by Microsoft Employee

Customer is getting an error when trying to run the Historial Aged Trial Balance report.  Why would someone get this and how can we fix it?

 

*This post is locked for comments

  • RE: The stored procedure rmHistoricalAgedTrialBalance returned the following results DBMS: 2627, Microsoft GP: 0.

    It appears they may have opened a support ticket to get a 'RM Duplicate Document ' script as the error is pretty much due to data, in this case having duplicate records trying to be inserted into the temporary table, i.e. ##021383F, thus the error message.

    In order to troubleshoot something like this, you'd need to look at what is being inserted into the temporary table and where the data is being pulled from, when it causes the duplicate error message, then find the duplicate record(s) to fix them.

  • Romryan Profile Picture
    Romryan on at
    RE: The stored procedure rmHistoricalAgedTrialBalance returned the following results DBMS: 2627, Microsoft GP: 0.

    LSandhawalia,

    Did you sort this issue and what was the solution. I am encountering this issue.

    Kindly assist.

    RomRyan

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: The stored procedure rmHistoricalAgedTrialBalance returned the following results DBMS: 2627, Microsoft GP: 0.

    I opened a GP case. Thanks for the help though. I appreciate it.

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,730 on at
    RE: The stored procedure rmHistoricalAgedTrialBalance returned the following results DBMS: 2627, Microsoft GP: 0.

    May I add you should run the RM Duplicate Document Script. Dave is correct, there is probably bad data in one or more of your tables that is causing this. I believe you can obtain this script from Microsoft. You may need to open a case for this.

  • Dave Dusek Profile Picture
    Dave Dusek on at
    RE: The stored procedure rmHistoricalAgedTrialBalance returned the following results DBMS: 2627, Microsoft GP: 0.

    When you run the rm hatb, we call a stored proc called 'rmHistoricalAgedTrialBalance'.  The stored proc is not encrypted.  This proc inserts records into temp tables that are then used when the report prints.  The proc is trying to insert a duplicate into one of the temp tables.  You should be able to turn the sql profiler on and run it and let it get the error.  Then look at the profile and find the error.  You should be able to see the record it is failing on.  That might give you some idea of what is going on.  There are three temp tables passed into the 'rmHistoricalAgedTrialBalance' proc.  They are RM HATB Customer TEMP, RM HATB Document TEMP and RM HATB Applied TEMP in that order.  So if you do a dexterity script log, you will see the temp table names passed in and you should be able to figure out what table it's failing on as well.  I guess that's where I would start.  Sounds like a data issue for this customer.

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,269 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,198 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans