Internal error: Could not load file or assembly 'Microsoft.Dynamics.Nav.DotNetBridge, Version=8.0.0.0

Some time we may get the below error while import the objects

---------------------------
Microsoft Dynamics NAV Development Environment
---------------------------
Internal error: Could not load file or assembly 'Microsoft.Dynamics.Nav.DotNetBridge, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
---------------------------
OK
--------------------------- Solution. This is due to  running the client from C\program files (x86) folder which is for 32 bit applications . We should run the dev client from C:\Program Files (x86)\Microsoft Dynamics NAV\80\RoleTailored Client to resolve the issue.

Error : There is a syntax error while compiling NAV16 object

Recently I got an issue with compiling the object in NAV2016, I am getting the below error while compile the object .

---------------------------
Microsoft Dynamics NAV Development Environment
---------------------------
There is a syntax error.
---------------------------
OK
---------------------------

But when I check the code everything seems to correct as show below

Now I copied the code in notepad++ and found some special characters as  shown below 

   

I removed them and used the code in NAV and my object got compiled. I hope it will help some one.                                                                                                                   

Login failed for user 'XXXX'. 4060,"42000",[Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot open database XXXXXX requested by the login. The login failed.

The below error occurs when we try to convert the database from NAV2009 to NAV2013.


The following SQL Server error or errors occurred:

18456,"28000",[Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'XXXXXX' 4060,"42000",[Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot open database "XXXXXX'" requested by the login. The login failed.

Solution:

In this case ,please follow the below steps

1. We have to restore the NAV2009 backup again 

2. Open the database In NAV2009 and remove all tables which have property “LinkedObject“ Yes 

Note: Please also check the tables which are having LinkedObject=No.

It should be like below 

3. Try to convert the database in NAV20013.
4. Delete all temp windows logins\SID's

Now It will convert it in to NAV2013.

I hope this will help you.

Thanks!

Error:TableData 2000000001 does not exist.

We get the below error when we try to connect the database

To resolve this error,we need to set the below permission in Sql server

I hope it will help you.

Error while opening NAV2013 R2 database

Some times we used to get the below error while opening NAV2013 R2 database

Error :

---------------------------
Microsoft Dynamics NAV Development Environment
---------------------------
The Object table contains a Microsoft Dynamics NAV Development Environment field data type that is not compatible with the SQL Server data type:

Field: Version List
Type: Text248
SQL type: VARCHAR(80)
---------------------------
OK  
---------------------------

to resolve this error ,Simply run the below command in SQL Server

ALTER TABLE [dbo].[Object]

ALTER COLUMN [Version List] VARCHAR(248) NOT NULL

I hope this will help some one.

Thank you.

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.

An error occurred when opening the report designer. A supported version of Visual Studio could not be found

We will get the below error when visual studio does not exist in our system,But we have report Builder 

An error occurred when opening the report designer. A supported version of Visual Studio could not be found.

How to enable Report Builder : 

steps as below

1. Navigate to Tools - Options.

2. Set Property Use Report Builder as YES.

    

Now open the layout of any report, it will open with Report Builder as shown below.

I

Error : while validating RDL content: Value cannot be null

Once you upgrade databse to  NAV2015,we need to create a service for the databse otherwise some times we may get the below error

Microsoft Dyanamics NAV
----------------------------

Error while validating RDL content:
Value cannot be null.

Parameter name: path1
----------------------------

To resolve this issue,we need to create a service name and check the service name effected to our database through file --> database information-> service name

Error: To upgrade reports, you must have Microsoft SQL Server 2014 Report Builder 3.0 installed.

Some times we may get the below error when we upgrade fron NAV2013 to NAV2015

---------------------------
Microsoft Dynamics NAV Development Environment
---------------------------
To upgrade reports, you must have Microsoft SQL Server 2014 Report Builder 3.0 installed.
Binary fields can't be upgraded.
---------------------------

Microsoft SQL Server 2014 Report Builder 3.0 will automatically install when you install NAV2015.
Some times  it may un install  by some one then we need to install the Microsoft SQL Server 2014 Report Builder 3.0 .

NAV2009 Reporting Error

Sometimes the following error may occur while designing RDLC Report

     “The provided metadata is not valid”

This error can happen when the following conditions are true:

You are using Windows Vista and User Access Control (UAC) is turned on.

• The executable file that runs the Visual Studio development environment (devenv.exe) is set to run as an administrator.
• The executable file that runs the Classic client with Microsoft SQL Server (finsql.exe) is not set to run as an administrator.
• To resolve this issue, either turn off UAC or set both finsql.exe and devenv.exe to run as an administrator.

To turn off UAC

• In Control Panel, select User Accounts.
• In User Accounts, click Turn User Account Control On or Off.
• Clear the Use User Account Control (UAC) to help protect your computer check box.
• To set a program to run as an administrator
• Right-click the .exe file, and then select Properties.

In the Properties window, on the Compatibility tab, in the Privilege Level section, selectRun this program as an administrator.

NAV2015 Compilation Error-Unable to process changes because Service Instance has not created

The below error has  occurred  while compile or save the objects in NAV2015

 To resolve this error,we need to Create a service  or change the database name to the existing service

    and restart the service.

Check the server ports,server name,server instance name has populated or not as shown below 

Open Navision C\SIDE client Tools --> Options then these values.

                   

 

NAV2015 Error-Unable to process changes because current user cannot be authenticated

The below error has  occurred  while compile the objects in NAV2015

To resolve this error,we need to run either the below query in SQL Server

USE [Database Name]
GO
delete from [dbo].[User]
delete from [dbo].[Access Control]
delete from [dbo].[User Property]
delete from [dbo].[Page Data Personalization]
delete from [dbo].[User Default Style Sheet]
delete from [dbo].[User Metadata]
delete from [dbo].[User Personalization]

or provide the required permission to user.

Cannot build the page XXXX The metadata object Table XXXX was not found.

When you try to run an imported page in Nav 2013 you receive the following error:

Microsoft Dynamics NAV
—————————
Cannot build the page XXXX.
The metadata object Table XXXX was not found.
—————————
OK
—————————

TableRelation property of any field is having XXXX

Solution:

In the Development Environment design the SourceTable of the page XXXX.
Check all fields table relations that have the XXXX as TableRelation and fix them up writing the correct table.