[FIXED] Error when launching program

Posts   
 
    
mike
User
Posts: 24
Joined: 02-Oct-2003
# Posted on: 02-Oct-2003 18:03:02   

Hi, We just purchased the pro version today and installed it. When we launch the program we get an exception error:

CryptoAPI cryptographic service provider (CSP) for this implementation could not be acquired

can anyone tell me what may be causing this?

Thanks mike

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 02-Oct-2003 18:09:10   

hmmm. That error is related to the RSA crypto provider not being able to read the key-set of your user profile, which means you are not logged in, (as with f.e. the ASPNET user).

There are a couple of questions I have to ask you: On the machine you have installed it, is there a group policy active of some sort that limits severily your rights on the machine? Did you install it on a network drive? Did the demo application run on your machine (if you have installed it) ?

I'll check what might cause this error to come up in other occasions than with a 'user' profile that is inaccessable.

Frans Bouma | Lead developer LLBLGen Pro
mike
User
Posts: 24
Joined: 02-Oct-2003
# Posted on: 02-Oct-2003 18:19:37   

Thank you for your help. I just realized I had to install it through the admin.

Thanks mike

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 02-Oct-2003 18:19:38   

Is this key present on your system when you log in? (open regedit) HKLM\SOFTWARE\Microsoft\Cryptography\Defaults\Provider Types\Type 001

It should have 2 values, Name and TypeName. TypeName should be RSA Full (Signature and Key Exchange).

When it can't load any provider it can't continue and will throw the exception you saw. The RSA crypto provider is required to validate the signature on the license file. Normally this should work on any machine with a user logged in.

Please let me know what your particular situation is. You can mail me directly on support@llblgen.com , which works a little faster than this forum.

Frans Bouma | Lead developer LLBLGen Pro
Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 02-Oct-2003 18:20:47   

mike wrote:

Thank you for your help. I just realized I had to install it through the admin.

Did it work then? It should work with a normal user too... odd. I'll look further into this.

Frans Bouma | Lead developer LLBLGen Pro
gez
User
Posts: 5
Joined: 02-Oct-2003
# Posted on: 02-Oct-2003 23:51:38   

Hello,

I think that the issue here may involve the effective rights issued a new user in 2003 server. Basically, read only access is the default for just about everything unless you are an administrator or equivalent or you belong to a group that has more assigned rights.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 03-Oct-2003 09:19:48   

gez wrote:

Hello,

I think that the issue here may involve the effective rights issued a new user in 2003 server. Basically, read only access is the default for just about everything unless you are an administrator or equivalent or you belong to a group that has more assigned rights.

Good point. I have win2k3 server on a partition on the testserver here, I will test it, this is the case. I'm not that fond of relying on 'install as administrator', although vs.net does that too afaik.

Frans Bouma | Lead developer LLBLGen Pro
Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 06-Oct-2003 17:04:56   

This issue is related to the licenser bug which was using the wrong keystore. Patch will be uploaded tomorrow, October 7th.

Frans Bouma | Lead developer LLBLGen Pro
gez
User
Posts: 5
Joined: 02-Oct-2003
# Posted on: 06-Oct-2003 23:21:31   

Thanks for that.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 08-Oct-2003 10:27:27   

The fix for this problem is now available (October 7th upgrade).

Frans Bouma | Lead developer LLBLGen Pro