Hello
We are currently updating our NAV 2015 to NAV 2018 (CH).
I am stuck at task 14 (https://docs.microsoft.com/en-us/dynamics-nav/upgrading-the-data) where I have to run the data upgrade
I get the following error:
When I check the suggested Powershell Command, I can see several error messages called:
Error : Function 'UpdateSalesIcons' in the upgrade codeunit '104000' has failed because of the following
error: 'The server stopped the session (ID: 455) because of a stop session request.'.
There are some more errors with this message. One complete session message looks like that:
SessionId : 449
CodeunitId : 104000
FunctionName : CreateJobWebServices
CompanyName : COMPANY
StartTime : 20.04.2018 19:04:26
Duration :
State : FailedPendingResume
Error : The function CreateJobWebServices in the company initialization codeunit 104000 in company
COMPANY has failed due to the following error: 'The server stopped the session
(ID: 449) because of a stop session request.'.
ExecutionSourceId : 00000000-0000-0000-0000-000000000000
PostUpgrade : False
I imported all the modified objects and the Upgrade8001100.FOB file. I already restarted the NAV Instances, but no luck.
Did I miss something?
Thank you very much.
Best regards
Raphael
*This post is locked for comments
Yes: when you set a table with data x company to NO, in nav DB is created 1 table common fo all company. When you insert records in this table you can't reset property datapercompany to yes. You've to delete all records.. You can use T_new for saving & restoring data (many upgrade process use this method)
Maybe my question should have been, does it make a difference if the new table has data per company set to yes since the original table has common data.
But I understand the logic behind it. Basically, the goal is to set back those 2 tables has data per company instead of global, correct?
Because T_NEW has data per company YES
at step #2, why for each company since the data is global and not per company?
Backup db.
Before Start Upgrade
1) clone the T_X table in T_NEW 50000-99999 range (data per company yes)
2) for each company copy data from T_X in T_NEW
3) Delete all Data from Original T_X table
4) Change T_X table property to data per company yes
5) For each company copy data from T_NEW T_X
Start Upgrade
It's better to sinch tables (without setting data x company NO)
I'm having the same issue during our upgrade from 2013R2 to 2018.
The database has multiple companies and the item category and product group tables have been modified to have their data per Company set to NO
It fails on the first Company, running the data upgrade in serial mode.
It's failing on
The function UpdateItem in the company initialization codeunit 104000 in company ABC has failed due to the following error: 'Unable to upgrade Product Group (MEDICAL,CONSUMABLE) because of Code duplication. Please make sure that this product group has a unique Code, and retry the upgrade.'..
product code CONSUMABLE only exists for item category code MEDICAL, it's not duplicated in any other item category
What can I do?
It worked now, thank you very much.
(I had to delete the failing company as we do not need it anymore)
Alright, I will check that, thank you.
(I made another mistake, so I'll start over)
Seems a non standard table... If you have only that record and isn't used in item table (Table 27 - item category field is related to this table), delete the record and restart upgrade
Hello
There are 6 companies in the db. The item category table is empty for 5 companies, but in the failing company, there is the following line:
timestamp Code Parent Category Description Indentation Presentation Order Has Children Last Modified Date Time Id
0x0000000001CD5076 0 0 0 1753-01-01 00:00:00.000 00000000-0000-0000-0000-000000000000
The columns are the same for every company.
May I just delete this item category?
André Arnaud de Cal...
291,965
Super User 2025 Season 1
Martin Dráb
230,817
Most Valuable Professional
nmaenpaa
101,156