Hi guys, I am playing with the Data Extractor from Paessler. I know it is not supported anymore but maybe you can still answer a simple question where I am really struggling at moment. I tried the app itself and when I added username and password it is working as I hoped. So I wanted to run the tool via task scheduler so I tried following from the cmd
Dataextractor.exe -prtghost "localhost" -prtguser "prtg-user" -prtgpw "<yourprtgpassword>" -dbserver "SQL SERver" -db "PRTG_Extractor" -dbuser "PRTG-Extractor" -dbpw "<yourdbpassword>"
but this did not work. I simply get the blinking cursor and nothing happen.
Does someone know what I am doing wrong?
Article Comments
Sorry for my late reply. I did some additional testings in the meanwhile. If the access is possible via Port 80 I am adding the parameter -prtgport "80" and it is working.
If the access to PRTG is only possible via https I tried to change the parameter to Port 443. but this did not help.
How is the flag https in the extractor enabled on command line?
Jun, 2019 - Permalink
It might be possible that only TLS 1.0 is supported for this, not quite sure. What protocols are allowed within your webserver? They can be checked via
| Setup | System Administration | User Interface | Web Server | Connection Security |
|---|
Jun, 2019 - Permalink
Well this is not the reason why it is not working. When I manually set the flag https enabled on the Data Extractor it is working. I simply need to understand which parameter I need set to mark the flag https
Jun, 2019 - Permalink
Ah, now I get it. Sorry, this was a misunderstanding on my end. The parameters accepted in the commandline are the following:
- -prtghost
- -prtguser
- -prtgpw
- -prtgport
- -dbserver
- -db
- -dbuser
- -dbpw
- -sensorserver
- -sensorport
- -sensortoken
- -idfrom
- -idto
- -dbsspi
- -nosensordata
- -notoplistdata
Unfortunately, HTTPS isn't one of them. Since the PRTG webinterface does redirect any incoming connections to HTTPS automatically, this shouldn't be an issue. However, I'm not sure, why it's not working on your end :/ I'm afraid that we won't come to a satisfying conclusion here, as the tool is practically abandonware...
Jun, 2019 - Permalink
Thanks a lot for your reply (and sorry for my late answer).
At the end I created a workaround and was able to get the connection through port 80.
Just one more question: When the Database instance is running on a different port like 9877 and not 1433 is there a way to add the Port of the DB instance?
Jun, 2019 - Permalink
Hi there,
As far as I can tell there is no dedicated parameter for db port, the ui of the extractor also has no field for it. Does it fail when running on port 9877 for example? You could try appending the port like "yourdbserver:9877".
Kind regards,
Erhard
Jun, 2019 - Permalink
Does it work when you execute the line manually in the command line?
May, 2019 - Permalink