| Previous | Next |
| UTC_E_AOT_NOT_RUNNING | UTC_E_SCENARIODEF_NOT_FOUND |
UTC_E_SCRIPT_TYPE_INVALID
Read this as a lifecycle result: RunScriptAction type discriminator
UTC_E_SCRIPT_TYPE_INVALID has the unsigned value 0x87C51004. In UTC it comes from scenario action execution, where RunScriptAction type discriminator owns the decision. Treat this HRESULT as a state-machine report, not as a generic telemetry outage for this HRESULT. The immediate contract failed because the scenario requested a script engine or script-kind value that the installed client does not accept, so diagnosis should remain at that boundary until a controlled comparison crosses it for this HRESULT.
Scenario actions run under service-controlled identity, timeout and cancellation rules for this HRESULT. The useful evidence is the exact action instance and its child process or script state, not a later generic service event for this HRESULT. stdout, stderr and native exit values should be retained separately from the UTC HRESULT for this HRESULT. Record the configuration package or scenario generation together with the Windows build; otherwise a repaired file can be tested against a stale in-memory graph and appear to fail for the same reason for this HRESULT.
Diagnostic record
| UTC diagnostic field | Value |
|---|---|
| Owning state or object | RunScriptAction type discriminator |
| Producing layer | scenario action execution |
| Do not confuse with | UTC_E_UNAPPROVED_SCRIPT means the type is recognized but policy does not approve that script |
| Decisive evidence | scenario action XML, script type token, schema version, file extension and target Windows build |
| Narrow comparison | replace only the type token with one accepted by the same client while keeping script contents unchanged |
The AllStat message names the immediate condition as “RunScriptAction contains an invalid script type” for this HRESULT. In practice, the useful extension is to ask whether the request was rejected before any side effect, after partial setup, or during cleanup for this HRESULT. Verify the existence and ownership of the expected output—session, directory, process, result object or emitted event—rather than assuming the message describes the final system state for this HRESULT.
Isolate one changing condition
- Export the relevant
Microsoft-Windows-UniversalTelemetryClient/Operationalevents and preserve their ActivityId or request correlation alongside this result. - Capture scenario action XML, script type token, schema version, file extension and target Windows build for this HRESULT. Do this before restarting the service or deleting any working directory for this HRESULT.
- Perform this one-variable comparison: replace only the type token with one accepted by the same client while keeping script contents unchanged for this HRESULT.
- After the comparison, record the next HRESULT and whether the requested session, action, trigger or output object was actually created for this HRESULT.
The most informative neighbor is UTC_E_UNAPPROVED_SCRIPT. The distinction is concrete: UTC_E_UNAPPROVED_SCRIPT means the type is recognized but policy does not approve that script for this HRESULT. Keeping both symbolic names in logs prevents a broad “DiagTrack error” bucket from hiding whether the failure occurred during parsing, authorization, resource acquisition, execution or teardown for this HRESULT.
Child-action accounting
Keep process creation, job assignment, timeout, cancellation, exit code and output capture as separate timestamps for this HRESULT. That sequence reveals whether the child failed itself, was terminated by UTC or never started for this HRESULT.
Operational response
Regenerate the action using the supported DiagTrack schema and approved script form for this HRESULT. Apply that change only to the owning boundary for this HRESULT. A successful repair must make the controlled case cross this boundary while retaining the intended policy, trace providers, destination and security context for this HRESULT.
Deleting the working directory, killing all ETW sessions or retrying in a tight loop can suppress this result temporarily while leaving the underlying lifecycle defect intact for this HRESULT.
- the same request now produces its documented success or nonfatal status without a second hidden retry
- the operational log shows one coherent request lifetime and no orphaned action, timer, process or trace session
- teardown followed by a second run does not reuse stale state or recreate RunScriptAction type discriminator
- the nearby condition remains distinguishable: UTC_E_UNAPPROVED_SCRIPT means the type is recognized but policy does not approve that script
Technical references
- Microsoft Open Specifications: Windows error-code registry — reference for scenario action execution while interpreting this result.
- Microsoft: Universal Telemetry Client configuration diagnosis — reference for scenario action execution while interpreting this result.
- Microsoft: UniversalTelemetryClient operational-log guidance — reference for scenario action execution while interpreting it.
- Microsoft: About Windows Error Reporting
Looking for a different code? Search another status or error code.