You’re offline. This is a read only version of the page.
Have now tried this a half dozen time and continue to get the same error message which I cannot resolve.
Two companies involved and 1 goes through fine - no errors, etc. The 2nd one (and, unfortunately the main one) fails in Utilities with the message that it is having a problem with the stored procedure dbo.glpcreatevoidrecord, and when you click ok it tells me that ERROR [Microsoft][SQL Native Client][SQL Server]Invalid column name 'VOIDED'. This all apparently pertains to GL30000 which had a column named VOIDED added for release 9 (but wasn't in 7.5). I am at a loss as to hbow to fix this. Anybody got any ideas - thank you.
*This post is locked for comments
Bill, did you ever get this resolved?
If you are still looking for assistance let us know.
Richard has given you a great solution in the dumping the 'non-converted' GP30000 to a temp table and using the GP Application, have it drop and recreate the GP30000 table.
Once in a while I have encountered this type of an issue and this is the only way I have been able to solve it.
Has worked for others, should work for you as well.
Hi Bill,
You can call me on Skype. My id is Evincible.
Thanks
Shafiq
You may be bumping into a trigger on this or some other table. Can you run SQL Profiler while the upgrade occurs? I would also try exporting the data of the GP30000 to a temp table and then using SQL Maintenance in GP drop and recreate this table and any associated stored procedures. Once a fresh empty copy of this table exists, create a script to insert the copied data back into the GL30000. There is a difference in this table structure somewhere. By dropping and recreating it you will eliminate the difference. I assume you have a sandbox to play in and have backups in place.
I have now checked the raw 7.5 sql data and both companies have identical table structure for GL30000, yet one updated correctly and other did not. Other than manually restructuring the table that didn't update correctly is there anything else that we can try? What process in the upgrade actually does the table update? On the utilities screen this appears to happen long before the stored procedures are updated, so why doesn't it do the update? Baffling, really
Bill, are you familiar with using SQL Server Management Studio(SSMS)? Does you current installation work fine using GP 7.5? If so, this may be the only issue you have. There may be others but you can try this. It sounds like somehow during previous upgrade that did not upgrade the GP 30000 table. I would start by going into the company that works in SSMS and look at the table structure of GL30000 in GP 7.5 and then compare it with what you see in the company that does not work. You could then change the structure using SSMS or through a SQL alter table script. The goal is to get all the tables structures in 7.5 in both companies to be the same prior to the upgrade.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (