Troubleshooting Office 2007 Setup Errors

Robin Hearne

unread,

Jan 26, 2009, 8:47:01 AM1/26/09

to

I've been deploying Office 2007 to a pilot team and I'm experiencing the same
error on a number of computers. The error is as follows:

'Error 1706. Setup cannot find the required files. Check your connection to
the network, or CD-ROM drive. For other potential solutions to this problem,
see C:\Program Files\Microsoft Office\OFFICE11\1033\SETUP.CHM.'

Despite the error occuring the setup appears to continue and everything
seems to work fine afterwards.

The installations are being performed by SCCM but there is no suggestion of
any issues with access to the distribution points during the installation.
In general most installations are completing without any errors occuring.
All of the computers have Office 2003 installed and we're not removing those
applications as part of the installation process.

The log entries either side of the error are as follows:

Running OSE version 12.0.4518.1014
LIS: start caching package "{90120000-0011-0000-0000-0000000FF1CE}"
LIS: creating download package "{90120000-0011-0000-0000-0000000FF1CE}-C"
LIS: start caching all files for package
"{90120000-0011-0000-0000-0000000FF1CE}-C"
LIS: start caching file "Setup.xml"
LIS: start caching file "osetup.dll"
LIS: start caching file "ID_00011.DPC"
LIS: start caching file "ProPlusWW.msi"
LIS: start caching file "OWOW64WW.cab"
LIS: start caching file "Office64WW.xml"
LIS: start caching file "ose.exe"
LIS: start caching file "setup.exe"
LIS: start caching file "ProPlsWW.cab"
LIS: start caching file "ProPlusWW.xml"
LIS: start caching file "Office64WW.msi"
LIS: finished start caching all files for package
"{90120000-0011-0000-0000-0000000FF1CE}-C"
LIS: finished starting caching package
"{90120000-0011-0000-0000-0000000FF1CE}"
LIS: wait for package "{90120000-0011-0000-0000-0000000FF1CE}" to complete
caching
LIS: package "{90120000-0011-0000-0000-0000000FF1CE}" caching completed
MSI(ERROR): 'Error 1706. Setup cannot find the required files. Check your
connection to the network, or CD-ROM drive. For other potential solutions to
this problem, see C:\Program Files\Microsoft Office\OFFICE11\1033\SETUP.CHM.'
Log level changed from: Standard to: Verbose
MSI(INFO): 'Action ended 07:54:05: InstallExecute. Return value 3.'
MSI(INFO): 'Action ended 07:54:05: INSTALL. Return value 3.'

I've not been able to identify anything unique about the computers that
experience the problem. The error re-occurs if I remove Office 2007 and then
re-install it.

Has anyone seen this before or have any suggestions on how I may
troubleshoot it further?

Thanks in advance.

Robin

Peter Foldes

unread,

Jan 26, 2009, 4:13:42 PM1/26/09

to

Robin

See the following
http://support.microsoft.com/kb/297834
--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Robin Hearne" <Robin...@discussions.microsoft.com> wrote in message
news:1454D61B-4D2F-4737...@microsoft.com...

Robin Hearne

unread,

Jan 27, 2009, 9:03:01 AM1/27/09

to

Hi Peter,

I'd looked at that article during my initial investigation, but I'm afraid
that it doesn't appear to help very much. Given the path stated in the error
(i.e the fact that it relates to Office11 rather than Office12) , I suspect
that the installation process is trying to access Office 2003 files from the
Adminstrative Installation Point. However the original Adminstrative
Installation Point for Office 2003 is still accessible and so there should be
no issues obtaining files from that location.

Robin

Peter Foldes

unread,

Jan 27, 2009, 1:11:19 PM1/27/09

to

So there should be no issues also using that MS KB that I posted for you

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Robin Hearne" <Robin...@discussions.microsoft.com> wrote in message

news:EF0C5FDD-066F-41E0...@microsoft.com...

Robin Hearne

unread,

Jan 28, 2009, 8:31:01 AM1/28/09

to

The article relates to a problem caused by the administrative installation
point being no longer available. This is not the case in my scenario, so
none of the suggested resolutions would appear to be applicable.

Robin

Peter Foldes

unread,

Jan 28, 2009, 2:06:06 PM1/28/09

to

Hi Robin

OK. Good Luck then. I still say that is the fix for your issue. Anyway all the best

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Robin Hearne" <Robin...@discussions.microsoft.com> wrote in message

news:894C7417-B42D-40EC...@microsoft.com...