"Special Requirements to perform bulk actions" error on attempted Workspace Restore or Rebuild

0

Hello,

I'm attempting to restore or rebuild a workspace that was active yesterday but then suddenly became unavailable (unreachable) with the standard "unable to connect" message. The unable to connect behavior has persisted for more than 24 hours.

Things that have been tried:

  1. Reboot Workspace - still unreachable.
  2. Stop / Start Workspace - it stops and then we restart it, but it is still unable to connect.
  3. Adjusting / adding root and user disk space - the space is adjusted and reflected in the workspaces listing.

Additional notes:

  1. No changes to Security Groups or IP Whitelisting has occurred.
  2. Other users and workspaces have continued to function fine.
  3. I also created a 2nd workspace for the same person (to verify it isn't overarching network/firewall issues) -- and they are able to connect just fine.

Also: My user has full global admin privileges and explicitly has all of the AmazonWorkspaces* policies attached.

Does anyone else have any helpful hints / tips before we write this workspace off and start over?

Neal

已提問 2 年前檢視次數 251 次
1 個回答
0

Hello Neal,

In troubleshooting, can you access the WorkSpaces through RDP? If not have you tried the instructions connect to a WorkSpaces using RDP?

If you are able to get into the WorkSpace, then you can review the OS logs to see what may be causing the WorkSpace to become unavailable.

You should also enable advance logging on the WorkSpace client and attempt to connect. This will provide you with additional details on when/where in the logon process is failing.

Last, if you have AWS Premium Support plan, please open an support ticket and upload the logs and specify the WorkSpace ID/Information for a support engineer to investigate.

profile pictureAWS
專家
Dzung_N
已回答 2 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南