crypto service provider

crypto service provider

Postby jreeves1 » Tue 23 Oct 2012 21:48

visual studio 2012 .net4
blended solution with projects in vb and c#
running postgres with separate database for each user SSL
using dev express reports
connecting to postgres with devart
this one user has 2 workstations....one runs the reports with no problem, the other returns an error on every report: 'Couldn't acquire crypto service provider context.'

emptied the folder at \program data\microsoft\crypto\rsa
the files were re-created. same error on running reports.
help.

-Jim
jreeves1
 
Posts: 4
Joined: Tue 23 Oct 2012 21:41

Re: crypto service provider

Postby Pinturiccio » Tue 30 Oct 2012 13:42

We could not reproduce the issue. Could you please provide additional information?

jreeves1 wrote:this one user has 2 workstations....one runs the reports with no problem, the other returns an error on

1. What do you mean when you say 'workstations'?
2. The number of applications and the number of computers on which you run this application.
3. The number of OS users and database users that are used for reproducing the issue.
4. You connect with one database user to two different databases. Am I right?
5. Your OS version. If you run the application on several computers, please tell us all OS versions.
6. dotConnect for PostgreSQL version and edition. You can check the version and edition of dotConnect for PostgreSQL by selecting About dotConnect for PostgreSQL from the PostgreSQL submenu of the Tools menu in Visual Studio. You will see the dialog box displaying the version and edition of dotConnect for PostgreSQL;
7. If you use only the 2nd workstation, is the issue reproduced?

If possible, please create and send us a small test project with the corresponding DDL/DML scripts for reproducing the issue.
Pinturiccio
Devart Team
 
Posts: 2020
Joined: Wed 02 Nov 2011 09:44

Re: crypto service provider

Postby jreeves1 » Wed 02 Oct 2013 19:32

this has popped up again.
the end user is running windows vista.
jreeves1
 
Posts: 4
Joined: Tue 23 Oct 2012 21:41

Re: crypto service provider

Postby Pinturiccio » Fri 04 Oct 2013 13:55

Please tell us your version of dotConnect for PostgreSQL.
Pinturiccio
Devart Team
 
Posts: 2020
Joined: Wed 02 Nov 2011 09:44

Re: crypto service provider

Postby jreeves1 » Fri 04 Oct 2013 14:03

dotConnect for PostgreSQL 6.2.77.0
Devart.Data 5.0.536.0
jreeves1
 
Posts: 4
Joined: Tue 23 Oct 2012 21:41

Re: crypto service provider

Postby Pinturiccio » Fri 04 Oct 2013 14:43

Please provide the following information:
1. Is the issue reproduced in the same way as you wrote in your post a year ago?
2. Tell us the kind of your application. Is it a Windows application, or a Windows service or ASP.NET application, running on IIS, or something else?
3. Does the user account, that runs the application, have the privileges to read and write to the "\program data\microsoft\crypto\rsa" folder?
4. the text and stack trace of the exception.
Pinturiccio
Devart Team
 
Posts: 2020
Joined: Wed 02 Nov 2011 09:44

Re: crypto service provider

Postby jreeves1 » Fri 04 Oct 2013 14:54

the error message is the same as the original post.
The application is a windows desktop app that uses Devart to connect to a postgresql server.
The user is running as admim.
The process we use to control distribution of updates and populate pdfs require read/write into both the program files and program data folders.
The text of the error is "Couldn't acquire crypto service provider context."
When this error came up last year, we deleted the files in the \crypto folders and the issue went away. I now have 2 different users with the same issue. In most cases, the user has other workstations that run with no problem, but will have 1 or 2 workstations that error with this issue.
jreeves1
 
Posts: 4
Joined: Tue 23 Oct 2012 21:41

Re: crypto service provider

Postby Pinturiccio » Fri 04 Oct 2013 16:17

Probably, the reason of the issue is the following. The user that runs the application may be doesn't have permissions for reading/writing to the 'ProgramData\Microsoft\Crypto\RSA' folder on the computer, where the issue is reproduced. This is the folder, which Windows creates to store keys for SSL connections. A user that created this folder, has access to it. If some other user account worked with SSL encryption before on this computer, the folder is already created and the current user does not have access to this folder.

The issue can be solved in two ways:
1. Delete the 'ProgramData\Microsoft\Crypto\RSA' folder. When SSL is used, new folders are created in the 'ProgramData\Microsoft\Crypto\RSA' folder, and current user will have rights to access them. However, if you have several users on this computer, other user accounts will not have access to these folders and won't be able to work with SSL.
2. Give full access rights to these folders for the user that use your application. This should solve the issue.
Pinturiccio
Devart Team
 
Posts: 2020
Joined: Wed 02 Nov 2011 09:44


Return to dotConnect for PostgreSQL