Error Reading Response Missing /prtg
ease planning, as well. Free PRTG Download >> What is this? This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions! Learn more Top Tags 5747× prtg 1842× snmp 1466× sensor 936× wmi 622× notifications 467× maps View all Tags Error reading response: missing /prtg Votes:0 Your Vote: Up Down I am monitoring a number of VMware hosts with PRTG (build 12.3.3.2855). The VMware devices are monitored by a remote PRTG probe in the same site (and IP subnet) as the VMware hosts. I am decommissioning the server the PRTG probe is installed on, so have installed a new remote PRTG probe in the same site. When I move the devices to the new probe many of the sensors alarm with the message "Error reading response: missing /prtg". If I move the device back to the original probe then the alarms clear. Both remote probes are running Windows Server 2008 R2 Standard in 64bit. Any ideas? Thanks esxi probe prtg remote-probe vmware Created on Oct 15, 2012 9:54:43 AM by Paul Huxham (0) ●1 Permalink 2 Replies Votes:0 Your Vote: Up Down Hi, please check if the .NET Framework 4 is installed on the "new" probe machine. If not, please install the same and the error should clear. Best regards Add comment Created on Oct 15, 2012 9:58:42 AM by Konstantin Wolff [Paessler Support] Permalink Votes:0 Your Vote: Up Down Yes, I installed .NET 4 and that's fixed the problem! Many thanks for the super-fast response! Best regards Paul Add comment Created on Oct 15, 2012 10:15:03 AM by Paul Huxham (0) ●1 Permalink Please log in or register to enter your reply. Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available. © 1998 - 2016 Paessler AG Solutions • Imprint • Contact • Sitemap • Privacy Policy • U
ease planning, as well. Free PRTG Download >> What is this? This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions! Learn more Top Tags 5747× prtg 1842× snmp 1466× sensor 936× wmi 622× notifications 467× maps View all Tags "Error reading response: missing /prtg" - from time to time Votes:0 Your Vote: Up Down We frequently encounter the error message "Error reading https://kb.paessler.com/en/topic/42383-error-reading-response:-missing-prtg response: missing /prtg" on a bunch of our sensors, often the ones of type XMLEXESENSOR. In our shop we have a cluster probe with two nodes. The above error only shows up on the first node, while the sensor on the other node says "OK". After a while ( could be minutes ) the error disappears and the sensor show https://kb.paessler.com/en/topic/51983-error-reading-response:-missing-prtg-from-time-to-time OK. Needless to say that this behavior is annoying when someone relies on the status of the sensor. I've found a number of related discussions but none of the suggested solutions are appropriate. Any suggestions/ideas on how to solve this issue? Or directions for further investigating the problem would be helpfull. error prtg xml Created on May 13, 2013 8:40:23 AM by MarcProvant (0) ●1 Permalink 1 Reply Votes:0 Your Vote: Up Down Could you enable "Write result to disk (Filename: "Result of Sensor [ID].txt") " for one of these sensors and send the resulting log to support@paessler.com? Also, when you send over those results, can you include your system logs? Add comment Created on May 13, 2013 2:33:32 PM by Greg Campion [Paessler Support] Permalink Please log in or register to enter your reply. Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your
Palo Alto Networks Firewalls » 06/14/2013 The Extreme Basics of PRTG custom sensors with PowerShell If you're not already familiar with PRTG, I recommend that you find a spare machine someplace to set up the demo and give http://blogs.lockstepgroup.com/2013/06/the-extreme-basics-of-prtg-custom-sensors-with-powershell.html it a try. As you might have read in some of our previous posts, we've deployed PRTG to great effect on several of our clients' networks. From a high level, PRTG is pretty standard network/device monitoring fare. There's plenty of comparisons to be made between PRTG, SolarWinds, WhatsUp Gold, and so forth, but today I'm going to discuss the one feature of PRTG that has pushed it ahead of error reading the pack: Custom Sensors. Out-of-the-box, PRTG supports a pretty wide gamut of sensors and should be able to give you reasonably comprehensive monitoring of most network devices. To get beyond the data that the packaged sensors provide, you can roll-your-own custom sensors. Custom sensors for PRTG are very simple: a script or a program gathers some data and returns it back to PRTG in a structured XML format. PRTG will error reading response execute the sensor at the interval you define and graph the returned results. We've had good success writing sensors of this type in PowerShell, which is what I'm going to cover here today - but some of this can apply to any compiled executable as well. Step One: Install PRTG Ensure that you've got it up and running and graphing data, and that you can reach the PRTG web GUI using your web browser. Firefox and Chrome or the very latest versions of IE (9, 10) strongly recommended. Step Two: Fix the PowerShell execution policy This one tends to get overlooked. On a 32-bit server, this is simple: open a PowerShell prompt with admin rights and enter Set-ExecutionPolicy RemoteSigned (other options: "AllSigned" if your scripts are all signed with Authenticode certificates, or "Unrestricted" if you just want to disable execution preventions across the board). However on 64-bit hosts (which is honestly the only architecture I've ever installed the PRTG core server on), there's an extra step: you need to set the 32-bit PowerShell execution policy, rather than the native 64-bit PowerShell policy.. Method One: locate the"Windows PowerShell (x86)" shortcut in the start menu and set the execution policy there (Set-ExecutionPolicy RemoteSigned). Method Two: run this co