Archive for the ‘Uncategorized’ Category

How To Fix The 80004005 Error

Thursday, July 14th, 2011

The 80004005 error occurs when you try to use ActiveX Data Objects (ADO) or ODBC to connect to a Microsoft Access database. The error you may receive will look something like this:

“The Microsoft Jet Database Engine cannot open the file ‘(unknown)'”


“Microsoft OLE DB Provider for ODBC Drivers error ‘80004005’
[Microsoft][ODBC Microsoft Access 97 Driver] The Microsoft Jet database engine cannot open the file ‘(unknown)’. It is already opened exclusively by another user, or you need permission to view its data.”

What Causes The 80004005 Error

There are several causes of the 80004005 error, some of which include:

  • The account that Microsoft Internet Information Server (IIS) is using (which is usually IUSR) does not have the correct Windows NT permissions for a file-based database or for the folder that contains the file.
  • The file and the data source name are marked as Exclusive.
  • Another process or user has the Access database open.

How To Fix The 80004005 Error

Step 1 – Check The Permissions On The File

It is recommended that you check the permissions on the file and the folder. Make sure that you have the ability to create and/or destroy any temporary files. Temporary files are usually created in the same folder as the database, but the file may also be created in other folders such as the WINNT folder.

Step 2 – Verify The File And Data Source

It is important to verify the file and data source because the file has to be in proper working order and must be protected from damage or corrupt. Other wise your computer will experience some difficulty trying to use the correct files.

Step 3 – Close Any Visual InterDev Projects

It is recommended that you close down any other Visual InterDev projects that contain a data connection to the database. This way your computer won’t be confused and will be able to work properly.

Step 4 – Clean Out The Registry

One of the big causes of 80004005 errors is through the “registry” database of your computer. This is a large database which stores vital information & settings for your PC, and is used continually to help Windows to read the files, settings & options that it needs to run. Although the registry is one of the most important parts of every Windows system, it’s continually causing a large number of problems thanks to the way it will often become corrupted and unreadable. This is the cause behind many 80004005 errors, and needs to be resolved by using a reliable “registry cleaner” application.

This step is best completed by downloading Frontline Registry Cleaner, and letting it clean out any of the problems that your system may have inside.

How To Repair Runtime Error 76

Saturday, March 19th, 2011

Runtime Error 76 is a common Windows error that will be displayed on your screen when your system encounters a file that it cannot read or process properly, which usually happens either because the file has become damaged, gone missing or somehow become unregistered with the Windows operating system.  A common example of this error is when you have installed Microsoft Office in your computer and then the system accidentally removes one of its required components. The next time Windows tries to find the component it, it won’t be able to and as a result it will generate the runtime error 76, displaying the file name that is missing.  You need to repair the error by finding out which file is missing or corrupted, and then take steps to repair it.  This tutorial will help you find a fix for the runtime error 76.

What Causes Runtime Error 76?

The typical error message that shows up on your screen looks like this:

  • “Runtime Error 76: Path Not Found”

The error message is created by the system to let you know that your system has encountered a file that Windows cannot process or locate from its intended directory. This means the file is most likely corrupted or has been misplaced by the system. The problem can also easily be caused by damage to the settings inside the registry. You need to resolve the problem in order to fix the error – follow steps describe next to do so.

How To Fix Runtime Error 76

Step 1 – Re-Install The Application Causing The Errors

To directly tackle the error, the first thing that you need to do is identify the program which is causing the error message to show on your screen.  It’s likely that if you re-install it, the error will stop appearing.  Re-installing will replace the various program files the application is using and grant it fresh, working copies to use.  You need to uninstall the program first, which you can do by following these steps:

  • Click Start
  • Select Run
  • Type “appwiz.cpl” and click OK
  • From the list, select the program and click the “Uninstall” or “Remove” button
  • Restart your PC once the removal is finished

To re-install the program, insert the CD installer or locate and run the file installer from your hard drive. If you can’t find the installer file, you may also be able to download it from the internet. Follow the install wizard to complete the installation.  This process should resolve the problem and fix the runtime 76 error.  However, if the runtime error persists, proceed to the next step.

Step 2 – Clean Out Your PC With A “Registry Cleaner”

A vitally important module in your Windows system known as the registry could be the reason for the error.  It is basically a central database that stores a large number of registry keys that are needed by Windows to retrieve file and program settings. Without these settings, Windows won’t be able to load your programs properly. Unfortunately, the registry often suffers setbacks such as corruption, or misplaced registry keys, and this is when errors occur. Cleaning the registry will almost certainly eliminate the runtime error 76. To do so, you will need to use a ‘registry cleaner’ to do the cleaning for you.  To remove 99% of errors inside the registry, we highly recommend that you use this tool which has been found to be consistent and very versatile in restoring the health of your PC.