Specified driver could not be loaded due to system error1114

astewart · Joined: 15 Sep 2006 Posts: 24

Hello, I am having a problem using the ODBC query monitor.

I have two different computers running HostMonitor 5.92. Both are Win2k SP4 machines using the Oracle in OraHome90 driver for ODBC (ver 9.00.13.00). Yesterday I began trying to setup some ODBC query monitors. When I attempted to test a query, I would get the following error:

Error 4294967295: Specified driver could not be loaded due to system error 1114 (Oracle in OraHome90).

I did a search on your forums and found this thread: http://www.ks-soft.net/cgi-bin/phpBB/viewtopic.php?t=2939

Basically the other guy's problem was solved by rebooting his machine. I thought that was odd, but I tried it and after rebooting both my machines both of them could run the ODBC queries just fine.

Unfortunately, about 5 hours later one of the machines ODBC monitors went down with the reply "Error: Specified driver could not be loaded due to system error 1114 (Oracle in OraHome90)." which is the same error I was getting before the reboot. The machine was never touched after the new ODBC monitor was setup, so for some reason it just started throwing the error again. The second machine hasn't had this happen yet.

Any idea's on what to do so it doesn't get that error?

-Alex

KS-Soft · Joined: 03 Apr 2002 Posts: 12807 Location: USA

Sounds like a bug in the driver. Try to upgrade Oracle software.
Also you may try to enable "Do not use SQLFetchAbsolute command" option located on Misc page in the Options dialog.
Quote from the manual

astewart · Joined: 15 Sep 2006 Posts: 24

Upgrading the driver isn't really an option, as it is the same driver used on dozens of our production systems. Given that someone else had a similar problem with the MySQL ODBC 3.51 Driver (that's what the guy in the other thread had) and our ODBC driver works fine for all our other apps, it doesn't seem a likely cause to me.

The "Do Not use the SQLFetchAbsolute command" appears to already be enabled on both machines. I could try disabling it instead if you think that could help.

-Alex

KS-Soft · Joined: 03 Apr 2002 Posts: 12807 Location: USA

Google.com found different articles about this error but not many articles with solution. Some people refer to Windows Instantclient...
E.g. Oracle forum at http://forums.oracle.com/forums/thread.jspa?threadID=286332&tstart=30

astewart · Joined: 15 Sep 2006 Posts: 24

Interesting. I guess it may be the driver if it is popping up in other places, but I don't think changing it is an option for us

. I'll talk to some of our oracle people and see what they think.

Just an FYI, the other server also started showing the Error again. I don't understand why it would work at the beginning, and then stop working hours later with an error indicating it can't load something (which one would think was loaded many times before).

-Alex

astewart · Joined: 15 Sep 2006 Posts: 24

Hello again,
I talked to our Oracle people. They basically had two questions,

1) Do know of a version of the Oracle driver works (i.e. one you tested with).

2) Could you tell us what commands you are using to connect to the database so we could replicate them in a standalone app to see if the same problem occurs.

On a side note to number 2, I have been tinkering try to get this to work, and I setup a 'check Oracle server' monitor in addition to the 'ODBC monitor' now. The strange thing is, while the 'ODBC monitor' starts failing, the 'check Oracle server' monitor works fine. Does the 'check Oracle server' monitor connect differently somehow? What exactly is the 'check Oracle server' monitor checking?

If nothing come from this we decided we can workaround this problem by writing and ASP script to monitor the DB and then monitoring the ASP output instead, but it would be nice if we could get the imbedded ODBC monitor to work.

KS-Soft · Joined: 03 Apr 2002 Posts: 12807 Location: USA

astewart · Joined: 15 Sep 2006 Posts: 24

Thanks for the info, I'll play around with these commands and I'll let you guys know if I find anything.

Thanks again for being so responsive, you have a great product.

-Alex

KS-Soft · Joined: 03 Apr 2002 Posts: 12807 Location: USA

Thank you

Regards
Alex

CapQwerty · Joined: 14 Dec 2005 Posts: 36

We are thinking that this is a bug of some description that was introduced in version 6.2 as thats when it first showed up on our system.
We have similar problems as above. Eg server runds fine for a while then it throws that error.
If we go in via Test Properties click edit on the sql query than test it returns correctly.
Hostmon however still throws the same error when it does the test.
We only have 1 instance of the oracle client installed (v9.2.010) we have re-installed just to be sure.
We will today install 10.1.0.2 just to see if this changes things.

However we do believe that its in this case directly related to Hostmon.
Simply stopping and starting hostmon fixes it and any other tests still work external to hostmon.exe

Regards
Jason

KS-Soft · Joined: 03 Apr 2002 Posts: 12807 Location: USA

mos-eisley · Posted: Tue Nov 20, 2007 6:50 am Post subject:

In general, Oracle sucks at making ODBC drivers - that is my general perception (sorry if I have hurt anybody's feelings)

We have just moved HM backuplogging to Oracle 10g, since this is the default DB for the company. We actually stated on MS SQL, then MySQL, read this post: http://www.ks-soft.net/cgi-bin/phpBB/viewtopic.php?t=4078

This has caused me a lot of griefs, and moving to a clean server before the 10g client worked just fairly was the only option.

Still I am sometimes facing strange Oracle ODBC dialogs killing the machine etc....

If anybody has any good info on Oracle 10g ODBC/client, please contact me!!

KS-Soft Europe · Joined: 16 May 2006 Posts: 2832

mos-eisley · Posted: Tue Nov 20, 2007 7:09 am Post subject:

Well, the story is:

1. Last week I installed the server - we have about 20 "system DSN" entries, all set to "Oracle in OraHome". Oracle client is 10.2.0 - only installed Windows Support (ODBC) and OCI in a "Custom install"

2. This weekend one Oracle server in production crashed and was restated.

3. Monday morning, going on the HM server with RDP, I had load's of empty dialog boxes with the title "Oracle ODBC" ( I think it was ) and my syslog looked like this:

15-11-2007 13:19:38 Monitor started
15-11-2007 13:19:38 RCI enabled
16-11-2007 06:58:34 Primary log error. Cannot open log file "D:\InetPub\HostMonitor\wwwroot\Logs\log.htm" Logging initiated by "[SLA] pai06110 HTTP Live" test.
16-11-2007 15:46:33 Action "Restart service" was not executed by RMA "aaliitnt13" RMA Error: 301 - Cannot connect to the Service Control Manager. The RPC server is unavailable.
16-11-2007 15:48:33 Action "Restart service" was not executed by RMA "aaliitnt13" RMA Error: 301 - Cannot connect to the Service Control Manager. The RPC server is unavailable.
17-11-2007 03:00:08 Primary log error. Cannot open log file "D:\InetPub\HostMonitor\wwwroot\Logs\log.htm" Logging initiated by "Temperature TC" test.
18-11-2007 03:00:08 Primary log error. Cannot open log file "D:\InetPub\HostMonitor\wwwroot\Logs\log.htm" Logging initiated by "[SLA] pai07200 HTTP Web" test.
18-11-2007 09:17:32 Error: Cannot execute SQL query. ErrorCode = 4294967295: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specifie
19-11-2007 06:45:44 Backup log error. ODBC error code: 4294967295 (General error. [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_DBC faile) Logging initiated by "aaliitnas01 Ping" test.
19-11-2007 06:45:46 Backup log error. ODBC Error: Access violation at address 7C82BC32 in module 'ntdll.dll'. Read of address 00000004 Logging initiated by "aaliitnas01 Service OfficeScan Realtime Scan" test.
19-11-2007 06:45:46 More than 8 consecutive log errors occured. Backup logging paused for 5 min (use Options dialog to resume logging manually).
19-11-2007 06:45:47 Error: Cannot execute SQL query. Access violation at address 7C82BC32 in module 'ntdll.dll'. Read of address 00000004
19-11-2007 06:45:48 Error: Cannot execute SQL query. Access violation at address 7C82BC32 in module 'ntdll.dll'. Read of address 00000004
19-11-2007 06:45:48 Error: Cannot execute SQL query. Access violation at address 7C82BC32 in module 'ntdll.dll'. Read of address 00000004
19-11-2007 06:45:48 Error: Cannot execute SQL query. Access violation at address 7C82BC32 in module 'ntdll.dll'. Read of address 00000004
19-11-2007 06:45:48 Error: Cannot execute SQL query. Access violation at address 7C82BC32 in module 'ntdll.dll'. Read of address 00000004
19-11-2007 06:45:48 Error: Cannot execute SQL query. Access violation at address 7C82BC32 in module 'ntdll.dll'. Read of address 00000004
19-11-2007 06:45:48 Error: Cannot execute SQL query. Access violation at address 7C82BC32 in module 'ntdll.dll'. Read of address 00000004
19-11-2007 06:46:49 Error: Cannot execute SQL query. Access violation at address 7C82BC32 in module 'ntdll.dll'. Read of address 00000004
19-11-2007 06:46:49 Error: Cannot execute SQL query. Access violation at address 7C82BC32 in module 'ntdll.dll'. Read of address 00000004
19-11-2007 06:46:49 Error: Cannot execute SQL query. Access violation at address 7C82BC32 in module 'ntdll.dll'. Read of address 00000004
19-11-2007 06:47:49 Error: Cannot execute SQL query. Access violation at address 7C82BC32 in module 'ntdll.dll'. Read of address 00000004
19-11-2007 06:47:49 Error: Cannot execute SQL query. Access violation at address 7C82BC32 in module 'ntdll.dll'. Read of address 00000004
19-11-2007 06:47:49 Error: Cannot execute SQL query. Access violation at address 7C82BC32 in module 'ntdll.dll'. Read of address 00000004
19-11-2007 06:47:50 Error: Cannot execute SQL query. Access violation at address 7C82BC32 in module 'ntdll.dll'. Read of address 00000004
19-11-2007 06:51:08 SNMP Trap Listener: UDP port #162 opened for listening
19-11-2007 06:51:08 Monitor started
19-11-2007 06:51:08 RCI enabled

Consequence: No logging of tests in my Oracle DB most of the weekend.

Rebooted the server, and for the moment it seems to be ok again.
I have deleted the eventlog

KS-Soft Europe · Joined: 16 May 2006 Posts: 2832

I think, you should enable "Do not use SQLFetchAbsolute command" option, located in "User DSN/System DSN" section on "Miscellaneous" tab of the "Options" dialog. Quote from the manual:
http://www.ks-soft.net/hostmon.eng/mframe.htm#options.htm#MiscODBC
==================================
Do not use SQLFetchAbsolute command
Not every ODBC driver supports SQL_FETCH_ABSOLUTE command. HostMonitor tries to use this command and if driver returns error, HostMonitor use cycle with SQL_FETCH_NEXT command.
It works fine with most ODBC drivers. However ODBC driver which comes with Oracle client v.8 (and may be some other drivers) has bug in error handler. This bug can cause ODBC driver to crash.
That's why this option was implemented. Use it if you experience problem with ODBC driver.
==================================

Also you may play with "Enable connection pooling" option.

Regards,
Max