I was wondering if anyone could help me with this issue.
I have got a customer that is getting the following error in his server.log file
|20151028193012||I||#04104||NAIMSERV||ePolicy Orchestrator server started.|
|20151028193012||X||#04104||MOD_EPO||Set SPIPE input package size limit to 10485760 bytes|
|20151028193012||X||#04104||MOD_EPOREPO||Using 250 worker threads, 6 busy threads|
|20151028193012||I||#04104||MOD_EPOREPO||Database initialization: Starting.|
|20151028193012||I||#04104||MFEFIPS||Loading: "D:\Program Files (x86)\McAfee\ePolicy Orchestrator", Role = Officer, Mode = Normal|
|20151028193012||I||#04104||MFEFIPS||MFEFIPS_Status() returned 1|
|20151028193012||I||#04104||MOD_EPOREPO||Database initialization: Succeeded.|
|20151028193012||E||#05960||EPODAL||ePOData_Connection.cpp(872): COM Error 0x80040E14, source=Microsoft OLE DB Provider for SQL Server, desc=The target table 'EPOAgentHandlerNotify' of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause without INTO clause., msg=IDispatch error #3092|
The symptoms is that when he starts to deploy any task it will suddenly stop and the only way to resolve this issue is to restart his apache service, the version of ePolicy orchestrator he is using is 5.1.1
Does anyone have any idea what this could be?
Hi Charles Latty,
This issue is due to agent handler is showing under active and inactive at a time, and workaround is to stop and start the service will revert back to active AH
This issue is resolved in EPO 5.1.2
For more information, go through the KB82843
Additionally: I suggest, when the issue persist, instead of restart the service open the agent handler page and see it is shwoing under inactive as well.
This issue occurs with EPO 5.1.0 and 5.1.1
As you mentioned it is EPO 5.1.1, I am sure this is causing the issue
Hope this answered your query
Thank you very much for your reply.
I checked the article you were referring to which is KB82843 which links to article Default 'Agent Handler Status' report does not accurately report the status of handlers
Is this correct, i did notice that it says that it is resolved in epo 5.1.2
Yes, this issue resolved in EPO 5.1.2, and moreover, I suggest to go with EPO 5.1.2 ONLY, since I have referred the bug number from this article and didn't find it has been resolved in higher versions of EPO ( Ex: 5.3.x).
Hope this answered your questions.
The article subject line you mentioned is absolutely right