RE: Error 17835 - When encryption and Shared Memory are enabled



Hi,
I understand that you encountered the error message when your clients
connected to some of your SQL Server instances.
If I have misunderstood, please let me know.

To narrow down this issue, could you please first answer me the following
questions:
1. Did you encounter this error when you connected to your SQL Server
instance locally?
Shared Memory will only be used when you connected to your SQL Server
instance locally, so this issue should not be related to Shared Memory if
you remotely connected to your SQL Server instance.

2. Did your SQL Server instance use a certificate explicitly specified by
you for encryption?
If you used a certificate, I recommend that you refer to this article
to configure your server and client computers:
How to: Enable Encrypted Connections to the Database Engine (SQL
Server Configuration Manager)
http://msdn.microsoft.com/en-us/library/ms191192.aspx

3. If you did not explicitly specify a certificate, what is the result if
you configure your client connection settings "Force Protocol Encryption"
to True and "Trust Server Certificate" to True?
In this case, SQL Server 2005 instance will generate a self-signed
certificate and you can configure the settings on your clients via opening
SQL Server Configuration Manager on your client computer, right clicking
SQL Native Client Configuration, clicking Properties and then setting the
two options. If you see "No properties are available", that means your
client registry key was messed up and led to the connection error. To fix
this, please reinstall SNAC(SQL Native Client).


Hope this helps. If you have any other questions or concerns, please feel
free to let me know.


Best regards,
Charles Wang
Microsoft Online Community Support
===========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
===========================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
============================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================

.



Relevant Pages

  • Re: Connection Error: ADO.Net and SQL Server 2005
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... I can connect to the server through an ODBC connection ... It is very puzzling because this client doesn't seem to have anything ...
    (microsoft.public.sqlserver.connect)
  • Re: Losing connections with SQL 2005
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... SQL Server automatically detects if the client falls into the sea or gets ... Does the Connection pooling mechanism do this on its ... Upgrading our app is a really big task, ...
    (microsoft.public.sqlserver.connect)
  • Re: netbios and named pipes sql replication.
    ... Once the client switched to named pipes, ... > connection with. ... > When we took named pipes support off the SQL server with the MS patch, ... > We had to manually walk thru the ODBC setup and configure the CLIENT ...
    (microsoft.public.sqlserver.replication)
  • Re: Problem connection to SQL Server with ODBC
    ... What protocols are being used by the client and what is the ... Are you using an alias for the connection? ... SQL Server Clients May Change Protocols When They Try ...
    (microsoft.public.sqlserver.connect)
  • Re: Remote Connection to SQL 2005
    ... I think you have an application, so can you show your Connection String? ... It's going to be the error message which will help us to solve the problem. ... You better investigate the problem from SQL Error Logs if it's only about SQL Server connection. ... If your SQL Server Instance is a Named Instance then ensure the Browser Service is running. ...
    (microsoft.public.sqlserver.setup)