I haven't seen this error in a while and could not find where I had documented it, so I figured it would be a good idea to get this on the blog. Afterall, if it could happen here, it could probably happen other places as well.
Logs from execmgr.log:
Program exit code 30060
Looking for MIF file to get program status
Script for Package:CEN000B4, Program: Microsoft Office Profession Edition 2007 - Install failed with exit code 30060
The installation failed immediately after beginning. Considering the package has been successful across the enterprise, I came to the conclusion that it had to be a problem with the workstation itself. After contacting the technician who built the machine, I was told that the standard enterprise image had not been used, but instead the machine had been built from scratch.
My next check was the Office setup log located: C:\WINDOWS\Temp\SetupExe[numbers heree].log (This file will show up either here, if you are pushing the installation with the SMS service accounts, or in C:\Documents and Settings\[login ID of person installing]\Local Settings\Temp.)
Invalid Version of MSI.DLL; skipping OCT-Customization.
Not showing message because suppress modal has been set. Title: 'Setup Errors', Message: 'Applying a Setup customization file requires Windows Installer 3.1 or greater. Please contact your administrator.'
Message returned: 1
Error: Applying a Setup customization file requires Windows Installer 3.1 or greater. Please contact your administrator. Type: OCTWrongMSIDll.
Catalyst execution finished: 12/10/2008 21:47:42. Return code: 30060. Exception caught: OCTWrongMSIDll.
PERF: TickCount=824872328 Name=RunSetup Description=End function
The first line in this log pointed right at the problem. A quick check of the MSI.DLL version revealed that it was version 3.0.XXXXX which definitely not work in our case. A trip out to Microsoft for the correct version and we were set.