I have just upgraded my Wyse to the 8.0_030 beta (Wyse R10) connected to my VDI which had a disconnected session on it (XenDesktop 8.6.200 VDA) and got a "Virtual Driver Error"
I saw this as well. Connected from a R10 running 7.1.207 to Win7 64 bit VDA 5.6.200; disconnected then tried to connect from a new D10, and got the "Virtual Driver Error" message. I was then unable to connect to the virtual desktop again until I restarted the virtual desktop.
We have this very same issue : Virtual Device Error at connection time to our old Citrix Metaframe XP Farm.
we have just purchased a couple of D10D; we used to use C10LE
These new D10D came with firmware 8.0_37 and needs to connect to an old Citrix Metaframe XP. Up to now, it is impossible to have a connection, we also have error "Virtual Driver Error".
C10LE with firmware 7.1_207 does not have the error BUT if I upgrade the firmware to 8.0_37, I have exactly the same error message. Going back to firmware 7.1.207 correct the issue.
We can reproduced this error all time on both D10D & C10LE with firmware 8.0_37.
I am trying to play around with the display settings but this does not correct the issue.
I just experienced this same error with one of my users. I was replacing the user's PC with a Wyse Xenith 2 terminal running firmware v2.0.026.
She disconnected from her Xendesktop session, I swapped the hardware, then she received this error when trying to log back on via the new terminal. I was able to successfully log onto 2 other vdi sessions as other users after making no changes to the terminal and while logged onto the terminal as myself, the user having the problem was able to log onto her vdi session through our web portal with no problems.
The problem went away immediately after manually rebooting her virtual machine and has not recurred.
No one else has experienced this and I cannot reproduce it at all.
I came across this thread and thought it may be helpful to add to it with what we've experienced....
We are having a very hard time trying to replicate this issue.
Could you please define what steps you are are doing to trigger this? As much detail as you can provide will be of great help for us. No detail is insignificant.
I had this again after upgrading to the new 8.0_31 beta firmware. I had to restart the R10 from the power button, but I didn't have to restart my VDI and it connected fine the second time.
lulin
73 Posts
2427
0
Posted June 18th, 2015 07:00
is it a ramdom issue or reproducible