brice626
asked on
Trouble with cabinet caching prevents Office 2003/2007 install
I'm at my wits' end.
I've got a copy of Office 2007 Enterprise Edition. I already had Office 2003 Professional Edition installed. When I go to install Office 2007, it pops up a screen saying "Setup cannot find Office.en-us\OfficeLR.cab.
I go to the below file to view the log:
C:\Documents and Settings\username\Local Settings\Temp\SetupExe(200
and see:
--------------------------
Cannot detect OSE service. Return code: 1060
Running OSE version 12.0.4518.1014
Cannot detect OSE service. Return code: 1060
Running OSE version 12.0.4518.1014
LIS: wait for package "{90120000-0115-0409-0000-
LIS failed to cache download "{90120000-0115-0409-0000-
--------------------------
Before the obvious question gets asked -- no, the CD is not dirty :) It is brand new and installed Office 2007 perfectly on my laptop. I've tried it in both CD-ROM drives on the desktop (one is a CD-RW, one is a DVD+RW). I have tried copying all the files to the hard drive and running setup there - no errors during copy, but the same error during install.
I thought, perhaps this just doesn't want to upgrade my Office 2003 installation. Let's remove it.
I remove Office 2003, reboot, and try the Office 2007 installer. Same error. I say "Alright, the hell with this", and go to reinstall Office 2003 and LO AND BEHOLD... as soon as the install begins... I get to the step "Current action: Waiting for cabinets to be cached to local installation source" and get an error: "Installation Error: File not Found. A required installation file Q3561405.CAB could not be found".
Same deal as Office 2007... I know the file is there and I point the installer to it but it just pops up the same screen again.
I head to check out the logs again, and see this:
--------------------------
WaitCacheImpersonate: Error 0x80070017: failed an attempt to cache cabinet: Q3561405.CAB
--------------------------
I seem to have a problem with the LIS or Local Installation Source mechanism that Office uses both in version 2003 and 2007. Same type of caching error.
Things I've tried:
- installing from ISO rather than CD (same problem with both versions)
- running registry cleaner (latest version of CCleaner several times)
- deleting reg keys with GUID names from HKLM\SOFTWARE\Microsoft\Of
- deleting all files from temp directory (no effect)
- deleting all files from Windows Prefetch directory (no effect)
- deleting all files from MSOCache directory (no effect)
- reinstalling Windows Installer 3.1 (no effect)
- trying an administrative install of 2003 - doesn't exist for 2007 - failed
- trying to use LISTOOL (intially says MSO.dll is missing or damaged... expected since I uninstalled Office. On second run, says The Office Source Engine (ose.exe) can not be started.
- sharing the CD over the network from the computer where it did install correctly, and trying to install over the network (no effect)
Any ideas, guys and gals?
I've got a copy of Office 2007 Enterprise Edition. I already had Office 2003 Professional Edition installed. When I go to install Office 2007, it pops up a screen saying "Setup cannot find Office.en-us\OfficeLR.cab.
I go to the below file to view the log:
C:\Documents and Settings\username\Local Settings\Temp\SetupExe(200
and see:
--------------------------
Cannot detect OSE service. Return code: 1060
Running OSE version 12.0.4518.1014
Cannot detect OSE service. Return code: 1060
Running OSE version 12.0.4518.1014
LIS: wait for package "{90120000-0115-0409-0000-
LIS failed to cache download "{90120000-0115-0409-0000-
--------------------------
Before the obvious question gets asked -- no, the CD is not dirty :) It is brand new and installed Office 2007 perfectly on my laptop. I've tried it in both CD-ROM drives on the desktop (one is a CD-RW, one is a DVD+RW). I have tried copying all the files to the hard drive and running setup there - no errors during copy, but the same error during install.
I thought, perhaps this just doesn't want to upgrade my Office 2003 installation. Let's remove it.
I remove Office 2003, reboot, and try the Office 2007 installer. Same error. I say "Alright, the hell with this", and go to reinstall Office 2003 and LO AND BEHOLD... as soon as the install begins... I get to the step "Current action: Waiting for cabinets to be cached to local installation source" and get an error: "Installation Error: File not Found. A required installation file Q3561405.CAB could not be found".
Same deal as Office 2007... I know the file is there and I point the installer to it but it just pops up the same screen again.
I head to check out the logs again, and see this:
--------------------------
WaitCacheImpersonate: Error 0x80070017: failed an attempt to cache cabinet: Q3561405.CAB
--------------------------
I seem to have a problem with the LIS or Local Installation Source mechanism that Office uses both in version 2003 and 2007. Same type of caching error.
Things I've tried:
- installing from ISO rather than CD (same problem with both versions)
- running registry cleaner (latest version of CCleaner several times)
- deleting reg keys with GUID names from HKLM\SOFTWARE\Microsoft\Of
- deleting all files from temp directory (no effect)
- deleting all files from Windows Prefetch directory (no effect)
- deleting all files from MSOCache directory (no effect)
- reinstalling Windows Installer 3.1 (no effect)
- trying an administrative install of 2003 - doesn't exist for 2007 - failed
- trying to use LISTOOL (intially says MSO.dll is missing or damaged... expected since I uninstalled Office. On second run, says The Office Source Engine (ose.exe) can not be started.
- sharing the CD over the network from the computer where it did install correctly, and trying to install over the network (no effect)
Any ideas, guys and gals?
Let me know how it goes. I'm pretty curious now!
ASKER
I'm curious where the SMS references came from? This is just a local CD install on one computer.
I gave the articles a shot -- I'd seen the one about "decoding" the log which is how I found out to look for the errors I posted. There doesn't seem to be much about caching on Microsoft's site unfortunately.
I gave the articles a shot -- I'd seen the one about "decoding" the log which is how I found out to look for the errors I posted. There doesn't seem to be much about caching on Microsoft's site unfortunately.
ASKER
Well, I got almost all the way thought the 2007 install, or so I thought.
I set up several alternate sources for the installer.
1) My original CD
2) A copy of that CD in a second drive
3) A folder on my hard drive holding copies of the files on the 2007 CD
4) The ISO from which I burned the original CD, mounted virtually
I first got the same error about not being able to find a file. I noticed that the installer was trying to copy the file that it said was missing to the cache directory, C:\MSOCache (the contents of subdirectories under MSOCache which had large GUID name matched each CD directory's contents). Bizarrely and with no explanation, sometimes pointing the installer to a different one of the four sources worked. Other times, I had to just go round-robin through all four until it worked. Other times, I manually copied the file in question from one of the four sources to the relevant MSOCache directory. Like pointing the installer, sometimes one source would work and sometimes it wouldn't.
I got all the way to the very end of the installer with this witchcraft and thought I was home free UNTIL... AT THE VERY END...
Error 1937.An error occurred during the installation of assembly component {91B2FA33-228C-4BF3-B1C8-7
It only took it about four hours to coax it that far. And when it hit that error, it automatically rolled back the whole damn thing.
I set up several alternate sources for the installer.
1) My original CD
2) A copy of that CD in a second drive
3) A folder on my hard drive holding copies of the files on the 2007 CD
4) The ISO from which I burned the original CD, mounted virtually
I first got the same error about not being able to find a file. I noticed that the installer was trying to copy the file that it said was missing to the cache directory, C:\MSOCache (the contents of subdirectories under MSOCache which had large GUID name matched each CD directory's contents). Bizarrely and with no explanation, sometimes pointing the installer to a different one of the four sources worked. Other times, I had to just go round-robin through all four until it worked. Other times, I manually copied the file in question from one of the four sources to the relevant MSOCache directory. Like pointing the installer, sometimes one source would work and sometimes it wouldn't.
I got all the way to the very end of the installer with this witchcraft and thought I was home free UNTIL... AT THE VERY END...
Error 1937.An error occurred during the installation of assembly component {91B2FA33-228C-4BF3-B1C8-7
It only took it about four hours to coax it that far. And when it hit that error, it automatically rolled back the whole damn thing.
Wow that seriously sucks.
Here are some similar issues and possible solutions (most seem related to .NET Framework):
http://www.pcreview.co.uk/forums/thread-1233418.php
Here's a whole document on troubleshooting and removing and reinstalling .NET Framework 1.1.
http://support.microsoft.com/kb/824643/en-us
I would actually suggest removing all versions of .NET Framework from your machine using the above article and/or Add/Remove Programs, rebooting, then installing .NET 3.0 exclusively.
Microsoft .NET Framework 3.0 Redistributable Package
http://www.microsoft.com/downloads/details.aspx?FamilyID=10CC340B-F857-4A14-83F5-25634C3BF043&displaylang=en
Let me know if that worked!
Here are some similar issues and possible solutions (most seem related to .NET Framework):
http://www.pcreview.co.uk/forums/thread-1233418.php
Here's a whole document on troubleshooting and removing and reinstalling .NET Framework 1.1.
http://support.microsoft.com/kb/824643/en-us
I would actually suggest removing all versions of .NET Framework from your machine using the above article and/or Add/Remove Programs, rebooting, then installing .NET 3.0 exclusively.
Microsoft .NET Framework 3.0 Redistributable Package
http://www.microsoft.com/downloads/details.aspx?FamilyID=10CC340B-F857-4A14-83F5-25634C3BF043&displaylang=en
Let me know if that worked!
ASKER
No luck I'm afraid. Removed Framework 1.1 and installed the 3.0 redistributable package, rebooted, and tried Office 2007. Got the same error of file not found. From the log:
--------------------------
Executing chained package: OfficeMUI.en-us
02/07/2007 23:29:43 Installing chained package: OfficeMUI.en-us
PERF: TickCount=156545 Name=Verify MSI local install source Description=Begin function
Cannot detect OSE service. Return code: 1060
Running OSE version 12.0.4518.1014
Cannot detect OSE service. Return code: 1060
Running OSE version 12.0.4518.1014
LIS: wait for package "{90120000-0115-0409-0000-
LIS failed to cache download "{90120000-0115-0409-0000-
Source Resolution succeeded
LIS: start caching file "OfficeLR.cab"
LIS failed to cache download "{90120000-0115-0409-0000-
Source Resolution succeeded
--------------------------
I'm next going to try copying the contents of the MSOCache directory from my (working) laptop to the desktop and then launching the install... we'll see how that goes.
--------------------------
Executing chained package: OfficeMUI.en-us
02/07/2007 23:29:43 Installing chained package: OfficeMUI.en-us
PERF: TickCount=156545 Name=Verify MSI local install source Description=Begin function
Cannot detect OSE service. Return code: 1060
Running OSE version 12.0.4518.1014
Cannot detect OSE service. Return code: 1060
Running OSE version 12.0.4518.1014
LIS: wait for package "{90120000-0115-0409-0000-
LIS failed to cache download "{90120000-0115-0409-0000-
Source Resolution succeeded
LIS: start caching file "OfficeLR.cab"
LIS failed to cache download "{90120000-0115-0409-0000-
Source Resolution succeeded
--------------------------
I'm next going to try copying the contents of the MSOCache directory from my (working) laptop to the desktop and then launching the install... we'll see how that goes.
ASKER
Meh, that didn't work either :(
Wow brice. This is so super stinky. :(
I have this suspicion that it's the OS installation on that computer that's causing problems. Because you said you installed it on your laptop just fine, right? My next experiment would be to either a) create a new partition on the drive and install XP again and try the Office 2007 installation there) then I could confirm that it was that Windows installation causing the problem... -OR- I might go WHOLE HOG and wipe the system and reinstall Windows on the primary partition and then the installation of Office 2007.
I know it's a messy solution, but ... I guess it depends how frustrated you are and how much data you'd have to back up... or if you have enough room for another partition just too see what happens (you can always revert the partition when you're done with it).
Sorry, man. Let me know what you decide to do.
I have this suspicion that it's the OS installation on that computer that's causing problems. Because you said you installed it on your laptop just fine, right? My next experiment would be to either a) create a new partition on the drive and install XP again and try the Office 2007 installation there) then I could confirm that it was that Windows installation causing the problem... -OR- I might go WHOLE HOG and wipe the system and reinstall Windows on the primary partition and then the installation of Office 2007.
I know it's a messy solution, but ... I guess it depends how frustrated you are and how much data you'd have to back up... or if you have enough room for another partition just too see what happens (you can always revert the partition when you're done with it).
Sorry, man. Let me know what you decide to do.
ASKER
Thanks for the sympathy! It is a frustrating situation.
I'd pretty much resigned myself to a reinstall last night when my last trick failed. I'll leave this ? open for another 24 hours or so and see if I garner any other replies, else I'll be formatting. It's been about a year since my last full nuke of the system, so it'll probably be for the best anyway.
Thanks for the suggestions though!
I'd pretty much resigned myself to a reinstall last night when my last trick failed. I'll leave this ? open for another 24 hours or so and see if I garner any other replies, else I'll be formatting. It's been about a year since my last full nuke of the system, so it'll probably be for the best anyway.
Thanks for the suggestions though!
ASKER
Almost had a heart attack after I reinstalled -- and did so with an original XP cd since my slipstreamed SP2 CD wasn't working -- and got the same error message.... but thank god, after I hit continue once, it went all the way through. I'm imaging this puppy... never want to have to go go through again.
Thanks for the suggestions, all. Too bad I had to resort to my last option. Thanks again!
Thanks for the suggestions, all. Too bad I had to resort to my last option. Thanks again!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I experienced this problem and the solution was to copy the Office 2007 CD to the PC's hard disk, manually extract the officelr.cab file to the same location and then re-run the installation.
Just for the record, problems with caching are sometimes the result of a corrupted file. I had an external hard drive that I kept my extracted, MSDN copy of Visio 2003 on, and I just had to reinstall it today. To my surprise I got caught up with the same error.
I used MD5summer to get an MD5 checksum on the problem file (YS561401.CAB), then looked at the checksum for that file in the VISPRO.XML file (in the ...\FILES\SETUP subdirectory of the install source), and they were different. Basically the drive was going bad and had corrupted a few bytes in the file.
So I redownloaded the ISO from Microsoft, unpacked it somewhere else, and copied the newly-unpacked version of that same file over top of the problem version, and then hit the Continue button, and it worked fine.
I used MD5summer to get an MD5 checksum on the problem file (YS561401.CAB), then looked at the checksum for that file in the VISPRO.XML file (in the ...\FILES\SETUP subdirectory of the install source), and they were different. Basically the drive was going bad and had corrupted a few bytes in the file.
So I redownloaded the ISO from Microsoft, unpacked it somewhere else, and copied the newly-unpacked version of that same file over top of the problem version, and then hit the Continue button, and it worked fine.
SMS: Cannot Install SMS Client Software on a Target Computer That Is Running Windows XP, Windows NT, or Windows 2000
http://support.microsoft.com/kb/207429
Here's information on how to interpret an Office installation log:
How to use a setup log file to troubleshoot setup problems in Office
http://support.microsoft.com/kb/826511/en-us
And this talks about some of the problems deploying Office (includes more info about SMS problems):
Supported installation methods for deploying Office 2003
http://support.microsoft.com/kb/828377/en-us
I'm wondering now if the initial installation didn't partially install SMS and that's what's mucking up the whole thing... even the Office 2K3 installation.
I suggest following the instructions here for downloading, installing and running the removal tool found in SMS 2003 Toolkit 2:
http://www.windowsitpro.com/Article/ArticleID/45480/45480.html
Then try to reinstall Office 2003. If that works, then you will know for certain that the problem is with the Office 2007 installation and SMS.