Re: Error re-installing SQL Server 2005



Great! Thanks for the feedback, I documented this problem in my web site.

--
Ekrem Önsoy



"Kevin" <Kevin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:4239F1EF-3087-4629-8A04-77D485458CAA@xxxxxxxxxxxxxxxx
Ekrem,
yes, the fix worked. i actually was able to export the reg entries from my
machine, since it is also installed there. copying the reg entries from that
post didn't work because it is missing the 1st line below:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client]

[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"

--
Kevin Struckhoff
Analytics Mgr.


"Ekrem Önsoy" wrote:

Hello Kevin,

There's a solution in the following link and it seems from the posts that it
works:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=392835&SiteID=1

It'd be good if you feedback.

--
Ekrem Önsoy



"Kevin" <Kevin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C86987A7-B24A-4C41-BE63-035DF3C19ED3@xxxxxxxxxxxxxxxx
> I'm getting this error now trying to re-install sql server 2005 > database
> and
> reporting services. I had it installed ok and it was working fine. i > then
> decided to try out sql server 2008 rc0. i'm not sure the uninstall > cleaned
> up
> correctly. anyway, i was able to get some of the product re-installed > but
> not
> all of the righ parts. here's the error:
>
> -----------------------------
>
> 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.
>
> For help, click:
> http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=29515&EvtType=lib%5codbc_connection.cpp%40Do_sqlScript%40OdbcConnection%3a%3aconnect%40connect%40x15
>
> This link is useless. here the link info:
>
> Details
> ID: 29515
> Source: setup.rll
>
> We're sorry
> There is no additional information about this issue in the Error and > Event
> Log Messages or Knowledge Base databases at this time. You can use the
> links
> in the Support area to determine whether any additional information > might
> be
> available elsewhere.
>
>
> how do i resolve this issue? i don't see where the sql native client > can
> be
> configured.
>
> thanks for you help.
>
> -- > Kevin Struckhoff
> Analytics Mgr.


.



Relevant Pages

  • Re: Error re-installing SQL Server 2005
    ... i actually was able to export the reg entries from my ... SQL Server Setup could not connect to the database service for server ... Refer to server error logs and setup logs for ... For details on how to view setup logs, ...
    (microsoft.public.sqlserver.setup)
  • Re: Error re-installing SQL Server 2005
    ... SQL Server Setup could not connect to the database service for server ... Refer to server error logs and setup logs for more ... For details on how to view setup logs, ... Kevin Struckhoff ...
    (microsoft.public.sqlserver.setup)
  • Re: SQL Server Setup could not connect to the database service for server configuration
    ... I'd go to SQL Error Logs and see a more detailed message about the error. ... I am getting following error while trying to install SQL Server 2005. ... For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online. ...
    (microsoft.public.sqlserver.setup)
  • RE: 400 MB log folders
    ... I understand that you would like to know if the SQL Server 2005 setup logs ... setup issues of SQL Server 2005 installation and service packs ...
    (microsoft.public.sqlserver.setup)
  • Re: Cluster will not fail over.
    ... Could not recover the master database! ... If you intend to stay on SP3 (for SQL Server), you should at least apply the ... >> From SQL server logs ...
    (microsoft.public.sqlserver.clustering)