-
-
Notifications
You must be signed in to change notification settings - Fork 39
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.
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
Attempted to write progress on an uninitialized ProgressRecord #274
Comments
Hi @benclaussen1, Please be advised a new pre-release version of PrtgAPI has now been released which should include a fix for this issue. Please see the manual installation instructions for details on how to run this pre-release version. This issue specifically only occurs when executing a pipeline in the form Variable -> Third Party Cmdlet PrtgAPI doesn't have special handling for (e.g. Regards, |
Awesome! Thanks for the prompt fix! I’m out of town until next week but will install when I return.
Out-GridView isn’t an everyday thing for me and PRTG. I submitted the issue since the error requested so
…________________________________
From: lordmilko ***@***.***>
Sent: Thursday, March 3, 2022 01:59
To: lordmilko/PrtgAPI
Cc: Ben Claussen; Mention
Subject: Re: [lordmilko/PrtgAPI] Attempted to write progress on an uninitialized ProgressRecord (Issue #274)
Hi @benclaussen1<https://github.com/benclaussen1>,
Please be advised a new pre-release version of PrtgAPI has now been released which should include a fix for this issue. Please see the manual<https://github.com/lordmilko/PrtgAPI/wiki/Installation#manual> installation instructions for details on how to run this pre-release version.
This issue specifically only occurs when executing a pipeline in the form Variable -> Third Party Cmdlet PrtgAPI doesn't have special handling for (e.g. Out-GridView) -> PrtgAPI Cmdlet, so depending on how you use PowerShell this issue may or may not have a big impact in day to day usage of PrtgAPI
Regards,
lordmilko
—
Reply to this email directly, view it on GitHub<#274 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALE7XUOXZUEID2RLLFIRZN3U6BPL7ANCNFSM5PLJZYTA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Tested this morning... Working perfectly for me. Thanks! |
Describe the bug
While updating our deprecated DNS sensors, I was going to remove the old ones when I received this error:
After running
Disable-PrtgProgress
my pipeline executed successfully.Steps to reproduce
What is the output of 'Get-PrtgClient -Diagnostic'?
Additional context
No response
The text was updated successfully, but these errors were encountered: