Hello,

I found that one of my probe was stopped. So, I tried to start it. But I got an error:

[Window Title] PRTG Probe Administration Tool

[Content] PRTG Probe Service could not be started: The service did not respond to the start or control request in a timely fashion

[OK]

Also, I saw endless dialogbox popup: [Window Title] Prtg probe administrator

[Content] The filename, directory name, or volume label syntax is incorrect.

[OK]

Do I have to reinstall this probe?

Regards, Il Mo Jung

Article Comments

Are you able to stop and start the probe manually, from Window's Service Manager? If not, I would suggest killing the task and reinstalling the probe. If that does not work, please open a ticket by sending an email to support@paessler.com. Please also forward us your log files for analysis.


Sep, 2013 - Permalink

PRTG service can be started manually from Windows' service manager. What would be the difference between starting from services.msc and from PRTG admin console?


Sep, 2013 - Permalink

Once it is started properly from the Service Manager, are you able to stop and start the service via the Administration tool?


Sep, 2013 - Permalink

Yes, I can.


Sep, 2013 - Permalink

Is it working properly now, then?


Sep, 2013 - Permalink

Yes, it is. Which condition can cause this?


Sep, 2013 - Permalink

To be honest, this should not really happen, particularly not if stopping / restarting the probe externally then fixes the issue. In order to check if we can discern what the problem was, please forward us your log files as outlined under How can I upload log files to Paessler support team? referring to this thread. Please forward both the core and the probe server log files.


Sep, 2013 - Permalink

What is the ticket number for this issue?


Sep, 2013 - Permalink

Send us a mail to support@paessler.com with reference to this thread - that way a ticket will be opened and you will receive an automatic response including the ticket number.


Sep, 2013 - Permalink

Except for minor entries that would not cause this issue we cannot directly identify anything that would have caused this problem. Have you experienced this issue since? If not, our guess would be this was a coincidental hangup and would ask you to watch this and let us know if the issue happens again.


Sep, 2013 - Permalink

At least, I think that the code part which might cause endless popup: [Content] The filename, directory name, or volume label syntax is incorrect.

should be re-checked. I will report if the same case is found. Thank you.


Sep, 2013 - Permalink

This seems to have been more of a result of the hangup than the cause, reason why it unfortunately does not yield information as to what made the service not start properly. And yes, please let us know if you experience the issue again.


Sep, 2013 - Permalink