Small tip!! Some times things so small take up so much of your precious time that you start getting frustrated. The following is a common error people get when trying to connect with an Excel or Access DB using the Oledb:
Could not find the installable ISAM.
I agree there could be many reasons for this error to occur. For example, the drivers on your system are corrupted, in that case, you will have to reinstall the drivers or may the registry entries are corrupted. For that you will have to modify the registry. (If that is the case, you may want to look at the MS KB article that provides the solution). In my case, the problem was that I was using the latest Office 2007 and I was trying to connect to an Excel file using the following connection string:
string excelConnectionString = @"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:Tempmetadata.xls;Extended Properties=Excel 12.0";
Can you locate the problem in the connection string? Give it a try! The string is syntatically correct then where is the problem? The problem is with the "Extended Properties". If I replace "Excel 12.0" with "Excel 8.0" (which is the correct version actually), the problem goes away. I was about to modify my registry when luckily I noticed the correct version and modified my connection string and everything started working fine.
The error message that one gets is so generic that anyone will be easily deluded and this wastes time.
Good luck to anyone stuck with the same or similar problem!
Could not find the installable ISAM.
I agree there could be many reasons for this error to occur. For example, the drivers on your system are corrupted, in that case, you will have to reinstall the drivers or may the registry entries are corrupted. For that you will have to modify the registry. (If that is the case, you may want to look at the MS KB article that provides the solution). In my case, the problem was that I was using the latest Office 2007 and I was trying to connect to an Excel file using the following connection string:
string excelConnectionString = @"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:Tempmetadata.xls;Extended Properties=Excel 12.0";
Can you locate the problem in the connection string? Give it a try! The string is syntatically correct then where is the problem? The problem is with the "Extended Properties". If I replace "Excel 12.0" with "Excel 8.0" (which is the correct version actually), the problem goes away. I was about to modify my registry when luckily I noticed the correct version and modified my connection string and everything started working fine.
The error message that one gets is so generic that anyone will be easily deluded and this wastes time.
Good luck to anyone stuck with the same or similar problem!
No comments:
Post a Comment