scotthawks Posted April 4, 2005 Posted April 4, 2005 I am trying to create an unattended installation for office 2003. i followed all the steps in the tutorial. all goes fine for starting the installation. the installation will start, but then just disappear. i am running in vmware enviroment. does this make a difference?Thanks.
Dahi Posted April 4, 2005 Posted April 4, 2005 Run setup with the /qb option so you can see which error is causing it to failsetuppro.exe transorms=Unattended.mst /QB
scotthawks Posted April 5, 2005 Author Posted April 5, 2005 had the /QB arguments. does not give error message, just disappears.
scotthawks Posted April 5, 2005 Author Posted April 5, 2005 had the /QB arguments. does not give error message, just disappears.<{POST_SNAPBACK}>actually i had this argument - /qb-tried the /QB and got error message saying installation source corrupt. using nlite to create image. tried copying files again, but still same error.
jpeshek Posted April 5, 2005 Posted April 5, 2005 case should not matter in the switch; if you have access to another computer you could eliminate whether VMware is the problem; I am not familiar with virtual PC software and can be of no further help
scotthawks Posted April 7, 2005 Author Posted April 7, 2005 finally got an error to come up. says source files are corrupt. tried copying files again, and burning iso again, still same. any ideas?
clavicle Posted April 7, 2005 Posted April 7, 2005 I had also faced the same problem and after more than installations found the trouble. In my case the unattend.mst had the paths of invalid directories. I had made the unattend.mst to direct to the usershell folders, the location of these folders was changed, different from the default. The application data folder and data folders to be precise pointed to some other location rather than the %userprofile% in the documents and settings folders.This led the installation of office to complete without unattended.mst but when mst was included the fault recurred.I simply reset the location of data folders and all worked well. I hope it helps you!!
tguy Posted April 18, 2005 Posted April 18, 2005 If you still get stuck, append this to your command line:/L*v\"%temp%\pcsinst.log\"It will create a log file in verbose mode called pcinst.log in your temp directory. You can open up the log and review for errors.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now