Runtime Errors

Hi there

I am involved in a product that has been known to develop some Runtime Errors. Many have been sorted out by the developer, but I have to search the net sometimes for resources. Does anyone here know of some good sites that help with Runtime Errors - do they give clear indications where the problem might be.

The one I have had the moment is -

Runtime Error 53

File Not Found.

Like I say I am not the developer of this and know absolutely nothing about the program as such. My job is to try and help research - when he is not about which i often - what may have happened. Obviously with the above a crucial file has gone missing, but it is not defined. I am not sure if it is a .dll file or a more simplistic file. Users do't seem to have a reason why it happens. Sometimes they just open it and it appears, so I can only say reinstall the software, which works. Users FTP files into their database that sits locally on their own desktop.

If anyone knows of a really good and reliable site that explains these things, I would be so so interested.

Cheers

I presume this is a VB program, in which case there isn't a anywhere I know of that can help with 'decoding' the error messages. This one means that a file the program was using (not likely to be a DLL, maybe a text file or the database file).

We can often help here find the cause and solution, but an important thing is to handle the errors in the program, rather than just let the default error messages show.

An error handler doesn't need to be complex (just a messagebox with 'Retry' / 'Cancel' is enough for some cases), but can be a huge improvement in situations like this.

If you add an extra little piece of info to the message you can also tell exactly which line the error occured on, and therefore the likely causes (and hopefully solution). This info is ERL, or Error Line number. Unfortunately for this to work you need to put numbers at the start of each line of code, but if you use something like MZTools (link below) then it can put all the numbers in for you.

Do you have access to the source code for this program?

Hi there

I am not the developer, and to be honest, I know nothing about the code.

The program is launched by an .exe file, and it appeared when trying to launch it. What I want to know really is it looking for a file or a .dll. If so, and there are hundreds involved in the database, where am I likely to find the cause?

It might not be possible, but with so little text to go on as part of the runtime error, it is like finding a needle in haystack.

Would a missing .dll file cause the error, or a missing .exe file, or any other file? I am rubbish at this, but my guess is that if you try and launch a .exe file and you get that message, then the .exe file is missing (I have no idea how that would happen) but it does work after reinstalling the CD again, containing .dll files, .exe files. cdx files.

So.........does a particular file cause the error?

(I know this has been already partly answered and copied an pasted this from another forum I posted on.)

in tools in set up factory you can scan an .exe for all its dependancys (files the .exe relys on ) sounds like you want something similar if your not sure what files this exe relys on

It is usually caused by the program trying to open a file (text file or similar) that doesn't exist where it is expected to be. I've only ever seen that once for a DLL, and hundreds of times due to code not checking that the file exists before trying to read it/move it etc.

It could for example be that it is looking for a file called "c:\folder\file.txt", and if file.txt doesn't exist in c:\folder then the error will be generated.

It may be that a file that the program used gets deleted under certain circumstances (if there was bad data in it?), and re-installing the program is a way to re-create it. As the program works when re-installed it doesn't sound as if it is DLL related (as DLL's shouldn't get deleted, and can't be while being used).

Unfortunately without seeing the code (and without it having proper error handling) all we can offer is educated guesses.

Thanks for the great answer, makes sense. I wish it made some indication of what file was missing, as we could email that file out. Here is some additional information. (Ive posted this elsewhere, so ignore the bits you have answered. :D )

Remembering I have no idea how the program is written or specific folders etc, and being as layman as you can to me - I really don't mind - could it be a .dll file causing that error or one of the others types of file. All of the .dll files are located in System32 - for XP obviously - so could it be one of those causing the problem. There is a major one called foxlink.dll - I think its major - amongst others that we get people to unregister when the uninstall the program.

The .exe file and other files linked to the database sit locally at c:\program files\

As the problem happens when the product is launched from a desktop shortcut, and the .exe files are sat locally, is it likely that the file not found is in that folder and not the system 32? Could it be the .exe file thats gone? It does appear when lauching the main program and other features that go with the product.

I know that I cannot test this now until I get another person report this, and it is very very infrequent, but would be great to have an idea of what it might be. It makes sense that it is an .exe file, but someone is free to call me a dilbert if that is not ever likely to be the cause! Presumably, and if it happens again, I should get them to search their local drive for .exe files.

If it is not an .exe file, does that mean the first bit engages as it were, but goes boobs up when it looks for the next command.

The long and short is, would I get Runtime Error 53 File not found if the .exe file was missing, or would I get something even worse if no .exe file was present.

There is also a .ini file that sits on the c:drive pointing to the location of the main folder. Could that be something that could have gone missing to?

Cheers for your help guys, I find this all facinating without actually be 100% certain of what I talk about !! :afrog:

I'm glad you are intrigued - that's the best way to learn!

It won't be the EXE file missing, as the error happens inside the EXE.
I doubt it is a DLL, as explained above.
The INI file is likely to be the culprit, I'd recommend checking it is still there next time this occurs (and the same for the files you expect to be in "Program Files").

Quote:

---

Originally Posted by UK GENT

The .exe file and other files linked to the database sit locally at c:\program files\

As the problem happens when the product is launched from a desktop shortcut, ...as opposed to actually starting up the exe itself???

---

Could it be that your shortcut has its "Start in" directory improperly pointing somewhere?

Perhaps pointing it to the directory that contains the actual .exe will help?

Cheers for all your help, and you have been understanding of a person who does not write the code.

The .ini file could be the culprit and i'l check that is happens again. If it was any other file held with the folder that sits in Program Files, id be stuffed giving advice to customers over the phone, as there are at least a hundred files within the named product folder.

What ever causes it to not launch the software, or an optimiser that comes with the software, would seem likely to be the.ini file.

Any more suggestions would be appreciated.