Cocould not find installable isam (the installable isam cannot be found)

A website called openaspx is really shameless, and the source of plagiarism is not explicitly indicated. Open source does not mean stealing!

A system has the ability to import Excel Data to the able. In the test environment, some business personnel found that the import was unsuccessful one day. prompt "cocould not find installable isam" (English OS, Chinese may be "unable to find installable isam ").

I found a lot of information on the Internet. Generally, the connection string is incorrect. For example, if the datasource words are connected together, it should be data source; or the extended properties value must be enclosed by quotation marks; or the semicolon is missing. for details, refer to [1].

However, the source code of this system has not been modified for a long time, and it has been used well before. suspected to be an office problem. I found that Office 2003 was uninstalled (Because office 2010 was used). Do I need to install Excel 2003? However, it is reasonable to say that excel 2010 should be forward compatible, and Microsoft does not need to remove it.

Later I saw [2] and suddenly remembered whether the registry error was caused by uninstalling Office 2003? So I registered several key DLL manually according to the [2] method and tried it. it looks like [2] is also a reprinted Microsoft Help document. in addition, the following DLL files are not available only when the Office is installed. If not, search for "40.dll" on the system disk ", you can find these files in the Windows \ servicepackfiles \ i386 directory on the system disk. Copy them to system32 and register them. if Excel is found, you can register the following DLL files: msexcl40.dll, msexch40.dll, and msrd2x40. DLL, msrd3x40. DLL.

Problem description:
The "cocould not find installable isam" error message is received in access or SQL server, or some file classes are lost.

Solution:

1. Improper use of the Registry Editor may cause serious problems and you may need to reinstall the operating system. Microsoft cannot guarantee that you can solve problems caused by improper use of the Registry Editor. You are at your own risk to use the Registry Editor. To solve this problem, you can try to manually register this file, or you must correct the path name in the Windows registry and then install or replace the problem file. To do this, follow these steps.

Note: In error message 1 mentioned in the "Symptom" section, this file name is directly associated with the operation you are trying. The file name is mentioned in the text of the error message 2 mentioned in the "Symptom" section.
1. Find related files in the following table:
File Name import/export isam: Windows Registry
Microsoft Excel HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ jet \ 4.0 \ engines \ Excel
Msexch40.dll Microsoft Exchange HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ jet \ 4.0 \ engines \ exchange
Msrd2x40. dll Microsoft Jet 2.x HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ jet \ 4.0 \ engines \ jet 2.x
Msrd3x40. dll Microsoft Jet 3.x HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ jet \ 4.0 \ engines \ jet 3.x
Msltus40.dll Lotus 1-2-3 HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ jet \ 4.0 \ engines \ Lotus
Mspbde40.dll imprise paradox HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ jet \ 4.0 \ engines \ Paradox
Mstext40.dll text HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ jet \ 4.0 \ engines \ Text
Msxbde40.dll DBASE HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ jet \ 4.0 \ engines \ xbase
2. Use Microsoft Windows Resource Manager to search for files.
3. If the file is found, write down the path name of the file. If the file cannot be found, go to step 13.
4. Open the Windows Registry Editor.
5. Find the Registry subitem described in this table and check the path name according to the actual path name. If this registry key does not exist, go to Step 8.
6. If the path is incorrect, correct the path. If the path is correct, continue with these steps.
7. Disable Registry Editor.

If you change this path, repeat the initial error process.
8. If the error persists, use the regsvr32.exe utility to manually register the file.

Regsvr32.exe utility is used to register DLL and ActiveX controls in the Windows registry. You can use this file to solve the problem of incorrect matching. DLL files. To use the regsvr32.exe utility to re-register the. dll file, go to the next step.
9. Verify that the regsvr32.exe file is in a Windows system folder.

For example, the regsvr32.exe file is usually located in C: \ WINDOWS \ SYSTEM or c: \ winnt \ system32.
10. Click start and then click Run ".
11. In the "run" dialog box, type the following command in the "open" box.

Note: The name and path of regsvr32.exe may be different in the computer. Run the following command to register an Excel isam:

Regsvr32 c: \ winnt \ system32 \ msexcl40.dll

Note: another way to register a DLL is to use Windows Resource Manager to find the DLL.

Double-click this DLL. In the "publish" dialog box, click "regsvr32.exe" and click "OK ".

This creates a permanent association between all DLL and regsvr32.exe. You can double-click another unregistered DLL to register the DLL.

For more information about how to obtain this file, click the following article number to view the article in the Microsoft Knowledge Base:
267279 (http://support.microsoft.com/kb/267279/) regsvr32.exe can be downloaded from the download center
12. If the error persists or the path name has been corrected in step 5, rename the file.
13. Start the "Add/delete programs" tool, start the Office 2000 installer, and then click "repair office ".

In addition, [3] also mentioned the method for importing the registry, but because I don't know which DLL registry is, I am afraid to try it on the server. The repost is as follows:

This problem has plagued me for two months.
In Delphi 7, when ADO was jet oledb 4.0 was used properly, it would suddenly appear
"Microsoft. Jet. oledb.4.0 unable to find the provider or uncertain"
Today, two VMS disappear after the VM login attempts over oledb 4.0
Maybe it's something about a traditional software system. On the platform, JET 4.0 will be back ....
The following are missing login information

Windows Registry Editor Version 5.00

[Hkey_classes_root \ CLSID \ {dee35071-506b-11cf-b1aa-00aa00b8de95}]
@ = "Microsoft JET 4.0 ole db Provider error lookup"

[Hkey_classes_root \ CLSID \ {dee35071-506b-11cf-b1aa-00aa00b8de95} \ inprocserver32]
@ = "C: \ Windows \ system32 \ msjetoledb40.dll"
"Threadingmodel" = "both"

[Hkey_classes_root \ CLSID \ {dee35071-506b-11cf-b1aa-00aa00b8de95} \ progid]
@ = "Microsoft. Jet. oledb. errorlookup.4.0"

[Hkey_classes_root \ CLSID \ {dee35071-506b-11cf-b1aa-00aa00b8de95} \ versionindependentprogid]
@ = "Microsoft. Jet. oledb. errorlookup"

[Hkey_classes_root \ CLSID \ {dee35070-506b-11cf-b1aa-00aa00b8de95}]
@ = "Microsoft. Jet. oledb.4.0"
"Oledb_services" = DWORD: fffffffe

[Hkey_classes_root \ CLSID \ {dee35070-506b-11cf-b1aa-00aa00b8de95} \ extendederrors]
@ = "Microsoft JET 4.0 ole db Provider error lookup"

[Hkey_classes_root \ CLSID \ {dee35070-506b-11cf-b1aa-00aa00b8de95} \ extendederrors \ {dee35071-506b-11cf-b1aa-00aa00b8de95}]
@ = "Microsoft JET 4.0 ole db providererror lookup"

[Hkey_classes_root \ CLSID \ {dee35070-506b-11cf-b1aa-00aa00b8de95} \ inprocserver32]
@ = "C: \ Windows \ system32 \ msjetoledb40.dll"
"Threadingmodel" = "both"

[Hkey_classes_root \ CLSID \ {dee35070-506b-11cf-b1aa-00aa00b8de95} \ ole db provider]
@ = "Microsoft JET 4.0 ole db provider"

[Hkey_classes_root \ CLSID \ {dee35070-506b-11cf-b1aa-00aa00b8de95} \ progid]
@ = "Microsoft. Jet. oledb.4.0"

[Hkey_classes_root \ CLSID \ {dee35070-506b-11cf-b1aa-00aa00b8de95} \ versionindependentprogid]
@ = "Microsoft. Jet. oledb"

If you have any questions, just try again.
Save it as Reg branch and try again to see if this problem has been solved.

Reference:

[1] http://www.cnblogs.com/zyc2/articles/182492.html

[2] http://www.cnblogs.com/zgqys1980/archive/2010/11/23/1885661.html

[3] http://www.cnblogs.com/dotneter/archive/2008/11/28/1343132.html