Add TSG: Get-SolutionUpdate intermittent NullReferenceException (2505-2604)#331
Closed
AlBurns-MSFT wants to merge 1 commit into
Closed
Add TSG: Get-SolutionUpdate intermittent NullReferenceException (2505-2604)#331AlBurns-MSFT wants to merge 1 commit into
AlBurns-MSFT wants to merge 1 commit into
Conversation
…-2604) Customer-facing troubleshooting guide for an intermittent NullReferenceException from Get-SolutionUpdate / Get-SolutionUpdateEnvironment during solution updates on builds 2505-2604 (resolved in 2605+). The applicability gate uses only customer-observable signals (build range, exact error, intermittent behavior); guidance is retry -> contact support, with the permanent fix being an update to 2605+. Cross-links the existing GatewayTimeout TSG and indexes the new page in TSG/Update/README.md. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: AlBurns-MSFT <6195567+AlBurns-MSFT@users.noreply.github.com>
|
|
||
| This article applies when **all** of the following are true: | ||
|
|
||
| 1. The cluster is on a build in the range **2505-2604** (23H2 `11.25xx`-`11.26xx`, or 24H2 `12.25xx`-`12.26xx`). Confirm the current version from the Azure portal (your Azure Local instance -> **Updates**), or from `Get-SolutionUpdate | ft Version, State` once the cmdlet returns. |
There was a problem hiding this comment.
Since we are confirming current stamp version, we should use Get-SolutionUpdateEnvironment instead of Get-SoluitonUpdate on the device. But since those 2 cmdlets are also impacted, I'm thinking that we should use Get-StampInformation instead which is through ECE
Collaborator
Author
|
I'm going to pull this draft and not merge. The keep retrying you will likely succeed advice doesn't hold up upon a second look. I don't think this will actually help anyone avoid a support case if they run into this and cant resolve through a retry. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a customer-facing troubleshooting guide for an intermittent
NullReferenceExceptionfromGet-SolutionUpdate/Get-SolutionUpdateEnvironmentseen during solution updates on builds 2505-2604. The failure is transient (a retry usually succeeds) and is resolved in build 2605 and later.Why
There is currently no public article for this symptom -- only the existing
Get-SolutionUpdate GatewayTimeoutTSG, which covers the hang / timeout variant of the same cmdlet, not the intermittentNullReferenceException. Customers who hit the NRE have nothing to self-identify against.Guidance shape
TSG/Update/README.md.Status
Draft -- opened for the Update Service PG to review the wording and confirm this is the right public surface and framing before it merges.