Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Sensor-Property-Change-Bug #271

Closed
eklatzer opened this issue Feb 22, 2022 · 1 comment
Closed

Sensor-Property-Change-Bug #271

eklatzer opened this issue Feb 22, 2022 · 1 comment
Labels
duplicate Questions raised by people who don't know how to search through previous issues :P

Comments

@eklatzer
Copy link

eklatzer commented Feb 22, 2022 •
edited
Loading

Describe the bug

Hello, when updating the Object-Property ExeFile of a sensor the value for the script in PRTG looks weird:

image

Steps to reproduce

PrtgClient client = new PrtgClient(<URL>, <User>, <Passhash>, AuthMode.PassHash);
client.SetObjectProperty(13104, ObjectProperty.ExeFile, "sensor.exe");

What is the output of 'Get-PrtgClient -Diagnostic'?

PrtgAPI v0.9.16
PRTG v21.4.72.1649+
Operating system where the code is run: Windows 10 Pro
Operating system of the PRTG instance: Windows Server 2019 Standard

Additional context

No response
@eklatzer eklatzer added the alleged-bug Bugs raised by people helpfully using the Bug Report template! label Feb 22, 2022
@lordmilko
Copy link
Owner

Duplicate of #268

@lordmilko lordmilko marked this as a duplicate of #268 Feb 23, 2022
@lordmilko lordmilko added duplicate Questions raised by people who don't know how to search through previous issues :P and removed alleged-bug Bugs raised by people helpfully using the Bug Report template! labels Feb 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate Questions raised by people who don't know how to search through previous issues :P
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lordmilko @eklatzer