Install SQL Server2005 Error:[Native Client]Encryption not supported on the client

Question

Product: Microsoft SQL Server 2005 -- Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Encryption not supported on the client. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

Answer 1

This is a reported problem but we don't have a workaround figured out yet. Sorry...

 

Pal

Answer 2

Has a workaround been figured out? I'm experiencing the same issue.

Answer 3

I am experience this problem.  Just did a fresh install of Windows Server 2003 + SP1.  Added DNS, DHCP, AD, then tried to install SQL 2005.  Nothing else was on the box.

Answer 4

i went through alot of the "native client" hell... :)    For some reason on some installs the native client gets out of whack.

I had to import this, please note you do this AT YOUR OWN RISk.  But it worked perfect for me.

When I was reloading my server, the native client "reinstall" wouldnt show.  I knew I had uninstalled it so i was "wtf" its not uninstalling.

So I installed the natice client, imported this into the registry and everything ran fine.

Before you import this you might want to just verify all these keys exists.  If they do, your problem is elsewhere.

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client]
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo]
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\DB-Lib]
"AutoAnsiToOem"="ON"
"UseIntlSettings"="ON"
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0]
"ProtocolsSupported"=hex(7):73,00,6d,00,00,00,74,00,63,00,70,00,00,00,6e,00,70, 
00,00,00,76,00,69,00,61,00,00,00,00,00
"ProtocolOrder"=hex(7):73,00,6d,00,00,00,74,00,63,00,70,00,00,00,6e,00,70,00, 
00,00,00,00
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\GeneralFlags]
"NumberOfFlags"=dword:00000002
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\GeneralFlags\Flag1]
 
"Label"="Force protocol encryption"
"Value"=dword:00000000
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\GeneralFlags\Flag2]
 
"Label"="Trust Server Certificate"
"Value"=dword:00000000
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\LastConnect]
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\np]
"DLLname"="SQLNCLI"
"NumberOfFlags"=dword:00000000
"NumberOfProperties"=dword:00000001
"ProtocolName"="Named Pipes"
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\np\Property1]
"Name"="Default Pipe"
"Value"="sql\\query"
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\sm]
"DLLname"="SQLNCLI"
"NumberOfFlags"=dword:00000000
"NumberOfProperties"=dword:00000000
"ProtocolName"="Shared Memory"
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\tcp]
"DLLname"="SQLNCLI"
"NumberOfFlags"=dword:00000000
"NumberOfProperties"=dword:00000003
"ProtocolName"="TCP/IP"
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\tcp\Property1]
"Name"="Default Port"
"Value"=dword:00000599
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\tcp\Property2]
"Name"="KEEPALIVE (in milliseconds)"
"Value"=dword:00007530
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\tcp\Property3]
"Name"="KEEPALIVEINTERVAL (in milliseconds)"
"Value"=dword:000003e8
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\VIA]
"DLLname"="SQLNCLI"
"NumberOfFlags"=dword:00000000
"NumberOfProperties"=dword:00000002
"ProtocolName"="VIA"
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\VIA\Property1]
"Name"="Default Server Port"
"Value"="0:1433"
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\VIA\Property2]
"Name"="Default Client NIC"
"Value"="0"

 

 

Answer 5

EDIT NOTE: I removed my over two year old post because it is no longer relevant.

Answer 6

umm....  no you didnt find a simpler work around.

We tried that, multiple times... 

Your "uninstall" doesnt fully uninstall/reinstall correctly.

 

 

Answer 7

EDIT NOTE: I removed my over two year old post because it is no longer relevant.

Answer 8

Any progress on this problem yet? I still can't install the product after 4 months. This is totally unacceptable.

Answer 9

I'm in the same boat (up the creek... etc)

Seems to me I'm going to have to rebuild...

 

 

Answer 10

Thanks a bunch, Mikes2nd. I was trying to see if I could solve this problem without tampering with the registry, but I couldn't. I tried your suggestion and it worked like a charm. If I were you, I would print the contents of this blog as evidence and submit a hefty bill to Microsoft for solving a problem that they should have fixed. Keep up the good work.

Answer 11

Franco? Thought you said the registry tweak worked for you?

I also had to do a complete fresh install of SQL.  Don't even try the upgrade routine.

I hope MS figures out what the problem is.

What initially occured was a failed upgrade install.  Then i completely uninstalled and tried reinstalling.

Not until I loaded that registry did it allow a "fresh" install to go in and take.

Yes the only other way I was thinking was a complete nuke and reinstall.

 

 

Answer 12

The registry tweak worked for me. I uninstalled everything that had to do with Microsoft SQL Server, MSSQLServer and MSSQL Native Client. I deleted the same keys from the registry and the folders from Program Files. I then imported your Native Client registry settings and did a fresh install from the CD and everything was fine. I ignored the Native Client install on the CD. Like I said in my earlier post, you should bill Microsoft.

Answer 13

Hi,

 

I also hit this error and applied the REG hack and then clicked on retry in the installaler and hay preseto it carried on and installed. 

Thanks saved me hours of work re-building the server.

 

Gary

Answer 14

Cool, this worked for me. Just for general information, these keys were missing because i performed a manual uninstall of MSDE2000 per Microsofts instructions. Fortunatly I backed up the registry keys before I deleted them. Cheers!

Answer 15

I hope you don't take this wrong, but I LOVE YOU MAN (Mikes2nd).

This post brought a tear to my eye.

Thank you! Thank you!

Answer 16

Hi all,

 

i am in trouble..... could any one help me in how could i import the registries??

thanks alot

Answer 17

Eh... this might be over your head but you can just make this a .reg file and click on it.

You ever use regedit?  Search on the web

Answer 18

I created a txt file and cut/paste the values in this forum.

I add this line to the top of the txt file:

"Windows Registry Editor Version 5.00" (without the quotes)

and saved the txt file.

Then I changed the extension from .txt to .reg

I could then click on it and import it, no problem.

-David

Answer 19

 

Thanks all.....

Thanks alot David .... I appreciate it

Answer 20

I have a Small Business Server 2003, and I also did a manual removal of a faulty Express2005 installation and MSDE. Applying the regisrtry fix solved it all and now it plays nice.thank you Mikes2nd!

Answer 21

Mikes2nd,

You hint was really time saver. Worked smoothly for me. Thanks a bunch.You just forget to tell that you have to put:

Windows Registry Editor Version 5.0

And save it as .reg

These hints are just as complement.

Answer 22

Hi.

I am sitting in Norway - it is late at night and I am helping a colleague who is installing a new customer in Dubai. I am on VPN with a faulty sql 2005 server. Tried to uninstal / reinstall and got this error. Your regfix did the trick.

 

I am deeply grateful!

 

Espen

Answer 23

 Excellent Mikes2nd

You got Low Level Solution to High Level Problem

 

In my Case this problem started

(1) When I upgraded to XP with SP2

(2) I upgraded because SQL did not work way I wanted in a first place

(3) Created Installation Problem rather than Instances so I started removing files at lower level

(3) Reinstallation Failed with during Databse Engine Installation with MsiExec

(4) Tried to fix Reninstall/Update and So on...But In Vain

(5) Finally Used your way using .REG

(6) Ran into Reg Import problem Version /Text Editor save as .REG (REGEDIT4 v/s 5.0 I guess!!!)

(7) Fixed that Problem by Selection ANSI on a MSSQLSERVER exported file

(8) During Reinstallation MsiExec still Threw an Error

(9) But Regardless of the above error all items were successfully Installed.

 

Thank you

Answer 24

The registry fix and everything worked out fine....Every little step in this document helped....Thanks all

Answer 25

Here is a Knowledge Base article on removing previous traces of SQL Server:

http://support.microsoft.com/kb/909967

 

I found it very helpful. It was completely successful at fixing the most messed up machine I've encountered to date.

Answer 26

John Paul Cook wrote:

Here is a Knowledge Base article on removing previous traces of SQL Server: http://support.microsoft.com/kb/909967   I found it very helpful. It was completely successful at fixing the most messed up machine I've encountered to date.

 

while thats a great guide.  Don't think it was around for me at the time but I'm not sure it will work for the native client issues.

 

A registry restorer or something similar will work to get your machine back to the state you were in before though there's no promise the same native client issue wont pop right back up.

 

concerning native client It simply says:

Step 4: Uninstall the Microsoft SQL Server Native Client component

If all the other steps were successful, uninstall the Microsoft SQL Server Native Client component by using Add or Remove Programs.

Note Do not uninstall the Microsoft SQL Server Native Client component if you have SQL Server 2000 components installed.

 

 

This problem is all about the native client and the protocols it can use, this registry info places the native client in a working state.

 

I am going to try some new SQL 2000 to SQL 2005 upgrades and see what happens.  I will only install the native client(check it to see how it looks).  If it looks bad fix it. Then try to complete the upgrade.

 

After a successful install of the native client your client "registry" should look like what I posted in most cases.

Answer 27

Mikes2nd wrote:

John Paul Cook wrote: Here is a Knowledge Base article on removing previous traces of SQL Server: http://support.microsoft.com/kb/909967   I found it very helpful. It was completely successful at fixing the most messed up machine I've encountered to date.   while thats a great guide.  Don't think it was around for me at the time but I'm not sure it will work for the native client issues.

 

 

 

It resolved my native client problem. I'm not asserting it will solve every problem or even your problem, but I do recommend people consider it before the registry fix.

Answer 28

thats a great guide of course but...

 

I think once this error shows up we all go through the "full uninstall" process but that is definately a guide to use to make sure its a true "full" uninstall.

 

I uninstalled mutliple times and reinstalled to no avail and that can get very time consuming considering the size/complexity of sql server.  Even going through that whole process in that KB article could take hours and sometimes we don't have that kind of time.

 

Did you actually recieve the native client encryption error? because everything mentioned in that guide really doesnt mention the guts of the native client so like I said it should have no little on this specific issue.

 

It just says "uninstall the native client", it doenst tell you any details other than that and thats the problem most here in this thread are experiencing it seems.

 

the native client will uninstall but it isnt fully uninstalled(the kb article needs more depth on that subject) or there is some info thats causing the native client to install incorrectly.

 

The production server I had to use this registry fix on is up and running fine(applied sp2 just recently) and ive never run into problems since.  I think people are using this as a quick fix to that error message and it looks like its just that.  Of course "quick" fixes can sometimes lead to problems but so far everythings been fine.

 

Like I said all this registry hack is made up of is the correct registry settings for the client.  You could theoretically reregister it at anytime if you have the standard settings on your native client.  I compared mine to whats currently on a couple servers and thats what I see.

 

Answer 29

Mikes2nd wrote:

thats a great guide of course but...   Did you actually receive the native client encryption error? because everything mentioned in that guide really doesnt mention the guts of the native client so like I said it should have no little on this specific issue.

 

I no longer have the error message. But I clearly remember that I was trying to uninstall SQL native client. The buttons in Add/Remove Programs for native client were disabled. The procedure in the KB article didn't take excessively long, maybe 15 minutes. I can more easily persuade others to accept it than a registry fix.

Answer 30

***********************************PERFECT******************************

Thanks so much.... added the "Windows Registry Editor Version 5.00" at the top of a text file, dropped this and clicked and did it all while the install was waiting for me to click "retry"!!!

Answer 31

Thanks mate, worked perfectly after i clicked retry but it failed afterwards. i found this in the log file but its not helping me:

Error: Action "LaunchLocalBootstrapAction" threw an exception during execution.  Error information reported during run:
"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 1603
Aborting queue processing as nested installer has completed
Message pump returning: 1603

 

Any ideas  ?

Answer 32

Thanx the registery hack worked like a charm !!!

Answer 33

REG import worked for me.
WinXP SP-2

Answer 34

Hi Mike,

 

Just a quick note to let you know the same thing happened to me.

 

Cause was a failed SP2 install which made a complete mess of the install.

 

There's no way to back of a SQL service pack, and the SQL2005 uninstall failed spectacularly..

 

Trawling through the regisrty manually removing anything to do with SQL

 

Killing all the service entries too.

 

Then finally running the reinstall again and got the encryption error.

 

All I did was run your script and hit retry and it worked.

 

Thanks a bundle - saved a trip to the data center

 

 

Rob

 

PS:  The registry file needed this at the top b4 it would run (without the quotes)

"Windows Registry Editor Version 5.00"

Answer 35

Worked perfectly....thanks

 

Answer 36

RobertCW wrote:

Hi Mike,   Just a quick note to let you know the same thing happened to me.   Cause was a failed SP2 install which made a complete mess of the install.   There's no way to back of a SQL service pack, and the SQL2005 uninstall failed spectacularly..   Trawling through the regisrty manually removing anything to do with SQL   Killing all the service entries too.   Then finally running the reinstall again and got the encryption error.   All I did was run your script and hit retry and it worked.   Thanks a bundle - saved a trip to the data center     Rob   PS:  The registry file needed this at the top b4 it would run (without the quotes) "Windows Registry Editor Version 5.00"

 

havent been back in a while but glad to see it working for a SP2 install issue.

 

Yeah i've concluded this is essentially a "registry" reset for the Native Client to what it should be to allow a install to continue on.   You will not be able to continue without these changes since its corrupted.  This sets it in line.

 

Glad to see it saving time for so many.  Nothing like spending hours trolling for registry settings trying to figure out whats missing/extra

 

 

 

Answer 37

Thanks God and Mikes2nd this works. After two days of spending my time. Just create a reg file with the contens of the Mikes2nd post and install into the registry. Rerun the setup and enjoy.

 

Answer 38

<snip> The reg fix mentioned above applied during install WORKED!! THANK YOU!!!

 

<edit> uninstalling and installed the SQL Native Client  -- NOT! DIDNT WORK..C'mon that would be one of the first things we thought of...

Answer 39

Mike,

 

Many Thanks, registry import worked for me too!!!

 

I am really thankful to you as i was struggling with it for 2 days.

 

Keep posting.

 

Best Regards,

Suyog

Answer 40

Thanks, the registry hack also worked for me.

Answer 41

worked for me too except, now sqlncli provider works but sqloledb still does not
i get an error message saying it not installed

i had installed sp2 and then sp2 cumulative update 5 to fix it

according to microsoft support this error is not replicatable.  if anybody can give a process to replicate it please post it here

Answer 42

I had the problem, but did'nt use the newest  installation file. Then I ran the upgrade with SQL 2005 express SP2 and it solved the problem

 

 

 

Answer 43

Still working. Thanks.

 

Answer 44

I can't believe that after all this time - this problem still exists!!!   I also had the problem after an unsuccessful  SP2 install. Eventually I bit the bullet and went with the registry hack...  and all worked like a charm. Thanks a million.

 

Answer 45

Mike Caldwell wrote:

<snip> The reg fix mentioned above applied during install WORKED!! THANK YOU!!!   <edit> uninstalling and installed the SQL Native Client  -- NOT! DIDNT WORK..C'mon that would be one of the first things we thought of...

 

<Edit>

 

So far SQL 2008 installs for me are working flawless.

 

But I do see its "advisable" to "preinstall" the 2008 release patch 1 then install.

 

I didn't have any problems with fresh installs I've done so far.

Answer 46

Inflammatory posts edited? Cmon there is some pretty thin skin around here.

 

John Paul was wrong even after insisting he had the solution multiple times...is all we pointed out. Jeeze you guys need to relax.

Answer 47

The registry tweak worked for me as well. I actually exported it from a working machine and imported on the problematic machine. Great Job Mike, saved me a lot of time. Cheers!!

Answer 48

I had same error and found an easy fix.  

 

 I used add/remove programs and repaired the SQL Native client install.  Then I rebooted the server prior to re-trying and it worked.

 

My scenario was a bit different though.  I had previously installed SQL 2k5 32-bit on a 64-bit o/s and then uninstalled it before installing the 64-bit version where I got the error.

 

But this may be worth a try for those not wanting to use a scary registry hack.

 

Answer 49

Again for the 50th time

 

We all tried that man. This same error pops up. 

 

I feel like im still fighting with John Paul

 

seriously we all go through the uninstall/reinstall. And poof the error shows again.

 

If you didnt get the error back Im glad.  But when you do get the error back, use this scary registry import

 

Also just so you know, I have never had any problems ever since once applying this "Hack".

 

Servers have run flawless, all service packs installed fine.  That was a long time ago of course, like the second week SQL 2005 came out. Im off of 2005 and onto all 2008 installs now.

Answer 50

Hi everybody.
I looked for this error on the Microsoft KB, and I found an article in which, among the issues solved by the .Net Framework 2.0 SP1, there was also this error.
I had a Windows 2003 Server with SP2 and .Net Framework 2.0 without SP installed. I was a little bit skeptic about this article but I installed the SP, removed the previous installation of SQL Server 2005 and then reinstalled it and it worked.
If you experience the same issue, you can try this procedure, before applying the registry hack that of course works fine (I didn't apply that, I only installed the .Net SP and it worked).
Bye
Giancarlo

Answer 51

Just to confirm this works.  On our build servers Windows Server 2003 SP2 using SQL Server 2005 SP2, one was giving a hard time removing and reinstalling SQL.  Doing the typical troubleshooting, uninstalling using Add/Remove programs, deleting files/folders and searching in the registry to remove ALL traces of problem application before trying a reinstall did not work.

I had to use sc delete <ServiceName> to kill the SQL services but it was this REG import which allowed the SQL installer to continue successfully.

Thanks!

Answer 52

Also to confirm that this works with one caveat.  We had to install a 32 bit SQL Install on Windows 2008 64 bit.  The only change is that you want to import over the WOW6432Node info over (same info different place), Here is what mine happened to look like

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer]

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client]

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\SNI9.0]
"ProtocolsSupported"=hex(7):73,00,6d,00,00,00,74,00,63,00,70,00,00,00,6e,00,70,\
  00,00,00,76,00,69,00,61,00,00,00,00,00
"ProtocolOrder"=hex(7):73,00,6d,00,00,00,74,00,63,00,70,00,00,00,6e,00,70,00,\
  00,00,00,00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\SNI9.0\GeneralFlags]
"NumberOfFlags"=dword:00000002

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\SNI9.0\GeneralFlags\Flag1]
"Label"="Force protocol encryption"
"Value"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\SNI9.0\GeneralFlags\Flag2]
"Label"="Trust Server Certificate"
"Value"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\SNI9.0\LastConnect]

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\SNI9.0\np]
"DLLname"="SQLNCLI"
"NumberOfFlags"=dword:00000000
"NumberOfProperties"=dword:00000001
"ProtocolName"="Named Pipes"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\SNI9.0\np\Property1]
"Name"="Default Pipe"
"Value"="sql\\query"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\SNI9.0\sm]
"DLLname"="SQLNCLI"
"NumberOfFlags"=dword:00000000
"NumberOfProperties"=dword:00000000
"ProtocolName"="Shared Memory"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\SNI9.0\tcp]
"DLLname"="SQLNCLI"
"NumberOfFlags"=dword:00000000
"NumberOfProperties"=dword:00000003
"ProtocolName"="TCP/IP"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\SNI9.0\tcp\Property1]
"Name"="Default Port"
"Value"=dword:00000599

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\SNI9.0\tcp\Property2]
"Name"="KEEPALIVE (in milliseconds)"
"Value"=dword:00007530

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\SNI9.0\tcp\Property3]
"Name"="KEEPALIVEINTERVAL (in milliseconds)"
"Value"=dword:000003e8

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\SNI9.0\VIA]
"DLLname"="SQLNCLI"
"NumberOfFlags"=dword:00000000
"NumberOfProperties"=dword:00000002
"ProtocolName"="VIA"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\SNI9.0\VIA\Property1]
"Name"="Default Server Port"
"Value"="0:1433"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\SNI9.0\VIA\Property2]
"Name"="Default Client NIC"
"Value"="0"

 

Answer 53

YOU ROCK!  My client has been trying to reinstall Business Contact Manager 2007 for days and this got us over our main hurdle.  Thank you!!!

---

Kevin L Berg

Answer 54

Like everyone else on this forum, you have provided an answer for what has been a never ending nightmare for me. THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Answer 55

My loyal fans!  I thank you for your support! 

Hah rep me or something :)  oh wait just vote my post as helpful :)

Answer 56

Thanks God and Mikes2nd this works. This very helpfull.. :)