web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

GP2010 SP3 company upgrade error : SynchronizeTableData() of form duSQLAccountSync

(0) ShareShare
ReportReport
Posted on by 28,058 Moderator

Hi Everyone,

Has anyone heard about any issue during the company upgrade process with the not too famous error message "The stored procedure SynchronizeTableData() of form duSQLAccountSynch : 27 Pass Through SQL returned the following results: DBMS:50000, MS Dynamics GP: 0"

It seems to affect the GP dictionnary 0 and arise on the table APR_DIA40200... which doesn't exist. However there is a table APR_DIA40200_T that seems to be a TEMP Table just created by the upgrade process... Enabling the SQL DEX log in the DEX.ini reveals some other interesting details :

/*  Date: 07/09/2012  Time: 13:34:28
stmt(22752888):*/
/*Begin_APR_DIA40200_T*/
if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[APR_DIA40200_T]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)
drop table [dbo].[APR_DIA40200_T]
CREATE TABLE [dbo].[APR_DIA40200_T](
 [SRCECODE] [char](7) NOT NULL,
 [SRCDSCR] [char](51) NOT NULL,
 [DEX_ROW_ID] [int] IDENTITY(1,1) NOT NULL,
 CONSTRAINT [PKAPR_DIA40200_T] PRIMARY KEY NONCLUSTERED
(
 [SRCECODE]
) ON [PRIMARY]
) ON [PRIMARY]

setuser
EXEC sp_bindefault N'[dbo].[GPS_CHAR]', N'[dbo].[APR_DIA40200_T].[SRCECODE]'
EXEC sp_bindefault N'[dbo].[GPS_CHAR]', N'[dbo].[APR_DIA40200_T].[SRCDSCR]'
setuser

GRANT  SELECT ,  UPDATE ,  INSERT ,  DELETE  ON [dbo].[APR_DIA40200_T]  TO [DYNGRP]

/*End_APR_DIA40200_T*/

Furthermore, when the script tries to read some data input from a temp file, it fails to insert into the APR_DIA40200 table that does not exist in my case...


/*  Date: 07/09/2012  Time: 13:34:28
SQLSTATE:(00000) Native Err:(15511) status(0):*/
SWSTATUS DUMP*/

/*  Date: 07/09/2012  Time: 13:34:28
stmt(22752888):*/
BULK INSERT [FTW]..[APR_DIA40200_T] FROM 'C:\Program Files\Microsoft Dynamics\GP2010\DATA\Temp\APR_DIA40200.out' WITH (CODEPAGE = 'ACP', KEEPNULLS, FIELDTERMINATOR = '||', ROWTERMINATOR = '#EOR#\n')

/*  Date: 07/09/2012  Time: 13:34:28
stmt(22752888):*/
exec duAN_SynchronizeTable 'APR_DIA40200','APR_DIA40200_T','D'
/*
/*  Date: 07/09/2012  Time: 13:34:28
SQLSTATE:(01000) Native Err:(50000) stmt(22752888):*/
[Microsoft][SQL Server Native Client 10.0][SQL Server]Table specified not found*/
/*
/*  Date: 07/09/2012  Time: 13:34:28
SQLSTATE:(00000) Native Err:(50000) stmt(22752888):*/
*/

Any hints ?

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Beat Bucher  GP Geek  GPUG All Star Profile Picture
    28,058 Moderator on at

    OK,

    for those who are interested in the root cause of this Synch Error message... most of the time it happens because a table that the upgrade process wants to populate doesn't exist. Thanks to the SQL DEX trace log, I was able to figure out the error message.

    So what now ? after looking at the Excel reference document about the GP2010 table definitions, I spoted a few dictionnaries in my DYNAMICS.SET file that were probably added for some testing but for which we do not have a valid license in the production... removing those entries seems to have solved the issue.

    The table that was causing the issue APR_DIA40200 was part of the HRM Self Service Suite. There were also a couple of other modules that I removed, knowing they had nothing to do in my startup file.

    One thing to learn from this : when you do upgrade in a test environment, always take a fresh copy of your production DB's... never assume it's the same state :-). Tinkering in a test bed can lead to several discrepancies between the real prod state and the test bed system.

    Since my company was half-way upgraded, removing the faulty objects didn't get rid of the error message, because it was trying to catch up where it stalled. You've to go into the DB_Upgrade table in the DYNAMICS DB and remove for the faulty company the lines with the module numbers that are not registered to your production company. The TWO company is such an example where all the modules are registered, because it's a demo company... Make sure that only what's in your DYNAMICS.SET is listed in the DB_Ugrade table for the selected company to upgrade.

  • Community Member Profile Picture
    on at

    In my case it was due to corruption in the DYNAMICS database during migration to a new server.  Running DBCC CHECKTABLE (tablename) showed corruption.  If you're not sure of the table (visible just above the progress bar) or if you clicked OK and missed the table name, a full DBCC CHECKDB on the database will show if the database is okay.

  • TSMurphy Profile Picture
    372 on at

    If you find yourself here after searching the internet and doing a GP2015 or GP2015r2 upgrade.  Reference this link from the Dynamics team for troubleshooting:  community.dynamics.com/.../draft-known-upgrade-issues-when-upgrading-to-microsoft-dynamics-gp-2015-r2

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Community Member Profile Picture

Community Member 2

#2
Victoria Yudin Profile Picture

Victoria Yudin 1

#2
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans