11-08-2012 07:04 AM
What is with this error and why is it so common when patching from 7.1 to 7.1.0.4? I see it often and sometimes the cause is an extra msiexec process running but even without that I still see it.
Anything else I can look for? This happens a lot on Windows 2003 servers.
11-14-2012 05:51 AM
Am I really the only one who has seen this?
11-14-2012 06:58 AM
Could you post install.log found under app data/symantec(veritas) this would help us in identifying what executables are initiated during upgrade process leading multiple msiexec to run