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@microsoft.com.
===========================================================
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.
============================================================

Signature
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================
SQLChuck - 27 Jun 2008 22:44 GMT
Thanks for your response. And exactly, that is my point. Shared memory should
have nothing to do with remote clients. That’s why the cause is unclear. In
the environment described earlier all that was required was to disable shared
memory, restart SQL Server Service and restart remote clients. Once remote
clients were restarted they could connect fine.
Addition Info: In this environment server side encryption and a custom
certificate (explicitly specified) is used. Certificate is installed on local
computer certificate store and SQL Server service is running under
LocalSystem credentials.
At client side both “Force Protocol Encryption” and “Trust Server
Certificate” is set to NO.
Since shared memory should have nothing to do with remote clients not sure
why that affects connectivity. Still looking.
Thanks,
Charles
Charles Wang [MSFT] - 30 Jun 2008 10:27 GMT
Hi,
Thank you for your response.
We are discussing this issue internally, however could you please also
confirm with me whether this issue persists if you set "Force Protocol
Encryption" to Yes on your client with Shared Memory enabled on your server?
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@microsoft.com.
=========================================================

Signature
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================
SQLChuck - 01 Jul 2008 01:18 GMT
If I set the "Force Protocol Encryption" on the client side to Yes (On all in
one box, no remote clients), then the connectivity seems to be fine. I have
not yet had a chance to work with remote clients.
Thanks,
Charles
Charles Wang [MSFT] - 03 Jul 2008 10:18 GMT
Hi,
Thank you for your response.
Could you please further check with us what the result is if you set the
"Force Protocol Encryption" on your remote clients to Yes? Regarding the
shared memory issue, currently we have not been able to explain since it
looks really not making sense here, however we am trying to establish an
environment to see if we can reproduce your issue. The process may need a
little long time. I appreciate your patience.
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@microsoft.com.
=========================================================

Signature
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================
Charles Wang [MSFT] - 07 Jul 2008 11:23 GMT
Hi,
Based on my test and our internal discussions, we do not think that this
issue is really caused by Shared Memory protocol since we cannot reproduce
this issue at my side. As I had mentioned, I recommend that you first check
if you can work around this issue by setting "Force Protocol Encryption" on
your remote client computer.
Appreciate your understanding that since this issue was environment
specific and that it was hard to be reproduced at our side, to track the
root cause, dump analysis would be required, however this job requires your
contacting Microsoft Customer Support Services (CSS) for further research.
If you want to track the root cause, I recommend that you contact CSS via
telephone so that a support professional can assist you in a more efficient
manner. Please be advised that contacting phone support will be a charged
call.
To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
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@microsoft.com.
=========================================================

Signature
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================
SQLChuck - 09 Jul 2008 17:58 GMT
Hi,
Thanks. I opened a case with CSS and working with them. I appreciate your
help.
Regards,
Charles
> Hi,
> Based on my test and our internal discussions, we do not think that this
[quoted text clipped - 31 lines]
> =========================================================
>
Hi,
Just a kind reminder, I have not received your response. Please feel free
to post back at your convenience if you need further assistance.
Have a great day!
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@microsoft.com.
=========================================================

Signature
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================