Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unable to find a dll in system32

Status
Not open for further replies.

agentwalker

Programmer
Jun 10, 2007
31
GB
I've got a VB6 app that uses a dll called "decrypt" which basically just decrypts some licence keys.

This dll sits in the windows/system32 folder and i'm referencing it in VB6 using the following.

Private Declare Function IsLicenseKey Lib "decrypt.dll" Alias "IsLicenseKey" (ByVal chrLicenseKey As String, ByVal intKeyLength As Long) As Long


The problem i'm having is that for some reason i'm now getting the following error in the event log

The VB Application identified by the event source logged this Application Utility: Thread ID: 3380 ,Logged: Runtime Error
Number:48
Description:File not found: decrypt.dll
ProcName:Utility.LicenceKeys.CheckLicenseKey
Source:Utility
AppVersion:1.1.1
AppPath:C:\rdev\app\Com\

This has worked no problem until a few days ago.
The decrypt.dll is defiantly in the system32 folder and because its not a COM dll you can't register it using regsvr32, you just place it in there and the app can usually find it/

Anyone have any ideas and suggestions ?

Cheers
 
This error is defined in the Help files as being caused by one of the following:
- The file isn't DLL-executable.
If the file is a source-text file, it must be compiled and linked to DLL executable form.

- The file isn't a Microsoft Windows DLL.
Obtain the Microsoft Windows DLL equivalent of the file.

- The file is an early Microsoft Windows DLL that is incompatible with Microsoft Windows protect mode.
Obtain an updated version of the DLL.

- The DLL references another DLL that isn't present.
Obtain the referenced DLL and make it available to the other DLL.


- The DLL or one of the referenced DLLs isn't in a directory specified by your path.
Move the DLL to a referenced directory or place its current directory on the path
 
Yep, that'd be the explanation I plump for. Agentwalker, if you should be able to use the Dependency Walker to verify this (under Visual Studio 6.0 Tools)

That's versions 1.0. The latest version should be available here:
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top