Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / GP2016 to GP2016R2 upg...
Microsoft Dynamics GP (Archived)

GP2016 to GP2016R2 upgrade error on

(0) ShareShare
ReportReport
Posted on by sandipdjadhav 18,265

Hello,

While upgrading GP2016 to GP2016R2, getting error on following. When run below statement it gives error "Column name or number of supplied values does not match table definition."  Any help on this will be highly appreciable.

CREATE PROCEDURE SVC_Create_IV_Serial  @SerialNumber char(21),  @ItemNumber char(31),  @LocationCode char(15),  @unitcost numeric(19,5),  @Sold tinyint As declare @dateseq integer if not exists(select * from IV00200 where ITEMNMBR = @ItemNumber and SERLNMBR =@SerialNumber) begin select @dateseq = (select Max(DTSEQNUM) from IV00200 where ITEMNMBR = @ItemNumber and LOCNCODE = @LocationCode) + 1 select @dateseq  = isnull(@dateseq,1) insert IV00200  select @ItemNumber, @LocationCode, CONVERT(varchar(10),GETDATE(),102) + ' 00:00:00', @dateseq, @SerialNumber, '', '', @unitcost, 1, '', 0, @Sold, 1, '' end    

Thanks much

Sandip

*This post is locked for comments

  • himanshu@isystechworks.com Profile Picture
    himanshu@isystechwo... 5 on at
    RE: GP2016 to GP2016R2 upgrade error on

    Hi Sandeep,

    I am doing the up-gradation from GP 2016 R2 to GP 2018 R2 and facing the same error.

    Did you get the answer of your query.

    Thanks.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: GP2016 to GP2016R2 upgrade error on

    How are you upgrading, in place GP upgrade or DB move to newer sql server and GP upgrade on the new sql server?

  • Derek Albaugh Profile Picture
    Derek Albaugh on at
    RE: GP2016 to GP2016R2 upgrade error on

    Usually this type of error message is referencing the table having a different amount of columns then this script, which is attempting to create this stored procedure, is expecting the table to have.

    We see this sometimes occur if the DU000030 table had records in it from a prior upgrade, which can cause tables to get skipped during the upgrade.

    Id' recommend restoring back to the prior version and making sure the DU000030 table in the DYNAMICS/system database is empty before starting the upgrade again, otherwise, if you can't restore everything back, restore only this one company database failing with this error, and use KB 920900 to reset the tables, which will include truncating the DU000030 table for this one company database.

    Thanks

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans