https://community.splunk.com/t5/Getting-Data-In/Monitoring-using-quot-WinPrintMon-quot-why-are-some-universal/m-p/134627#M27675 <P>Did you ever figure out the answer to this? I am seeing the same errors appear on our servers.</P> Thu, 10 Dec 2015 02:32:21 GMT robert_miller 2015-12-10T02:32:21Z https://community.splunk.com/t5/Getting-Data-In/Monitoring-using-quot-WinPrintMon-quot-why-are-some-universal/m-p/134626#M27674 <P>I monitor using "WinPrintMon" on several hundred servers - 17 of those servers gives this error-message at each poll:</P> <PRE><CODE>04-14-2015 12:05:09.990 +0200 ERROR ExecProcessor - message from ""C:\Program Files\SplunkUniversalForwarder\bin\splunk-winprintmon.exe"" splunk-winPrintMon - monitorHost::ProcessRefresh: Failed ProcessRefresh: error = '0x800706ba'. Restart. </CODE></PRE> <P>It's always the same 17 servers - any tips?</P> <PRE><CODE>[WinPrintMon://printer] type = printer interval = 600 baseline = 1 disabled = 0 index = windows [WinPrintMon://job] type = job interval = 600 baseline = 1 disabled = 0 index = windows [WinPrintMon://driver] type = driver interval = 600 baseline = 1 disabled = 0 index = windows [WinPrintMon://port] type = port interval = 600 baseline = 1 disabled = 0 index = windows </CODE></PRE> Tue, 14 Apr 2015 10:16:49 GMT https://community.splunk.com/t5/Getting-Data-In/Monitoring-using-quot-WinPrintMon-quot-why-are-some-universal/m-p/134626#M27674 bravon 2015-04-14T10:16:49Z https://community.splunk.com/t5/Getting-Data-In/Monitoring-using-quot-WinPrintMon-quot-why-are-some-universal/m-p/134627#M27675 <P>Did you ever figure out the answer to this? I am seeing the same errors appear on our servers.</P> Thu, 10 Dec 2015 02:32:21 GMT https://community.splunk.com/t5/Getting-Data-In/Monitoring-using-quot-WinPrintMon-quot-why-are-some-universal/m-p/134627#M27675 robert_miller 2015-12-10T02:32:21Z https://community.splunk.com/t5/Getting-Data-In/Monitoring-using-quot-WinPrintMon-quot-why-are-some-universal/m-p/134628#M27676 <P>The solution was painfully simple - the "Print service" was disabled on the servers. Enabled the print service and the errors stopped.</P> Thu, 10 Dec 2015 11:12:05 GMT https://community.splunk.com/t5/Getting-Data-In/Monitoring-using-quot-WinPrintMon-quot-why-are-some-universal/m-p/134628#M27676 bravon 2015-12-10T11:12:05Z https://community.splunk.com/t5/Getting-Data-In/Monitoring-using-quot-WinPrintMon-quot-why-are-some-universal/m-p/134629#M27677 <P>how did you enable it?</P> Wed, 13 Jun 2018 16:01:11 GMT https://community.splunk.com/t5/Getting-Data-In/Monitoring-using-quot-WinPrintMon-quot-why-are-some-universal/m-p/134629#M27677 lmakonnen2 2018-06-13T16:01:11Z https://community.splunk.com/t5/Getting-Data-In/Monitoring-using-quot-WinPrintMon-quot-why-are-some-universal/m-p/134630#M27678 <P>I have same issues and the problem is that I don't hove access to the servers reporting this error. Can you share how you enabled the services. </P> Wed, 13 Jun 2018 16:04:21 GMT https://community.splunk.com/t5/Getting-Data-In/Monitoring-using-quot-WinPrintMon-quot-why-are-some-universal/m-p/134630#M27678 lmakonnen2 2018-06-13T16:04:21Z https://community.splunk.com/t5/Getting-Data-In/Monitoring-using-quot-WinPrintMon-quot-why-are-some-universal/m-p/699678#M115891 <P>Some additional details why it happens here:</P><P>&nbsp;</P><P><A href="https://community.splunk.com/t5/Getting-Data-In/splunk-winprintmon-exe-splunk-winPrintMon-monitorHost/m-p/680673" target="_blank">https://community.splunk.com/t5/Getting-Data-In/splunk-winprintmon-exe-splunk-winPrintMon-monitorHost/m-p/680673</A></P> Fri, 20 Sep 2024 09:36:41 GMT https://community.splunk.com/t5/Getting-Data-In/Monitoring-using-quot-WinPrintMon-quot-why-are-some-universal/m-p/699678#M115891 edoardo_vicendo 2024-09-20T09:36:41Z