Installer runs when office products start

[Geoffrey Scrace]

Hi
I have not found the answer to this problem yet:
On Windows NT4 sp 6. (Windows & Office fully patched.)
When Office 2000 products are executed by users, windows installer runs.
This does not happen for administrator.
I have seen this problem many times in this group and have applied the
recommended fixes but the problem remains.The only solution that would work
is to give users administrative privs.

I have:
1.Reinstalled Office 2000

2.Added users to the adminstrators group. Start Word, allow the Windows
Installer to do it's stuff, then remove the user from the administrator
group.

3.Adjusted the OSAShortcut and UserData Dwords in HKEY_CURRENT_USER etc.

4. Copied the administator profile to the default user.

None of these have cured the problem. The closest I got was by adding
UserData Dwords to the Office registry entries. This reduced the number
clicks on the Error 1706 dialog from about 6 to 1.
I have this on 2 NT and 1 win2000 boxes and I suspect that it will come back
every time
I create a new user.
Anybody managed to solve this?

 

[suresh]

Off2000: Error 1706 when lauching help within O
(SOX010316700102)
TITLE: Off2000: Error 1706 when lauching help within O
[SOABU ]
Action: Customer had his users instal [2000 -
W_98558 ]
ID: SOX010316700102 CRT:Mar 16 2020 MOD:Mar 16 2020
STS:Cust

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>
*** Proble Description ***
Action:

Customer had his users install Office 2000 from an admin
point and some users
install from a burn CD that was copied from their admin
point. The issue only
happens on the machines where the users installed Office
2000 from the burned
CD. When the users open any of the Office applicatons,
click on the help menu
they receive the following:

It launches the windows installer saying it is gathering
information, then it
prompts them with the following error message:

Error 1706. No valid source could be found for product
Microsoft Office 2000
SR-1 Professional. The Windows installer cannot continue.



If he inserts the CD on the machine four times when they
launch the help menu,
it does not ask for the source anymore.



Result:

Users were not able to use the Help files
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>

*** Resolution *** 03/16/2001 12:48:35 PM jenniep
Cause:

1.) We reviewed customer's application event log and
noticed the following:

a.) noticed it had the following:

Detection of product '{00010409-78E1-11D2-B60F-
006097C998E7}', feature
'ProductNonBootFiles', component '{0963F771-523D-11D2-
A189-00A0C90AB50F}'
failed

b.) {0963F771-523D-11D2-A189-00A0C90AB50F} means it
failed at OSAShortcut

2.) We reviewed customer's verbose reg log file and
noticed the following:

a.) MSI (c) (DC:AC): Failed to connect to server. Error:
0x80040154

b.) Failed to connect to server means Office did not get
installed with
elevated priliveges, so when a normal user logs onto the
workstation it cannot
create certain registry keys

c.) when you get "Failed to connect Server" in your
verbose log it means that
the Windows Installer is not registered properly on the
machine. It could
have been unregistered by the operating system, the SP1
service pack for
Windows 2000, or during Office or after Office.

d.) found another line in customer's verbose reg log
file that said the
following:

MSI (c) (DC:AC): SOURCEMGMT: Attempting to use
LastUsedSource from source
list.

MSI (c) (DC:AC): SOURCEMGMT: media source 'DMNO2KSP2;1'
is invalid.

e.) the above lines tell us that the volume was not
created using the same
volume label as the original Office 2000 CD

f.) the burn CD must use the same volume label as the
original 2000 CD and
this will prevent the 1706 error message

g.) found another line in customer's verbose reg log
file that said the
following:

Property(C): TRANSFORMS =
C:\WINNT\Installer\{00010409-78E1-11D2-B60F-006097C998E7}
\OfficeProWOAccess.MST
T

h.) this above tells us that Office 2000 was installed
with a mst file named
OfficeProWOAccess.MST

3.) Reviewed customer's mst file and noticed the file
was created with an
older version of the Custom Installation Wizard build 2810

4.) We recreated the mst file with the newer version of
the CIW and it added
more features to the mst file.

5.) When customer re-registered the windows installer
using the unreg and
regserver of the msiexec, you did not get this error
message in your new
verbose log and this allow a user to login and get all
the necessary registry
keys created by the windows installer and that is why you
are not seeing any
error messages anymore.



Resolution:

1.) Customer re-created his mst file with the newest CIW
and needed to import
a registry key and once we saved it as NT format, he was
able to import the
registry key in his mst file

2.) Customer burned a new copy his Office 2000 admin
point to a CD and used
the volume label from the select CD

3.) Customer installed his image of his operating system
and Office 2000 and a
new user was able to click on the help menu properly

4.) We agreed that the issue was somewhere in the
deployment of some other
software or editing the machine caused the windows
installer to unregister and
correcting the volume label CD issue will not produce any
issues in the
future.

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>

 

[suresh]

Off2000: Error 1706 when lauching help within O
(SOX010316700102)
TITLE: Off2000: Error 1706 when lauching help within O
[SOABU ]
Action: Customer had his users instal [2000 -
W_98558 ]
ID: SOX010316700102 CRT:Mar 16 2020 MOD:Mar 16 2020
STS:Cust

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>
*** Proble Description ***
Action:

Customer had his users install Office 2000 from an admin
point and some users
install from a burn CD that was copied from their admin
point. The issue only
happens on the machines where the users installed Office
2000 from the burned
CD. When the users open any of the Office applicatons,
click on the help menu
they receive the following:

It launches the windows installer saying it is gathering
information, then it
prompts them with the following error message:

Error 1706. No valid source could be found for product
Microsoft Office 2000
SR-1 Professional. The Windows installer cannot continue.



If he inserts the CD on the machine four times when they
launch the help menu,
it does not ask for the source anymore.



Result:

Users were not able to use the Help files
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>

*** Resolution *** 03/16/2001 12:48:35 PM jenniep
Cause:

1.) We reviewed customer's application event log and
noticed the following:

a.) noticed it had the following:

Detection of product '{00010409-78E1-11D2-B60F-
006097C998E7}', feature
'ProductNonBootFiles', component '{0963F771-523D-11D2-
A189-00A0C90AB50F}'
failed

b.) {0963F771-523D-11D2-A189-00A0C90AB50F} means it
failed at OSAShortcut

2.) We reviewed customer's verbose reg log file and
noticed the following:

a.) MSI (c) (DC:AC): Failed to connect to server. Error:
0x80040154

b.) Failed to connect to server means Office did not get
installed with
elevated priliveges, so when a normal user logs onto the
workstation it cannot
create certain registry keys

c.) when you get "Failed to connect Server" in your
verbose log it means that
the Windows Installer is not registered properly on the
machine. It could
have been unregistered by the operating system, the SP1
service pack for
Windows 2000, or during Office or after Office.

d.) found another line in customer's verbose reg log
file that said the
following:

MSI (c) (DC:AC): SOURCEMGMT: Attempting to use
LastUsedSource from source
list.

MSI (c) (DC:AC): SOURCEMGMT: media source 'DMNO2KSP2;1'
is invalid.

e.) the above lines tell us that the volume was not
created using the same
volume label as the original Office 2000 CD

f.) the burn CD must use the same volume label as the
original 2000 CD and
this will prevent the 1706 error message

g.) found another line in customer's verbose reg log
file that said the
following:

Property(C): TRANSFORMS =
C:\WINNT\Installer\{00010409-78E1-11D2-B60F-006097C998E7}
\OfficeProWOAccess.MST
T

h.) this above tells us that Office 2000 was installed
with a mst file named
OfficeProWOAccess.MST

3.) Reviewed customer's mst file and noticed the file
was created with an
older version of the Custom Installation Wizard build 2810

4.) We recreated the mst file with the newer version of
the CIW and it added
more features to the mst file.

5.) When customer re-registered the windows installer
using the unreg and
regserver of the msiexec, you did not get this error
message in your new
verbose log and this allow a user to login and get all
the necessary registry
keys created by the windows installer and that is why you
are not seeing any
error messages anymore.



Resolution:

1.) Customer re-created his mst file with the newest CIW
and needed to import
a registry key and once we saved it as NT format, he was
able to import the
registry key in his mst file

2.) Customer burned a new copy his Office 2000 admin
point to a CD and used
the volume label from the select CD

3.) Customer installed his image of his operating system
and Office 2000 and a
new user was able to click on the help menu properly

4.) We agreed that the issue was somewhere in the
deployment of some other
software or editing the machine caused the windows
installer to unregister and
correcting the volume label CD issue will not produce any
issues in the
future.

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>

 

[suresh]

Off2000: Error 1706 when lauching help within O
(SOX010316700102)
TITLE: Off2000: Error 1706 when lauching help within O
[SOABU ]
Action: Customer had his users instal [2000 -
W_98558 ]
ID: SOX010316700102 CRT:Mar 16 2020 MOD:Mar 16 2020
STS:Cust

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>
*** Proble Description ***
Action:

Customer had his users install Office 2000 from an admin
point and some users
install from a burn CD that was copied from their admin
point. The issue only
happens on the machines where the users installed Office
2000 from the burned
CD. When the users open any of the Office applicatons,
click on the help menu
they receive the following:

It launches the windows installer saying it is gathering
information, then it
prompts them with the following error message:

Error 1706. No valid source could be found for product
Microsoft Office 2000
SR-1 Professional. The Windows installer cannot continue.



If he inserts the CD on the machine four times when they
launch the help menu,
it does not ask for the source anymore.



Result:

Users were not able to use the Help files
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>

*** Resolution *** 03/16/2001 12:48:35 PM jenniep
Cause:

1.) We reviewed customer's application event log and
noticed the following:

a.) noticed it had the following:

Detection of product '{00010409-78E1-11D2-B60F-
006097C998E7}', feature
'ProductNonBootFiles', component '{0963F771-523D-11D2-
A189-00A0C90AB50F}'
failed

b.) {0963F771-523D-11D2-A189-00A0C90AB50F} means it
failed at OSAShortcut

2.) We reviewed customer's verbose reg log file and
noticed the following:

a.) MSI (c) (DC:AC): Failed to connect to server. Error:
0x80040154

b.) Failed to connect to server means Office did not get
installed with
elevated priliveges, so when a normal user logs onto the
workstation it cannot
create certain registry keys

c.) when you get "Failed to connect Server" in your
verbose log it means that
the Windows Installer is not registered properly on the
machine. It could
have been unregistered by the operating system, the SP1
service pack for
Windows 2000, or during Office or after Office.

d.) found another line in customer's verbose reg log
file that said the
following:

MSI (c) (DC:AC): SOURCEMGMT: Attempting to use
LastUsedSource from source
list.

MSI (c) (DC:AC): SOURCEMGMT: media source 'DMNO2KSP2;1'
is invalid.

e.) the above lines tell us that the volume was not
created using the same
volume label as the original Office 2000 CD

f.) the burn CD must use the same volume label as the
original 2000 CD and
this will prevent the 1706 error message

g.) found another line in customer's verbose reg log
file that said the
following:

Property(C): TRANSFORMS =
C:\WINNT\Installer\{00010409-78E1-11D2-B60F-006097C998E7}
\OfficeProWOAccess.MST
T

h.) this above tells us that Office 2000 was installed
with a mst file named
OfficeProWOAccess.MST

3.) Reviewed customer's mst file and noticed the file
was created with an
older version of the Custom Installation Wizard build 2810

4.) We recreated the mst file with the newer version of
the CIW and it added
more features to the mst file.

5.) When customer re-registered the windows installer
using the unreg and
regserver of the msiexec, you did not get this error
message in your new
verbose log and this allow a user to login and get all
the necessary registry
keys created by the windows installer and that is why you
are not seeing any
error messages anymore.



Resolution:

1.) Customer re-created his mst file with the newest CIW
and needed to import
a registry key and once we saved it as NT format, he was
able to import the
registry key in his mst file

2.) Customer burned a new copy his Office 2000 admin
point to a CD and used
the volume label from the select CD

3.) Customer installed his image of his operating system
and Office 2000 and a
new user was able to click on the help menu properly

4.) We agreed that the issue was somewhere in the
deployment of some other
software or editing the machine caused the windows
installer to unregister and
correcting the volume label CD issue will not produce any
issues in the
future.

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>

 

[suresh]

Off2000: Error 1706 when lauching help within O
(SOX010316700102)
TITLE: Off2000: Error 1706 when lauching help within O
[SOABU ]
Action: Customer had his users instal [2000 -
W_98558 ]
ID: SOX010316700102 CRT:Mar 16 2020 MOD:Mar 16 2020
STS:Cust

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>
*** Proble Description ***
Action:

Customer had his users install Office 2000 from an admin
point and some users
install from a burn CD that was copied from their admin
point. The issue only
happens on the machines where the users installed Office
2000 from the burned
CD. When the users open any of the Office applicatons,
click on the help menu
they receive the following:

It launches the windows installer saying it is gathering
information, then it
prompts them with the following error message:

Error 1706. No valid source could be found for product
Microsoft Office 2000
SR-1 Professional. The Windows installer cannot continue.



If he inserts the CD on the machine four times when they
launch the help menu,
it does not ask for the source anymore.



Result:

Users were not able to use the Help files
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>

*** Resolution *** 03/16/2001 12:48:35 PM jenniep
Cause:

1.) We reviewed customer's application event log and
noticed the following:

a.) noticed it had the following:

Detection of product '{00010409-78E1-11D2-B60F-
006097C998E7}', feature
'ProductNonBootFiles', component '{0963F771-523D-11D2-
A189-00A0C90AB50F}'
failed

b.) {0963F771-523D-11D2-A189-00A0C90AB50F} means it
failed at OSAShortcut

2.) We reviewed customer's verbose reg log file and
noticed the following:

a.) MSI (c) (DC:AC): Failed to connect to server. Error:
0x80040154

b.) Failed to connect to server means Office did not get
installed with
elevated priliveges, so when a normal user logs onto the
workstation it cannot
create certain registry keys

c.) when you get "Failed to connect Server" in your
verbose log it means that
the Windows Installer is not registered properly on the
machine. It could
have been unregistered by the operating system, the SP1
service pack for
Windows 2000, or during Office or after Office.

d.) found another line in customer's verbose reg log
file that said the
following:

MSI (c) (DC:AC): SOURCEMGMT: Attempting to use
LastUsedSource from source
list.

MSI (c) (DC:AC): SOURCEMGMT: media source 'DMNO2KSP2;1'
is invalid.

e.) the above lines tell us that the volume was not
created using the same
volume label as the original Office 2000 CD

f.) the burn CD must use the same volume label as the
original 2000 CD and
this will prevent the 1706 error message

g.) found another line in customer's verbose reg log
file that said the
following:

Property(C): TRANSFORMS =
C:\WINNT\Installer\{00010409-78E1-11D2-B60F-006097C998E7}
\OfficeProWOAccess.MST
T

h.) this above tells us that Office 2000 was installed
with a mst file named
OfficeProWOAccess.MST

3.) Reviewed customer's mst file and noticed the file
was created with an
older version of the Custom Installation Wizard build 2810

4.) We recreated the mst file with the newer version of
the CIW and it added
more features to the mst file.

5.) When customer re-registered the windows installer
using the unreg and
regserver of the msiexec, you did not get this error
message in your new
verbose log and this allow a user to login and get all
the necessary registry
keys created by the windows installer and that is why you
are not seeing any
error messages anymore.



Resolution:

1.) Customer re-created his mst file with the newest CIW
and needed to import
a registry key and once we saved it as NT format, he was
able to import the
registry key in his mst file

2.) Customer burned a new copy his Office 2000 admin
point to a CD and used
the volume label from the select CD

3.) Customer installed his image of his operating system
and Office 2000 and a
new user was able to click on the help menu properly

4.) We agreed that the issue was somewhere in the
deployment of some other
software or editing the machine caused the windows
installer to unregister and
correcting the volume label CD issue will not produce any
issues in the
future.

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>

 

[suresh]

Off2000: Error 1706 when lauching help within O
(SOX010316700102)
TITLE: Off2000: Error 1706 when lauching help within O
[SOABU ]
Action: Customer had his users instal [2000 -
W_98558 ]
ID: SOX010316700102 CRT:Mar 16 2020 MOD:Mar 16 2020
STS:Cust

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>
*** Proble Description ***
Action:

Customer had his users install Office 2000 from an admin
point and some users
install from a burn CD that was copied from their admin
point. The issue only
happens on the machines where the users installed Office
2000 from the burned
CD. When the users open any of the Office applicatons,
click on the help menu
they receive the following:

It launches the windows installer saying it is gathering
information, then it
prompts them with the following error message:

Error 1706. No valid source could be found for product
Microsoft Office 2000
SR-1 Professional. The Windows installer cannot continue.



If he inserts the CD on the machine four times when they
launch the help menu,
it does not ask for the source anymore.



Result:

Users were not able to use the Help files
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>

*** Resolution *** 03/16/2001 12:48:35 PM jenniep
Cause:

1.) We reviewed customer's application event log and
noticed the following:

a.) noticed it had the following:

Detection of product '{00010409-78E1-11D2-B60F-
006097C998E7}', feature
'ProductNonBootFiles', component '{0963F771-523D-11D2-
A189-00A0C90AB50F}'
failed

b.) {0963F771-523D-11D2-A189-00A0C90AB50F} means it
failed at OSAShortcut

2.) We reviewed customer's verbose reg log file and
noticed the following:

a.) MSI (c) (DC:AC): Failed to connect to server. Error:
0x80040154

b.) Failed to connect to server means Office did not get
installed with
elevated priliveges, so when a normal user logs onto the
workstation it cannot
create certain registry keys

c.) when you get "Failed to connect Server" in your
verbose log it means that
the Windows Installer is not registered properly on the
machine. It could
have been unregistered by the operating system, the SP1
service pack for
Windows 2000, or during Office or after Office.

d.) found another line in customer's verbose reg log
file that said the
following:

MSI (c) (DC:AC): SOURCEMGMT: Attempting to use
LastUsedSource from source
list.

MSI (c) (DC:AC): SOURCEMGMT: media source 'DMNO2KSP2;1'
is invalid.

e.) the above lines tell us that the volume was not
created using the same
volume label as the original Office 2000 CD

f.) the burn CD must use the same volume label as the
original 2000 CD and
this will prevent the 1706 error message

g.) found another line in customer's verbose reg log
file that said the
following:

Property(C): TRANSFORMS =
C:\WINNT\Installer\{00010409-78E1-11D2-B60F-006097C998E7}
\OfficeProWOAccess.MST
T

h.) this above tells us that Office 2000 was installed
with a mst file named
OfficeProWOAccess.MST

3.) Reviewed customer's mst file and noticed the file
was created with an
older version of the Custom Installation Wizard build 2810

4.) We recreated the mst file with the newer version of
the CIW and it added
more features to the mst file.

5.) When customer re-registered the windows installer
using the unreg and
regserver of the msiexec, you did not get this error
message in your new
verbose log and this allow a user to login and get all
the necessary registry
keys created by the windows installer and that is why you
are not seeing any
error messages anymore.



Resolution:

1.) Customer re-created his mst file with the newest CIW
and needed to import
a registry key and once we saved it as NT format, he was
able to import the
registry key in his mst file

2.) Customer burned a new copy his Office 2000 admin
point to a CD and used
the volume label from the select CD

3.) Customer installed his image of his operating system
and Office 2000 and a
new user was able to click on the help menu properly

4.) We agreed that the issue was somewhere in the
deployment of some other
software or editing the machine caused the windows
installer to unregister and
correcting the volume label CD issue will not produce any
issues in the
future.

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>

 

[suresh]

Off2000: Error 1706 when lauching help within O
(SOX010316700102)
TITLE: Off2000: Error 1706 when lauching help within O
[SOABU ]
Action: Customer had his users instal [2000 -
W_98558 ]
ID: SOX010316700102 CRT:Mar 16 2020 MOD:Mar 16 2020
STS:Cust

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>
*** Proble Description ***
Action:

Customer had his users install Office 2000 from an admin
point and some users
install from a burn CD that was copied from their admin
point. The issue only
happens on the machines where the users installed Office
2000 from the burned
CD. When the users open any of the Office applicatons,
click on the help menu
they receive the following:

It launches the windows installer saying it is gathering
information, then it
prompts them with the following error message:

Error 1706. No valid source could be found for product
Microsoft Office 2000
SR-1 Professional. The Windows installer cannot continue.



If he inserts the CD on the machine four times when they
launch the help menu,
it does not ask for the source anymore.



Result:

Users were not able to use the Help files
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>

*** Resolution *** 03/16/2001 12:48:35 PM jenniep
Cause:

1.) We reviewed customer's application event log and
noticed the following:

a.) noticed it had the following:

Detection of product '{00010409-78E1-11D2-B60F-
006097C998E7}', feature
'ProductNonBootFiles', component '{0963F771-523D-11D2-
A189-00A0C90AB50F}'
failed

b.) {0963F771-523D-11D2-A189-00A0C90AB50F} means it
failed at OSAShortcut

2.) We reviewed customer's verbose reg log file and
noticed the following:

a.) MSI (c) (DC:AC): Failed to connect to server. Error:
0x80040154

b.) Failed to connect to server means Office did not get
installed with
elevated priliveges, so when a normal user logs onto the
workstation it cannot
create certain registry keys

c.) when you get "Failed to connect Server" in your
verbose log it means that
the Windows Installer is not registered properly on the
machine. It could
have been unregistered by the operating system, the SP1
service pack for
Windows 2000, or during Office or after Office.

d.) found another line in customer's verbose reg log
file that said the
following:

MSI (c) (DC:AC): SOURCEMGMT: Attempting to use
LastUsedSource from source
list.

MSI (c) (DC:AC): SOURCEMGMT: media source 'DMNO2KSP2;1'
is invalid.

e.) the above lines tell us that the volume was not
created using the same
volume label as the original Office 2000 CD

f.) the burn CD must use the same volume label as the
original 2000 CD and
this will prevent the 1706 error message

g.) found another line in customer's verbose reg log
file that said the
following:

Property(C): TRANSFORMS =
C:\WINNT\Installer\{00010409-78E1-11D2-B60F-006097C998E7}
\OfficeProWOAccess.MST
T

h.) this above tells us that Office 2000 was installed
with a mst file named
OfficeProWOAccess.MST

3.) Reviewed customer's mst file and noticed the file
was created with an
older version of the Custom Installation Wizard build 2810

4.) We recreated the mst file with the newer version of
the CIW and it added
more features to the mst file.

5.) When customer re-registered the windows installer
using the unreg and
regserver of the msiexec, you did not get this error
message in your new
verbose log and this allow a user to login and get all
the necessary registry
keys created by the windows installer and that is why you
are not seeing any
error messages anymore.



Resolution:

1.) Customer re-created his mst file with the newest CIW
and needed to import
a registry key and once we saved it as NT format, he was
able to import the
registry key in his mst file

2.) Customer burned a new copy his Office 2000 admin
point to a CD and used
the volume label from the select CD

3.) Customer installed his image of his operating system
and Office 2000 and a
new user was able to click on the help menu properly

4.) We agreed that the issue was somewhere in the
deployment of some other
software or editing the machine caused the windows
installer to unregister and
correcting the volume label CD issue will not produce any
issues in the
future.

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>

 

[suresh]

Off2000: Error 1706 when lauching help within O
(SOX010316700102)
TITLE: Off2000: Error 1706 when lauching help within O
[SOABU ]
Action: Customer had his users instal [2000 -
W_98558 ]
ID: SOX010316700102 CRT:Mar 16 2020 MOD:Mar 16 2020
STS:Cust

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>
*** Proble Description ***
Action:

Customer had his users install Office 2000 from an admin
point and some users
install from a burn CD that was copied from their admin
point. The issue only
happens on the machines where the users installed Office
2000 from the burned
CD. When the users open any of the Office applicatons,
click on the help menu
they receive the following:

It launches the windows installer saying it is gathering
information, then it
prompts them with the following error message:

Error 1706. No valid source could be found for product
Microsoft Office 2000
SR-1 Professional. The Windows installer cannot continue.



If he inserts the CD on the machine four times when they
launch the help menu,
it does not ask for the source anymore.



Result:

Users were not able to use the Help files
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>

*** Resolution *** 03/16/2001 12:48:35 PM jenniep
Cause:

1.) We reviewed customer's application event log and
noticed the following:

a.) noticed it had the following:

Detection of product '{00010409-78E1-11D2-B60F-
006097C998E7}', feature
'ProductNonBootFiles', component '{0963F771-523D-11D2-
A189-00A0C90AB50F}'
failed

b.) {0963F771-523D-11D2-A189-00A0C90AB50F} means it
failed at OSAShortcut

2.) We reviewed customer's verbose reg log file and
noticed the following:

a.) MSI (c) (DC:AC): Failed to connect to server. Error:
0x80040154

b.) Failed to connect to server means Office did not get
installed with
elevated priliveges, so when a normal user logs onto the
workstation it cannot
create certain registry keys

c.) when you get "Failed to connect Server" in your
verbose log it means that
the Windows Installer is not registered properly on the
machine. It could
have been unregistered by the operating system, the SP1
service pack for
Windows 2000, or during Office or after Office.

d.) found another line in customer's verbose reg log
file that said the
following:

MSI (c) (DC:AC): SOURCEMGMT: Attempting to use
LastUsedSource from source
list.

MSI (c) (DC:AC): SOURCEMGMT: media source 'DMNO2KSP2;1'
is invalid.

e.) the above lines tell us that the volume was not
created using the same
volume label as the original Office 2000 CD

f.) the burn CD must use the same volume label as the
original 2000 CD and
this will prevent the 1706 error message

g.) found another line in customer's verbose reg log
file that said the
following:

Property(C): TRANSFORMS =
C:\WINNT\Installer\{00010409-78E1-11D2-B60F-006097C998E7}
\OfficeProWOAccess.MST
T

h.) this above tells us that Office 2000 was installed
with a mst file named
OfficeProWOAccess.MST

3.) Reviewed customer's mst file and noticed the file
was created with an
older version of the Custom Installation Wizard build 2810

4.) We recreated the mst file with the newer version of
the CIW and it added
more features to the mst file.

5.) When customer re-registered the windows installer
using the unreg and
regserver of the msiexec, you did not get this error
message in your new
verbose log and this allow a user to login and get all
the necessary registry
keys created by the windows installer and that is why you
are not seeing any
error messages anymore.



Resolution:

1.) Customer re-created his mst file with the newest CIW
and needed to import
a registry key and once we saved it as NT format, he was
able to import the
registry key in his mst file

2.) Customer burned a new copy his Office 2000 admin
point to a CD and used
the volume label from the select CD

3.) Customer installed his image of his operating system
and Office 2000 and a
new user was able to click on the help menu properly

4.) We agreed that the issue was somewhere in the
deployment of some other
software or editing the machine caused the windows
installer to unregister and
correcting the volume label CD issue will not produce any
issues in the
future.

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>

 

[suresh]

Off2000: Error 1706 when lauching help within O
(SOX010316700102)
TITLE: Off2000: Error 1706 when lauching help within O
[SOABU ]
Action: Customer had his users instal [2000 -
W_98558 ]
ID: SOX010316700102 CRT:Mar 16 2020 MOD:Mar 16 2020
STS:Cust

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>
*** Proble Description ***
Action:

Customer had his users install Office 2000 from an admin
point and some users
install from a burn CD that was copied from their admin
point. The issue only
happens on the machines where the users installed Office
2000 from the burned
CD. When the users open any of the Office applicatons,
click on the help menu
they receive the following:

It launches the windows installer saying it is gathering
information, then it
prompts them with the following error message:

Error 1706. No valid source could be found for product
Microsoft Office 2000
SR-1 Professional. The Windows installer cannot continue.



If he inserts the CD on the machine four times when they
launch the help menu,
it does not ask for the source anymore.



Result:

Users were not able to use the Help files
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>

*** Resolution *** 03/16/2001 12:48:35 PM jenniep
Cause:

1.) We reviewed customer's application event log and
noticed the following:

a.) noticed it had the following:

Detection of product '{00010409-78E1-11D2-B60F-
006097C998E7}', feature
'ProductNonBootFiles', component '{0963F771-523D-11D2-
A189-00A0C90AB50F}'
failed

b.) {0963F771-523D-11D2-A189-00A0C90AB50F} means it
failed at OSAShortcut

2.) We reviewed customer's verbose reg log file and
noticed the following:

a.) MSI (c) (DC:AC): Failed to connect to server. Error:
0x80040154

b.) Failed to connect to server means Office did not get
installed with
elevated priliveges, so when a normal user logs onto the
workstation it cannot
create certain registry keys

c.) when you get "Failed to connect Server" in your
verbose log it means that
the Windows Installer is not registered properly on the
machine. It could
have been unregistered by the operating system, the SP1
service pack for
Windows 2000, or during Office or after Office.

d.) found another line in customer's verbose reg log
file that said the
following:

MSI (c) (DC:AC): SOURCEMGMT: Attempting to use
LastUsedSource from source
list.

MSI (c) (DC:AC): SOURCEMGMT: media source 'DMNO2KSP2;1'
is invalid.

e.) the above lines tell us that the volume was not
created using the same
volume label as the original Office 2000 CD

f.) the burn CD must use the same volume label as the
original 2000 CD and
this will prevent the 1706 error message

g.) found another line in customer's verbose reg log
file that said the
following:

Property(C): TRANSFORMS =
C:\WINNT\Installer\{00010409-78E1-11D2-B60F-006097C998E7}
\OfficeProWOAccess.MST
T

h.) this above tells us that Office 2000 was installed
with a mst file named
OfficeProWOAccess.MST

3.) Reviewed customer's mst file and noticed the file
was created with an
older version of the Custom Installation Wizard build 2810

4.) We recreated the mst file with the newer version of
the CIW and it added
more features to the mst file.

5.) When customer re-registered the windows installer
using the unreg and
regserver of the msiexec, you did not get this error
message in your new
verbose log and this allow a user to login and get all
the necessary registry
keys created by the windows installer and that is why you
are not seeing any
error messages anymore.



Resolution:

1.) Customer re-created his mst file with the newest CIW
and needed to import
a registry key and once we saved it as NT format, he was
able to import the
registry key in his mst file

2.) Customer burned a new copy his Office 2000 admin
point to a CD and used
the volume label from the select CD

3.) Customer installed his image of his operating system
and Office 2000 and a
new user was able to click on the help menu properly

4.) We agreed that the issue was somewhere in the
deployment of some other
software or editing the machine caused the windows
installer to unregister and
correcting the volume label CD issue will not produce any
issues in the
future.

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<><><><><><><><><><>