Issue with 2011 year end update GP10.0

(0) Share

Report

Posted on by Community Member

We ran the GP 10.0 year end update and it shows that all companies updated successfully. However when we attempt to close 2011 for Payroll we receive and error Invalid Column Nmae EmployerKind. I see that his field should have been added to the UPR10100 and UPR40100 during the DB upgrade. i looked at these two tables and this column is not there although again it shows the correct version 1779, and all cojmpanies have green checks marks in utilities. Any ideas would be greatly appreciated.

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (1)

Richard Wheeler 75,850 Moderator on at

Like (0)

Report

My first suggestion would be to roll your backups back in from before the application of the year end update. Include your DYANAMICS database. It appears the upgrade did indeed miss these table upgrades. Given that it missed these two who knows how many others were missed. Launch GP Utilities again and process the upgrade. Hopefully these will not be missed again. If not, let us know and we will continue on with other suggestions.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks Richard, we are trying the above.

Was this reply helpful? Yes No
Suggested answer

Vinutha Holla 705 on at

Like (0)

Report

The issue above is happening because the UPR10100 and the UPR40100 tables DID NOT UPDATE correctly. These tables MUST be taken through Utilities again. Here are the step:

1. Have all users exit Microsoft Dynamics GP.

2. Delete those two tables ONLY from the DU000030 for that company:

10.0

delete DYNAMICS..DU000030 where fileNumber = 467 and companyid = XXXXX

delete DYNAMICS..DU000030 where fileNumber = 468 and companyid = XXXXX

2010

delete DYNAMICS..DU000030 where fileNumber = 507 and companyid = XXXXX

delete DYNAMICS..DU000030 where fileNumber = 508 and companyid = XXXXX

3. Set the DB_Upgrade back for the update

update DYNAMICS..DB_Upgrade set db_status = 23, db_verOldBuild=XXXXX (Replace with the patch version they updated from)

where PRODID= 0 and db_name = 'XXXXX' (Replace with their company's INTERID)

4. Delete the record in the DU000020 for that company

delete DYNAMICS..DU000020 where PRODID = 0 and companyid =XXXXX (Replace with their companyid)

5. Launch Utilities again and update the company.

6. Verify the Employerkind column is in the UPR10100 and the UPR40100.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thank you Vinutha. We ran the above on the advice of mS, and it did not work either. It is not updating those tables. We first tried to restore all the backups and run ultilities, that did not work. We then ran the above and re-ran utilities and that did not work. We are awaiting a response from MS as this is critical, so if you have any other suggestions, please send along. thanks again.

Was this reply helpful? Yes No
Aaron Donat on at

Like (0)

Report

Carolyn, please share your case number and I will see who has your case and what the status is.

Thanks!

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Aaron,

Thank you for the follow up! Incident number is 112010269823246. Ron Alexander at our organization is actually working on this now and his info is in the case as well.

Thanks again.

Carolyn

Was this reply helpful? Yes No
Aaron Donat on at

Like (0)

Report

Thanks!

Was this reply helpful? Yes No
Verified answer

Aaron Donat on at

Like (0)

Report

To anyone else that reads this post. This GP 10 Year End Update issue is being caused by the three conversion scripts failing to get added to the DU000010 table. With this not happening, it is causing a FALSE/POSTIVE conversion state where the conversion runs fine, the but database model changes have not yet been delivered.

Microsoft is working on identifying this issue and will post something once the issue has been identified.

Thanks!

Was this reply helpful? Yes No
L Vail 65,271 on at

Like (0)

Report

Hi Carolyn,

We exported our data out of the tables that failed to update, used SQL Maintenance to recreate the tables, imported our data back in and filled in the new fields with the appropriate data. For instance, the value in the EmployerKind field was 1 for each of our employees.

It got us where we could close payroll, but who knows what other evil lurks in the tables.

Can anyone give us a list of the UPR Tables that should have been updated so that we can check it against our current table definitions?

Kind regards,

Leslie

Was this reply helpful? Yes No
Aaron Donat on at

Like (0)

Report

Leslie...

I wouldn't recommend that course of action to everyone. The problem here (still trying to confirm) is that the conversion scripts that control the data model changes with the year end update are not getting loaded in teh DU000010 table. At least that was Carolyn's problem today.

I am current working on reproducing the issue and trying to narrow the issue down. But we do not want poeple dumping the data and inserting it back across. We need to get DynUtils to function as it is supposed to.

The tables updated are :

W200006 - Dynamics DB

UPR10100

UPR40100

Thanks!

Was this reply helpful? Yes No