Re: Connection to SQL Server CE Windows Service via C# - Error 250

Hmmm. That really feels strange. I suppose that you could try the same
experiment, of a new database with a password to see if it's something
specific to your database or if it's really the password itself. You could
try SQLCE 3.5, too, if it does seem to be just the password.

Paul T.

"Blue Fish" <BlueFish@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8CCF2322-377A-4231-877E-F5361371D4A8@xxxxxxxxxxxxxxxx
Encryption is not specified in the connection string. This is SQL Server
Compact 3.1 (2005).

I am explicitly provinding the Data Source and Password attributes in the
connection string.

I have since created a new database, with an empty password. I am able to
connect to it via the windows service under the Local Service account.

However, I would like to have the database password protected.

"Paul G. Tobey [eMVP]" wrote:

Is encryption specified in the connection string? How are you requesting
access, user name and password explicit in the connection string?

Paul T.

"Blue Fish" <BlueFish@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D21D3EBD-9561-40A9-A21D-C2C62A5020A7@xxxxxxxxxxxxxxxx
Operating System: Windows XP Professional (5.1, Build 2600) Service
Pack 2

I'm using SQL Server Compact Edition as a private data store.

The reason I mentioned a permissions issue is that I can connect to the
same
DB via C# in a Windows application that is not running as a service
under
the
Local Service account.

So my theory was that the Local Service account is somehow restircted
in a
way that prevents it from accessing the appropriate encryption
mechanism
to
connect to the DB.

"Paul G. Tobey [eMVP]" wrote:

Funny, I'd assume that the problem is that the operating system
doesn't
support encryption. What is the connection string? What version of
Windows
CE is running and what's built into it?

Paul T.

"Blue Fish" <Blue Fish@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A3453930-4081-46F8-B488-337DDC5CC97E@xxxxxxxxxxxxxxxx
SQL Server CE 2005, Visual Studio 2005, C#

I have a windows service that I wrote that runs under the Local
Service
account. I cannot connect to my SQL Server CE database. Every call
to

_dbConnection.Open();

yields Error 25080 - The operating system does not support
encryption.
Now
I assume that the issue is permissions, but does anyone know of how
to
resolve this issue?








.

Relevant Pages

  • Re: Connection to SQL Server CE Windows Service via C# - Error 250
    ... This is probably 3rd time I am hereing to a case the encryption related ... In SQL CE v3.1 case, can you try using Crypto API under the same credentials ... specific to your database or if it's really the password itself. ... connect to it via the windows service under the Local Service ...
    (microsoft.public.sqlserver.ce)
  • Re: Connection to SQL Server CE Windows Service via C# - Error 250
    ... specific to your database or if it's really the password itself. ... connect to it via the windows service under the Local Service account. ... way that prevents it from accessing the appropriate encryption ... I have a windows service that I wrote that runs under the Local ...
    (microsoft.public.sqlserver.ce)
  • Re: Connection to SQL Server CE Windows Service via C# - Error 250
    ... Paul T. ... specific to your database or if it's really the password itself. ... connect to it via the windows service under the Local Service account. ... way that prevents it from accessing the appropriate encryption ...
    (microsoft.public.sqlserver.ce)
  • Re: Connection to SQL Server CE Windows Service via C# - Error 250
    ... Paul T. ... specific to your database or if it's really the password itself. ... connect to it via the windows service under the Local Service account. ... way that prevents it from accessing the appropriate encryption ...
    (microsoft.public.sqlserver.ce)
  • Re: Newbie - Is this Reasonable?
    ... because this hash is stored in the database. ... So you use PKCS5v2 to generate a key hash from a salt and the user's passphrase, then store the salt and the hash in a database. ... are even more critical in database applications because the payoff from tampering with selected fields may be much higher, fields tend to be fixed-length so it's easier to tamper with them in a meaningful way, and databases lend themselves to off-line analysis, so the attacker can marshall more resources and take more time to attack your system. ... You're using a stream cipher for encryption. ...
    (sci.crypt)
Loading