Skip to main content

NAV 2013 NAV 2013 R2 Upgrade Error - Data Source name not found and no default drivers specified.

Hi all,

I am in process of upgrading a database from NAV 2009 SP1 to NAV 2013 R2 in one step. Earlier the One Step was not working for me but i hope this time i will be able to complete it. Keeping my finger crossed.

During upgrade step 1 i faced a issue that i would like to share with you all. After Step 1 of Data Migration when i tried to open the database in NAV 2013.

NAV 2013 gave me below error -

Error: [Microsoft][ODBC Driver Manager] Data Source name not found and no default driver specified. State ID: IM002




Reason for Error -
The SQL Server Native Client was not installed.

Resolution -

1. Open the product DVD of NAV 2013.
2. Navigate to the Pre- requisites Component Folder.
3. Open Microsoft SQL Server 2012 Express.
4. Install the sqlncli64 (Native Client for SQL) as shown below.


I hope if someone will face the issue, will be able to resolve same using above steps.

Will keep you updated if the Upgrade Process from NAV 2009 SP1 to NAV 2013 R2 is completed.

Wish me luck.

"These postings are provided "AS IS" with no warranties and confer no rights. You assume all risk for your use."

Regards,
Saurav Dhyani
saurav-nav.blogspot.com

Comments

Post a Comment

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.