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

(0) Share

Report

Posted on by Community Member

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

I have the same question (0)

All responses (5)

Answers (0)

Dave Dusek on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Richard Wheeler 75,850 Moderator on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

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

Was this reply helpful? Yes No
Romryan on at

Like (0)

Report

LSandhawalia,

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

Kindly assist.

RomRyan

Was this reply helpful? Yes No
Derek Albaugh on at

Like (0)

Report

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.

Was this reply helpful? Yes No