CryptAcquireContext - returning file not found

Question

2.00/5 (1 vote)

See more:

I used your winaes class for the crypto api and it works great on my machine and a windows server 2003. But for some reason on the clients machine, it fails to acquire a context. Its reporting file not found.

Yet the Microsoft RSA and AES crypto provider is there in the registry, and I see its path.

It's running on a 32bit machine and the path is just the "dll" name rsaenh.dll...on my server 2003 vm it works (yes we have to use this old server)...

anyway, any insights as to why windows would report the file not found?

We've change the path to directly point to the .dll still no dice...

I realize its been a while but maybe you're more familiar with the cryptoapi and could shed some light.

Thanks,

Bitslayer

Posted 15-May-14 10:53am

bitslayer

Add a Solution

Comments

[no name] 15-May-14 19:26pm

You need to ask that author of that class. They would know more about their code than we would. http://www.codeproject.com/Articles/34508/WinAES-A-C-AES-Class

Code-o-mat 16-May-14 8:04am

You sure your process' bitness and the DLL's bitness is the same? I believe e.g. if you try to load a 64 bit dll into a 32 bit process you will get "file not found" (i had to find this out the hard way myself). I might be remembering wrong though...

KarstenK 16-May-14 8:33am

some combination wont work on some windows versions. It is a bit tricky.

Show the code plz ;-)

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)