Troubleshooting
Problem
This technote identifies a possible cause and resolution to the error, Unable to open project through the COM server, which can occur when opening an IBM® Rational® RequisitePro® project.
Symptom
The full error message is as follows:
ODBC Error: Unable to open project through the COM server. Exception occurred (HRESULT DISP_E_EXCEPTION) Provider cannot be found. It may not be properly installed.
Cause
If this error is localized to a specific machine it is very possible that the Microsoft Data Access Components (MDAC) might have been compromised with the installation of new software on the system.
Note: MDAC includes ActiveX Data Objects (ADO), OLE DB, and Open Database Connectivity (ODBC).
Resolving The Problem
To repair MDAC take the following steps.
- Down load the MDAC checker from Microsoft's Web site. The MDAC checker will be in a zip file called cc_pkg.exe:
http://www.microsoft.com/downloads/details.aspx?FamilyID=8F0A8DF6-4A21-4B43-BF53-14332EF092C9&displaylang=en - Run the MDAC checker on the computer that is having the problem. This tool will give three options. Choose the first option that is entitled Perform an analysis of your machine and automatically determine the release version.
- Once the MDAC's release level is determined, there are three methods that may be used to attempt to repair MDAC. All three methods may be used.
- Download the version of MDAC that exists on the computer that is having the problem and reinstall that version of MDAC. Down loads for MDAC are available at the following Web site:
http://msdn.microsoft.com/en-us/data/aa937729.aspx - Upgrade the version of MDAC that exists on the machine by downloading a later version of MDAC and installing it.
- Be sure that the software on your machine is compatible with the version of MDAC that you are installing:
http://msdn.microsoft.com/en-us/data/aa937729.aspx - Repair the version of MDAC that is currently installed on the machine.
- The Match sub entry includes all details about all MDAC components and registry entries that are matched to the selected MDAC version.
- The Mismatch sub entry includes entries for components and registry entries that exist in the current selected MDAC version, but where a mismatch was found. Typically, these are the components that you must investigate when you suspect that there are any MDAC installation or configuration issues.
- The Not Found sub entry refers to components or registry keys that are not found (do not exist) in the selected MDAC version.
- In the DOS shell go to the location where the file mdac_typ.exe is located.
- Create the directory that you want to extract the contents of mdac_typ.exe into.
- Execute the following command.
mdac_typ.exe /C /T:c:\hmdac
Note: hmdac is the directory you created to hold the contents mdac_typ.exe. - For any Mismatch or Not Found entries:
- Locate the correct version of the dll in the files your extracted from MDAC.
Note: Be sure to look in the Cab files. - Copy the file to its correct location.
- Use the appropriate .xml file that is located in the MDAC's Inputstream sub directory to determine the files correct location.
- For File entries use filestream.xml
- For Com entries use comstream.xml
- For Registry entries registrystream.xml
- The organization of the .xml files is explained in the MDAC checker's help files under the topic Modifying Data Input Files
- Reregister the file using Microsoft's Regsvr32 utility.
1. Run the MDAC checker and select the second option that is entitled Perform an analysis against a selected version. Select the version of MDAC that is on the machine.
2. Download the version of MDAC that exists on your machine. The file you will down load is called mdac_typ.exe. Downloads for MDAC are available at the following Web site:
http://msdn.microsoft.com/en-us/data/aa937729.aspx
3. The entries File Details, Com Details, and Registry Details will appear on the left side of the explore tool. Each entry could have a Match, MisMatch, and Not Found sub entry.
4. Extract the contents of the MDAC_typ.exe .exe file that you down loaded by doing the following:
5. File, Com, and Registry Errors:
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21193836