Error: AWHOST32 cannot find MSVCR80.DLL, service not start

[Pascal KOTTE]

Well, a lot of existing problem & article around MSVCR80.DLL, and how to recover...

http://answers.microsoft.com/en-us/windows/forum/windows_vista-windows_programs/msvcr80dll-problem/e5e1ae2f-f109-4bde-af20-ebcb7244fb5c
http://msdn.microsoft.com/en-us/library/ms235299(v=vs.80).aspx
 

Currently we face about 6 clients, this problem, on 300 (also after reboot): Those clients are of course installed with at least 2 or 3 versions of the C runtime library under WinSxS system folder:

• 8.0.50727.42
• 8.0.50727.762
• 8.0.50727.3053

http://www.symantec.com/docs/TECH111184  not really helpfull...

I wonder how can I investigate, identify into windows how to see which DLL AWHOST32 try to load, and fail... Perhaps some missing reading rights, and WinSxS folder, or registry?

I do not try yet:

• reinstall the PCA host
• install a runtime distribution package !

I guess they will not solve this issue, the install PCA host was result 0 (OK) !

Any body same problem ?

[Pascal KOTTE]

When starting the service I got the error 1053 did not respond...

I am afraid need to do a hard in depth cleaning, before reinstalling...

[Pascal KOTTE]

I find an article http://www.symantec.com/docs/TECH111184 , to run a removal...

I will try to get access one the failed machine to test this...

[ShawnOfTheFarm]

Did this just start out of the blue or did some thing trigger it?   I have seen lots of msv errors related to the use of packager when performing an upgrade.  It is best to uninstall pcA before installing a new version.  Packager should be able to upgrade an existing package but doesn't always include all the needed files and some times errors are then seen.

cheers.

[Pascal KOTTE]

But some PCA host clients stop working after this upgrade...

[ShawnOfTheFarm]

what was on the machines before? and did you remove that first?

[Pascal KOTTE]

Yes, previous version was there. No need to remove them, the PCA solution does the removal previous version. (don't know if it is the plugin Altiris 12.6, or the host PCA agent 12.5 making the remove). For 400 PCs, it was OK. Only 6 got the problem.

Of course, the previous settings are loosed, but it was OK to reset them the Altiris global settings we configure.

I see we can prevent this in there http://www.symantec.com/docs/TECH110760

I wonder if not a parallel windows auto-update running in the same time to "crash" the awhost32 install ?

[Pascal KOTTE]

And on 4 machines, the uninstall of the PCA agent just disable the Windows Keyboard USB driver... No way to login, except using Dameware (or edit registry remotly to force auto-logon, for on screen keyboard usage).

Device error persistent on the keyboard, no way if changing keyboard, or USB port, same poblem. Mouse is working, but we need being able to login before opening the on screen keyboard.

I Workaround using "autologon" remote regsitry change.