The trial version of PRTG has been working but I am approaching the end of the trial and, since I am using this at home with fewer than 100 sensors, I would like to continue to use the freeware version. However, the PRTG Core Server Service will not start. When I try to start the Core Server in Windows Services, I get the error message "Windows could not start the PRTG Core Server Service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion." I have tried rebooting, uninstalling/reinstalling, and several other suggestions from your Knowledge Base and Google searches. Please help.
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.
Dariusz,
There are several errors similar to the following:
Faulting application name: PRTG Server.exe, version: 17.4.36.3670, time stamp: 0x5a37cd3c Faulting module name: PaesslerSNMP.dll, version: 5.7.2.3, time stamp: 0x5981e9be Exception code: 0xc0000409 Fault offset: 0x000000000008474c Faulting process id: 0x630 Faulting application start time: 0x01d37ff44eefc51c Faulting application path: C:\Program Files (x86)\PRTG Network Monitor\64 bit\PRTG Server.exe Faulting module path: C:\Program Files (x86)\PRTG Network Monitor\64 bit\PaesslerSNMP.dll Report Id: a45b4540-cb9a-4494-8d55-3bb1d3ac0ab0 Faulting package full name: Faulting package-relative application ID:
Thanks for your help, Dave
Dec, 2017 - Permalink
Hi Datippin,
There is a known issue which effects the start of the core server. Please navigate to the directory "C:\Program Files (x86)\PRTG Network Monitor\64 bit" and check if there is a folder named ".\snmptemp\mib_indexes". If this is the case, rename the directory and try to start the service.
If such a directory does not exist, kindly check if there is a NET-SNMP installation located in the directory "C:\usr\".
We'd appreciate your feedback if the service starts correctly afterwards.
Best regards, Felix
Dec, 2017 - Permalink
Felix,
Renaming "mib_indexes" solved the problem. Thank you!
Best regards, Dave
Dec, 2017 - Permalink
If you have an existing NET-SNMP installation on your system, the environment variable %SNMPCONFPATH% might have been set as well. You can check this in a cmd shell by typing:
echo %SNMPCONFPATH%
If it returns a path i.e. D:\usr\etc\snmp, you're gonna have to have a look at the file snmp.conf found there, and see if "persistentDir" has been set in it.
On my system it has been set to "persistentDir D:/usr/snmp/persist"
This means PRTG will store its temporary MIB indexes in D:\usr\snmp\persist\mib_indexes and not in .\snmptemp\mib_indexes as suggested above.
I deleted the files found there (they were corrupt), and then I was able to start both the core server and probe services again.
The developers should take a look at this, as I think it's unwise that PRTG's NET-SNMP library uses the very same directory as a pre-existing NET-SNMP installation on the system for storing its temporary files.
Sep, 2021 - Permalink
Hello Ivan,
Thanks for sharing your findings with the community, much appreciated.
Kind regards,
Felix Saure, Tech Support Team
Sep, 2021 - Permalink
Hello Ivan,
Thanks for sharing your findings with the community, much appreciated.
Kind regards,
Felix Saure, Tech Support Team
Sep, 2021 - Permalink
Hi there,
Please open the Event Viewer of Windows and search for Errors under "Windows Logs > Applications". Is there any Error related to PRTG? If so, please post the upper details of the Error (which Applikation caused the issue, which DLL and so on).
Best regards.
Dec, 2017 - Permalink