Skip to content

Update serial-console-errors.md #1993

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.

Sign up for GitHub

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

Open
rafatecoy wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update serial-console-errors.md #1993

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions support/azure/virtual-machines/windows/serial-console-errors.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,7 @@ The serial console connection to the VM encountered an error: 'Forbidden'(Subscr
Azure Serial Console requests result in the error "Sorry, the serial console was unable to connect to the VM because the service didn't respond in a timely manner." | In rare circumstances, a communication failure might prevent the Azure node from correctly applying a boot diagnostics configuration. To resolve this issue, [try to reapply the VM state](vm-stuck-in-failed-state.md#resolution) in the Azure portal.
The serial console successfully connects to the VM, but no output is displayed, and user input is unresponsive. | Serial Console and logs might not be available after you run a live migration for Generation 2 VMs by having Trusted Launch and Secure Boot enabled. To resolve this issue, run a guest OS restart.
The serial console shows the error message: **Another connection is currently in progress to this VM. Please wait and retry the request.** | This message indicates that another user might have Serial Console open in the VM. If this situation isn't true, try to restore Azure Serial Console access by disabling and re-enabling boot diagnostics.
At Windows VM, after to connect to Serial Console and, at SAC, you try to open a command prompt session (by running the `cmd` command) it shows the error: **Unable to launch a Command Prompt. The service responsible for launching Command Prompt channels has not yet registered. This may be because the service is not yet started, is disabled by the administrator, is malfunctioning or is unresponsive.** | This may indicate that the service `Special Administration Console Helper (sacsvr)` service is disabled. Go to windows services and ensure that service's startup is set as `Automatic` and it starts successfully.

## Next steps

Expand Down