Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
CRYPTPAK.DLL-can't load under Win7-32 (not the obvious p
Message
From
23/05/2012 05:52:18
 
 
To
23/05/2012 02:20:31
Al Doman (Online)
M3 Enterprises Inc.
North Vancouver, British Columbia, Canada
General information
Forum:
Visual FoxPro
Category:
ActiveX controls in VFP
Environment versions
Visual FoxPro:
VFP 6 SP3
OS:
Windows 7
Miscellaneous
Thread ID:
01544106
Message ID:
01544123
Views:
38
Thanks for the response Al. The DLL (same copy) works fine elsewhere. The problem machine isn't running any other "system checker" of any kind (a thought I had too). I did try (just for kicks) to rename it but no joy there either. Any other ideas?

BTW Al, your name sounds familiar to me... have we met?

-Arne


>>Hi,
>>
>>Hoping someone can help with this.
>>
>>This is a legacy system written in VFP6 I haven't gotten around to updating to 9.
>>
>>I'm trying to register CRYPTPAK.DLL (which used to be a fairly common VB and Visual FoxPro encryption DLL). Never had a prob on any other install but:
>>
>>
>>(ADMINISTRATOR CMD Window)
>>
>> c:\windows\system32>regsvr32 cryptpak.dll
>>
>>(DLL is in the dir)
>>
>>I'm getting the msg:
>>
>>"The module "cryptpak.dll" was loaded but the entry-point DLLRegisterServer was not found.
>>
>>Make sure that "cryptpak.dll" is a valid DLL or OCX file then then try this again."
>>
>>Normally, this happens if there's a permissions error I *think*. Same setup works fine on many other machines running a mix of OS's.
>>
>>FWIW, the client system is running Norton (with Sonar) and I did try to disable Norton completely just to see. No joy.
>>
>>I also tried issuing "secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose" based on a forum suggestion but nada. Though that DID generate some interesting, but seemingly unrelated, errors in the log.
>
>If it's just one computer, is it possible the copy of the DLL is corrupted?
>
>On a quick Google, most of the hits seem to think cryptpak.dll is, or is part of, malware. Although you've disabled Norton, maybe something else thinks it's malware. Just for grins, maybe you could create a copy named something different e.g. CoolStuff.DLL, and try registering that.
arne@synercom-edi.com "There are no absolutes but this one."
President, synercom/edi - Event Ticketing Solutions
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform