You’re offline. This is a read only version of the page.
Hi Expert,
I am upgrading from NAV2013 to NAV2018, when i am doing Data Upgrade i am getting the below error
The function UpdateGeneralLedgerSetup in the company initialization codeunit 104000 in company Chicago Real Estate has failed due to the following error: 'The server
stopped the session (ID: 61) because of a stop session request.'.
The function UpdateGeneralLedgerSetup in the company initialization codeunit 104000 in company Chicago Real Estate has failed due to the following error: 'The server
stopped the session (ID: 61) because of a stop session request.'.
Please help me, how to resolve the issues
*This post is locked for comments
Contacting Microsoft support regarding this will not be of much help - both these versions are out of main stream support.
So I would rather suggest update to a newer version.
Upgrading data from NAV2013 to NAV2018 can sometimes result in errors due to differences in the data structures and schema between the two versions. Here are some steps you can take to troubleshoot the error:
Review the error message: Look at the error message and try to determine what the underlying issue might be. Often, the error message will provide some clues as to what is causing the problem.
Check the upgrade log: The upgrade log can provide more information on the specific step in the upgrade process where the error occurred. Review the log to see if there are any additional details that can help you pinpoint the issue.
Check for data inconsistencies: Run data consistency checks to identify any inconsistencies or data integrity issues in the NAV2013 data. Fixing these issues may resolve the upgrade error.
Analyze the data: Analyze the data to see if there are any significant differences between the NAV2013 and NAV2018 versions. Look for differences in field lengths, data types, and relationships between tables.
Check for missing dependencies: Check to see if there are any missing dependencies between tables, fields, or other objects. These can cause upgrade errors if they are not resolved prior to the upgrade.
Contact Microsoft support: If you are still unable to resolve the error, consider contacting Microsoft support for assistance. They can provide more specialized guidance and support for upgrading from NAV2013 to NAV2018.
Overall, upgrading data from NAV2013 to NAV2018 can be a complex process, and errors can occur due to a variety of factors. By following these steps and working with the appropriate support resources, you should be able to successfully upgrade your data to the newer version.
I would suggest refer this source further.
Thank you.
Getting this error,
SessionId : 91
CodeunitId : 104000
FunctionName : UpdateJobPlanningLinePlanningDueDate
CompanyName : CRONUS India Ltd.
StartTime : 24-08-2022 14:21:47
Duration :
State : FailedPendingResume
Error : The function UpdateJobPlanningLinePlanningDueDate in the company initialisation codeunit 104000 in
company CRONUS India Ltd. has failed due to the following error: 'Function ID 125 was called. The
object with ID 9998 does not have a member with that ID.'.
ExecutionSourceId : 00000000-0000-0000-0000-000000000000
PostUpgrade : False
sure, before you start make sur the active sessions are all killed you can restart the service, and / Or simply empty the table of the server instance at all:
DELETE FROM [My NAV Database Name].[dbo].[Server Instance]
IT is all about making sure no active sessions are there, sometimes restarting the service is enough.
thanks,
Rahman
Thanks Rahaman, but when debug before start Data upgrade i am getting below error,
can you please help me? working on NAV2013 to NAV2018
---------------------------
Microsoft Dynamics NAV Development Environment
---------------------------
Cannot start the data upgrade process because there are active sessions to the tenant database. You must make sure that there are no active sessions before you continue the upgrade process.
---------------------------
OK
---------------------------
First of all, try the data Upgrade in the DEV Client, use the serial mode and not parallel, and before you start data updgrade, use the debugger, and it should point you directly where the issue is coming.
I hope this helps.
Rahman
Increment SQL command timeout in administration console
Is there anything in the Application Event Log on the NAV Server Service machine related to this? Often when this happens it is some critical error caused by something else.
#1
Sohail Ahmed
2
#1
mmv
2
#1
Amol Salvi
2
Share
Report
All responses (
Answers (
