Personal Computer Fixes

How To Fix Runtime 53 Error

Runtime Error 53

When the user attempts to “call” an exported Dynamic Link Library (DLL) file from a Microsoft Transaction server (MTS) that is opened as a server package, they may receive runtime error 53. A DLL file is one which is readily available to programs to let them run routines. The Microsoft Transaction server is software that makes it easier for the user to implement large distributed applications. These two pieces of software of the Windows system therefore are in close relation to each other. Runtime error 53 can be fixed by moving the cause of the problem, the DLL to a different location. To find out how to do this, read on.

What Causes Runtime Error 53?

Runtime Error 53 usually appears as such:

Runtime error ’53’: File not found (yourfile.dll).

This can occur when the DLL that the application is attempting to look for cannot be found, or is not in the same place as the MTS component. “yourfile.dll” is the file name of the DLL file in question and you should take note of this. To resolve this problem, you must move the DLL file into the system32 folder on the C:\ drive. This error is best dealt with quickly to stop any further problems developing. Follow the following steps to find a solution.

How To Fix Runtime Error 53

Step 1 – Move The DLL File To The “C:\Windows\System32” Folder

Make a note of the DLL file that was causing the runtime error 53 and then:

  1. Perform a search of all your hard disks to find the current location of the DLL file
  2. Once the search has found the relevant file, copy it from it’s location (Right click > Copy)
  3. In Windows Explorer, go to C:\Windows\System32.
  4. Once inside this folder, paste the DLL file in there.

Since the MTS component is located in the system 32 folder, it automatically starts its search in there first. Providing the component with the DLL file it requires in the correct folder will mean that it should pick it up quickly. The runtime error 53 occurs when a particular MTS component is opened as a Server Package. When this happens, the COM component is created in an isolated process space, Mts.exe. Now, the default location for the Mts.exe file is %SystemRoot%\System32. This is the reason why Mts.exe fails to find the required DLL file when it does not exist in the search path. This should solve the problem, if it did not then carry on to the next step.

Step 2 – Re-Install The Application Causing The Error

If you find that Step 1 does not work, or is not applicable, then you should look to reinstall any application causing the error you’re seeing. This is quite easily done if the program is a third-party piece of software from Windows. Here’s how to re-install the software that could be damaged:

  • Click “Start” > Control Panel > Add / Remove Programs
  • Locate the program causing the error
  • Click “Remove” / “Uninstall” to get rid of the program
  • Restart Your System
  • Install the program again
  • Test to see if the error shows

It’s often the case that the program that’s showing the error will either have some sort of corrupt file or setting that’s preventing it from running correctly. The easiest and most effective way to resolve this error is to re-install the program, which will wipe all the files that it uses. If you find this does not fix the errors you’re seeing, you may wish to progress onto the next steps:

Step 3 – Manually Add / Replace The File On Your PC

If you know which file is damaged / missing, you should look to replace it on your PC. This can be done by following the steps below:

1) Download the file from the Internet

2) Unzip the new file onto your computer’s hard drive

3) Browse to c:\Windows\System32

4) Locate the current file on your system

5) Rename the current file to <<filename>>BACKUP.dll

6) Copy & paste the new file into C:\Windows\System32

7) Click Start > Run (Or search”run” on Vista & Win7)

8 ) Type “cmd” in the box that appears

9) Type “regsvr32 <<filename>>” on the black screen

10) Press enter

This will replace the missing file on your PC with a fresh, new copy that your PC should be able to access again. However, if this does not solve the error, you may wish to try using Step 4 below:

Step 4 – Clean Out The Registry

Registry cleaners can play a very important role in how well Windows operates, and can help stop the Runtime 53 error. The registry is basically a central database which stores vital settings and information for your system, allowing Windows to remember a huge number of details for your PC. Unfortunately, the registry is also prone to becoming corrupt, leaving your system running extremely slowly and unreliably. To fix this problem, you should use a ‘registry cleaner’ to scan through your registry and repair any of the damaged parts of it that are causing your computer to run extremely slowly or with errors. You can download our recommended registry cleaner below:

» Download Windows Repair Tool

Share

Highly Recommended

Our Best Registry Cleaner ToolThis is our recommended cleaning tool that works to fix 99% of all the errors and issues on your PC. You can use this cleaner to stop viruses, errors and faults with your system.

We have found that this tool has consistently the most effective and versatile, allowing you to quickly fix most problems on your PC.

Click Here To Download A Free Scan




© 2017 Personal Computer Fixes. All rights reserved.

This website may receive compensation for some of the recommendations we make on some products.