Dynamics NAV

Thursday, 22 December 2016

Obsolete tables in NAV2016

The below list of tables were obsoleted\removed in NAV2016.

  Tables  452,453,464,465 and 11414

Monday, 28 November 2016

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.

Friday, 5 August 2016

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.                                                                                                                   

Tuesday, 19 July 2016

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!

Friday, 8 July 2016

How to Block Direct posting in NAV

Sometimes General Ledger (G/L) and sub ledgers (Customer,Vendor,Bank...) values won’t get tally, when users directly post transaction entries to these accounts using journals. 

To avoid these mistakes, Microsoft Dynamics NAV has a simple method to control this. This functionality called as Block for Direct Posting.

In order to block an account from direct posting, you need to go to particular G/L Account Card and uncheck  the "Direct Posting" check box. 

Once tick mark is removed, Microsoft Dynamics NAV will not allow any user to post journal entries directly to the particular G/L account. (At any given time you can put the tick mark back and allow to post directly).










Thursday, 2 June 2016

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.

Wednesday, 4 May 2016

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.

Wednesday, 20 January 2016

Error while running Power shell

Some times we may get the below error while import module in like power shell

'Run only scripts that you while scripts from the internet can be useful ,this script can potentially harm your computer. If you trust this script, use the unblock-file cmdlet to allow to run without this warning message. Do you want to run c:\program files (x86)\microsoft dynamics NAV\90\Role Tailored Client\Microsoft Dynamics.nav.Apps.Tools.Format.ps1xml?'

as shown below


Solutions                                                                                                                                                     
   To resolve this issue,please foollow the below steps,
1.             Right-click on the .ps1 file in question, and select Properties
2.              Click Unblock in the file properties
  3.        OK.