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!

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).