This error message comes up when I try to install MS Office 2007. Setup cannot find Word.en-us WordMUI.msi. Download link of Office 2007 suite.

I have a package called Microsoft Office Professional 2007 which can be used on both Windows XP x86 and Windows 7 x64. I have deployed this software in my SCCM environment. But, it throws an error like 'run time exceeded' in SCCM report. L298 Motor Driver Ic more. But, we i checked this software by installing manually in Windows 7 x64 machine using system account, It was installed successfully within 45 minutes. But, it won't work when i deployed the same package via SCCM. I guess there is no issue with the source of MS Office 2007 package.

Can anyone please help me. Drivers Wanted Campaign. I tried to increase the 'Maximum allowed run time (minutes)' to 180 minutes from 120 minutes.

In Programs properties (Requirements tab). But I still get the same error even in that 180th minute. Yes, the installation will run without any user interaction. We are using install.vbs script file to install MS Office 2007, which will automate the installation process without any user interaction. It is also installed successfully using SCCM software distribution in Windows XP x86 platform, but not installed in Windows 7 x64 bit OS via SCCM software distribution. And also it can work when we install manually using system account in Windows 7 x64 OS.

We tried to install MS Office 2007 manually using system account in Windows 7 x64 OS (as in SCCM generally uses system account to install the softwares in its client), it get installed and working fine. But i don't know where is the issue, when we deploy that same package to Windows 7 x64 OS using SCCM, it is failed with an error 'run time exceeded'. When tracing issues like this for Office, i have found the Office setup logfile, and the ccmexec.log file, reveal the cause of the issue. Office setup logfile would be in c: windows temp setup and named like this: SetupExe(0442FAC).log the execmgr.log file should be with all the other ConfigMgr logs on that client, and after the timeout, reboot, and execmgr.log reveals something like 'reboot occurred while waiting for user input' if this is your case, then it's surely that for some reason the install/setup is trying to ask the user a question/confirmation, which will fail when running as LocalSystem on a newer OS like Win7.

Hi, this logfile you have found is the log of an office uninstall performed by user 'cshadmin' [I found a file like this SetupExe(4958118C).log in C: Users cshadmin AppData Local Temp] as you can see in various places in this logfile, message dialogs have been raised e.g. 'do you want to uninstall?' And 'do you want to reboot?' The logfile is fairly easy to understand (the important pieces for understanding what is going on) the execmgr.log shows that your program is failing to acccess the DP using the computer$ account, and falling back to the NAA. This is fine. You don't seem to have any issue with access to the package, and your script seems to be firing ok, but i can't see what your script is doing, so the office setup logfile (the proper one) will be important.

It should be at c: windows temp on an x86 system. Not sure if the same on x64 system also, note that 'user input' may be simply showing a completion message with an OK button.

This will cause the same thing. It must be totally silent, to succeed. A splash screen without any buttons is fine.

Anything with a button/checkbox is no good. The office customisation interaction setting should be set to 'none' for totally silent, or if set to basic, you must suppress modal dialogs, no completion notice, agree to EULA, etc.