Office 2007 beta 2 Setup Error

[Jesse]

Hi Noel,

Thanks again for your reply. I finally got it working...
Unfortunately, I did it in a very unscientific manner and introduced a
bunch of variables and I am not too sure which one physically resolved
my issue.

For the benefit of anyone else experiencing this problem here is what I
did.

1. I performed the steps that Noel provided around setting up an admin
file (setup /admin). However, when I ran the setup I selected an
Upgrade and received the same Error 1706.

2. I then used "Windows Install Clean Up" to attempt to clear any
legacy registry and install files related to Office 2007 Beta 2. And
then I re-ran the setup using the same MSP file from Attempt 1. This
time I selected "Customize" but left all the default values and
everything ran through smoothly.

I am not too sure if it is Noel's fix or the Windows Install Clean Up
that fixed things, but certainly something for alll of you to try.

Regards,

Jesse

 

[Jesse]

Hi Noel,

Thanks again for your reply. I finally got it working...
Unfortunately, I did it in a very unscientific manner and introduced a
bunch of variables and I am not too sure which one physically resolved
my issue.

For the benefit of anyone else experiencing this problem here is what I
did.

1. I performed the steps that Noel provided around setting up an admin
file (setup /admin). However, when I ran the setup I selected an
Upgrade and received the same Error 1706.

2. I then used "Windows Install Clean Up" to attempt to clear any
legacy registry and install files related to Office 2007 Beta 2. And
then I re-ran the setup using the same MSP file from Attempt 1. This
time I selected "Customize" but left all the default values and
everything ran through smoothly.

I am not too sure if it is Noel's fix or the Windows Install Clean Up
that fixed things, but certainly something for alll of you to try.

Regards,

Jesse

 

[Jesse]

Hi Noel,

Thanks again for your reply. I finally got it working...
Unfortunately, I did it in a very unscientific manner and introduced a
bunch of variables and I am not too sure which one physically resolved
my issue.

For the benefit of anyone else experiencing this problem here is what I
did.

1. I performed the steps that Noel provided around setting up an admin
file (setup /admin). However, when I ran the setup I selected an
Upgrade and received the same Error 1706.

2. I then used "Windows Install Clean Up" to attempt to clear any
legacy registry and install files related to Office 2007 Beta 2. And
then I re-ran the setup using the same MSP file from Attempt 1. This
time I selected "Customize" but left all the default values and
everything ran through smoothly.

I am not too sure if it is Noel's fix or the Windows Install Clean Up
that fixed things, but certainly something for alll of you to try.

Regards,

Jesse

 

[Jesse]

Hi Noel,

Thanks again for your reply. I finally got it working...
Unfortunately, I did it in a very unscientific manner and introduced a
bunch of variables and I am not too sure which one physically resolved
my issue.

For the benefit of anyone else experiencing this problem here is what I
did.

1. I performed the steps that Noel provided around setting up an admin
file (setup /admin). However, when I ran the setup I selected an
Upgrade and received the same Error 1706.

2. I then used "Windows Install Clean Up" to attempt to clear any
legacy registry and install files related to Office 2007 Beta 2. And
then I re-ran the setup using the same MSP file from Attempt 1. This
time I selected "Customize" but left all the default values and
everything ran through smoothly.

I am not too sure if it is Noel's fix or the Windows Install Clean Up
that fixed things, but certainly something for alll of you to try.

Regards,

Jesse

 

[Noel Prior]

Hey Bob,

Points well noted, thanks a lot, although MS do point out there could
be installation failures if you are installing other apps apart from
the standard Office Pro, (I have the complete suite installed, Visio,
SharePoint Designer etc) by using "transforms" (patches now in 2007) in
the folder to run automatically, have not tested this, as my aim was to
get 2007 to actually install as painlessly as possible.

Actually I am not used to installing Office via setup.exe, I am more
used to installing from an administrative installation point on the
network using the .msi file via group policy, which bypasses setup.exe
entirely. The msi file to use obviously is the main office install one,
which lists the sequences/dependencies of the individual office apps
etc.

However this is a Beta and problems can be expected to happen,
especially after I rushed into the install without reading the
requirements first (lazy git that I am!). The /admin install was a
quick fix for me, and hopefully it can get others out of a bind as
well.

 

[Noel Prior]

Hey Bob,

Points well noted, thanks a lot, although MS do point out there could
be installation failures if you are installing other apps apart from
the standard Office Pro, (I have the complete suite installed, Visio,
SharePoint Designer etc) by using "transforms" (patches now in 2007) in
the folder to run automatically, have not tested this, as my aim was to
get 2007 to actually install as painlessly as possible.

Actually I am not used to installing Office via setup.exe, I am more
used to installing from an administrative installation point on the
network using the .msi file via group policy, which bypasses setup.exe
entirely. The msi file to use obviously is the main office install one,
which lists the sequences/dependencies of the individual office apps
etc.

However this is a Beta and problems can be expected to happen,
especially after I rushed into the install without reading the
requirements first (lazy git that I am!). The /admin install was a
quick fix for me, and hopefully it can get others out of a bind as
well.

 

[Noel Prior]

Hey Bob,

Points well noted, thanks a lot, although MS do point out there could
be installation failures if you are installing other apps apart from
the standard Office Pro, (I have the complete suite installed, Visio,
SharePoint Designer etc) by using "transforms" (patches now in 2007) in
the folder to run automatically, have not tested this, as my aim was to
get 2007 to actually install as painlessly as possible.

Actually I am not used to installing Office via setup.exe, I am more
used to installing from an administrative installation point on the
network using the .msi file via group policy, which bypasses setup.exe
entirely. The msi file to use obviously is the main office install one,
which lists the sequences/dependencies of the individual office apps
etc.

However this is a Beta and problems can be expected to happen,
especially after I rushed into the install without reading the
requirements first (lazy git that I am!). The /admin install was a
quick fix for me, and hopefully it can get others out of a bind as
well.

 

[Noel Prior]

Hey Bob,

Points well noted, thanks a lot, although MS do point out there could
be installation failures if you are installing other apps apart from
the standard Office Pro, (I have the complete suite installed, Visio,
SharePoint Designer etc) by using "transforms" (patches now in 2007) in
the folder to run automatically, have not tested this, as my aim was to
get 2007 to actually install as painlessly as possible.

Actually I am not used to installing Office via setup.exe, I am more
used to installing from an administrative installation point on the
network using the .msi file via group policy, which bypasses setup.exe
entirely. The msi file to use obviously is the main office install one,
which lists the sequences/dependencies of the individual office apps
etc.

However this is a Beta and problems can be expected to happen,
especially after I rushed into the install without reading the
requirements first (lazy git that I am!). The /admin install was a
quick fix for me, and hopefully it can get others out of a bind as
well.

 

[Noel Prior]

Hey Bob,

Points well noted, thanks a lot, although MS do point out there could
be installation failures if you are installing other apps apart from
the standard Office Pro, (I have the complete suite installed, Visio,
SharePoint Designer etc) by using "transforms" (patches now in 2007) in
the folder to run automatically, have not tested this, as my aim was to
get 2007 to actually install as painlessly as possible.

Actually I am not used to installing Office via setup.exe, I am more
used to installing from an administrative installation point on the
network using the .msi file via group policy, which bypasses setup.exe
entirely. The msi file to use obviously is the main office install one,
which lists the sequences/dependencies of the individual office apps
etc.

However this is a Beta and problems can be expected to happen,
especially after I rushed into the install without reading the
requirements first (lazy git that I am!). The /admin install was a
quick fix for me, and hopefully it can get others out of a bind as
well.

 

[Noel Prior]

Hey Bob,

Points well noted, thanks a lot, although MS do point out there could
be installation failures if you are installing other apps apart from
the standard Office Pro, (I have the complete suite installed, Visio,
SharePoint Designer etc) by using "transforms" (patches now in 2007) in
the folder to run automatically, have not tested this, as my aim was to
get 2007 to actually install as painlessly as possible.

Actually I am not used to installing Office via setup.exe, I am more
used to installing from an administrative installation point on the
network using the .msi file via group policy, which bypasses setup.exe
entirely. The msi file to use obviously is the main office install one,
which lists the sequences/dependencies of the individual office apps
etc.

However this is a Beta and problems can be expected to happen,
especially after I rushed into the install without reading the
requirements first (lazy git that I am!). The /admin install was a
quick fix for me, and hopefully it can get others out of a bind as
well.

 

[Noel Prior]

Hey Bob,

Points well noted, thanks a lot, although MS do point out there could
be installation failures if you are installing other apps apart from
the standard Office Pro, (I have the complete suite installed, Visio,
SharePoint Designer etc) by using "transforms" (patches now in 2007) in
the folder to run automatically, have not tested this, as my aim was to
get 2007 to actually install as painlessly as possible.

Actually I am not used to installing Office via setup.exe, I am more
used to installing from an administrative installation point on the
network using the .msi file via group policy, which bypasses setup.exe
entirely. The msi file to use obviously is the main office install one,
which lists the sequences/dependencies of the individual office apps
etc.

However this is a Beta and problems can be expected to happen,
especially after I rushed into the install without reading the
requirements first (lazy git that I am!). The /admin install was a
quick fix for me, and hopefully it can get others out of a bind as
well.

 

[Noel Prior]

Hey Bob,

Points well noted, thanks a lot, although MS do point out there could
be installation failures if you are installing other apps apart from
the standard Office Pro, (I have the complete suite installed, Visio,
SharePoint Designer etc) by using "transforms" (patches now in 2007) in
the folder to run automatically, have not tested this, as my aim was to
get 2007 to actually install as painlessly as possible.

Actually I am not used to installing Office via setup.exe, I am more
used to installing from an administrative installation point on the
network using the .msi file via group policy, which bypasses setup.exe
entirely. The msi file to use obviously is the main office install one,
which lists the sequences/dependencies of the individual office apps
etc.

However this is a Beta and problems can be expected to happen,
especially after I rushed into the install without reading the
requirements first (lazy git that I am!). The /admin install was a
quick fix for me, and hopefully it can get others out of a bind as
well.

 

[TravisO]

I got the same problem, unable to find setup.chm even though I
uncompressed the main installer and saw the file exists in there.

I downloaded my copy on June 8th, so it's definetly NOT an issue about
a bad download.

I did find a lazy work around (creating the Admin install is the best
way), if you uncompress the 1 large install file to it's own folder,
just run the *WW.msi package.

If it's office 2007 it's: ProWW.msi
If it's onenote 2007 it's: OneNoteWW.msi

Keep in mind it's a silent install, it won't ask any question, it
installs everything, but it did not overwrite my Office 2003 setup.

 

[TravisO]

I got the same problem, unable to find setup.chm even though I
uncompressed the main installer and saw the file exists in there.

I downloaded my copy on June 8th, so it's definetly NOT an issue about
a bad download.

I did find a lazy work around (creating the Admin install is the best
way), if you uncompress the 1 large install file to it's own folder,
just run the *WW.msi package.

If it's office 2007 it's: ProWW.msi
If it's onenote 2007 it's: OneNoteWW.msi

Keep in mind it's a silent install, it won't ask any question, it
installs everything, but it did not overwrite my Office 2003 setup.

 

[TravisO]

I got the same problem, unable to find setup.chm even though I
uncompressed the main installer and saw the file exists in there.

I downloaded my copy on June 8th, so it's definetly NOT an issue about
a bad download.

I did find a lazy work around (creating the Admin install is the best
way), if you uncompress the 1 large install file to it's own folder,
just run the *WW.msi package.

If it's office 2007 it's: ProWW.msi
If it's onenote 2007 it's: OneNoteWW.msi

Keep in mind it's a silent install, it won't ask any question, it
installs everything, but it did not overwrite my Office 2003 setup.

 

[TravisO]

I got the same problem, unable to find setup.chm even though I
uncompressed the main installer and saw the file exists in there.

I downloaded my copy on June 8th, so it's definetly NOT an issue about
a bad download.

I did find a lazy work around (creating the Admin install is the best
way), if you uncompress the 1 large install file to it's own folder,
just run the *WW.msi package.

If it's office 2007 it's: ProWW.msi
If it's onenote 2007 it's: OneNoteWW.msi

Keep in mind it's a silent install, it won't ask any question, it
installs everything, but it did not overwrite my Office 2003 setup.

 

[TravisO]

I got the same problem, unable to find setup.chm even though I
uncompressed the main installer and saw the file exists in there.

I downloaded my copy on June 8th, so it's definetly NOT an issue about
a bad download.

I did find a lazy work around (creating the Admin install is the best
way), if you uncompress the 1 large install file to it's own folder,
just run the *WW.msi package.

If it's office 2007 it's: ProWW.msi
If it's onenote 2007 it's: OneNoteWW.msi

Keep in mind it's a silent install, it won't ask any question, it
installs everything, but it did not overwrite my Office 2003 setup.

 

[TravisO]

I got the same problem, unable to find setup.chm even though I
uncompressed the main installer and saw the file exists in there.

I downloaded my copy on June 8th, so it's definetly NOT an issue about
a bad download.

I did find a lazy work around (creating the Admin install is the best
way), if you uncompress the 1 large install file to it's own folder,
just run the *WW.msi package.

If it's office 2007 it's: ProWW.msi
If it's onenote 2007 it's: OneNoteWW.msi

Keep in mind it's a silent install, it won't ask any question, it
installs everything, but it did not overwrite my Office 2003 setup.

 

[TravisO]

I got the same problem, unable to find setup.chm even though I
uncompressed the main installer and saw the file exists in there.

I downloaded my copy on June 8th, so it's definetly NOT an issue about
a bad download.

I did find a lazy work around (creating the Admin install is the best
way), if you uncompress the 1 large install file to it's own folder,
just run the *WW.msi package.

If it's office 2007 it's: ProWW.msi
If it's onenote 2007 it's: OneNoteWW.msi

Keep in mind it's a silent install, it won't ask any question, it
installs everything, but it did not overwrite my Office 2003 setup.

 

[dgamble21401]

We just received our Volume User release (Large US university) and it
has the same issue!

I've searched the Internet and our IT department spoke with Microsoft
and their only advise was to reinstall the machines!!! They have no
solution!!!!

I think we're @#$^%!