Click here to Skip to main content
15,885,546 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Hi all,

A customer has called me to solve a problem in one old computer.

The original programmer is not working anymore so it is impossible to get in touch with him.

After starting the application shows an error message:

------------------------------------------
drvex32.dll
------------------------------------------
Error {2453312400-220159082-2187847450} in class definition.
------------------------------------------

It is a Windows XP computer.

I have no more information and googling for drvex32.dll or the shown number doesn't help...

The customer had a problem with the computer, cloned the HDD and worked with the cloned drive to install applications that were asked to reinstall at the windows XP start up...

I can access the original HDD.

It seems the only that happened is that they have powered off the computer several times without a UPS...

What would you do to try to solve the problem?

Thank you very much for your help! :thumbsup:

What I have tried:

- I've made a backup of the registry of the original hdd.
- I've tried to reinstall applications that failed.
- I've copied the MSJava.dll library as dependency walker said it was lacking.
Posted
Updated 24-Oct-17 3:23am
Comments
Richard MacCutchan 23-Oct-17 9:03am    
Without the source code of that DLL it is impossible to do anything.
ZurdoDev 23-Oct-17 14:14pm    
Do basic troubleshooting.

Log on with a different profile and test it.
Try it in safe mode.
Check event viewer for other errors.
Grant Everyone full control to any folders it uses.
Etc, etc.

1 solution

The customer managed to find the source code of the application...

At the end:

- The battery on the motherboard died.
- The original programmer had a function that was looking at a specific registry key and if the date specified there was bigger than the current date in the system the application locked itself...

The message that appeared was simply a hardcoded set of strings in a messagebox... and the suspicious DLL did not existed at all...


So removing that registry key has solved the issue...

:elephant:ing :sunshine:
 
Share this answer
 

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



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900