We did an upgrade of one of our vCenter servers to v5 prior to the latest PRTG upgrade. We have upgraded PRTG and our remote probes to the newest v9.2 edition and were hoping that would cure the connection issues with vCenter. After the v9.2 upgrade we also discovered our remote probe did not have .Net 4 installed so we installed that and restarted the remote probe server.

After all this we could add new SOAP sensors but our existing sensors would not connect. We had to add new SOAP sensors and delete the old ones. This will cause us problems on our next 3 vCenter upgrades as we do not want to lose the historical information contained in the existing sensors.

Is there any way to prevent this from happening on our next upgrade? Or was this issue related to our having the vCenter 5 upgrade done prior to the PRTG upgrade that supported v5?

Thanks,

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Hi,
I'm afraid what you describe is the normal behaviour of these sensors. We decided not to update existing sensors as we changed the monitoring method which could have led to inconsitance in monitored data. You will have to re-add the sensors I'm afraid. If you need the historic data you may keep the old sensors in paused state.
Best regards


Mar, 2012 - Permalink