Share
ReportWe updated our GP with the year end update.
Getting the following error while trying to update 1099 amounts.
Any help is appreciated.
Thank you.
Categories:
You’re offline. This is a read only version of the page.
36
We updated our GP with the year end update.
Getting the following error while trying to update 1099 amounts.
Any help is appreciated.
Thank you.
Our GP partner helped us troubleshoot the error. This was stemming from the GP forms and reports directories which were corrupted after the year end update. These had to be recreated locally and then updated on the shared drive since all the clients were looking at the shared drive on the server.
Thanks Derek.
I do see the "VENDDBA" column in PM00200. I even tried the Dexsql.log but it doesn't show the error or I do not know how to read that log as it is quite lengthy.
We do not have any third party software as we print our 1099's directly from GP.
I will have to contact a GP consultant to get this fixed.
Having said that, this year's update patch sent out by Microsoft has had quite a few bugs. We have had to restore our report dictionary as it was corrupt and would not print checks correctly. A lot of time goes into all of this and we cannot kick users out during the day to perform all of this.
I hope Microsoft addresses these issues.
Hiren
I've seen the “Unhandled script exception" / "SCRIPTS – data area” / “Exception_Class_Script_Addressing" errors show after an upgrade to GP 18.2/18.3 due to the PM00200 table not receiving the new VENDDBA column it should have, so you can rule that out, running this script against each company if you are currently on 18.2 or later for GP:
Select VENDDBA, * from PM00200
Otherwise, does this error show anything more below what the screenshot is showing? Dexsql.log?
If you have third parties or customizations, you can try renaming the GP directory after getting all users out, and then run a Repair against that GP install, which will completely re-create the GP directory without third parties nor customizations, even without modified forms/reports dictionary files, then login to the 'new' GP directory and see if you can re-create this message.
If you can't, then it may be a third party or customization that is causing the issue and you'd need to add them back to this 'new' install, one by one, testing after each one, until you identify the cause.
Let us know what you find out...
Thanks
#1
André Arnaud de Cal...
291,391
Super User 2024 Season 2
#2
Martin Dráb
230,445
Most Valuable Professional
#3
nmaenpaa
101,156
All responses (
Answers (
