Runtime Errors, The Complete Guide  

How to Fix Runtime Errors

Runtime Errors - Everything You Need To Know

 

"A runtime error is an error that a computer encounters while attempting to run a program. It means that a set of instructions given to it has not been carried out properly."

A runtime error usually allows programs to run to completion, while stop errors cause programs to cease running and compile errors occur when the source code of a piece of software is being complied into executable binary files.

 

Runtime errors can be caused be a variety of sources, and can occasionally be challenging to decipher. However, with a little bit of research and thought, a solution to most runtime error problems can be found.

For example, computers commonly access many different types of hardware when running the millions of programs that are available to users. Some programs access printers, others access web-cams, and others may access entertainment systems. A failure in any component of the devices has the potential to cause a runtime error.

Some runtime errors can cause unexpected results and render a program unusable. Others may allow programs to run to completion leaving a cryptic message and error code, but otherwise appear to function normally.

Hardware and Software Incompatibility

 

Apart from hardware failure other sources of runtime errors are both hardware and software incompatibility. For a wide array of reasons, some types of hardware conflict with other types. The same applies to software: some refuse to work at the same time. Errors and incompatibility problems between early mice and printers were common, for example, because each shared a serial port.

Beta Software Development

Yet other runtime errors may be caused by a poorly written or incomplete software program. It's not hard to write basic computer programs in C or C++, Java or many other languages and compile them. Runtime errors are commonly encountered in the testing and development of software. The timing of runtime errors sometimes has value, giving software programmers and developers clues as to the source of problems. The specific error message produced is also useful.

Slow Running Web Scripts

Scripts in pages on the Web are notorious for causing runtime errors and poor performance. Often a pop-up window is displayed notifying the user of a runtime error. These errors often won't cause the computer to slow down or perform poorly on their own. However, displaying a pop-up notification with every runtime error that occurs when navigating error-prone websites becomes tedious. Depending on the operating system and web browser being used, script runtime error notifications may be turned off, along with script debugging.

Runtime Errors Caused By Malicious Software

There are all sorts of different types of viruses and other software authored by people with nefarious intentions. Malware, scum-ware and adware are some of the names given to software of this type. Malware may cause runtime errors by design or because it is poorly written. The performance of most computers can be severely compromised if they are not rendered completely unusable when infected with malicious software. It should be noted that the majority of runtime errors encountered are harmless.

Spelling Variations

In various literature runtime errors are also known as run time errors and run-time errors depending on the source and type of computer described. Runtime errors can occur in any type of computer.

 

Common Microsoft Windows Runtime Errors

Windows is the most widely used computer operating system in the world. Many of the different runtime errors commonly encountered will be with Windows. Fortunately, Windows also provides some of the best documentation.

Check For Latest Windows Update

Computers running later versions of Windows have the ability to automatically check for updates. Users have the ability to change these settings. An out-of-date operating system is a potential cause of several runtime errors and a good place to attempt their elimination.

To determine whether a computer running Windows 7 has the latest Windows update installed click on the "Start" button and enter "Update" in the search box. Choose "Windows Update" from the list provided. When the window opens click on "Check for updates" on the left hand side.

Check Memory Usage

A computer that does not have the recommended amount of RAM to run programs may produce runtime errors. Most software providers provide minimum recommended RAM amounts in software descriptions and literature. Ensure a computer has enough RAM installed to support the execution of desired programs. Hard drives are another type of memory. A computer may also encounter runtime errors if it runs out of hard drive space or comes close to it. Upgrades to CPUs and other hardware may also aid in the elimination of runtime errors.

To determine how much of its hard drive space a computer is using click on the Windows "Start" button then click on "Computer". When the window opens right click on the C: drive and select properties.

Under the "General" tab and pie chart showing the amount of hard drive space being used is displayed.

To check how much RAM is being used press CTRL-ALT-DELETE and click on "Start Task Manager" When the dialogue box opens select the "Performance" tab. This displays the percentage and net amount of a computer's CPU and RAM resources are being used in real time. High usage numbers above consistently above 90% may cause runtime errors. Upgrading hardware is a practical and easy solution to this problem.

A memory leak is a condition where a program uses a location in RAM and then fails to clear it once finished. This results in an ever-growing amount of memory that becomes tied up. This situation can result in runtime errors. Memory leaks in third-party software are difficult to resolve. Contacting the software vendor is the best option.

Check Status And Error Logs

Different computers have different ways of keeping track of errors that occurring and endeavoring to prevent them or reduce their incidence in the future. When Windows 7 encounters a run time error the default setting is that a dialogue box asking the user if they would like a report to be sent to Microsoft is displayed. An error report is also generated.

To access the error report of a computer running Windows 7 click on the "Start" button and then click on "Control Panel" under the heading Systems and Security. When the window opens scroll down and click on "Review computer's status".

This will provide a listing of errors the computer has encountered and reports that have been sent to Microsoft.

Update Antivirus Software

New viruses are popping up all the time. Having effective antivirus software is essential. Microsoft Security Essential is available free of charge and detect and remove almost all types of viruses and malware.

 

Remove Unnecessary Software

Many computer users may have dozens of unused programs cluttering their hard drives. Even worse, many program load into a computer's start menu, stealing precious system resources and possibly acting as a root cause of runtime errors. Programs running in the background may also conflict with programs users wish to run.

To remove software from a computer running Windows 7, click on the "Start" menu and then enter "run" in the search box. Select "Run" from the available choices. In the small dialogue box enter exactly "msconfig" and click "OK" or press enter. In the "System Configuration" Window that opens choose the "Startup" tab.

This will display a listing of programs that the computer loads automatically upon start-up. Many software vendors design installation packages to automatically place their programs in users' "Startup" menus in hopes of gaining visibility and encouraging use. From the list displayed uncheck programs unnecessarily loaded at start up.

List Of Microsoft Windows Runtime Error Codes And Their Meaning

Runtime Error 3: "Return Without GoSub"

Unless encountered in the development of software, users seeing this message are either dealing with corrupted files or shoddy software. Reinstalling the program, restarting the computer and closing background programs may help to solve this issue or identify its source.

Runtime Error 5: "Illegal function call"

This may be caused by a number of programs. The first step is to determine if any updates are available for the software and to uninstall it, close all background programs and restart the computer, reinstall the software and then restart again. If the runtime error is still encountered contacting the author of the software is recommended.

Runtime Error 6: "Overflow"

Another runtime error caused by various types of software. Determine if the latest updates for the software are installed and then close all background programs. Reinstall the software and restart the computer. At this point, if runtime errors are still encountered contacting the programs' creator is the only alternative.

Runtime Error 7: "Out of memory"

Standard memory deficiencies can cause this error code. In many cases adding more RAM or a larger hard drive may solve the issue. It is not impossible for programs to have memory leaks or for memory to go bad: both RAM and files stored on a hard drive. All of these issues have the potential to cause this error.

Runtime Error 9: "Subscript out of range"

Error code 9 may be generated by a number of programs in different situations. Restarting the computer, reinstalling the software, closing all background programs and observing the results may provide answers. Otherwise, contacting the author of the software is the best option.

Runtime Error 10: "Duplicate definition"

Different programs depend on various types of definitions. The presence of duplicates may generate this message. Checking for the latest updates and reinstalling the software, restarting the computer and closing background programs may solve this issue, otherwise contacting the program vendor is recommended.

Runtime Error 11: "Division by zero"

Of course, dividing by zero results in infinity and is not allowed by computers. Ensure software is running the most recent updates and reinstall if the problem persists. Closing background programs that may be causing conflicts may also solve this error.

Runtime Error 13: "Type mismatch"

This is another common error that can often be solved by checking for the latest version of the software, reinstalling the software, re-starting the computer and closing background programs. Make sure the computer has enough RAM installed and the operating system meets the software vendor's recommendations.

Runtime Error 14: "Out of string space"

Runtime error 14 may be generated by number of different programs. Ensuring the software has been updated with the most recent version, reinstalling it, restarting the computer and closing background programs often solves this error. Software vendors may be able to provide solutions if available.

Runtime Error 16: "Expression too complex"

Unless this error has occurred in the development of software it suggests corrupted files or poorly written code. Installing the software from scratch, restarting the computer and closing background programs may help in some instances. Program authors may be able to provide information as well.

Runtime Error 17: "Can't perform the requested operation"

First, check to make sure the program running is the latest version. Removing and reinstalling the program causing the runtime error code 17, as well as restarting the computer and closing other programs running may also be of aid. Software developers may be able to provide information too.

Runtime Error 18: "User interrupt occurred"

Some programs may produce the error when CTL-ALT-DEL or CTL-BRK are pressed. Contacting the program vendor and checking for the latest updates may help. Reinstalling the software, restarting the computer and closing potentially conflicting background programs may help solve the error problem as well.

Runtime Error 19: "No resume"

The "No resume" error may be caused by a number of programs. Checking the vendor's website for fixes or updates may solve the problem. Restarting the computer and closing background programs may help as well.

Runtime Error 20: "Resume without error"

Unless it occurred in the development of software, this error implies corrupted data or a poorly written program. Check for the most recent version of the program an upgraded if necessary. Try un-installing and reinstalling the program, restarting the computer and closing other potentially conflicting programs. Vendors may have answers if these fixes aren't successful.

Runtime Error 28: "Out of stack space"

A stack is a type of data storage scheme. Error code 28 may be solved by installing the latest program version or reinstalling the software and restarting the computer. Try closing background programs that may be conflicting as well. Program authors may have answers or fixes available.

Runtime Error 35: "Sub, function or property not defined"

An undefined definition suggests corrupted files unless encountered during program development. Ensure the software has the latest updates installed. Reinstalling the program, restarting the computer and closing concurrently-running programs may help too.

Runtime Error 47: "Too many DLL application clients"

This error can occur when the number of dynamic linked list application clients exceeds 50. Try reducing the number of clients. Closing terminate-and-stay-resident programs and other background programs may help solve this issue as well.

Runtime Error 48: "Error in loading DLL"

This indicates a problem with a dynamic linked list. Either it is missing, damaged or otherwise unable to run. Check for the latest software updates with the vendor. Reinstall the program, restart the computer and try again.

Runtime Error 49: "Bad DLL calling convention"

A convention used by the program does not match that of the dynamic linked list. Verify that the software is running the lattes update. Reinstalling the program, restarting the computer and closing background programs may help with error code 49 as well.

Runtime Error 51: "Internal error"

Contacting the software vendor and verifying that the latest version of the software that caused the error is installed, along with reinstalling the software, restarting the computer and closing background programs may help solve this issue.

Runtime Error 52: "Bad file or file name"

This error means that there is corrupted data or a file with a name that does not conform to naming conventions. Check for the latest program update. If that doesn't work installing the software again, restarting the computer and shutting down background programs may help. Otherwise contacting the program's author is the best option.

Runtime Error 53: "File not specified"

A program has attempted to call a file or dynamic linked list that is not in location specified. First, check for recent program updates and install them. If unsuccessful, try reinstalling the software from scratch, restarting the computer and closing concurrently running applications. Developers may have answers as well.

Runtime Error 54: "Bad file mode"

Unless encountered in the development of a program this means that software is out of date or possibly corrupted. Check for the latest updates and trying reinstalling the program. Then restart the computer and close background and terminate-and-stay-resident programs.

Runtime Error 55: "File already open"

In most cases Window will not allow files to be opened when they are in use by other programs. Try closing background and terminate-and-stay-resident programs. Otherwise contacting the author of the program is the best solution.

Runtime Error 58: "File already exists"

A program is trying to create a file with a name that already exists. Reinstalling the software and closing concurrently-running programs may solve this problem. Program vendors may have solutions available as well. Check for the most recent program updates.

Runtime Error 59: "Bad record length"

Unless users find this error when developing programs, checking for the latest updates and reinstalling the software is a good first step. Restart the computer and close background programs as well. Software developers may have solutions available as well.

Runtime Error 61: "Disk full"

This means that a hard drive or other drive is full. Try deleting programs or installing a larger storage device.

Runtime Error 62: "Input past end of file"

Ensure the program is updated with the latest version. Try reinstalling the software, restarting the computer and closing other programs. Companies selling software may have answers available on their websites or by contacting their technical support lines.

Runtime Error 63: "Bad record number"

This error can be caused by several programs. Check for the latest program updates. Reinstalling the software, along with rebooting the system and closing other programs may also help stop these errors from occurring.

Runtime Error 67: "Too many files"

Limits are placed on the number of files that may be opened at once. Try closing background and terminate-and-stay-resident programs. Updating to the latest software version may help as well.

Runtime Error 68: "Device unavailable"

A program is trying to access a device that is not connected, faulty or turned off. Check cables and power status of devices in question. Replace unusable hardware.

Runtime Error 70: "Permission denied"

Error 70 is produced when a program attempts to access a resource for which the user running it does not have authorization. In most cases, obtaining proper authorization and verifying credentials should stop these errors from occurring.

Runtime Error 71: "Disk not ready"

A program is trying access a hard drive or disk that is improperly inserted, offline or faulty. Check cables and device statuses. Make sure CDs and DVDs are inserted properly.

Runtime Error 74: "Can't rename with different drive"

Try updating the software causing error code 74 with the latest update. If that doesn't work, try reinstalling it, restarting the computer and closing background programs. If these steps don't solve the problem contacting the program vendor is the best option.

Runtime Error 75: "Path/File access number"

Check to see that the software is updated and running the most current version. Reinstalling the software, restarting the computer and closing programs running concurrently may also help. Program developers may be able to offer solutions as well.

Runtime Error 76: "Path not found"

The program is asking the operating system to look for files in a location that doesn't exist. If user-generated try another directory. Otherwise, try installing the latest program updates or reinstalling the software, restarting the computer and closing other programs. Vendors may have information with regard to the cause of error code 76.

Runtime Error 91: "Object variable or with block variable not set"

This program error may be caused by a number of different programs. Ensure the most current updates are installed. If this doesn't work, try reinstalling the software, reinstalling the computer and closing background programs. Software developers may have answers or fixes in place as well.

Runtime Error 92: "For loop not initialized"

This error has a number of potential causes. Make sure you are running the most recent version of the program causing error code 92. Restarting the computer or closing other programs may help solve this issue. Also, try removing and reinstalling the program. Software developers may have fixes in place or other information available as well.

Runtime Error 93: "Invalid pattern string"

Error code 93 has a number of possible sources. Update to program to the latest version, restart the computer and close background programs. If this doesn't work try reinstalling the program. Otherwise contacting the vendor is the best option.

Runtime Error 94: "Invalid used of null"

A null data set is empty. There are restrictions on how null data may be used. Try reinstalling programs causing this error and updating with available upgrades. Rebooting systems and closing possibly conflicting background programs may help as well. Software vendors may have fixes available or other solutions too.

Runtime Error 216: "At Address"

This error can occur with computers that are affected with the SubSeven Trojan virus. Users can scan their computer for this virus using this link. If the virus is present an antivirus program is required to remove it. Microsoft Security Essentials is one of several free antivirus solutions available.

Runtime Error 217

This error is associated with registries that contain too many entries and viruses. Scan your computer using reputable antivirus software if you encounter runtime error 217.

Runtime Error 321: "Invalid file format"

The program is trying to open a file with an unexpected format. If user-generated try opening a file with a different format. Updating the program to the latest version may help this problem as well.

Runtime Error 322: "Can't create necessary temporary file"

A drive or other storage device is unable to accept orders to store temporary files. Try deleting unnecessary files or installing drives with more available storage. Updating the program to the latest version or reinstalling it may solve these errors as well.

Runtime Error 400: "Form already displayed"

Several different programs could be the source of this error. Install the most recent updates. If that doesn't solve the issue, trying installing the program again from scratch, restarting the computer and closing concurrently running programs. Program authors may have solutions available as well.

Runtime Error 422: "Property not found"

A program is attempting access a property that is not available. This error may be the result of several problems. First, try updating software to make sure it running the most recent version. If that doesn't work try removing the program and installing it again. A reboot or closing other programs that may be conflicting may help as well.

Runtime Error 424: "Object required"

This error may occur when a data access object is improperly referenced or the data object files are corrupted or otherwise unavailable. Check to make sure that drives are properly installed and that disks are inserted correctly. Microsoft also offers specific support for runtime error 424.

Runtime Error 429: "ActiveX component can't create object..."

This error has a number of potential causes. Faulty drives or RAM could cause error 429 as could corrupted or out of date files. Update software with the latest version. If this doesn't stop the errors try restarting the computer and shutting other programs down. Program authors may have solutions available too.

Runtime Error 430: "Class doesn't support automation"

Unless encountered during software development this error implies that files or data has been corrupted due to faulty memory or storage, or that the program is out of date. Try updating the program to the latest version. If this doesn't halt the errors, try installing the program again, rebooting the system and closing background programs. The authors of the programs may have fixes in places as well.

Runtime Error 432: "File name or class name not found..."

The program is looking for a file or class that is not available. Unless encountered during the development of a program, trying reinstalling the software and updating with available upgrades to the latest version. Restarting the computer and closing other potentially conflicting programs may also solve error 432 problems.

Runtime Error 438: "Object doesn't support this property or method"

Try updating software to make sure the latest version is running. If that doesn't work removing the software and installing again from scratch may solve error 438 problems. Restart the computer and close other programs that may cause conflicts. Program developers may have answers as well.

Runtime Error 439: "Argument type mismatch"

Many programs have the potential to cause this error. Try closing other programs and reinstalling the software. Check for software updates and to see if the vendor has fixes in place.

Runtime Error 440: "Automation error"

Try reinstalling the program and checking for updates. If this doesn't work reboot the computer and close other programs. Software vendors may be able to offer solutions as well.

Runtime Error 442: "Connection to type library lost"

Simply restarting the computer and the program may solve this problem. Otherwise, check that you are running the most recent version of the software. Closing background programs may also solve error 442 problems.

Runtime Error 443: "Automation value doesn't have default value"

If developing software this error means that programmers must explicitly give specifications for properties or methods. Restarting a computer or the program may solve error code 443 issues. Try updating software to the latest version and closing other programs. Program writers may have solutions available as well.

Runtime Error 445: "Object doesn't support this action"

Error 445 may be fixed by reinstalling the program or checking that the most recent updates are installed. Rebooting the system and closing other programs may help solve these errors as well. Otherwise, contacting the program vendor may be necessary.

Runtime Error 446: "Object doesn't support named arguments"

This error may be cause by a number of programs. Try installing the most recent updates. If this isn't successful, try reinstalling the program, restarting the computer and closing any other programs running that could possibly cause conflicts. Programmers and developers may have solutions available as well.

Runtime Error 447: "Object doesn't support current locale setting"

The may be caused by dynamic linked lists that out of date. Updating programs to the most current version may solve this problem.

Runtime Error 448: "Named argument not found"

Named arguments must be defined. Programs that attempt to access undefined arguments will receive this error. Updating the most recent version of the software can help with error 448. In some cases reinstalling software may help as well.

Runtime Error 449: "Argument not optional"

The number of arguments is not optional. This error may be the result of out of date or corrupted program files. Try reinstalling the program and checking for available updates. If these steps do no solve the error 449 issue contacting the software vendor may be the best option.

Runtime Error 450: "Invalid property assignment"

A procedure's definition includes the number of allowable arguments. Exceeding or falling short of this number will cause runtime error 450. If not encountered during development try reinstalling the program causing the error and checking for updates.

Runtime Error 451: "Property let procedure not defined"

This error occurs when operations are detailed that are only allowed for collections. However, the object being operated upon isn't a collection. This error is usually only encountered by program developers.

Runtime Error 452: "Invalid Ordinal"

This error is usually encountered by developers when test software and involves incorrectly attempting to call a dynamic linked list with a number instead of a name. Rewriting the offending code is necessary.

Runtime Error 453: "Specified DLL function not specified"

A dynamic linked list has been called but the function isn't specified. Updating programs to the most recent version or reinstalling programs may help with error 453. Contacting the program developer may also provide answers.

Runtime Error 454: "Code resource not found"

This error is limited to Macintosh computers. A reference to a resource that is not present was made by a program. Check to see if the resource is available and bring it online.

Runtime Error 455: "Code resource lock error"

This is another Macintosh-only error. A program has attempted to access a resource but was unable to lock it, which is mandatory. Checking for software updates and reinstalling programs that give error 455 may solve the issue. Otherwise contacting the software vendor is the best option.

Runtime Error 457: "This key is already associated with an element in this collection"

Unless encountered in the development of a program this error means that files or data has been corrupted. Make sure the most recent version of the program is installed and try reinstalling it. If this doesn't work try restarting the computer and closing other programs that may be causing conflicts.

Runtime Error 458: "Variable uses a type not supported in Visual Basic"

The program is attempting to use an unsupported type. This error is usually only encountered in program development. End users who receive this error are advised to contact the publisher of the software.

Runtime Error 459: "This component doesn't support events"

This is encountered to program development when programmers improperly use the WithEvents variable. End users who encounter the problem are advised to try reinstalling their software and checking for updates. Software publishers may have information available as well.

Runtime Error 735: "Can't save file to TEMP directory"

This error can be caused due to a damaged drive or a storage device that is full. Check to ensure the hard drive are working correctly. Try installing a larger hard drive.

Runtime Error 744: "Search text not found"

The 744 "search text not found" runtime error occurs when a program searches for text that does not exist. Possible causes could be that the wrong file has been accessed or that there are more than one file with the same name.

Runtime Error 746: "Replacements too long"

This error is a result of a replacement exceeding the maximum length. Ensure replacements are below the maximum. For end users, installing the latest program update or reinstalling the program may solve this problem. Software vendors may have further information or fixes in place as well.

Runtime Error 901: "Input buffer would be larger than 64k"

Ensure than the computer is running the most recent version. Try reinstalling the program, rebooting the system and closing other programs. If this doesn't work contacting the software vendor is recommended.

Runtime Error 902: "Operating system error"

Ensure that the program is running with the most recent update and that it is compatible with the version of Windows being used. Reinstalling the software and closing other programs may help as well.

Runtime Error 903: "External procedure not found"

Try closing other programs running, including terminate-and-stay-resident programs. If this doesn't work, reinstalling the software and checking for updates may solve error 903 issues. Otherwise contacting the software publishers is the recommended option.

Runtime Error 904: "Global variable type mismatch"

A program has attempted to use a function or procedure on a data type that was unexpected. Rebooting the computer, restarting the software, reinstalling the software and checking for updates may help solve error 904 issues.

Runtime Error 905: "User-defined type mismatch"

A user input is of the wrong type. Attempt to input data in the format expected by the program. Reinstalling the program and checking for updates may also fix this problem.

Runtime Error 906: "External procedure interface mismatch"

Make sure that the software has been updated and is running its most recently released version. Close background programs and reinstall the software. If that doesn't work contacting the software vendor is recommended.

Runtime Error 1004: "Application defined error"

This is an error that is associated with entering strings longer than 911 characters in Microsoft Excel. To solve this problem edit spreadsheets so that no cells contain more than 911 characters.

Runtime Error 31001: "Out of memory"

The system has exhausted the RAM available to it and is in need of more. If more than one program is running, try closing unnecessary programs. If this doesn't work, adding more RAM to a system may solve the problem. Some poorly designed programs may have memory leaks, which will eventually consume all the memory available to them, no matter how much is added.

Runtime Error in Java

Java is a program that is used to create web content. Mistakes in the Java code or incomplete files can cause this error. Refreshing the web page, restarting the browser or restarting the computer should solve Java runtime errors.

Runtime Error in AOL

AOL runtime errors can occur due to a number of causes. Most often it will involve the AOL Messenger program or AOL dial-up software. Reinstalling the software may solve the problem. Running antivirus software that scans the computer's registry is recommended as well.

 

Runtime Error Types

How to Fix Runtime Errors

Internet Media Types (MIME)

 

 

privacy