- Newest
- Most votes
- Most comments
Hello,
Greetings!
This message applies to ON-DEMAND fleet types where SESSION has extended the RESERVATION time of 2minutes.
Eventually ending in this error “Failed to reserve a session - Your session cannot be started”
In some case it could show another message “Your session is being prepared" but if after 15min still no connection check if:
The following group policy was enabled and set to a value which doesn't allow appstream to logon to the machine. The path to the group policy is as follows:- Computer Configuration | Administrative Templates | Windows Components | Windows Logon Options | Disable or enable software Secure Attention Sequence The policy option should be set to either “Services” or “Services and Ease of Access applications”. Please double check with the user the above GPO is set correctly and there is no other GPO to block windows custom credential provider to logon to the machine.
It is important to [ note] the common causes are applications services delaying the process, start up scripts, anti-virus scanning Appstream and operating system files as well as group policies.
What prevents instance from reaching ready state >> Operating System issues or AutoScaling activity, specifically manual API calls that change desired capacity.
Further, I was also able to find another repost article that can help in addressing the issue. [+]https://repost.aws/questions/QUXwwFgA8MRoOtFl9ngZUmcA/appstream-your-session-is-taking-longer-than-expected-to-prepare-fails
However, if you still face the issue I would advise you to reach out to AWS premium support for further troubleshooting as this may require access to resources or live troubleshooting with the HAR logs from any active session where you faced the issue.
[+] How do I create a HAR file from my browser for an AWS Support case? https://aws.amazon.com/premiumsupport/knowledge-center/support-case-browser-har-file/
[+] How do I get technical support from AWS? https://repost.aws/knowledge-center/get-aws-technical-support
I hope the above information is helpful.
Stay safe and have a good day!
Thanks for responding. The machines never fail. I agree it could be GPO, antivirus, gremlins etc but I am hoping for more than a trial and error method of solving this problem and I don't have access to premium support.
Relevant content
- asked 8 months ago
- Accepted Answerasked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago