Thursday, December 13, 2012

VMware View 5.1.1 printer redirection with ThinPrint no longer works after upgrade from 5.0

--------------------------------------------------------------------------------------------------------------------------------------------------------------------

Update December 17, 2012

I received an update from the engineer I was working with on this case today to inform me that the new 5.1.2 agent was out and to try it and it looks like upgrading the agent:

VMware View Agent Version: 5.1.1.799444

clip_image002[4]

… to:

VMware View Agent Version: 5.1.2.928164

clip_image002

… fixes the issue as the TPAutoConnect.exe no longer crashes.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------

Just last weekend on Sunday December 9, 2012 was when I had a scheduled VMware View 5.1.1 – Build 799444 upgrade:

image

… for a client that was still on VMware View 5.0 and as well as the upgrade went, I was informed by the client on Monday morning that their remote users were no longer seeing their local printers in their home office.  This prompted me to log into my own virtual desktop from remote to have a look and I immediately noticed that I too as well did not see the local printers I had available from my laptop.  Subsequent logins would sporadically show the following window:

ThinPrint AutoConnect component

ThinPrint AutoConnect component has stopped working

Windows can check online for a solution to the problem.

Check online for a solution and close the program

Close the program

Problem Event Name: APPCRASH

TPAutoConnect.exe

Application Version: 8.8.734.1

image

Browsing through the event logs also showed the following event logged upon restarting the virtual desktop and logging on:

Faulting application name: TPAutoConnect.exe, version: 8.8.734.1, time stamp: 0x4f97fe6d

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x00000000

Faulting process id: 0x1530

Faulting application start time: 0x01cdd734dcd7ce35

Faulting application path: C:\Program Files\VMware\VMware Tools\TPAutoConnect.exe

Faulting module path: unknown

Report Id: 215ff1d9-4328-11e2-a1e8-005056be7ab3

image

Doing a few searches on Google revealed one or two forum posts with other users complaining but no solution so once I realized this was probably something I couldn’t personally troubleshoot and fix, I opened up a support ticket.  It took a few days until I was able to speak with the support engineer assigned to my case and it looks like this was a known issue with VMware View 5.1.1 with the VMware View Agent 5.1.1.799444:

image

I was asked to review the following KB:

Printer redirection fails when using PCoIP with the View 5.1.1 Agent
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2036725

… which I was sort of surprised that I didn’t come across but then realized that it was dated December 10th (one day after the upgrade).

I have since uploaded the VMware View Agent logs to VMware via the following KB:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1017939

… so that the engineer can confirm.  From what I was able to ask the engineer during our short phone conversation, it doesn’t look like I can downgrade the VMware Agent to fix this and the only workaround is to use RDP instead of PCoIP.  I have since done a test by switching the protocol to RDP and the printer redirection began to work.

1 comment:

Joe Clarke said...

Per the 5.1.2 release notes resolved issues:

View Client

Network printers were not being redirected into desktop virtual machines after upgrading to View 5.1.