This content has been marked as final. Show 2 replies
I do sometimes get this with 3.2.2 and new machines. What works for me is to migrate the vm to another server and retry the console connection
Thanks, Bjoern...it is happening in our dev environment where I do not have another server available.