August 24, 2016 at 8:40 am
Sqlcmd: Error: Connection failure. SQL Native Client is not installed correctly. To correct this, run SQL Server Setup.
This is SQL Server 2014 Express with Tools.
Client terminal had 2008 R2 installed, the process is uninstall 2008 R2 and then install SQL 2014. Which I thought had went perfectly, but one thing remains.
There is residue from the old 2008 R2 install in Programs and Features. And it reads:
Sql Server Setup has encountered the following error:
Could not load file or assembly 'Microsoft.SQLServer.Configuration.WizardFramework,
Version=10.0.0.0, Culture=neutral, PublicToken=89845dcd8080cc91' or one of its dependencies.
The Module was expected to contain an assembly manifest..
So this morning I:
Removed SQL Server 2014 and all programs associated with it.
Nuked the SQL Server folder in C:\Program Files\
Reinstalled SQL Server 2014
No help.
The POS that is running SQL is performing fine, but the issue is making backups via command prompt with a script.
I have installed 2008 R2, but it will not allow me to 'repair' the original instance.
Any help is appreciated, please and thank you.
Chris
August 24, 2016 at 8:49 am
Have you double-checked that you are picking up the right version of sqlcmd.exe?
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
August 24, 2016 at 8:53 am
Phil Parkin (8/24/2016)
Have you double-checked that you are picking up the right version of sqlcmd.exe?
Well that is a great question. I am not sure I know how to perform that action. Can you point me in the right direction?
I was assuming the program was using SQL 2014 since the 2008 R2 instance is bad, but this all makes since regarding the behavior.
Thank you, Phil for your assistance.
August 24, 2016 at 10:53 am
I didn't nuke the (x86) folder as well! I didnt realize SQL installed there (64-bit version)
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply