Error during upgrade to NAV 2013 R2

TimoBo

During the upgrade from NAV 2013 to NAV 2013 R2 an error occurs when trying to open the Windows Client to perform Upgrade Step 2.

---------------------------
Microsoft Dynamics NAV Development Environment
---------------------------
The following SQL error was unexpected.

Cannot drop the index 'dbo.CRONUS Ltd_$Vendor Ledger Entry.$15', because it does not exist or you do not have permission.

Caution: Changing any part of an object name could break scripts and stored procedures.

Caution: Changing any part of an object name could break scripts and stored procedures.

Caution: Changing any part of an object name could break scripts and stored procedures.

The database is installed locally on a SQL 2008 R2 instance. The NAV Service runs on the Network Service user which is sysadmin. My Windows user is also sysadmin. I have restarted the service. The license has been upgraded to a 2013 R2 development license. I have followed all upgrade steps as described on MSDN.

I noticed that an other user also mentioned this problem in this topic: viewtopic.php?f=32&t=59261&start=30 but nobody responded.

Any advice would be appreciated.

ara3n

try and see if there are any disabled keys and remove them from the table.

dmc-dk

Try requesting the latest NAV 2013 R2 Platform HF build - this issue must be fixed there.

mdPartnerNL

dmc-dk wrote:

Try requesting the latest NAV 2013 R2 Platform HF build - this issue must be fixed there.

What does HF means? How to request the latest? via Partner source?

tedl30

mdPartnerNL wrote:

dmc-dk wrote:

Try requesting the latest NAV 2013 R2 Platform HF build - this issue must be fixed there.

What does HF means? How to request the latest? via Partner source?

HF - Hot Fix

mdPartnerNL

Yes, while typing I understood therefore the other questions: How to request the latest? via Partner source?

tedl30

mdPartnerNL wrote:

Yes, while typing I understood therefore the other questions: How to request the latest? via Partner source?

I didn't find it on partner source.

geordie

mdPartnerNL wrote:

Yes, while typing I understood therefore the other questions: How to request the latest? via Partner source?

If you have a PartnerSource account you can check the latest here.

tedl30

geordie wrote:

mdPartnerNL wrote:

Yes, while typing I understood therefore the other questions: How to request the latest? via Partner source?

If you have a PartnerSource account you can check the latest here.

On this link only update for NAV 2013 not for 2013 R2

thegunzo

The first update for NAV 2013 R2 has not been released so no need to look for it.

dmc-dk

The hotfix pages for both 2013 and 2013 R2 can be found here:

http://blogs.msdn.com/b/nav/archive/2013/11/22/upgrade-toolkit-for-upgrading-data-from-microsoft-dynamics-nav-2009-r2-and-microsoft-dynamics-nav-2009-sp1-to-microsoft-dynamics-nav-2013-r2.aspx

Kind regards,
DMC

Juha

I got the same error when upgrading from 2013 to 2013R2.
My observation is that Navision is naming the indexes different in 2013 and 2013R2. In 2013 the indexes are named 0,1,2,3,.. based on the active keys. In 2013R2 the numbers comes the key index both active and non-active.
When you have 2 inactive indexes on Vendor Ledger Entry , the 15th index is named COMPANYNAME$Vendor LedgerEntry.$13 in 20013 and COMPANYNAME$Vendor LedgerEntry.$15 in 20013R2.
I fixed it by creating a index COMPANYNAME$Vendor LedgerEntry.$15 on Vendor Ledger Entry from SQL, before importing the 2013R2 objects

mdPartnerNL

Looks to be the solution, thx for the help and lets wait for the topicstarters reaction.

TimoBo

Thanks for the input. We have applied a workaround by simply enabling all the keys in the table in NAV before upgrading and resetting the keys after upgrading. By enabling all the keys the necessary SQL indexes are created beforehand and the error is avoided. This is basically the same solution as Juha suggested.

omyvadiya

Hi,

I am facing the same issue, but couldn't able to resolve it.
Steps i followed.
1. Normal Converting of db.
2. Merging the difference and then i imported the .txt files into the Nav 2013R2 demo (new db)->got the fobs->imported in converted db..before the data upgrade.
And i got the same error.

Note- i know the fob must not be uploaded now, its used while data upgrade, but i was having the same issue with Nav 2013R2 db in which i imported the merged objects.
After compiling i face the same issue.
](*,) ](*,) ](*,) ](*,) ](*,)

dmc-dk

Did you download the NAV 2013 R2 Update Rollup 1 and replaced the platform files?

Can be downloaded here: https://mbs2.microsoft.com/Knowledgebase/KBDisplay.aspx?scid=kb;en-us;2901573
Announced here: http://blogs.msdn.com/b/nav/archive/2013/11/30/announcement-of-update-rollups-for-microsoft-dynamics-nav-2013-r2.aspx

Kind regards,
DMC

omyvadiya

Thanks Dmk-Dk

daborg

Does anyone have a solution to fix this system wide as a one-shot deal? We've got an ISV solution with hundreds of tables and over the course of the last 2 years we've disabled many keys throughout the system in order to increase performance. Now after upgrading our product to 2013 R2, we have countless tables that cause index errors and require manually updating the indexes in SQL Mgmt Studio. This is crazy!! ](*,)

ara3n

daborg download the update. it fixes your issues

dmc-dk wrote:

Did you download the NAV 2013 R2 Update Rollup 1 and replaced the platform files?

Can be downloaded here: https://mbs2.microsoft.com/Knowledgebase/KBDisplay.aspx?scid=kb;en-us;2901573
Announced here: http://blogs.msdn.com/b/nav/archive/2013/11/30/announcement-of-update-rollups-for-microsoft-dynamics-nav-2013-r2.aspx

Kind regards,
DMC

tedl30

ara3n wrote:

daborg download the update. it fixes your issues

dmc-dk wrote:

Did you download the NAV 2013 R2 Update Rollup 1 and replaced the platform files?

Can be downloaded here: https://mbs2.microsoft.com/Knowledgebase/KBDisplay.aspx?scid=kb;en-us;2901573
Announced here: http://blogs.msdn.com/b/nav/archive/2013/11/30/announcement-of-update-rollups-for-microsoft-dynamics-nav-2013-r2.aspx

Kind regards,
DMC

Are anybody test thit KB: When you add a new field or change or delete an existing field in an existing table, you receive the following error message: "The table definition is invalid and cannot be validated"

ara3n

Set the tools->Option "Prevent data loss from table changes" to No

daborg

ara3n wrote:

daborg download the update. it fixes your issues

I'm not convinced this actually does fix the issue. I have a few machines where the user has done this and the issue still exists and anytime they import modifications to tables that are affected by the indexing issue, they get errors and have to manually fix the indexes in SQL.

The full scope of what has happened is that the 2013 database was initially opened by the original released 2013 R2 client, not the hot fixed one. Even after applying the hot fix and recompiling everything (with the prevent data loss setting off) the issue still exists and the indexes are still numbered like they are in 2013, not like they are in 2013 R2. #-o