ntdll.dll Access Violation causing Hostmon failures

All questions related to installations, configurations and maintenance of Advanced Host Monitor (including additional tools such as RMA for Windows, RMA Manager, Web Servie, RCC).
Post Reply
eljefegt
Posts: 8
Joined: Tue Dec 06, 2016 11:56 am
Location: US

ntdll.dll Access Violation causing Hostmon failures

Post by eljefegt »

Recently, Hostmon has been having issues where our tests begin erroring out with a variety of System COM object errors on browser tests and "Error: Script returns no results."

Sometimes restarting the service will correct the issues, but other times, a server reboot is required, as restarting the service results in an error.

This is a bit urgent as it has begun occurring much more frequently and is not readily apparent if someone isn't staring at the RCC.

In the Event Log I see: Access violation at address 7730EBCB in module 'ntdll.dll'. Write of address 00000014

Any suggestions as to what could have started causing this to occur? Any recent patches that have been reported to cause issues?
KS-Soft
Posts: 12821
Joined: Wed Apr 03, 2002 6:00 pm
Location: USA
Contact:

Post by KS-Soft »

Please send request to support@ks-soft.net and provide more details, such as HostMonitor version, Windows version, Service Pack, Antivirus monitor...
Also, do you use ODBC logging or ODBC test method? If yes, what ODBC driver do you use?

What exactly test methods fail?
Test status? Unknown?
Test Reply value? "Error: Script returns no results."? I assume "Shell Script" tests return this error? Other test methods work fine?

Could you check resource usage for each process? You may use standard Windows Task Manager to check Handles, GDI and USER objects. What is the total resource usage on the system? How many handles/threads/GDI objects used by hostmon.exe process?

Could you setup HostMonitor to check for resources as well using Memory and Dominant Process test methods (check handles, threads, VMem)?
Use Private log file(s) and Full logging mode for these tests.
where our tests begin erroring out with a variety of System COM object errors on browser tests
Sorry, we do not understand what this means.
Normally HostMonitor does not use COM objects (for most of tests).
What means "browser tests"?

Regards
Alex
Post Reply