Friday, 19 June 2015
Tuesday, 12 May 2015
Friday, 24 April 2015
Exception Info: Microsoft.Dynamics.Nav.Types.Exceptions.NavNCLFieldNotFoundException
Some times client will crash when we convert from NAV2009 R2 to NAV2013.
We may get the following error when we check the Event Viewer
Application: Microsoft.Dynamics.Nav.Client.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Microsoft.Dynamics.Nav.Types.Exceptions.NavNCLFieldNotFoundException
Stack:
at Microsoft.Dynamics.Nav.Client.FormBuilder.BuilderSessionInitializer.Initialize()
at Microsoft.Dynamics.Framework.UI.Builder.Initialize()
at Microsoft.Dynamics.Framework.UI.UISession.Initialize()
at Microsoft.Dynamics.Nav.Client.WinClient.NavWinFormsClientSession.InitializeUISession()
at Microsoft.Dynamics.Framework.UI.Windows.ClientSessionBase.SetupSessions()
at Microsoft.Dynamics.Framework.UI.Windows.ClientSessionBase.InitCore()
at Microsoft.Dynamics.Nav.Client.WinClient.NavWinFormsClientSession.InitCore()
at Microsoft.Dynamics.Framework.UI.ClientSessionCore.Init()
at Microsoft.Dynamics.Framework.UI.Windows.ClientSessionBase.Run()
at Microsoft.Dynamics.Nav.Client.WinClient.NavClientErrorHandler.ExecuteAndCatchExceptions(System.Func`1<Int32>)
at Microsoft.Dynamics.Nav.Client.WinClient.ExceptionHandler.DoExecute(System.Func`1<Int32>)
at Microsoft.Dynamics.Nav.Client.WinClient.StartWinFormsClient.RunCore()
at Microsoft.Dynamics.Nav.Client.WinClient.StartWinFormsClient.Run(Boolean)
at Microsoft.Dynamics.Nav.Client.WinClient.StartWinFormsClient.RunAndDispose()
at Microsoft.Dynamics.Nav.Client.Program.ExecuteNormally(System.Func`1<Int32>)
at Microsoft.Dynamics.Nav.Client.Program.Main(System.String[])
Solution :
When we get this error ,that means our all the tables are not compiled .So we need to recompile all the objects.Tables those are having data should be compiled.
Wednesday, 22 April 2015
Tip : How to import only objects from Navision backup (FBK) files
We can import objects directly from NAV backup FBK file without restore
If you have a Navision backup (the FBK file) with the application objects included, then you can import these objects directly without restoring the whole backup.
In the Object designer choose import and select the .FBK file instead of the suggested .FOB or .TXT.
Navision will then import only the objects.
NAV UPGRADE Error : Invalid object name 'XXXX.dbo.company$xxxxx' The table for which the above error is occurring does not exists in NAV database or could not be found in SQL
We get the below error while converting the database from NAV2009 to NAV2013.
Invalid object name 'XXXX.dbo.company$xxxxx' The table for which the above error is occurring does not exists in NAV database or could not be found in SQL
Solution :
Object Metadata must have Table Reference in NAV2009 which table object does not exists in the current database.
We have to remove the record and start upgrade again from the beginning.
Invalid object name 'XXXX.dbo.company$xxxxx' The table for which the above error is occurring does not exists in NAV database or could not be found in SQL
Solution :
Object Metadata must have Table Reference in NAV2009 which table object does not exists in the current database.
We have to remove the record and start upgrade again from the beginning.
NAV Upgrade Error : Login failed error while upgrading from NAV2009 to NAV2015
The following error occur when we try to open the NAV2009 database with NAV2013 client in upgrade process and you can’t open the database in NAV2009 anymore, can’t fix the error and can’t continue further with upgrade process.
---------------------------
Microsoft Dynamics NAV Development Environment
---------------------------
The following SQL Server error or errors occurred:
18456,"28000",[Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'xxxxx'.
4060,"42000",[Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot open database "xxxxxx-xxxx" requested by the login. The login failed.
---------------------------
OK
---------------------------
Solution:
Restore the NAV2009 backup again and remove all tables which have property “LinkedObject“ Yes before converting the database to NAV2013.
Subscribe to:
Posts (Atom)