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

Sunday, March 11, 2012

Errors in the encryption library Error

I'm getting the following error:

Error 74 Errors in the encryption library: Failed to encrypt sensitive data. Possibly the encryption key is inaccessible because of improper service account change. 0 0

I've tried deleting the database and directory from the data directory. This doesn't fix it. I still get the same error. However if I change the name of the target and deploy the problem is resolved.

I'd like to retain the original name for the database if I can. Could somebody explain why it's got this problem with the original name and how I go about fixing it. Thanks.

Mark

Try backing up all rest of the databases on your server. Then stop the service and delete everything from the data directory.
You can see the location of your data directory in DataDir server property.

Start the service, restore rest of your databases and at this point you should be able to depoy your database under original name.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Wednesday, February 15, 2012

Error: SQL Server Requires Encryption On

Hello All,

I have a commercial application built for Pocket PC's that connects to SQL Server 2005 via TCP/IP over wireless networks. In installations for our sales people we installed SQL 2005 Express on their notebooks for demonstrations. In one of these installs we are getting the following error message: "An error occurred - SQL Server requires Encryption On". We do not use encrypted connections and I have verified encryption is turned off in the Options tab in SQL 2005 login screens.

Here is the connection string we use in the app.config file on the Pocket PC's:
<add key="connStr" value="Data Source=192.168.0.19,1433;Initial Catalog=SQL0018;User ID = User01;Password=PW01"/>

Other apps on the notebook are connecting to this same SQL Server without any issues. Thank you in advance for any help here,

Jack

From the description and the error message that you copied, the failure seems to be coming from the client (Pocket PC software).

It seems like you are indeed trying to connect to a SQL Server instance that requires encryption, it may be possible that the settings on that particular instance were changed but the service was not restarted.

I would also recommend asking on the SQL Server data access forum in case they have a better answer: http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=87&SiteID=1

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

|||

Thanks for the reply Raul, but the problem turned out to be a boolean in the registry on the machine running SQL Express. Here is the post in SQL Server Data Access forum that solved it.

The registry key that controls this behaviour is below (assuming express is the first SQLServer you installed on the machine). If that key is set to 1, then set it to 0 and it should fix your problem.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib\ForceEncryption

Thanks to John for that post.

Jack

Error: SQL Server Requires Encryption On

Hello All,

I have a commercial application built for Pocket PC's that connects to SQL Server 2005 via TCP/IP over wireless networks. In installations for our sales people we installed SQL 2005 Express on their notebooks for demonstrations. In one of these installs we are getting the following error message: "An error occurred - SQL Server requires Encryption On". We do not use encrypted connections and I have verified encryption is turned off in the Options tab in SQL 2005 login screens.

Here is the connection string we use in the app.config file on the Pocket PC's:
<add key="connStr" value="Data Source=192.168.0.19,1433;Initial Catalog=SQL0018;User ID = User01;Password=PW01"/>

Other apps on the notebook are connecting to this same SQL Server without any issues. Thank you in advance for any help here,

Jack

Move to Sql Server Express forum. Thanks!