[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2574
  • Last Modified:

VMWARE View Client

Hi everyone,
I'm hoping that someone will be able to help me out with an issue I am having. We have several users who are complaining about a runtime error when they are working on their Virtual Desktops.  The error message (below) pops up and clicking on 'ok' (their only option) disconnects them from their desktop. They are allowed to immediately sign back in &  when it reopens their desktop they have not lost what they are working on.  This is a nuisance of a problem, it would be much more severe if this mesage closed everything they were working on, but as it only forces the View Client connection closed for a moment without shutting down what they are working on it only proves to be an irritation.  However, it's an irritation that I would like to get cleared up.  

*Error Message*
Microsoft Visual C++ Runtime Library
Runtime Error!
Program: C:\Program Files\VMWare\VMware View\Client\bin\wswc.exe
abnormal program termination

Also, the users that are reporting this issue are logging in to a normal PC and connecting to a Virtual Desktop via a VMWare View Client icon. Has anyone experienced/solved this issue previously?

Thanks in advance for any assistance you can provide to me!
ASB_Tech
0
ASB_Tech
Asked:
ASB_Tech
  • 7
  • 6
3 Solutions
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
What operating system is the VMware View Client installed on?

What version of the VMware View client are toy using 4.5 or 4.6?

and what build number of the clent are you using?
0
 
ASB_TechAuthor Commented:
I have a report of this message coming from a user on each of the following OS's:  XP Pro, Vista Business, & Windows7 Professional.

VMWare View Client  - 4.0.1

Build # - 233023
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Have they been updated recently with Windows Updates?

Are you on View 4.0?
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I would look at 4.0.2 Build 294291, just install and test on a test PC first to check if it can connect to 4.0.1 server, and if so, try on these affected PCs (one at a time)
0
 
ASB_TechAuthor Commented:
Updates would have been last run on these machines at least a week prior to this problem occuring.
Yes, we are currently on View 4.0.

I reinstalled our current build on the XP machine yesterday, so we will see if that limits the frequency of the error today. This was the 'fix' the last time we experienced this issue, although it was not a true fix it just slowed the occurences of the runtime errors, users were still getting the error about once a day. Better than once an hour, but something I would like to get fully resolved if possible.
0
 
ASB_TechAuthor Commented:
To me, it seems that this is an error that the PC is experiencing, as I have not had any users that are connecting via a Thin Client device complain/mention this problem before.  I myself use a Thin Client to connect to my Virtual Desktop and have not seen this runtime error in 18 months, except when someone sends me a snapshot of it occuring.

I'll give the 4.0.2 build a try on Monday morning if reinstalling the current build does not temper the frequency of the error message today.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
im not sure if VMware are developing v4 any further now that 4.6 has been released, it is known that Windows Updates have broken View Clients, if you can provide evidence to VMware which update usually a .Net framework patch, is causing the issue they may issue an updated 4.0.2 client.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
unfortunately PCs never have fixed configurations, with updates and applications being applied. One of the benefits of using thin clients.
0
 
ASB_TechAuthor Commented:
Looks like the 'temp fix' is to reinstall current buil don the PC, it slows the occurence of the error down to once or twice a day as opposed to 4 or 5 times every couple hours...

Not overly thrilled that Windows Updates seem to be able to shake View Client'ss foundation so much, but not much I can do about that except rant & rave,, we'll re-install the 4.0 version on the afficted PC's & look to upgrade to View Client 4.5 or 4.6 in the near future.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Jump straight to VMware View 4.6 if possible.

Windows Updates can affect any software application, it's the .NET framework Security Updates that seem most problematic.

Any organisation should really test all updates that come out from Microsoft on Microsoft patch tuesday, to check they are suitable for their environment, before applying. I know this is difficult, but this should be done.
0
 
ASB_TechAuthor Commented:
This is not an abandoned question.

We are trying to work with VMWare in resolving this issue.  The wanted us to run a WMI repair tool, which we did, and that tempered the frequency of the runtime error but did not stop/fix it.  The error would come back on the hourly frequency within a couple days of running the WMI repair tool.

We are waiting to hear back on further suggestions / fixes to try.
0
 
ASB_TechAuthor Commented:
Through a lot of phone calls & troubleshooting with VMWare we have identified this a a problem with the Virtual Desktop image that the Desktop Pool is based off of.  We are moving the affected users to a new desktop pool as our fix.

Initially we thought this conflict between the PC & VMware View Client was on the PC side, since that was where the error was being thrown.  However, after exhaustive testing, which included created mock pools based off of our other gold images, it was determined that it was in fact occuring on the VMware side of the equation.  We reached this conclusion after I was unable to replicate the issue using the View Client connection to my VD.  This inability to recreate the error led to test the permissions on the wswc.exe file on the PC.  When this did not have any resolution (added a test user to have all of my memberships & tested connections to various images) we began focusing on the images themselves.  

We revisted the affected users & found that they were all in the same desktop pool.  That led to a series of tests including having myself (no errors prior to this) logging in to a VD based off of that image. Low and behold I received the error (much more testing than this btw).  Therefore we decided to create a new desktop pool based off of a new image to move any users affected by the Runtime Error.  We have decided not to persue why this image is having a conflict witht the VIew Client unless this occurs again.

Bottom line, this Runtime Error is caused by the View Desktop conflicting with the View Client executable on the PC.  The error will appear as though a problem is occuring on the PC but the true culprit is a faulty/defective image that the VD is based on.
0
 
ASB_TechAuthor Commented:
Solution based off of testing in conjunction with vmware
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 7
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now