Showing posts with label encryption. Show all posts
Showing posts with label encryption. Show all posts

Thursday, March 29, 2012

Error when using SSL encryption for SQL server 2000

Hi,
I am having trouble connecting to SQL server 2000 using SSL.
My environment is as follows:
1. Microsoft Certificate server running on a Windows 2000 server machine.
2. SQL Server 2000 running on a Win NT machine with SP6 installed. SQL
Server service pack 3a has been installed.
3. Client machine running Windows XP with SQL Server service pack 3a
installed.
We use a type 4 JDBC secure driver to connect to SQL server from our Java ap
plication running on the client machine.
We also setup the certificate as described in the article 276553 - HOW TO: E
nable SSL Encryption for SQL Server 2000 with Certificate Server.
The installation of the certificate was successful. However, when I tried to
connect to the SQL server using SQL Query Analyzer, I received the followin
g error message.
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Encryption not supported on SQL Serv
er
Thanks,
Chacko.Usually, you receive that error if you enable SSL from the client and the
server doesn't have the certificate.
But, the bad news is you won't be able to use SSL with a type 4 Java driver.
The implementation of protocol encryption requires the driver to access
SSL. In
particular protocol encryption uses SSL APIs implemented in NT. Type 4 JDBC
drivers have a problem in that they are not allowed to directly call system
dlls. There is no library in Java 1.4 or below that emulates the protocol
encryption behavior of SSL from Windows NT.
If your JDBC application requires protocol encryption to SQL 2000,
you will have to use alternate method of encryption such as IPSEC or use a
suitable SSL enabled Type 3 JDBC Driver.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi Kevin,
Thanks for your response.
We did generate and install the certificate using the web browser and not us
ing MMC since it is a Win NT 4.0 box. When we look at the certificate on the
database server machine via the IE properties applet, the certificate shows
up fine as described in th
e Microsoft setup document. So, I am not sure where I am going wrong. Is the
re any way to trouble shoot this issue?
Also, we are not even trying the connectivity with the type 4 JDBC driver ye
t even though that is what we want to do ultimately. However, right now we a
re using Query Analyzer on the client machine to test the communication. We
get the error when we try a
nd login to the database via Query Analyzer.
About the type 4 JDBC driver, the documentation from i-net OPTA type 4 JDBC driver says
that it supports SSL for SQL Server 2000. Am I misunderstanding something here? You ca
n find information about i-net OPTA at [url]http://www.inetsoftware.de/English/Produkt[
/url]
e/OPTA/default.htm
Your thoughts are greatly appreciated.
Thanks Kevin.
Chacko.

Error when using rskeymgmt to backup encryption key

When I run the rskeymgmt program to backup the encryption key, I get the
following error:
The Report Server Windows service is not responding to RPC requests. The
service may not be running.
I have checked, and the service is running. We are using SQL Server 2005
sp2. The command I am using is:
rskeymgmt -e -fc:\rskey\rsdbkey.txt -psomepassword
Any ideas why this is failing. I was able to run the program some time ago.
Thanks.On May 2, 11:50 am, "Tim Kelley" <tkel...@.company.com> wrote:
> When I run the rskeymgmt program to backup the encryption key, I get the
> following error:
> The Report Server Windows service is not responding to RPC requests. The
> service may not be running.
> I have checked, and the service is running. We are using SQL Server 2005
> sp2. The command I am using is:
> rskeymgmt -e -fc:\rskey\rsdbkey.txt -psomepassword
> Any ideas why this is failing. I was able to run the program some time ago.
> Thanks.
This link might be helpful:
http://www.technologyone.org/new-6210113-3731.html
Regards,
Enrique Martinez
Sr. Software Consultant

Tuesday, March 27, 2012

Error when starting SQL SERVER service

Hello all,
When i am starting SQL Server, I am getting an error saying "Encryption Error When starting SQL Server service.. on connecttionbopen.... " What could be the problem ?
Please help me with the steps..
Saiwhat are the log on properties of the sql server services on your server?
have u recently changed the password for the server?
or else try using some other protocol from client/server utility.|||hello Harshal,
Actually when i am logging in to the database using my regular user details i am getting this error. Infact i am not able to see the Properties of the SQL server from the Enterprise manager. When i right Click and select properties of the Service in E.M i am getting the same error.

I tried re-installing the SQL server in the same Directory.. But Still the problem hooks..

What should i do now ?

Sai|||RE:
...I tried re-installing the SQL server in the same Directory.. But Still the problem hooks..
Q1 What should i do now ?
Sai

A1 Much depends on the specific situation.

Some things to consider / investigate:

a If the server was previously functional; what environment changes may have been made prior to the server having the issue, i.e.(where any patches, development environments, upgrades, etc. applied)?

b If the server was previously functional; what was the nature of any activity performed prior to the server having the issue, e.g.(were there any peak / near peak resource utilization conditions present, where load tests, intrusion tests, etc., performed)?

{Somewhat similar issues on development machines may sometimes be traced to such things as corrupted / damaged registry keys and / or dlls. On occasion, the fix is relatively simple, but this is not always necessarily so.}

If inital efforts are unsucessful, and the time / resources to investigate in detail are not available, you may wish to consider completely reinstalling OS, MS Sql Server (from "scratch"). However, if the issue ultimately is caused by a misbehaving custom application or perhaps even failing hardware, it may well re-occur (until any underlying issues have been resolved).