Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Process triggers stopped working
#1
Suddenly, a few days ago process initiated triggers stopped working in my XP-computers. Could you please advise?

I am using QM version 2.3.3.0.
#2
If on single computer, I would say look in QM Options, maybe process triggers disabled, or try to reinstall QM.

Maybe recently you installed some new software?

For process triggers QM uses a driver. This macro tells whether QM driver is running.
Macro Macro1615
Code:
Copy      Help
out
Services.clsServices ses._create
int st=Services.Kernel_and_File_System_Drivers_20202020
ses.ServicesEnumType=&st
Services.clsService se
int n
foreach se ses
,n+1
,;out se.DisplayName
,str s=se.DisplayName
,if(s~"QM process triggers") out "QM driver running"; ret
if(n) out "QM driver not running"
else out "failed"
#3
Dear Gintaras,

Many thanks for your advice. However, although I tested whatever you proposed the problem was not solved. Let me mention (a) that I recently upgraded from AVG 9 to AVG2012 (b) when QM is loaded I get the message in QM output : "Failed to set process notifications. Process triggers will not work".

I restored back to an AVG9 Restore Point, Process Triggers worked perfectly then. Coming back to AVG2012 process triggers failed again.

I welcome any further advice.
Best regards
SImos

15-12-11 15:27:00
It is now cross-checked : AVG2012 disables QM process triggers. I wonder whether a solution could be given to this incompatibility.
#4
New finding : I have not this problem in one of my four PCs! Furthermore, this problem can be by-passed if AVG is temporarily disabled when QM is loaded for the first time after booting. Any idea is welcome.
#5
For process triggers QM uses Windows API function PsSetCreateProcessNotifyRoutine:
http://msdn.microsoft.com/en-us/library ... 85%29.aspx

On Windows Vista and later, max 64 clients supported. On 2000/XP only 8.

AVG uses the same function, maybe some other program too, and they occupy all the 8 slots. Then PsSetCreateProcessNotifyRoutine fails when QM calls it, and process triggers don't work. I cannot fix it, it is a Windows limitation. If you temporarily disable AVG, something in AVG may not work because PsSetCreateProcessNotifyRoutine will fail when AVG will call it.
#6
Dear Gintaras,

Many thanks indeed. I will try to substitute process triggers using some other method. For the shake of interest let me mention that the module in AVG which it should be disabled to have process triggers working is "Identity Protection".

Best regards. SImos.
#7
Dear Gintaras,

Is there any way to find out which programs use PsSetCreateProcessNotifyRoutine ? My intention would be to disable / remove these programs if less useful and allow both QM/process triggers and AVG/Identify Protection working properly.

Thanks/Regards
#8
probably not


Forum Jump:


Users browsing this thread: 5 Guest(s)