krys
New Member
Posts: 11
|
Post by krys on Sept 24, 2020 16:11:54 GMT
Got a weird one here, using UI outside of a task sequence. Take this code for an example: <UIpp Title="Test" Color="#282c5c" Flat="TRUE">
<Actions>
<Action Type="WMIRead" Variable="PartSN" Namespace="root\cimv2" Class="Win32_systemenclosure" Property="SerialNumber"/>
<Action Type="Info" Title="Serial" Name="SystemName" ShowBack="True" ShowCancel="True">
<![CDATA[<font size="12">Trunked serial = <b>%PartSN%</b></font>]]>
</Action>
</Actions>
</UIpp>
Simples, read WMI, sets variable and displays window with the SerialNumber. Works on most of the computers except a few, and I cannot find the reason why. It simply doesn't launch, and here's the error: I've confirmed WMI is intact on here, my theory is that it can't set the Variable. The initial problem was that I couldn't use DefaultValues at all, it wouldn't even produce an error in the log, and just refuse to launch. It would show that it was doing the step but then close the window. On a working machine, the step where 'Something went Terribly Wrong' is '+ Set the Task sequence Variable...' I have two same model workstations (HP 640 G2), imaged same date with the same TS. Running the same script located on a share. One can load UI++, the other gets this 'Something went Terribly Wrong'. Does anyone know where it sets the Variables? Maybe a hint to find out how this one machine is different. On another workstation (HP 800 G4) that had that the issue, I reimaged and the issue persisted. Would lead to hardware as issue but not model specific. Thoughts?
|
|
krys
New Member
Posts: 11
|
Post by krys on Sept 24, 2020 20:28:17 GMT
Shoot, Reimaging the same workstation with the issue did resolve in one case. Definitely not hardware related, just OS missing something...
|
|
krys
New Member
Posts: 11
|
Post by krys on Dec 23, 2020 17:11:59 GMT
This issue continues to plague me on a couple machines randomly in my environment.
Now it's appeared on my main computer where I have built and tested all my scripts. It used to work to do default actions, no longer.
The last thing the logs report is '*Getting asset information...' and then nothing, application shuts down.
I still get 'Something went Terribly wrong' when trying to do a simple WMIRead.
Is there a way to drill down to find out why it cannot read WMI?
|
|
krys
New Member
Posts: 11
|
Post by krys on Dec 23, 2020 17:42:01 GMT
Further to this. I did what testing I knew how.
Back rev a version (2.11.1.1) works to WMI Read, fails Default Values but that is a known bug, fixed in 2.11.1.2.
Using 2.11.1.2 x86 works using the same code that fails when using the x64.
Not sure what to make of that, but will continue using the x86 instead, as I don't understand the tangible difference.
|
|
|
Post by Jason on Dec 26, 2020 20:04:42 GMT
|
|
krys
New Member
Posts: 11
|
Post by krys on Jan 11, 2021 19:06:15 GMT
Hi Jason,
Sorry, I didn't get notification you had replied. Thanks for looking into it.
Same thing with the version from that link, tho it's coming up as 2.11.6.0. The log below is first running the x86 from the 3.0 download, then the x64. x86 works great, x64 'something went terribly wrong'
Anything I can do to test further?
-- UI++ Startup ---------------------------------------- UI++ 1/11/2021 12:59:13 PM 29524 (0x7354) UI++ version: 2.11.6.0. UI++ 1/11/2021 12:59:13 PM 29524 (0x7354) Not running from within a Task Sequence UI++ 1/11/2021 12:59:13 PM 29524 (0x7354) Not running in WinPE UI++ 1/11/2021 12:59:13 PM 29524 (0x7354) Loading configuration file "UI++.xml": No error UI++ 1/11/2021 12:59:13 PM 29524 (0x7354) Loading VBScript environment: Success. UI++ 1/11/2021 12:59:13 PM 29524 (0x7354) Begin configuration file read UI++ 1/11/2021 12:59:13 PM 29524 (0x7354) Found <WMIRead> Action: UI++ 1/11/2021 12:59:13 PM 29524 (0x7354) Initiating <WMIRead> Action: UI++ 1/11/2021 12:59:13 PM 29524 (0x7354) * Loaded WMI value from (namespace) root\cimv2, (class) win32_systemenclosure, (property) SerialNumber, (key) : 5CG7470CDJ UI++ 1/11/2021 12:59:13 PM 29524 (0x7354) + Set the task sequence variable 'PartSN' to the value '5CG7470CDJ' UI++ 1/11/2021 12:59:13 PM 29524 (0x7354) Found <Info> Action: SystemName UI++ 1/11/2021 12:59:13 PM 29524 (0x7354) Initiating <Info> Action: SystemName UI++ 1/11/2021 12:59:13 PM 29524 (0x7354) > OK button pushed ... moving to next action. UI++ 1/11/2021 12:59:16 PM 29524 (0x7354) -- UI++ Finished ---------------------------------------- UI++ 1/11/2021 12:59:16 PM 29524 (0x7354)
-- UI++ Startup ---------------------------------------- UI++ 1/11/2021 12:59:18 PM 29660 (0x73DC) UI++ version: 2.11.6.0. UI++ 1/11/2021 12:59:18 PM 29660 (0x73DC) Running from within a Task Sequence UI++ 1/11/2021 12:59:18 PM 29660 (0x73DC) Not running in WinPE UI++ 1/11/2021 12:59:18 PM 29660 (0x73DC) Loading configuration file "UI++.xml": No error UI++ 1/11/2021 12:59:18 PM 29660 (0x73DC) Loading VBScript environment: Success. UI++ 1/11/2021 12:59:18 PM 29660 (0x73DC) Begin configuration file read UI++ 1/11/2021 12:59:18 PM 29660 (0x73DC) Found <WMIRead> Action: UI++ 1/11/2021 12:59:18 PM 29660 (0x73DC) Initiating <WMIRead> Action: UI++ 1/11/2021 12:59:18 PM 29660 (0x73DC) * Loaded WMI value from (namespace) root\cimv2, (class) win32_systemenclosure, (property) SerialNumber, (key) : 5CG7470CDJ UI++ 1/11/2021 12:59:18 PM 29660 (0x73DC) Something went terribly wrong UI++ 1/11/2021 12:59:18 PM 29660 (0x73DC) -- UI++ Finished ---------------------------------------- UI++ 1/11/2021 12:59:18 PM 29660 (0x73DC)
|
|