Re: "Missing" Cab files installing office 2007 on localized Vista

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Emily,



The mentioned problem appears to be more widespread. I just followed the following steps:



* extracted all files from the Office 2007 Enterprise ISO using WinRAR and MagicISO, compared both, the extracted data was identical.

* used the extracted files to instal Office 2007 on Windows XP, worked fine.



* Installed Vista Ultimate x86 en-us on another system

* Let Windows Update install all updates, and installed Dutch (nl-nl) language pack, but keeping en-us system language and locale

* Start Setup. Crashes on EnterWW.cab, which is not available on any other Office version.



*reboot in Clean Boot Mode (which isn't very useful since there is no other software on the system yet)

* Start Setup. Crashes on EnterWW.cab



* Start Setup. Crashes on EnterWW.cab. Manually copy EnterWW.cab to C:\MSOCache\All Users\{90120000-0030-0000-0000-0000000FF1CE}-C, select source again. Crashes on EnterWW.cab, and EnterWW.cab is deleted from LIS by setup.

* Select source again, EnterWW.cab appears in LIS, only to disappear again after the file copy is complete.



So, what is the next step, if any?



Regards,

Frank


"Emily Lin [MSFT]" <v-emilyl@xxxxxxxxxxxxxxxxxxxx> wrote in message news:5Xv$WbDmHHA.1144@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi Frank,

If you have any questions or concerns, please feel free to let me know. I
am happy to be of assistance. :)

Sincerely,

Emily Lin,
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

======================================================
PLEASE NOTE: The partner managed newsgroups are provided to assist with
break/fix issues and simple how to questions.

We also love to hear your product feedback!
Let us know what you think by posting
from the web interface: Partner Feedback
from your newsreader: microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================



.

Relevant Pages

  • Re: Windows Installer does not install any files
    ... I am trying to install a VS2005 Windows Forms .Net project on a 64-bit Windows Server using Setup2.msi Setup.exe generated by Setup and Deployment project for a 64-bit operating system. ... The installer has encountered an unexpected error installing this package. ...
    (microsoft.public.vsnet.setup)
  • Re: Continual Error 1321 Trying to Install Office 2003
    ... As to evidence of which app installed wisptis, I suppose you'd have to set ... 2003 sure wants to install it and stalls when it can't because the progress ... Is there any way in the world to get into setup with some custom tool from ... *My Lack of MSFT Support Rant and View Hex Error Messages Do Nothing for the ...
    (microsoft.public.office.misc)
  • Re: Continual Error 1321 Trying to Install Office 2003
    ... it needs and now setup wants to stuff it back in. ... Wisptis is explained ... that will let me do a detailed enough or selective enough custom install to ... people running Office don't use a tablet. ...
    (microsoft.public.office.misc)
  • Re: reinstall intranet company web Error.
    ... AnalyzePhaseZero used 0 ticks ... KB832880 Setup encountered an error: Setup cannot continue because one or ... Setup cannot continue because one or more pre-requisites required to install ... For More details check the Log File C:\WINDOWS\KB832880.log ...
    (microsoft.public.windows.server.sbs)
  • Re: reinstall intranet company web Error.
    ... AnalyzePhaseZero used 0 ticks ... KB832880 Setup encountered an error: Setup cannot continue because one or ... more pre-requisites required to install KB832880 failed. ... For More details check the Log File ...
    (microsoft.public.windows.server.sbs)