Solution to Runtime Error 70

Runtime error 70 generally occurs due to insufficient security rights when you attempt to access a server from a remote application. You may also encounter the error when you try to open a copied file, but do not have sufficient rights because the file is currently being used.

In this article, we will discuss an instance of runtime error 70 and its solution.

Error 1

You may encounter the following error when you try to invoke the methods of a secure MTS (Microsoft Transaction Server) object from a Visual Basic (VB) application:

Runtime error ‘70’: Permission denied

Cause of the Error

Runtime error 70 in this case occurs when either of the following conditions is true:

  • You have turned on the Enable Authorization Checking for the component in Microsoft Transaction Server.
  • The Microsoft NT user that is trying to launch the objects from the VB application does not have the rights to invoke methods on the MTS component.

Resolution Tasks

To resolve the above runtime error, perform either of the actions:

  • Clear the Enable Authorization Checking option for the component. To do this, open the MTS Explorer and then open the Properties window for the component. Next, in the Security tab, clear the Enable Authorization Checking option.
  • Give the required rights to the NT user account that you are using to launch the MTS object from the Visual Basic application. You can do this by assigning the NT user id to one of the Roles that have the rights to invoke the methods of the MTS object.

What are the common causes of runtime errors?

A runtime error may occur due to a variety of reasons. The following are some of the most common reasons behind runtime errors:

  • Missing, damaged, or misplaced program files.
  • Corrupt or damaged registry entries.
  • Malware infection.
  • Incorrect software installation/unisntallation.
  • Insufficient System and memory resources.

How to prevent runtime errors

Listed below are some pointers that will help will you minimize the occurrence of runtime errors:

Install reliable protective software

As mentioned above, a common cause of runtime errors is malware infection. Install advanced security software, such as STOPzilla Antivirus and Spyware Cease and schedule regular malware scans to prevent malware programs, such as viruses, trojans, and worms from infecting your computer.

Perform regular registry scans

The registry stores critical data pertaining to your hardware, user profile, and software. In case entries stored in the registry are damaged, corrupt, or missing, you may receive recurring errors, including runtime errors. To prevent this, regularly clean your registry using a reliable registry cleaning application such as RegServe.

Ensure complete installation/unisntallation of programs

Incorrect installation/unisntallation of software may also cause runtime errors. When you install new software, ensure that the installation files are not damaged or corrupt. Also, make sure that the software is completely installed on your computer. Incomplete or incorrect installations are a major source of runtime errors.

Similarly, when uninstalling software, ensure that all its files, processes, and registry entries are also removed from the system. You may use a reliable third-party uninstaller tool, such as Perfect Uninstaller, for this task to ensure complete removal of software from your computer.