Below are Loaddata to DB tools that have been used since the Windows xp era.
The executable name xxxxx.exe is unknown.
It's a tool that I've used for many years, and I think the program itself has no problem.
The action is to upload the data in the input file to the database.
Recently, when I ran 'xxxxxx.exe' on Windows xp, the following error was displayed and I couldn't process it.
Access violation at address 0048 DCBF in module 'xxxxxxx.exe'.Read of address00000016.
In four patterns, data upload processing is performed to separate databases using the same program for each input file.
Two patterns (2DB) processing was normal and two patterns (2DB) processing errors occurred.
Determined that it occurred when there was insufficient memory and
Migrated EXE, dll, and required data from Windows xp to Windows 7.
After running 'xxxxxx.exe' on Windows 7,
The error is displayed in the same pattern as Windows xp and cannot be processed.
Replacement of previously backed up EXE and dll files also results in an error.
PC optimization, error checking, defragmentation, virus checking, etc., and
It was temporarily cured, but it cannot be handled with the same error again.
This time 3 patterns (3DB) processing is normal and 1 pattern (1DB) processing error.
PC optimization, error checking, defragmentation, virus checking, etc. will not help.
Read of address00000016.
if programming corrupts the database.
Do you experience errors such as
There is no program source, so I can't debug it.
I hope I can use the tool to avoid errors as much as possible.
How can I deal with this?
windows
Attach the debugger when the error occurs to determine where the cause is.As already mentioned, it is expected that there is a problem with the tools used in approximately .
Normally, you should debug and fix it.
I think it's a question when you can't do that.In that case, it may work by setting the settings on the Compatibility tab of the executable properties.
From a different perspective, ultimately
Read of address00000016.
Although the error is in , it is possible that the data was corrupted because it caused data corruption.In that case, after several runs, the Fault Tolerant Heap may act to avoid heap destruction.
© 2024 OneMinuteCode. All rights reserved.