Encryption not supported on SQL Server

Getting this error when trying to get into Enterprise
Manager on the local server. I can get into EM from other
machines. I also have an ASP application running locally
on the same SQL box that gets the same error when trying
to run. This all started recently after a reboot of the
server. I know some SQL stuff but I have just walked into
this support role. I need help to get the ASP app working
ASAP!This error usually indicates that you have checked the "Force Protocol
Encryption" option using the Client network utility or set the following
registry key on the server.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\Client\SuperSocketNetLib
Encrypt == 1
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Enabling Replication Question

Can I enable replication from a different server that has Enterprise
Manager install than the one that hosts the SQL database without any
problems or side effects?
I cannot enable replication from my server (Server A) hosting SQL
Server because the registration name is (local) instead of the server
name. Yes I know I can delete the registration and re-register it
with the server name BUT my ERP software vendor warns me by doing I
will break some of their core processing functionality because it
relies on the SQL Server registration name.
So to avoid this problem my though would be to enable replication from
(Server B) that has SQL Server Enterprise Manager installed and points
to Server A. My question is this - Can I successfully enable
replication through this process or will I encounter other problems or
create other issues?
I'm running SQL Server 2000.
Thanks for any information, comments or generally better ideas!Hi,
You can register server A in the Enterprise Manager on ANY machine
that has Enterprise Manager (and network access) -- including server B
-- and set up replication, or any other SQL administration tasks, on
server A.
Ken
On Feb 21, 5:31 pm, "dfrazell" <dfraz...@.estoneworks.com> wrote:
> Can I enable replication from a different server that has Enterprise
> Manager install than the one that hosts the SQL database without any
> problems or side effects?
> I cannot enable replication from my server (Server A) hosting SQL
> Server because the registration name is (local) instead of the server
> name. Yes I know I can delete the registration and re-register it
> with the server name BUT my ERP software vendor warns me by doing I
> will break some of their core processing functionality because it
> relies on the SQL Server registration name.
> So to avoid this problem my though would be to enable replication from
> (Server B) that has SQL Server Enterprise Manager installed and points
> to Server A. My question is this - Can I successfully enable
> replication through this process or will I encounter other problems or
> create other issues?
> I'm running SQL Server 2000.
> Thanks for any information, comments or generally better ideas!|||On Feb 21, 9:36 pm, "KenJ" <kenjohn...@.hotmail.com> wrote:[vbcol=seagreen]
> Hi,
> You can register server A in the Enterprise Manager on ANY machine
> that has Enterprise Manager (and network access) -- including server B
> -- and set up replication, or any other SQL administration tasks, on
> server A.
> Ken
> On Feb 21, 5:31 pm, "dfrazell" <dfraz...@.estoneworks.com> wrote:
>
>
>
>
>
So to clarify - I can enable replication on Server A from Server B
regardless of the SQL registration name of Server A without any side
effects?
Thanks - Dave|||As the server name of Server A will be the correct one when looking from
Server B's enterprise manager, I see no problems here provided you have a
sysadmin user. Some of the settings are local to the ServerA though (eg the
distribution working folder) so you might want to use a remote desktop as
well to set up the necessary share.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com