SQL login error in conversion NAV2009SP1 to NAV2013 'R1'

greysgreys Member Posts: 29
edited 2014-03-06 in NAV Three Tier
Hi

I want to convert database CONVTO2013 to NAV2013R2 (via NAV2013 'R1'). I get a login error on the first step (NAV2009 -> NAV2013 R1)

What I did so far:

- I took a standard NAV2009 Cronus database and imported all our own objects.
- I created a SQL backup of it and restored in a virtual machine that only has NAV2013 (R1) installed. The machine is called NAV2013VIRTUAL
- I opened a nav2009 client and made sure the user NAV2013VIRTUAL\NAVCONVERTER was added as a windows user.
- I made sure NAV2013VIRTUAL\NAVCONVERTER has all the needed rights and roles in both NAV and SQL Server 2008 (dbo, sysadmin etc.)
- I made sure the Compatibility level of the database in Sql Server is correct (100).

- I opened the database in de NAV2013 Development Environment (build 36076).
- I confirm that I want to covert the database with OK.
- It starts redesigning and building keys.
- In the next step it says 'altering objects', all the way to 100%. Then it starts altering again, but when it gets to 5% I get the following message:

"The following SQL Server error or errors occured: 18456,"28000", Microsoft Sql Server Native Client 10.0 Login Failed for user NAV2013VIRTUAL\NAVCONVERTER. 4060, 42000. Cannot open database "CONVTO2013" requested by the login. The login failed.

So while it logs in perfectly at the start and the conversion starts, somewhere down the line it wants to log in again with the same user as it started with, but that is refused.... Has anyone encountered this problem yet?????

Best regards,
Greys

Answers

  • vremeni4vremeni4 Member Posts: 323
    Hi,

    The problem is caused by the fact that" Windows Access Control" and "Windows Login" tables do not exist in NAV 2013.

    To resolve the problem export all records from following three tables
    User
    Windows Login
    Windows Access Control
    in a CSV file. (dataport)
    After that delete all records from those three tables.
    This will disable NAV 2009 authentication.
    Make sure that user NAV2013VIRTUAL\NAVCONVERTER is a db_owner on the database.
    (I know it is not necessary but it can removed later )

    Upload a Developers licence that works for both NAV 2009 and NAV 2013.
    Now complete the technical upgrade.

    I hope this helps.
  • greysgreys Member Posts: 29
    Thanks, this indeed was the solution!!!

    Best regards,
    Greys
Sign In or Register to comment.