Skip to main content

Microsoft Dynamics NAV 2016 - Data Upgrade Error There is no active session within Filter.

Hi All,

In this article we will discuss how to resolve an issue that you may find during Upgrade to Microsoft Dynamics NAV 2016 Upgrade Step 2.


The Error does not allow you to start the Data Upgrade process and the Complete Error Message is -

SessionId : 0
CodeunitId : 104050
FunctionName : CheckPreconditions
CompanyName : <Companyname>
StartTime :
Duration :
State : Failed
Error : There is no Active Session within the filter.
Filters: Server Instance ID: 1024, Session ID: 74



So let's First try to understand why this Error Message -

  • If you know Events and Subscription have been Released with Microsoft Dynamics NAV 2016 which allow you to customize (Extend) Microsoft Dynamics NAV without modifying Standard Code Base.
  • You Might have upgraded the Code Base from previous Version using Events and Subscriptions, which might be subscription Standard Codeunit 1 Events Like Open Company.
  • Your Customer Might be using a Addon / Vertical which have Code using Events and Subscriptions,which might be subscription Standard Codeunit 1 Events Like Open Company.
Codeunit 1 is being called behind the scene, when you start the Data Migration Step 2. So If it have been subscribed and that custom code if end up with an error message then you will receive that error message in the Powershell When you look for upgrade Error.

I don't mean that you cannot (should not) use Events and Subscription. I always use Events and Subscription and suggest everyone to use it.

How to Resolve this Error Message - 
  • From Tools - Debugger, Open Event Subscriptions.

  • Filter For Codeunit 1 - Publisher Object Type - Codeunit, Publisher Object ID - 1.

  • Check Subscribers, if it is a Custom / Addon Object Delete it From Object Designer.
  • From Tools - Run Sync. Schema For All Tables - With Validation.
  • Run Upgrade Step 2 Again.
  • After Upgrade Process is complete, Re-import all objects Removed in Step 3.
Hope this helps you. Stay Connected, Yet More to Come.

Regards,

Comments

Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

RTC Report It is not possible to instantiate the Visual Studio bridge.

Hi all, As a Navision developers I have Multiple Versions of Navision running in single Machine. As discussed Earlier in the post how to run multiple Version of RTC in single machine. So my machine have following details for RTC Versions - NAV 2009 R2    - is installed. NAV 2009 SP1  - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\ NAV 2009         - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 IN\ This approach has been working great for execution of Classic and RTC Clients. However, after installing Dynamics NAV 2009 R2, if i tried to view the Layout for an NAV 2009 SP1 Report i was getting the following error: ---------------------------  Microsoft Dynamics NAV Classic  ---------------------------  It is not possible to instantiate  the Visual Studio bridge.  ---------------------------  OK    --------------------------- After searching for the error i figured out the issue was due to - Design change in NA

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.