Microsoft Dynamics GP (Archived)

GP 2010 Upgrade: "..did not have the correct structure.." error

(0) Share

Report

Posted on by Dawn Janson

140

Table (COMPANY.dbo.GL10111) did not have the correct structure prior to the conversion of this table.

Table (COMPANY.dbo.GL10110) did not have the correct structure prior to the conversion of this table.

Table (COMPANY.dbo.GL70500) did not have the correct structure prior to the conversion of this table.

Table (COMPANY.dbo.GL70501) did not have the correct structure prior to the conversion of this table.

All the messages have a Status=135 and PRODID = 0 and errornum = 0

These messages appeared in the DU000030 table after I tried to the Upgrade Company step in GP 2010. I installed GP 2010 on a server with SQL 2008 installed. I created backups of the DYNAMICS and COMPANY databases on my current GP 9.00.0385 install on SQL 2005 and restored these databases to the SQL 2008 server. I then ran the Upgrade Company step. It finished but then showed the window with the COMPANY database and a red X next to it indicating an error occurred. Then I ran the SELECT on the DU000030 database and found the errors above. Where do I go from here?

Thanks.

*This post is locked for comments

All responses (10)

Answers (0)

Community Member Microsoft Employee on at

Like (0)

Report

Re: GP 2010 Upgrade: "..did not have the correct structure.." error

Hola, en mi caso me paso igual, pero al ejecutar el script Table_List_Error.sql que viene en el archivo update.pdf me muestra mas detalle sobre el error. Varias columnas de estas tablas mostraban incongruencia con el marco de cuenta. Ejemplo el segmento 1 era de 10 longitud y el campo donde se guarda en la tabla GL10110 era de 7 char. Cambiando la estructura de la tabla de 7 a 10 o 11, y con esto se corrigio. Procedi a realizarlos para las demas tablas. Corri Utilidades y funciono perfecto. En mi caso funciono.

Saludos,

Victor Chen
Jonathan Fear on at

Like (0)

Report

Re: GP 2010 Upgrade: "..did not have the correct structure.." error

Hi Dawn,

Wanted to see if there was anything else you needed assistance with. Please let us know.

Thanks,

Jonathan Fear
Derek Albaugh on at

Like (2)

Report

Re: GP 2010 Upgrade: "..did not have the correct structure.." error

Hello Dawn,

Normally when we see these type of errors, it is because the account framework settings (which are held in the DYNAMICS database's SY003001 and SY00302 tables did not synch with the dictionary files, which hold all the scripts that Utilities uses to create new tables, views, procedures, etc.

The GL10110, GL10111, GL70500 and GL70501 tables, among others, get setup with a number of columns to correspond with the number of segments and those segment lengths that you have setup for the account framework.

If the dictionary files do not synch with the account framework, they will default to a number of segments of 5 and a segment length of 9.

When this happens, during the upgrade, Utilities will rename the GL10110 table to G10110L and then use the scripts I mentioned to create the GL10110 table at the new version you're upgrading to. If the new table is not created at the correct structure (number and length of segments), you'll get these type of upgrade errors when Utilities attempts to move the data from the original G10110L table to the new GL10110 table.

What we'd want to do at this point, if you're still at this point in the upgrade, is the following:

1. For the Dex.ini file, change SYNCHRONIZE=FALSE to SYNCHRONIZE=TRUE, then close and save changes to the Dex.ini. This file is held in the 'Data' folder for GP 10.0 and GP 2010.

2. Run this script to force the failed tables through the upgrade process again:

Delete DYNAMICS..DU000030 where Status <> 0 and Status <> 15

3. In the DYNAMICS..DB_Upgrade table, make sure the db_status column shows 23 for the company database failing on these tables.

4. Launch GP Utilities which should synchronize the account framework and then attempt to upgrade these failed tables again, then go on from there with the upgrade.

If the upgrade fails on these tables again, go back into the Dex.ini and verify that SYNCHRONIZE=FALSE, meaning the synchronization took place. If it still shows as TRUE, then the Dynamics GP code is probably bad and I would recommend either using different code or uninstalling/reinstalling.

If SYNCHRONIZE does show as FALSE, but the same tables are failing, then we'd have to see the results of the following scripts:

Select * from DYNAMICS..SY003001

Select * from DYNAMICS..SY00302

sp_help GL10110

sp_help GL10111

sp_help GL70500

sp_help GL70501

If the tables are incorrect, they would have to be fixed before going through the upgrade process.

One other note, we never want to drop and re-create any tables in Dynamics GP where we can lose the data in the tables. If the tables are empty, then this would be an option, but otherwise, we do not want to risk losing data. The only exception are Report Option tables, ending in **70500, as you will only lose report option information.

Thank you
Suggested answer

Dawn Janson 140 on at

Like (0)

Report

Re: GP 2010 Upgrade: "..did not have the correct structure.." error

Sorry for the late response - was sick a few days and then wanted to be sure the information I got from MS did actually fix my problem.

About the same time you sent the reply above, I found a section in the upgrade documentation that specifically discussed these 4 tables. While there was no reference to the actual error I received, I assumed it was related. At that point, I contacted MS at the phone number provided in the documentation and when I finally got a rep who knew about the GP 2010 upgrade, she knew exactly what I had done. While I had run the SQL statements that MS provided to CHECK these tables before doing the upgrade, the important step that I missed was:

You must have your DYNAMICS and COMPANY databases ON the server before running the WS Utilities.

While this sounds like it should the normal situation, I was INSTALLING GP 2010 on a brand new SQL 2008 server and was told by my local GP partner that in the past he had always let GP recreate the DYNAMICS database on the new server, THEN restored the DYNAMICS & COMPANY databases to perform the Upgrade Company task. You CANNOT do this with GP 2010. If you do, your account segment/framework information in your restored COMPANY database will not be recognized.

To fix this, MS sent me a couple of SQL statements to run, a change to a setting in Dex.ini, and then I restored my DYNAMICS/COMPANY databases, and reran the Upgrade Company task. The errors did not appear and it looks like the data is correct. So I guess the short answer to this problem is that you need to contact MS support. And yes, it cost me a support incident.
Community Member Microsoft Employee on at

Like (0)

Report

Re: GP 2010 Upgrade: "..did not have the correct structure.." error

I also did some research on the table affected. The GL10110 and 10111 are the GL Summary tables, the GL70500 and GL70501 are the report options tables. If following the steps above do not work - in your version 9 you could back up the database and then use the GP sql utilities to drop and recreate these tables. The report options would need to be re-entered by hand, but the summary information would be recreated when Reconcile-Financial are run. Did you run checklinks on any of your files prior to the upgrade? If so, did you receive any errors on the financial tables?
Community Member Microsoft Employee on at

Like (0)

Report

Re: GP 2010 Upgrade: "..did not have the correct structure.." error

You should run the capture logins script on the old server saving the results to a script like it states. In SQL server 2008, delete the Dynamics and Company databases. Then run the script that you created - you may get some errors on some of the lines, but all user logins will be recreated. Restore both the Dynamics and Company databases from SQL2005 to the SQL2008 instance by follow the instructions in the KB article. Once completed, open the GP2010 utilities. It will then read the restored Dynamics database/company databases(which are still at version 9) and will run the upgrade again. It really doesn't matter the order that you install the programs on the server - just the information to make the databases compatible & make sure to run all of the scripts.
Dawn Janson 140 on at

Like (0)

Report

Re: GP 2010 Upgrade: "..did not have the correct structure.." error

I have Customer Source and found a write up about following 878449 and I checked it out before posting out here ... BUT it's too late for me to follow these instructions. These instructions assume you are putting your DYNAMICS & COMPANY databases on the server BEFORE you install GP 2010. I need instructions that tell me how to either 1) completely uninstall GP 2010 on the server so I can put the databases on SQL 2008 BEFORE I install GP 2010 and then try to follow the exact order of 878449 instructions, OR 2) how to get the already installed GP 2010 software on the server to accept the restored DYNAMICS & COMPANY databases and correctly upgrade them.

In the DBUpgrade table of the DYNAMICS database that is currently installed on the SQL 2008/GP 2010, the version it thinks we are running on is 11.00.1524 for GP (product ID 0).
Community Member Microsoft Employee on at

Like (0)

Report

Re: GP 2010 Upgrade: "..did not have the correct structure.." error

Do you have access to customersource/partnersource? If so - follow the steps for KB article 878449. The account framework is stored in the DYNAMICS database and used in the company database. Once you have restored both of these databases everything should work correctly.

Also, make sure that your GP2010 is at Version 11.00.1307 or later.
Dawn Janson 140 on at

Like (0)

Report

Re: GP 2010 Upgrade: "..did not have the correct structure.." error

I installed GP 2010 SP 1 and let it create the DYNAMICS database on the new server. I then restored the DYNAMICS and COMPANY databases from the SQL 2005 backup files to SQL 2008 and set the compatibility on both to SQL 2008 and made sure the owner was DYNSA. At this point I started the Upgrade COmpany step. I'm wondering since I let it create the DYNAMICS database (as was suggested by another source) that it used the default account framework on that new DYNAMICS database. WHICH should not have been a problem if the account info is all stored in the databases, but there must be some place OTHER than the DYNAMICS database that stores info on the Account framework (registry, .ini, some other file?) and now it's all confused. At least that's what I'm guessing these cryptic messages are telling me.
Community Member Microsoft Employee on at

Like (0)

Report

Re: GP 2010 Upgrade: "..did not have the correct structure.." error

Did you follow the steps for moving databases from SQL 2005 to SQL 2008 - mainly setting the database options to SQL 2008 compatibiey? Did you install the latest service pack for GP 2010?