Office 2007 MI fails in a couple of computers
[font="times new roman"]We are pushing MS Office 2007 via KBOX Managaed installation. For the most part it works, but I do get a small number of computers that failed. Here is what we find in the event viewer:
[font="times new roman"]Exception Type: System.IO.IOException
Message: The process cannot access the file "C:\Program Files\KACE\KBOX\downloads\100" because it is being used by another process.
TargetSite: Void WinIOError(Int32, System.String)
HelpLink: NULL
Source: mscorlib
StackTrace Information
After the computer is restarted in the morning, the user can't find the shortcuts for the office suite, and when trying to run the executable from the program files folder, gets error message. We've been having to install the suite manually to get it functional.
Our question is if this is a bad MI or is there something the KBOX is not doing properly. If this was a bad MI, then why does it work in about 2/3 of the target computers. Any input is greatly appreciated.
[font="times new roman"]Exception Type: System.IO.IOException
Message: The process cannot access the file "C:\Program Files\KACE\KBOX\downloads\100" because it is being used by another process.
TargetSite: Void WinIOError(Int32, System.String)
HelpLink: NULL
Source: mscorlib
StackTrace Information
After the computer is restarted in the morning, the user can't find the shortcuts for the office suite, and when trying to run the executable from the program files folder, gets error message. We've been having to install the suite manually to get it functional.
Our question is if this is a bad MI or is there something the KBOX is not doing properly. If this was a bad MI, then why does it work in about 2/3 of the target computers. Any input is greatly appreciated.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
cblake
14 years ago
Without more to go on I'd suspect that multiple installations (or uninstallations) are trying to execute on those systems at the same time. Maybe there's some MI's running and some scripts or GPO's running? Not sure, but that's my first thought. Can you check logging for your Office install and report back what the logs say? Office Setup automatically creates log files in your %Temp% folder I believe.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
