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.

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

Measure-FleetCoreWorkload - Import-Counter function #191

Open
jayr0x opened this issue Nov 10, 2022 · 7 comments
Open

Measure-FleetCoreWorkload - Import-Counter function #191

jayr0x opened this issue Nov 10, 2022 · 7 comments

Comments

@jayr0x
Copy link

jayr0x commented Nov 10, 2022

Hello guys,
for context, I had to set my locale OS to English US to be able to run the script. After the first run, I've encountered the error below.
image

in the coreworkload log :
-11-10T20:18:31: COMPLETION CHECK 7 : 64/64 done (0,02s, total 12,59s)
PS>TerminatingError(Import-Counter): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: L’objet spécifié n’a pas été trouvé sur l’ordinateur."

TerminatingError(Import-Counter): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: L’objet spécifié n’a pas été trouvé sur l’ordinateur."
TerminatingError(Import-Counter): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: L’objet spécifié n’a pas été trouvé sur l’ordinateur."
TerminatingError(Import-Counter): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: L’objet spécifié n’a pas été trouvé sur l’ordinateur."
TerminatingError(Import-Counter): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: L’objet spécifié n’a pas été trouvé sur l’ordinateur."
2022-11-10T20:18:53: Iteration file content saved to C:\ClusterStorage\collect\result\error for triage
PS>TerminatingError(Import-Counter): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: L’objet spécifié n’a pas été trouvé sur l’ordinateur."
TerminatingError(Import-Counter): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: L’objet spécifié n’a pas été trouvé sur l’ordinateur."


Windows PowerShell transcript end
End time: 20221110201853


Do you have any idea what could be missing ?
The error says : the specified object can't be found on the computer.
My guess would be a specific counter name can't be found ?

@dl2n
Copy link
Member

dl2n commented Nov 11, 2022

Could you look at the output of "typeperf -q" and/or tell me if the performance counter set names are localized when in the French fr-fr locale? (I assume that was your original)

@jayr0x
Copy link
Author

jayr0x commented Nov 12, 2022

when the os is in french, the names are localized. but since i switch to english, to make the script working (at least the first run) it is correctly localized.
here is the export of the command typeperf -q
typeperf.txt

the only thing that I did not change since I think it would not matter for the reports are the Format.
image
image

@jayr0x
Copy link
Author

jayr0x commented Nov 17, 2022

any update possible on this "issue" ?

@dl2n
Copy link
Member

dl2n commented Nov 29, 2022

Sorry, just to be clear: when the localization is fr-fr (or not en-us), are the names of the counter sets (the output of typeperf -q) localized? That is what I was looking for when asking for that output - in the fr-fr localization.

Your txt output shows what I am already familiar with in the en-us case.

@jayr0x
Copy link
Author

jayr0x commented Nov 29, 2022

Yes like I said above, they are localized when the OS is in french version. But I don't think that matters because I've switched to EN-US when running the script.
typeperf_FR.txt

@KaiKirste
Copy link

Hello!

I have the same issue. Same VMFleet Version.
The Cluster-OS was setup with de-de Language and then set to en-us for the script to start running. But it stops after the first run with the same error.
One question: where ist $Blg set? I found nothing that fills the variable with input.
Could this be the Problem?

Greetings from Germany

@KaiKirste
Copy link

Good news (for me)!

It works after i have setup my nodes and cluster from scratch with English Windows Server 2019 Core Setup.
Prio test with German GUI Setup including change of systemlanguage to english and complete Setup of English GUI doesn't work.

Greetings

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants