"Invalid procedure call or argument" when sending: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
{{Bug}} | {{Bug}} | ||
::"Invalid procedure call or argument" | ::"Invalid procedure call or argument" | ||
| Line 11: | Line 11: | ||
This doesn't explain why this is a problem on just this laptop, but actually figuring that out would require getting yet another group from shared health involved, so might not be worth it for now. '''If another laptop gets the same problem we will need to look into what is actually causing the difference. ''' | This doesn't explain why this is a problem on just this laptop, but actually figuring that out would require getting yet another group from shared health involved, so might not be worth it for now. '''If another laptop gets the same problem we will need to look into what is actually causing the difference. ''' | ||
== Log == | |||
2022-04-13 - S7/Val got error as well | |||
2022-04-06 - H5/Lisa got the error when sending | |||
== Related articles == | == Related articles == | ||
{{Related Articles}} | {{Related Articles}} | ||
Revision as of 11:47, 2022 April 13
- "Invalid procedure call or argument"
- as of 2022-04 this is our most recently re-imaged laptop
- there were also some update messages that happened at the same time this started
- desktop confirmed that the office install is fine and that the newest version of Windows is installed
It turns out the error happens, specifically, when the collector answers the question whether the laptop is hooked up to a network cable - answering yes tries to run a netsh command, and that's what fails. So, the work-around is to just answer "no" to the network cable question.
This doesn't explain why this is a problem on just this laptop, but actually figuring that out would require getting yet another group from shared health involved, so might not be worth it for now. If another laptop gets the same problem we will need to look into what is actually causing the difference.
Log
2022-04-13 - S7/Val got error as well 2022-04-06 - H5/Lisa got the error when sending
Related articles
| Related articles: |