![]() If you Google "WTSVirtualChannelOpen Windows 2012 problem" you will find similar problem. Inside the program, data were tranferred in binary format buffers from server to client, in some packages there are some strange bytes inserted in the package, the result is the file was My other program Remote File Transfer got problem from this bug too. Hope that workaround may help some people until Microsoft recogizes this is a bug in their new Virtual Channel implemetation and provides some useful informations. When it starts working, it seems stable, but the error can happen at any time. The Virtual Channel could not be reopened I have to unload the whole module and retry the open and send process again. I have found the workaround method is when a error occurs during the communication, I have to close the Virtual Channel, and retry to open it (WTSVirtualChannelOpen) several times until it successes and retry the send (WTSVirtualChannelWrite) or if Sometimes WTSVirtualChannelWrite fails, return 0, but the GetLastError returns error message "The function completed Sometimes it fails at the first call in the session, not only from a repeating call as the information given from MSDN engineer. What I have found is Virtual Channel functions now become very unstable: ex: with WTSVirtualChannelOpen, I have lost almost 2 weeks to deal with this problem to make a workaround for my client to get a stable working version of my Remote Executer program. In the first thread, there are questions asked, and someone has given some information from Microsoft MSDN team but they want people pay for more support about that bug. But since Windows 2012, someone in MSDN team has changed the implementation of this protocol then everything that uses Virtual Channel as communication transport layer becomes unstable, sometimes it works, sometimes not. Up to Windows 2008R2 there were no change at all and everything works ![]() This was developed by Citrix than was resold to Microsoft. Usually all communications between server and client side under a remote session (RDP or ICA of Citrix) use Virtual Channel. I have clients suffering with this bug with all my programs using Virtual Channel. This problem is a bug in Virtual Channel.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |