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
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
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.
LSandhawalia,
Did you sort this issue and what was the solution. I am encountering this issue.
Kindly assist.
RomRyan
I opened a GP case. Thanks for the help though. I appreciate it.
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.
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.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,269 Super User 2024 Season 2
Martin Dráb 230,198 Most Valuable Professional
nmaenpaa 101,156