Question:
What can be done to correct the error '[Microsoft] [ODBC Microsoft Access Driver] The Microsoft Jet database engine cannot find the input table or query.'?The erroris returned when opening a saved integration or creating a new integration and then selecting the destination mapping area.
Answer:
The erroris indicatingthatIntegration Manager is unable to locate the ImDynPrv.mdb database. This database contains the Dynamics Objects that are available in the Destination Mapping window.Here are acouple ofcauses of this problem. One, an IM.ini filemay exist that specifies an incorrect database path location. Two, the IMFix.exe program was excuted. This program will ask the location of the ImDynPrv.mdb and Im.mdb files. If thelocations were entered incorrectly, the im.ini file that is created would be incorrect. Three, the registry of the workstation has incorrect paths listed. In this case, an im.ini file with the correct paths will resolve the issue. An example of an im.ini follows:
[IMProvider]
DBPath=c:\Dynamics\IM\IM.Mdb
HideMsgBox=Yes
[IMDynProvider]
DBPath=c:\Dynamics\im\dynamics_eenterprise provider\imdynprv.mdb
HideMsgBox=Yes
This article was TechKnowledge Document ID:18644
What can be done to correct the error '[Microsoft] [ODBC Microsoft Access Driver] The Microsoft Jet database engine cannot find the input table or query.'?The erroris returned when opening a saved integration or creating a new integration and then selecting the destination mapping area.
Answer:
The erroris indicatingthatIntegration Manager is unable to locate the ImDynPrv.mdb database. This database contains the Dynamics Objects that are available in the Destination Mapping window.Here are acouple ofcauses of this problem. One, an IM.ini filemay exist that specifies an incorrect database path location. Two, the IMFix.exe program was excuted. This program will ask the location of the ImDynPrv.mdb and Im.mdb files. If thelocations were entered incorrectly, the im.ini file that is created would be incorrect. Three, the registry of the workstation has incorrect paths listed. In this case, an im.ini file with the correct paths will resolve the issue. An example of an im.ini follows:
[IMProvider]
DBPath=c:\Dynamics\IM\IM.Mdb
HideMsgBox=Yes
[IMDynProvider]
DBPath=c:\Dynamics\im\dynamics_eenterprise provider\imdynprv.mdb
HideMsgBox=Yes
This article was TechKnowledge Document ID:18644