Error while Upgrading 7.6 to 2007A - duplicate key in object 'dbo.NNM1'

Question

Hello,
We are trying to upgrade our client from SBO 7.6 SP01 to SBO 2007 SP01 version (It is supported by sap to skip 2004 version)
Upgrade ends with the following error:
[Microsoft][SQL Server Native Client 10.0][SQL Server]The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.NNM1' and the index name 'NNM1_PRIMARY'. The duplicate key value is (0).
I can see with profiler, that upgrader is trying to do the following query:
ALTER TABLE [dbo].[NNM1]  ADD CONSTRAINT [NNM1_PRIMARY] PRIMARY KEY (Series)
As I can see, in SBO 7.6 nnm1 table numbering was different than in the new versions (for example 2007A) u2013
In 7.6 ver. Numbering in  u201Cseriesu201D column was starting from 0 within certain object, hereu2019s example:
<Objectcode>     <series>         <seriesname>
___17     __________0___     sales_order_series1
___17          __________1___     sales_order_series2
___17          __________2          ___sales_order_series3
___15          __________0          ___delivery_series1
___15          __________1          ___selivery_series2
In SAP 2007A version column series has unique values so for above example it should be:
<Objectcode>     <series>         <seriesname>
___17          __________0___          sales_order_series1
___17          __________1___          sales_order_series2
___17          __________2___          sales_order_series3
___15          __________3___          delivery_series1
___15          __________4___          selivery_series2
Anyone had that problem while upgrading from 7.6 to 2007A (or maybe from 7.6 to 2004?).

Answer 1

Dear Daniel,
Reported upgrade issue needs a further investigation therefore please log a support message with a component SBO-BC-UPG via the Service Market Place.
Please also attach 'UpgradeLog' files to the message. You will find the log files in the same directory as your B1 client (b1loggerPidxxxx_xxxxxxxxxxxxxx.txt; B1UpgradePidxxxx_xxxxxxxxxxxxxx.txt)
Regards,
Ladislav Meszaros
SAP Business One Forum Team