Runtime 70 Error Troubleshooting
Permission Denied?
The runtime 70 error is a rising star in the pc error world. It used to be a once in a while error, but as networked computers and user settings become more complex (hello, Windows 7TM!), the runtime 70 error is becoming ubiquitous.
There are a few things that cause the runtime 70 error.
- You don’t have the permissions to access the application you are trying to access
- The application you are trying to run is already running
- You’ve asked an application to do something it can’t do while it is running
- You’ve got a missing or corrupt file in the registry
A registry cleaner will fix most operating system errors.
Troubleshoot the Runtime 70 Error
Runtime 70 Caused by #1
The runtime 70 error is “permission denied.” If you don’t have admin level access on the pc – perhaps just a user access? – you must be unable to do the task from your current user level settings. This is a settings problem. See the admin to get your user settings adjusted so you can do the task.
Runtime 70 Error Caused by #2
If you are getting the runtime 70 error when you try to open an application, it may be that the software is already running. So many applications are set to initialize at bootup, you may not even be aware that the program is already launched when you try to start it. When you get the runtime 70 error: Clear it (or reboot if the error caused a crash), Hit F12 and then try to manually launch whatever application you were after. If that solved the runtime 70 error, then you don’t need to restart the program to access it. It was already running.
Runtime 70 Error Caused by #3
The Runtime 70 error will sometimes come up when you ask an application to do something it is not permitted to do while running, like copy a database. Close the program. Try the task while the program is not running.
Runtime 70 Error Caused by #4
Whenever you have multiple users noodling around in the settings, there is going to be old junk in your registry. The registry holds on to all settings for all users. So if someone on your system – especially with admin access – begins changing settings wily-nily, then there is the chance of registry corruption. So you might have registry damage which will cause many runtime errors, freezes, and crashes, including the runtime 70 error. Add running registry cleaner to your monthly pc maintenance tasks to solve the problem.
Discover if a Corrupt Registry is Causing Your Runtime 70 Error…
Enjoy a Free Diagnostic Scan of your Registry!
And if registry damage is the problem you can fix it in less than 10 minutes.
