I have an MS Access 2013 application that opens a connection to an Oracle database via an Oracle client.On occasion the application returns the following error when the ODBC connection is opened:Specified driver could not be loaded due to system error 1114: A dynamic link library (DLL) initialization routine failed. After discussing this issue on another forum I was able to put together a workaround. I can’t report the issue to Oracle without having some kind of 'support identifier' with them and have no idea of how to report this to Microsoft.The workaround is based on the observation that a query that makes use of the ODBC connection never has a problem when run within the Access GUI; the connection issue occurs only when I run the query within VBA. So, I created a very simple query that selectsonly one field (and actually returns no record) and uses the ODBC connection – call it the ‘peek’ query. I use a form containing a control that is bound to the peek query. When my application launches I open the form, immediately minimize it (so as not botherthe user) then close the form.
![](/uploads/1/2/7/7/127703854/117578963.jpg)
Error installing ODBC driver MySQL ODBC 5.3 ANSI Sriver, ODBC error 13. ODBC driver could not be loaded due to system error code 193.
After this, I can use the real query in VBA.The workaround has been in production for several months now and nobody has complained. Hi Ross,This error message is Microsoft Data Link Error, this error occurs on windows when attempting to start a service or load a system driver but the DLL you loaded or one of its dependencies returned FALSE. It typically point to a system DLL file which is locatedin system32 and can be fixed by using the System File Checker tool. In your case, I suspect that it occurs due to a calling failure connecting to ODBC driver and it pointed to an error link C:oracleproduct11.2.0client1SQORA32.DLL which is hosted by oracle.If they are analogous, a “repair” seems to be helpful, However since we are not expert about oracle program I‘d suggest you check if C:appOracleBINSQORA32.DLL file exists on your machine and contact with Oracle first, I think there you can get more effectivesuggestion by other experts who familiar with design of Oracle database. Your understanding is highly appreciated.By the way, I searched for you and seems like you are not alone about this issue.Please note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.Regards,D. WuPlease remember to mark the replies as answers if they help, and unmark the answers if they provide no help.
If you have feedback for TechNet Support, contact [email protected]. Thanks for all of your replies. I wasn’t sure where to post my question; since the ODBC connection is usually established without a problem this felt like a Windowsissue. I will follow up with Oracle.The DLL certainly exists since the connection can usually be established and rebooting the workstation usually solves the issue – though sometimes not for very long. The issuealso have to be common to all of my clients since every user reports this intermittent problem at one time or another.Cheers,Ross.
Hi Ross,Glad to help and thanks for your feedback.As you mentioned if this DLL exists/not corrupted and the connection can usually be established, the “repair/reinstall” might not be solution.Please check if any patch has been released by Oracle, if not try following up with Oracle.Meanwhile, if you found solution by yourself or Oracle. We would appreciate it if you could share with us and we will mark it as answer. It might help a lot of users who have similar issues.Your understanding is highly appreciated.Best Regards,D. WUPlease remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
After discussing this issue on another forum I was able to put together a workaround. I can’t report the issue to Oracle without having some kind of 'support identifier' with them and have no idea of how to report this to Microsoft.The workaround is based on the observation that a query that makes use of the ODBC connection never has a problem when run within the Access GUI; the connection issue occurs only when I run the query within VBA. So, I created a very simple query that selectsonly one field (and actually returns no record) and uses the ODBC connection – call it the ‘peek’ query. I use a form containing a control that is bound to the peek query.
When my application launches I open the form, immediately minimize it (so as not botherthe user) then close the form. After this, I can use the real query in VBA.The workaround has been in production for several months now and nobody has complained.
Can anyone help?I am trying to setup a system DSN (on SQL2K SP4) to setup a linked server to a Domino backend.I am trying to setup the SQLNotes ODBC as a System DSN but I get the error message:Microsoft ODBC Administrator'The setup routines for theLotus NotesSQL Driver (.nsf) ODBC driver could not be loaded due to system errorcode 126'I can set this up as a file DSN no problem but as far as I can tell, you cannot setup a linked server to a File DSN.If anyone can tell me anything useful, I will be grateful. Thanks for that. The problem there is that I cannot create the system dsn. I get the error:'The setup routines for the Lotus NotesSQL Driver (.nsf) ODBC driver could not be loaded due to system error code 126'so had to set it up as a file DSN.Most of the bumph for this error says to check the registry is pointing to the same place the files are stored and this it does, so I don't know where to go from there. I installed teh latest MDAC but nothing changed.Can I not set up a Linked Server to a file dsn?The file DSN was setup OK. I know this because I can use it as a connection in DTS and successfully import various tables (although it does not work with the import wizard).I set the linked server up to the file dsn but I keep getting errors:'7399 Invalid Connection String attribute(not sure what I was supposed to enter in the 'Product String' dialog box) Datasource name not found and no default driver specified.'
Any help much appreciated. An internet search found the below atReason for the Error:NotesSQL expects to find Notes.ini in the LotusNotes directory. I am not at the machine where i had this problem now and can't get back there for a while, but does anyone know if this resolved the problem? I am sceptical because the Lotus client was installed on the server in question (this is part of the NotesSQL install process) and I accepted all the defaults. Surely the Lotus setup would have used the standard directory as specified above.?)Please let me know if this was fixed buy anyone else who had the same problem - and did you manage to setup a linked server?Thanks again.Wyatt.
Carl Federl (4/15/2008)An internet search found the below atReason for the Error:NotesSQL expects to find Notes.ini in the LotusNotes directory. If the file is not in this directory, the driver may crash when you use the ODBC Data Source Administrator to create a DSN, or the NotesSQL Authentication List Manager may report that it is unable to find a valid version of Notes.Solution:If you must place Notes.ini in a directory other than LotusNotes, add the directory to your PATH environment variable.I found that this solution wasn't quite enough. I installed NotesSQL within 'C:Program FilesLotusNotesSQL' which is not the default. I had to add this directory to the system path before I was allowed to create a system DSN via the Windows ODBC Data Source Manager.
A system restart did not seem to be required for this.John.
![](/uploads/1/2/7/7/127703854/117578963.jpg)