Adobe Reader tries to repeat install MOS 2003 and crashes

[Chad Harris]

On this box:

XP SP2 RC2
MOS2003
Adobe Reader 6

I cross posted, which I try to do rarely,. intentionally because this problem stretches across resources that might be in more than one group not to be rude so thanks for a little indulgence.

In short, trying to read a .pdf starts the Windows Installer for Office 2003 and I have it already and it works great.

For the past couple days, or possibly one day but I don't know exactly when, trying to view a .pdf brings up the Windows Installer, and tries to install MOS Office 2003. It tops out resources continually to make the system freeze, and it won't open the .pdf and I have to kill both the faltering .pdf and MSI.exe at Task Manager to move on. This has nothing to do with SP2 because it just started.

I've run detect and repair for Adobe Reader 6 and that doesn't help. MOS 2003 all apps and Word Mail Editor for Outlook are working perfectly. I'm up to date on every possible patch for each application that the MSFT Office site has to offer. So my questions:

1) Anyone know how to fix this? I could fish around for a restore point, or I could run System File Checker since I've got it pointing to the hard drive to use SP2 files instead of my older CD-ROM slipstreamed for SP1.

2) I could try to run a detect and repair in Word for example, but Word and Office work just fine so I'm not trying to repair them. My problem is that Adobe Reader brings up the Office installer over and over again, and even the cancel button won't stop the installer and it freezes the System and Reader won't open the .pdf.

3) This brings up the question when you run a Detect and Repair in an Office application will it revert back to before you upgraded Office with any of the available updates for MOS 2003 as I have?

4) Isn't the add/remove repair install a different procedure than Detect and Repair file wise or registry wise?

I have a clue as to something that might be causing this. For ridiculous reasons, Office installs wisptis.exe a pen adjunct for Tablet PC whether you have a Tablet or not instead of making it optional from the Office site,and Adobe Reader and Acrobat install wisptis.exe as well. I removed wisptis because it causes CPU and freeze problems, and I don't have a Tablet so I'm not using a Tablet pen--something that escaped the Microsoft Office developers.

I get these error in Event Viewer: (Again Office works just fine and I'm not trying to install it and don't think it's office that needs the repair. It has to do with the stupid wisptis add-in that MSFT and Adobe insisted on including for Tablet Pens that mimics spyware.

The Windows Installer service was successfully sent a start control.

Detection of product '{91E30409-6000-11D3-8CFE-0150048383C9}', feature 'WISPHidden' failed during request for component '{0495B4B9-264D-46D5-8C55-238BDC3EFBD4}'

Product: Microsoft Office Professional Edition 2003 -- Error 25090. Office Setup encountered a problem with the Office Source Engine, system error: -2147023838. Please open E:\Program Files\Microsoft Office\OFFICE11\1033\SETUP.CHM and look for "Office Source Engine" for information on how to resolve this problem.

Obviously reading a .pdf shouldn't send the Windows Installer a start control.

TIA very much,

Chad Harris

 

[Mary Sauer]

Error Message: Error 25090 Office Setup Encountered a Problem with the Office Source
Engine, System Error: -2147023836
http://support.microsoft.com/default.aspx?scid=kb;EN-US;827467
How To View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308427

--
Mary Sauer MS MVP
http://office.microsoft.com/
http://www.mvps.org/msauer/
news://msnews.microsoft.com
On this box:

XP SP2 RC2
MOS2003
Adobe Reader 6

I cross posted, which I try to do rarely,. intentionally because this problem
stretches across resources that might be in more than one group not to be rude so
thanks for a little indulgence.

In short, trying to read a .pdf starts the Windows Installer for Office 2003 and I
have it already and it works great.

For the past couple days, or possibly one day but I don't know exactly when, trying
to view a .pdf brings up the Windows Installer, and tries to install MOS Office 2003.
It tops out resources continually to make the system freeze, and it won't open the
..pdf and I have to kill both the faltering .pdf and MSI.exe at Task Manager to move
on. This has nothing to do with SP2 because it just started.

I've run detect and repair for Adobe Reader 6 and that doesn't help. MOS 2003 all
apps and Word Mail Editor for Outlook are working perfectly. I'm up to date on every
possible patch for each application that the MSFT Office site has to offer. So my
questions:

1) Anyone know how to fix this? I could fish around for a restore point, or I could
run System File Checker since I've got it pointing to the hard drive to use SP2 files
instead of my older CD-ROM slipstreamed for SP1.

2) I could try to run a detect and repair in Word for example, but Word and Office
work just fine so I'm not trying to repair them. My problem is that Adobe Reader
brings up the Office installer over and over again, and even the cancel button won't
stop the installer and it freezes the System and Reader won't open the .pdf.

3) This brings up the question when you run a Detect and Repair in an Office
application will it revert back to before you upgraded Office with any of the
available updates for MOS 2003 as I have?

4) Isn't the add/remove repair install a different procedure than Detect and Repair
file wise or registry wise?

I have a clue as to something that might be causing this. For ridiculous reasons,
Office installs wisptis.exe a pen adjunct for Tablet PC whether you have a Tablet or
not instead of making it optional from the Office site,and Adobe Reader and Acrobat
install wisptis.exe as well. I removed wisptis because it causes CPU and freeze
problems, and I don't have a Tablet so I'm not using a Tablet pen--something that
escaped the Microsoft Office developers.

I get these error in Event Viewer: (Again Office works just fine and I'm not trying
to install it and don't think it's office that needs the repair. It has to do with
the stupid wisptis add-in that MSFT and Adobe insisted on including for Tablet Pens
that mimics spyware.

The Windows Installer service was successfully sent a start control.

Detection of product '{91E30409-6000-11D3-8CFE-0150048383C9}', feature 'WISPHidden'
failed during request for component '{0495B4B9-264D-46D5-8C55-238BDC3EFBD4}'

Product: Microsoft Office Professional Edition 2003 -- Error 25090. Office Setup
encountered a problem with the Office Source Engine, system error: -2147023838.
Please open E:\Program Files\Microsoft Office\OFFICE11\1033\SETUP.CHM and look for
"Office Source Engine" for information on how to resolve this problem.

Obviously reading a .pdf shouldn't send the Windows Installer a start control.

TIA very much,

Chad Harris

 

[Mary Sauer]

Error Message: Error 25090 Office Setup Encountered a Problem with the Office Source
Engine, System Error: -2147023836
http://support.microsoft.com/default.aspx?scid=kb;EN-US;827467
How To View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308427

--
Mary Sauer MS MVP
http://office.microsoft.com/
http://www.mvps.org/msauer/
news://msnews.microsoft.com
On this box:

XP SP2 RC2
MOS2003
Adobe Reader 6

I cross posted, which I try to do rarely,. intentionally because this problem
stretches across resources that might be in more than one group not to be rude so
thanks for a little indulgence.

In short, trying to read a .pdf starts the Windows Installer for Office 2003 and I
have it already and it works great.

For the past couple days, or possibly one day but I don't know exactly when, trying
to view a .pdf brings up the Windows Installer, and tries to install MOS Office 2003.
It tops out resources continually to make the system freeze, and it won't open the
..pdf and I have to kill both the faltering .pdf and MSI.exe at Task Manager to move
on. This has nothing to do with SP2 because it just started.

I've run detect and repair for Adobe Reader 6 and that doesn't help. MOS 2003 all
apps and Word Mail Editor for Outlook are working perfectly. I'm up to date on every
possible patch for each application that the MSFT Office site has to offer. So my
questions:

1) Anyone know how to fix this? I could fish around for a restore point, or I could
run System File Checker since I've got it pointing to the hard drive to use SP2 files
instead of my older CD-ROM slipstreamed for SP1.

2) I could try to run a detect and repair in Word for example, but Word and Office
work just fine so I'm not trying to repair them. My problem is that Adobe Reader
brings up the Office installer over and over again, and even the cancel button won't
stop the installer and it freezes the System and Reader won't open the .pdf.

3) This brings up the question when you run a Detect and Repair in an Office
application will it revert back to before you upgraded Office with any of the
available updates for MOS 2003 as I have?

4) Isn't the add/remove repair install a different procedure than Detect and Repair
file wise or registry wise?

I have a clue as to something that might be causing this. For ridiculous reasons,
Office installs wisptis.exe a pen adjunct for Tablet PC whether you have a Tablet or
not instead of making it optional from the Office site,and Adobe Reader and Acrobat
install wisptis.exe as well. I removed wisptis because it causes CPU and freeze
problems, and I don't have a Tablet so I'm not using a Tablet pen--something that
escaped the Microsoft Office developers.

I get these error in Event Viewer: (Again Office works just fine and I'm not trying
to install it and don't think it's office that needs the repair. It has to do with
the stupid wisptis add-in that MSFT and Adobe insisted on including for Tablet Pens
that mimics spyware.

The Windows Installer service was successfully sent a start control.

Detection of product '{91E30409-6000-11D3-8CFE-0150048383C9}', feature 'WISPHidden'
failed during request for component '{0495B4B9-264D-46D5-8C55-238BDC3EFBD4}'

Product: Microsoft Office Professional Edition 2003 -- Error 25090. Office Setup
encountered a problem with the Office Source Engine, system error: -2147023838.
Please open E:\Program Files\Microsoft Office\OFFICE11\1033\SETUP.CHM and look for
"Office Source Engine" for information on how to resolve this problem.

Obviously reading a .pdf shouldn't send the Windows Installer a start control.

TIA very much,

Chad Harris

 

[Mary Sauer]

Error Message: Error 25090 Office Setup Encountered a Problem with the Office Source
Engine, System Error: -2147023836
http://support.microsoft.com/default.aspx?scid=kb;EN-US;827467
How To View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308427

--
Mary Sauer MS MVP
http://office.microsoft.com/
http://www.mvps.org/msauer/
news://msnews.microsoft.com
On this box:

XP SP2 RC2
MOS2003
Adobe Reader 6

I cross posted, which I try to do rarely,. intentionally because this problem
stretches across resources that might be in more than one group not to be rude so
thanks for a little indulgence.

In short, trying to read a .pdf starts the Windows Installer for Office 2003 and I
have it already and it works great.

For the past couple days, or possibly one day but I don't know exactly when, trying
to view a .pdf brings up the Windows Installer, and tries to install MOS Office 2003.
It tops out resources continually to make the system freeze, and it won't open the
..pdf and I have to kill both the faltering .pdf and MSI.exe at Task Manager to move
on. This has nothing to do with SP2 because it just started.

I've run detect and repair for Adobe Reader 6 and that doesn't help. MOS 2003 all
apps and Word Mail Editor for Outlook are working perfectly. I'm up to date on every
possible patch for each application that the MSFT Office site has to offer. So my
questions:

1) Anyone know how to fix this? I could fish around for a restore point, or I could
run System File Checker since I've got it pointing to the hard drive to use SP2 files
instead of my older CD-ROM slipstreamed for SP1.

2) I could try to run a detect and repair in Word for example, but Word and Office
work just fine so I'm not trying to repair them. My problem is that Adobe Reader
brings up the Office installer over and over again, and even the cancel button won't
stop the installer and it freezes the System and Reader won't open the .pdf.

3) This brings up the question when you run a Detect and Repair in an Office
application will it revert back to before you upgraded Office with any of the
available updates for MOS 2003 as I have?

4) Isn't the add/remove repair install a different procedure than Detect and Repair
file wise or registry wise?

I have a clue as to something that might be causing this. For ridiculous reasons,
Office installs wisptis.exe a pen adjunct for Tablet PC whether you have a Tablet or
not instead of making it optional from the Office site,and Adobe Reader and Acrobat
install wisptis.exe as well. I removed wisptis because it causes CPU and freeze
problems, and I don't have a Tablet so I'm not using a Tablet pen--something that
escaped the Microsoft Office developers.

I get these error in Event Viewer: (Again Office works just fine and I'm not trying
to install it and don't think it's office that needs the repair. It has to do with
the stupid wisptis add-in that MSFT and Adobe insisted on including for Tablet Pens
that mimics spyware.

The Windows Installer service was successfully sent a start control.

Detection of product '{91E30409-6000-11D3-8CFE-0150048383C9}', feature 'WISPHidden'
failed during request for component '{0495B4B9-264D-46D5-8C55-238BDC3EFBD4}'

Product: Microsoft Office Professional Edition 2003 -- Error 25090. Office Setup
encountered a problem with the Office Source Engine, system error: -2147023838.
Please open E:\Program Files\Microsoft Office\OFFICE11\1033\SETUP.CHM and look for
"Office Source Engine" for information on how to resolve this problem.

Obviously reading a .pdf shouldn't send the Windows Installer a start control.

TIA very much,

Chad Harris

 

[Mary Sauer]

Error Message: Error 25090 Office Setup Encountered a Problem with the Office Source
Engine, System Error: -2147023836
http://support.microsoft.com/default.aspx?scid=kb;EN-US;827467
How To View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308427

--
Mary Sauer MS MVP
http://office.microsoft.com/
http://www.mvps.org/msauer/
news://msnews.microsoft.com
On this box:

XP SP2 RC2
MOS2003
Adobe Reader 6

I cross posted, which I try to do rarely,. intentionally because this problem
stretches across resources that might be in more than one group not to be rude so
thanks for a little indulgence.

In short, trying to read a .pdf starts the Windows Installer for Office 2003 and I
have it already and it works great.

For the past couple days, or possibly one day but I don't know exactly when, trying
to view a .pdf brings up the Windows Installer, and tries to install MOS Office 2003.
It tops out resources continually to make the system freeze, and it won't open the
..pdf and I have to kill both the faltering .pdf and MSI.exe at Task Manager to move
on. This has nothing to do with SP2 because it just started.

I've run detect and repair for Adobe Reader 6 and that doesn't help. MOS 2003 all
apps and Word Mail Editor for Outlook are working perfectly. I'm up to date on every
possible patch for each application that the MSFT Office site has to offer. So my
questions:

1) Anyone know how to fix this? I could fish around for a restore point, or I could
run System File Checker since I've got it pointing to the hard drive to use SP2 files
instead of my older CD-ROM slipstreamed for SP1.

2) I could try to run a detect and repair in Word for example, but Word and Office
work just fine so I'm not trying to repair them. My problem is that Adobe Reader
brings up the Office installer over and over again, and even the cancel button won't
stop the installer and it freezes the System and Reader won't open the .pdf.

3) This brings up the question when you run a Detect and Repair in an Office
application will it revert back to before you upgraded Office with any of the
available updates for MOS 2003 as I have?

4) Isn't the add/remove repair install a different procedure than Detect and Repair
file wise or registry wise?

I have a clue as to something that might be causing this. For ridiculous reasons,
Office installs wisptis.exe a pen adjunct for Tablet PC whether you have a Tablet or
not instead of making it optional from the Office site,and Adobe Reader and Acrobat
install wisptis.exe as well. I removed wisptis because it causes CPU and freeze
problems, and I don't have a Tablet so I'm not using a Tablet pen--something that
escaped the Microsoft Office developers.

I get these error in Event Viewer: (Again Office works just fine and I'm not trying
to install it and don't think it's office that needs the repair. It has to do with
the stupid wisptis add-in that MSFT and Adobe insisted on including for Tablet Pens
that mimics spyware.

The Windows Installer service was successfully sent a start control.

Detection of product '{91E30409-6000-11D3-8CFE-0150048383C9}', feature 'WISPHidden'
failed during request for component '{0495B4B9-264D-46D5-8C55-238BDC3EFBD4}'

Product: Microsoft Office Professional Edition 2003 -- Error 25090. Office Setup
encountered a problem with the Office Source Engine, system error: -2147023838.
Please open E:\Program Files\Microsoft Office\OFFICE11\1033\SETUP.CHM and look for
"Office Source Engine" for information on how to resolve this problem.

Obviously reading a .pdf shouldn't send the Windows Installer a start control.

TIA very much,

Chad Harris

 

[Mary Sauer]

Error Message: Error 25090 Office Setup Encountered a Problem with the Office Source
Engine, System Error: -2147023836
http://support.microsoft.com/default.aspx?scid=kb;EN-US;827467
How To View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308427

--
Mary Sauer MS MVP
http://office.microsoft.com/
http://www.mvps.org/msauer/
news://msnews.microsoft.com
On this box:

XP SP2 RC2
MOS2003
Adobe Reader 6

I cross posted, which I try to do rarely,. intentionally because this problem
stretches across resources that might be in more than one group not to be rude so
thanks for a little indulgence.

In short, trying to read a .pdf starts the Windows Installer for Office 2003 and I
have it already and it works great.

For the past couple days, or possibly one day but I don't know exactly when, trying
to view a .pdf brings up the Windows Installer, and tries to install MOS Office 2003.
It tops out resources continually to make the system freeze, and it won't open the
..pdf and I have to kill both the faltering .pdf and MSI.exe at Task Manager to move
on. This has nothing to do with SP2 because it just started.

I've run detect and repair for Adobe Reader 6 and that doesn't help. MOS 2003 all
apps and Word Mail Editor for Outlook are working perfectly. I'm up to date on every
possible patch for each application that the MSFT Office site has to offer. So my
questions:

1) Anyone know how to fix this? I could fish around for a restore point, or I could
run System File Checker since I've got it pointing to the hard drive to use SP2 files
instead of my older CD-ROM slipstreamed for SP1.

2) I could try to run a detect and repair in Word for example, but Word and Office
work just fine so I'm not trying to repair them. My problem is that Adobe Reader
brings up the Office installer over and over again, and even the cancel button won't
stop the installer and it freezes the System and Reader won't open the .pdf.

3) This brings up the question when you run a Detect and Repair in an Office
application will it revert back to before you upgraded Office with any of the
available updates for MOS 2003 as I have?

4) Isn't the add/remove repair install a different procedure than Detect and Repair
file wise or registry wise?

I have a clue as to something that might be causing this. For ridiculous reasons,
Office installs wisptis.exe a pen adjunct for Tablet PC whether you have a Tablet or
not instead of making it optional from the Office site,and Adobe Reader and Acrobat
install wisptis.exe as well. I removed wisptis because it causes CPU and freeze
problems, and I don't have a Tablet so I'm not using a Tablet pen--something that
escaped the Microsoft Office developers.

I get these error in Event Viewer: (Again Office works just fine and I'm not trying
to install it and don't think it's office that needs the repair. It has to do with
the stupid wisptis add-in that MSFT and Adobe insisted on including for Tablet Pens
that mimics spyware.

The Windows Installer service was successfully sent a start control.

Detection of product '{91E30409-6000-11D3-8CFE-0150048383C9}', feature 'WISPHidden'
failed during request for component '{0495B4B9-264D-46D5-8C55-238BDC3EFBD4}'

Product: Microsoft Office Professional Edition 2003 -- Error 25090. Office Setup
encountered a problem with the Office Source Engine, system error: -2147023838.
Please open E:\Program Files\Microsoft Office\OFFICE11\1033\SETUP.CHM and look for
"Office Source Engine" for information on how to resolve this problem.

Obviously reading a .pdf shouldn't send the Windows Installer a start control.

TIA very much,

Chad Harris

 

[Mary Sauer]

Error Message: Error 25090 Office Setup Encountered a Problem with the Office Source
Engine, System Error: -2147023836
http://support.microsoft.com/default.aspx?scid=kb;EN-US;827467
How To View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308427

--
Mary Sauer MS MVP
http://office.microsoft.com/
http://www.mvps.org/msauer/
news://msnews.microsoft.com
On this box:

XP SP2 RC2
MOS2003
Adobe Reader 6

I cross posted, which I try to do rarely,. intentionally because this problem
stretches across resources that might be in more than one group not to be rude so
thanks for a little indulgence.

In short, trying to read a .pdf starts the Windows Installer for Office 2003 and I
have it already and it works great.

For the past couple days, or possibly one day but I don't know exactly when, trying
to view a .pdf brings up the Windows Installer, and tries to install MOS Office 2003.
It tops out resources continually to make the system freeze, and it won't open the
..pdf and I have to kill both the faltering .pdf and MSI.exe at Task Manager to move
on. This has nothing to do with SP2 because it just started.

I've run detect and repair for Adobe Reader 6 and that doesn't help. MOS 2003 all
apps and Word Mail Editor for Outlook are working perfectly. I'm up to date on every
possible patch for each application that the MSFT Office site has to offer. So my
questions:

1) Anyone know how to fix this? I could fish around for a restore point, or I could
run System File Checker since I've got it pointing to the hard drive to use SP2 files
instead of my older CD-ROM slipstreamed for SP1.

2) I could try to run a detect and repair in Word for example, but Word and Office
work just fine so I'm not trying to repair them. My problem is that Adobe Reader
brings up the Office installer over and over again, and even the cancel button won't
stop the installer and it freezes the System and Reader won't open the .pdf.

3) This brings up the question when you run a Detect and Repair in an Office
application will it revert back to before you upgraded Office with any of the
available updates for MOS 2003 as I have?

4) Isn't the add/remove repair install a different procedure than Detect and Repair
file wise or registry wise?

I have a clue as to something that might be causing this. For ridiculous reasons,
Office installs wisptis.exe a pen adjunct for Tablet PC whether you have a Tablet or
not instead of making it optional from the Office site,and Adobe Reader and Acrobat
install wisptis.exe as well. I removed wisptis because it causes CPU and freeze
problems, and I don't have a Tablet so I'm not using a Tablet pen--something that
escaped the Microsoft Office developers.

I get these error in Event Viewer: (Again Office works just fine and I'm not trying
to install it and don't think it's office that needs the repair. It has to do with
the stupid wisptis add-in that MSFT and Adobe insisted on including for Tablet Pens
that mimics spyware.

The Windows Installer service was successfully sent a start control.

Detection of product '{91E30409-6000-11D3-8CFE-0150048383C9}', feature 'WISPHidden'
failed during request for component '{0495B4B9-264D-46D5-8C55-238BDC3EFBD4}'

Product: Microsoft Office Professional Edition 2003 -- Error 25090. Office Setup
encountered a problem with the Office Source Engine, system error: -2147023838.
Please open E:\Program Files\Microsoft Office\OFFICE11\1033\SETUP.CHM and look for
"Office Source Engine" for information on how to resolve this problem.

Obviously reading a .pdf shouldn't send the Windows Installer a start control.

TIA very much,

Chad Harris

 

[Mary Sauer]

Error Message: Error 25090 Office Setup Encountered a Problem with the Office Source
Engine, System Error: -2147023836
http://support.microsoft.com/default.aspx?scid=kb;EN-US;827467
How To View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308427

--
Mary Sauer MS MVP
http://office.microsoft.com/
http://www.mvps.org/msauer/
news://msnews.microsoft.com
On this box:

XP SP2 RC2
MOS2003
Adobe Reader 6

I cross posted, which I try to do rarely,. intentionally because this problem
stretches across resources that might be in more than one group not to be rude so
thanks for a little indulgence.

In short, trying to read a .pdf starts the Windows Installer for Office 2003 and I
have it already and it works great.

For the past couple days, or possibly one day but I don't know exactly when, trying
to view a .pdf brings up the Windows Installer, and tries to install MOS Office 2003.
It tops out resources continually to make the system freeze, and it won't open the
..pdf and I have to kill both the faltering .pdf and MSI.exe at Task Manager to move
on. This has nothing to do with SP2 because it just started.

I've run detect and repair for Adobe Reader 6 and that doesn't help. MOS 2003 all
apps and Word Mail Editor for Outlook are working perfectly. I'm up to date on every
possible patch for each application that the MSFT Office site has to offer. So my
questions:

1) Anyone know how to fix this? I could fish around for a restore point, or I could
run System File Checker since I've got it pointing to the hard drive to use SP2 files
instead of my older CD-ROM slipstreamed for SP1.

2) I could try to run a detect and repair in Word for example, but Word and Office
work just fine so I'm not trying to repair them. My problem is that Adobe Reader
brings up the Office installer over and over again, and even the cancel button won't
stop the installer and it freezes the System and Reader won't open the .pdf.

3) This brings up the question when you run a Detect and Repair in an Office
application will it revert back to before you upgraded Office with any of the
available updates for MOS 2003 as I have?

4) Isn't the add/remove repair install a different procedure than Detect and Repair
file wise or registry wise?

I have a clue as to something that might be causing this. For ridiculous reasons,
Office installs wisptis.exe a pen adjunct for Tablet PC whether you have a Tablet or
not instead of making it optional from the Office site,and Adobe Reader and Acrobat
install wisptis.exe as well. I removed wisptis because it causes CPU and freeze
problems, and I don't have a Tablet so I'm not using a Tablet pen--something that
escaped the Microsoft Office developers.

I get these error in Event Viewer: (Again Office works just fine and I'm not trying
to install it and don't think it's office that needs the repair. It has to do with
the stupid wisptis add-in that MSFT and Adobe insisted on including for Tablet Pens
that mimics spyware.

The Windows Installer service was successfully sent a start control.

Detection of product '{91E30409-6000-11D3-8CFE-0150048383C9}', feature 'WISPHidden'
failed during request for component '{0495B4B9-264D-46D5-8C55-238BDC3EFBD4}'

Product: Microsoft Office Professional Edition 2003 -- Error 25090. Office Setup
encountered a problem with the Office Source Engine, system error: -2147023838.
Please open E:\Program Files\Microsoft Office\OFFICE11\1033\SETUP.CHM and look for
"Office Source Engine" for information on how to resolve this problem.

Obviously reading a .pdf shouldn't send the Windows Installer a start control.

TIA very much,

Chad Harris

 

[Chad Harris]

Mary--

As usual if I can get you to respond on the setup errors that keep on comin'
with Office 2003 or any other app I learn and have good luck. I have seen
the MSFT Event Viewer web casts and that KB and read Event Viewer Help.
Unfortunately, ayk, MSFT has chosen to be at a primitive stage in conveying
error help particularly with respect to Office. Often the KBs on setup
errors are ridiculously sparse or narrowly pointed at a special set of
circumstances. The OCA website does nothing except to take up cyberspace
now although there are plans possibly around the time of Longhorn OS and
Longhorn server to make it useful that get mentioned at meetings.

I was referring to the fact that a high percent of error messages in Event
Viewer are written in HEX which either Power Users or supermarket checkout
line companions can't use, or Hungarian notation or a language not meant for
the average Office or Windows user and I'm not sure every code head would
have tools to deal with the Hex.

I also think MSFT has a real failure in their Beta testing and bug vetting
of Office setup errors and whoever is the Office setup team for service
packs and Office in general needs to rethink every piece of code they write.
Look at the multiple problems all over since yesterday of people trying to
get in MOS 03 SP1. They should pull it until they fix the systemic bugs in
that setup--they are wasting a lot of people's time. Of course many people
are going to reach for Office SP! and they are in for a bumpy ride full of
setup errors of all shapes and sizes.

That said, you helped me. I'm not sure why all of a sudden many of my
installs have to have the Source Engine on and running because it doesn't
default to on on many of my boxes, so you have to check to make sure it's on
for some but not all Office hotfix installs to be successul.

I uninstalled Adobe 6, whose plugins I had trimmed greatly since I wasn't
going to use almost all of them and reinstalled it and also got the Updates
once I could find the folders because Adobe has learned from Redmond part of
the fun with software is to make a little Raiders of the Lost Ark game out
of finding the folders and files you have installed to make the Reader
updates run.

One of the cute little tricks Adobe has with respect to the Reader--I don't
think it happens in Adobe Acrobat or many other illustration apps like
Photoshop, ect. is to put a big 6.0 when it loads making you think you
didn't update, until you read the fine print and realize you have. Finding
updates for Reader on their site is also on the byzantine end of the
spectrum. Could I make what I just criticized easier??? Anyone could in a
NY heartbeat.

I plan to trim the plug-ins 90% with the plug-in trimmer I have for Adobe
when I get a chance.

Thanks for always being willing to help an being an excellent source of
useful KBs--and for the KB on the Office source engine. That situation
probably occurs not infrequently. I wish there were a way to know when it
had to be on so I guess the answer there is to let it start automatically.
I like to keep every service off I can to protect CPU--if I don't have
Outlook open, then I shut off the two out of three services ass. with BCM
(SQL) that are needed for BCM to open only and nothing else but show up as
processes at the trough in TM.

Best,

Chad Harris

 

[Chad Harris]

Mary--

As usual if I can get you to respond on the setup errors that keep on comin'
with Office 2003 or any other app I learn and have good luck. I have seen
the MSFT Event Viewer web casts and that KB and read Event Viewer Help.
Unfortunately, ayk, MSFT has chosen to be at a primitive stage in conveying
error help particularly with respect to Office. Often the KBs on setup
errors are ridiculously sparse or narrowly pointed at a special set of
circumstances. The OCA website does nothing except to take up cyberspace
now although there are plans possibly around the time of Longhorn OS and
Longhorn server to make it useful that get mentioned at meetings.

I was referring to the fact that a high percent of error messages in Event
Viewer are written in HEX which either Power Users or supermarket checkout
line companions can't use, or Hungarian notation or a language not meant for
the average Office or Windows user and I'm not sure every code head would
have tools to deal with the Hex.

I also think MSFT has a real failure in their Beta testing and bug vetting
of Office setup errors and whoever is the Office setup team for service
packs and Office in general needs to rethink every piece of code they write.
Look at the multiple problems all over since yesterday of people trying to
get in MOS 03 SP1. They should pull it until they fix the systemic bugs in
that setup--they are wasting a lot of people's time. Of course many people
are going to reach for Office SP! and they are in for a bumpy ride full of
setup errors of all shapes and sizes.

That said, you helped me. I'm not sure why all of a sudden many of my
installs have to have the Source Engine on and running because it doesn't
default to on on many of my boxes, so you have to check to make sure it's on
for some but not all Office hotfix installs to be successul.

I uninstalled Adobe 6, whose plugins I had trimmed greatly since I wasn't
going to use almost all of them and reinstalled it and also got the Updates
once I could find the folders because Adobe has learned from Redmond part of
the fun with software is to make a little Raiders of the Lost Ark game out
of finding the folders and files you have installed to make the Reader
updates run.

One of the cute little tricks Adobe has with respect to the Reader--I don't
think it happens in Adobe Acrobat or many other illustration apps like
Photoshop, ect. is to put a big 6.0 when it loads making you think you
didn't update, until you read the fine print and realize you have. Finding
updates for Reader on their site is also on the byzantine end of the
spectrum. Could I make what I just criticized easier??? Anyone could in a
NY heartbeat.

I plan to trim the plug-ins 90% with the plug-in trimmer I have for Adobe
when I get a chance.

Thanks for always being willing to help an being an excellent source of
useful KBs--and for the KB on the Office source engine. That situation
probably occurs not infrequently. I wish there were a way to know when it
had to be on so I guess the answer there is to let it start automatically.
I like to keep every service off I can to protect CPU--if I don't have
Outlook open, then I shut off the two out of three services ass. with BCM
(SQL) that are needed for BCM to open only and nothing else but show up as
processes at the trough in TM.

Best,

Chad Harris

 

[Chad Harris]

Mary--

As usual if I can get you to respond on the setup errors that keep on comin'
with Office 2003 or any other app I learn and have good luck. I have seen
the MSFT Event Viewer web casts and that KB and read Event Viewer Help.
Unfortunately, ayk, MSFT has chosen to be at a primitive stage in conveying
error help particularly with respect to Office. Often the KBs on setup
errors are ridiculously sparse or narrowly pointed at a special set of
circumstances. The OCA website does nothing except to take up cyberspace
now although there are plans possibly around the time of Longhorn OS and
Longhorn server to make it useful that get mentioned at meetings.

I was referring to the fact that a high percent of error messages in Event
Viewer are written in HEX which either Power Users or supermarket checkout
line companions can't use, or Hungarian notation or a language not meant for
the average Office or Windows user and I'm not sure every code head would
have tools to deal with the Hex.

I also think MSFT has a real failure in their Beta testing and bug vetting
of Office setup errors and whoever is the Office setup team for service
packs and Office in general needs to rethink every piece of code they write.
Look at the multiple problems all over since yesterday of people trying to
get in MOS 03 SP1. They should pull it until they fix the systemic bugs in
that setup--they are wasting a lot of people's time. Of course many people
are going to reach for Office SP! and they are in for a bumpy ride full of
setup errors of all shapes and sizes.

That said, you helped me. I'm not sure why all of a sudden many of my
installs have to have the Source Engine on and running because it doesn't
default to on on many of my boxes, so you have to check to make sure it's on
for some but not all Office hotfix installs to be successul.

I uninstalled Adobe 6, whose plugins I had trimmed greatly since I wasn't
going to use almost all of them and reinstalled it and also got the Updates
once I could find the folders because Adobe has learned from Redmond part of
the fun with software is to make a little Raiders of the Lost Ark game out
of finding the folders and files you have installed to make the Reader
updates run.

One of the cute little tricks Adobe has with respect to the Reader--I don't
think it happens in Adobe Acrobat or many other illustration apps like
Photoshop, ect. is to put a big 6.0 when it loads making you think you
didn't update, until you read the fine print and realize you have. Finding
updates for Reader on their site is also on the byzantine end of the
spectrum. Could I make what I just criticized easier??? Anyone could in a
NY heartbeat.

I plan to trim the plug-ins 90% with the plug-in trimmer I have for Adobe
when I get a chance.

Thanks for always being willing to help an being an excellent source of
useful KBs--and for the KB on the Office source engine. That situation
probably occurs not infrequently. I wish there were a way to know when it
had to be on so I guess the answer there is to let it start automatically.
I like to keep every service off I can to protect CPU--if I don't have
Outlook open, then I shut off the two out of three services ass. with BCM
(SQL) that are needed for BCM to open only and nothing else but show up as
processes at the trough in TM.

Best,

Chad Harris

 

[Chad Harris]

Mary--

As usual if I can get you to respond on the setup errors that keep on comin'
with Office 2003 or any other app I learn and have good luck. I have seen
the MSFT Event Viewer web casts and that KB and read Event Viewer Help.
Unfortunately, ayk, MSFT has chosen to be at a primitive stage in conveying
error help particularly with respect to Office. Often the KBs on setup
errors are ridiculously sparse or narrowly pointed at a special set of
circumstances. The OCA website does nothing except to take up cyberspace
now although there are plans possibly around the time of Longhorn OS and
Longhorn server to make it useful that get mentioned at meetings.

I was referring to the fact that a high percent of error messages in Event
Viewer are written in HEX which either Power Users or supermarket checkout
line companions can't use, or Hungarian notation or a language not meant for
the average Office or Windows user and I'm not sure every code head would
have tools to deal with the Hex.

I also think MSFT has a real failure in their Beta testing and bug vetting
of Office setup errors and whoever is the Office setup team for service
packs and Office in general needs to rethink every piece of code they write.
Look at the multiple problems all over since yesterday of people trying to
get in MOS 03 SP1. They should pull it until they fix the systemic bugs in
that setup--they are wasting a lot of people's time. Of course many people
are going to reach for Office SP! and they are in for a bumpy ride full of
setup errors of all shapes and sizes.

That said, you helped me. I'm not sure why all of a sudden many of my
installs have to have the Source Engine on and running because it doesn't
default to on on many of my boxes, so you have to check to make sure it's on
for some but not all Office hotfix installs to be successul.

I uninstalled Adobe 6, whose plugins I had trimmed greatly since I wasn't
going to use almost all of them and reinstalled it and also got the Updates
once I could find the folders because Adobe has learned from Redmond part of
the fun with software is to make a little Raiders of the Lost Ark game out
of finding the folders and files you have installed to make the Reader
updates run.

One of the cute little tricks Adobe has with respect to the Reader--I don't
think it happens in Adobe Acrobat or many other illustration apps like
Photoshop, ect. is to put a big 6.0 when it loads making you think you
didn't update, until you read the fine print and realize you have. Finding
updates for Reader on their site is also on the byzantine end of the
spectrum. Could I make what I just criticized easier??? Anyone could in a
NY heartbeat.

I plan to trim the plug-ins 90% with the plug-in trimmer I have for Adobe
when I get a chance.

Thanks for always being willing to help an being an excellent source of
useful KBs--and for the KB on the Office source engine. That situation
probably occurs not infrequently. I wish there were a way to know when it
had to be on so I guess the answer there is to let it start automatically.
I like to keep every service off I can to protect CPU--if I don't have
Outlook open, then I shut off the two out of three services ass. with BCM
(SQL) that are needed for BCM to open only and nothing else but show up as
processes at the trough in TM.

Best,

Chad Harris

 

[Chad Harris]

Mary--

As usual if I can get you to respond on the setup errors that keep on comin'
with Office 2003 or any other app I learn and have good luck. I have seen
the MSFT Event Viewer web casts and that KB and read Event Viewer Help.
Unfortunately, ayk, MSFT has chosen to be at a primitive stage in conveying
error help particularly with respect to Office. Often the KBs on setup
errors are ridiculously sparse or narrowly pointed at a special set of
circumstances. The OCA website does nothing except to take up cyberspace
now although there are plans possibly around the time of Longhorn OS and
Longhorn server to make it useful that get mentioned at meetings.

I was referring to the fact that a high percent of error messages in Event
Viewer are written in HEX which either Power Users or supermarket checkout
line companions can't use, or Hungarian notation or a language not meant for
the average Office or Windows user and I'm not sure every code head would
have tools to deal with the Hex.

I also think MSFT has a real failure in their Beta testing and bug vetting
of Office setup errors and whoever is the Office setup team for service
packs and Office in general needs to rethink every piece of code they write.
Look at the multiple problems all over since yesterday of people trying to
get in MOS 03 SP1. They should pull it until they fix the systemic bugs in
that setup--they are wasting a lot of people's time. Of course many people
are going to reach for Office SP! and they are in for a bumpy ride full of
setup errors of all shapes and sizes.

That said, you helped me. I'm not sure why all of a sudden many of my
installs have to have the Source Engine on and running because it doesn't
default to on on many of my boxes, so you have to check to make sure it's on
for some but not all Office hotfix installs to be successul.

I uninstalled Adobe 6, whose plugins I had trimmed greatly since I wasn't
going to use almost all of them and reinstalled it and also got the Updates
once I could find the folders because Adobe has learned from Redmond part of
the fun with software is to make a little Raiders of the Lost Ark game out
of finding the folders and files you have installed to make the Reader
updates run.

One of the cute little tricks Adobe has with respect to the Reader--I don't
think it happens in Adobe Acrobat or many other illustration apps like
Photoshop, ect. is to put a big 6.0 when it loads making you think you
didn't update, until you read the fine print and realize you have. Finding
updates for Reader on their site is also on the byzantine end of the
spectrum. Could I make what I just criticized easier??? Anyone could in a
NY heartbeat.

I plan to trim the plug-ins 90% with the plug-in trimmer I have for Adobe
when I get a chance.

Thanks for always being willing to help an being an excellent source of
useful KBs--and for the KB on the Office source engine. That situation
probably occurs not infrequently. I wish there were a way to know when it
had to be on so I guess the answer there is to let it start automatically.
I like to keep every service off I can to protect CPU--if I don't have
Outlook open, then I shut off the two out of three services ass. with BCM
(SQL) that are needed for BCM to open only and nothing else but show up as
processes at the trough in TM.

Best,

Chad Harris

 

[Chad Harris]

Mary--

As usual if I can get you to respond on the setup errors that keep on comin'
with Office 2003 or any other app I learn and have good luck. I have seen
the MSFT Event Viewer web casts and that KB and read Event Viewer Help.
Unfortunately, ayk, MSFT has chosen to be at a primitive stage in conveying
error help particularly with respect to Office. Often the KBs on setup
errors are ridiculously sparse or narrowly pointed at a special set of
circumstances. The OCA website does nothing except to take up cyberspace
now although there are plans possibly around the time of Longhorn OS and
Longhorn server to make it useful that get mentioned at meetings.

I was referring to the fact that a high percent of error messages in Event
Viewer are written in HEX which either Power Users or supermarket checkout
line companions can't use, or Hungarian notation or a language not meant for
the average Office or Windows user and I'm not sure every code head would
have tools to deal with the Hex.

I also think MSFT has a real failure in their Beta testing and bug vetting
of Office setup errors and whoever is the Office setup team for service
packs and Office in general needs to rethink every piece of code they write.
Look at the multiple problems all over since yesterday of people trying to
get in MOS 03 SP1. They should pull it until they fix the systemic bugs in
that setup--they are wasting a lot of people's time. Of course many people
are going to reach for Office SP! and they are in for a bumpy ride full of
setup errors of all shapes and sizes.

That said, you helped me. I'm not sure why all of a sudden many of my
installs have to have the Source Engine on and running because it doesn't
default to on on many of my boxes, so you have to check to make sure it's on
for some but not all Office hotfix installs to be successul.

I uninstalled Adobe 6, whose plugins I had trimmed greatly since I wasn't
going to use almost all of them and reinstalled it and also got the Updates
once I could find the folders because Adobe has learned from Redmond part of
the fun with software is to make a little Raiders of the Lost Ark game out
of finding the folders and files you have installed to make the Reader
updates run.

One of the cute little tricks Adobe has with respect to the Reader--I don't
think it happens in Adobe Acrobat or many other illustration apps like
Photoshop, ect. is to put a big 6.0 when it loads making you think you
didn't update, until you read the fine print and realize you have. Finding
updates for Reader on their site is also on the byzantine end of the
spectrum. Could I make what I just criticized easier??? Anyone could in a
NY heartbeat.

I plan to trim the plug-ins 90% with the plug-in trimmer I have for Adobe
when I get a chance.

Thanks for always being willing to help an being an excellent source of
useful KBs--and for the KB on the Office source engine. That situation
probably occurs not infrequently. I wish there were a way to know when it
had to be on so I guess the answer there is to let it start automatically.
I like to keep every service off I can to protect CPU--if I don't have
Outlook open, then I shut off the two out of three services ass. with BCM
(SQL) that are needed for BCM to open only and nothing else but show up as
processes at the trough in TM.

Best,

Chad Harris

 

[Chad Harris]

Mary--

As usual if I can get you to respond on the setup errors that keep on comin'
with Office 2003 or any other app I learn and have good luck. I have seen
the MSFT Event Viewer web casts and that KB and read Event Viewer Help.
Unfortunately, ayk, MSFT has chosen to be at a primitive stage in conveying
error help particularly with respect to Office. Often the KBs on setup
errors are ridiculously sparse or narrowly pointed at a special set of
circumstances. The OCA website does nothing except to take up cyberspace
now although there are plans possibly around the time of Longhorn OS and
Longhorn server to make it useful that get mentioned at meetings.

I was referring to the fact that a high percent of error messages in Event
Viewer are written in HEX which either Power Users or supermarket checkout
line companions can't use, or Hungarian notation or a language not meant for
the average Office or Windows user and I'm not sure every code head would
have tools to deal with the Hex.

I also think MSFT has a real failure in their Beta testing and bug vetting
of Office setup errors and whoever is the Office setup team for service
packs and Office in general needs to rethink every piece of code they write.
Look at the multiple problems all over since yesterday of people trying to
get in MOS 03 SP1. They should pull it until they fix the systemic bugs in
that setup--they are wasting a lot of people's time. Of course many people
are going to reach for Office SP! and they are in for a bumpy ride full of
setup errors of all shapes and sizes.

That said, you helped me. I'm not sure why all of a sudden many of my
installs have to have the Source Engine on and running because it doesn't
default to on on many of my boxes, so you have to check to make sure it's on
for some but not all Office hotfix installs to be successul.

I uninstalled Adobe 6, whose plugins I had trimmed greatly since I wasn't
going to use almost all of them and reinstalled it and also got the Updates
once I could find the folders because Adobe has learned from Redmond part of
the fun with software is to make a little Raiders of the Lost Ark game out
of finding the folders and files you have installed to make the Reader
updates run.

One of the cute little tricks Adobe has with respect to the Reader--I don't
think it happens in Adobe Acrobat or many other illustration apps like
Photoshop, ect. is to put a big 6.0 when it loads making you think you
didn't update, until you read the fine print and realize you have. Finding
updates for Reader on their site is also on the byzantine end of the
spectrum. Could I make what I just criticized easier??? Anyone could in a
NY heartbeat.

I plan to trim the plug-ins 90% with the plug-in trimmer I have for Adobe
when I get a chance.

Thanks for always being willing to help an being an excellent source of
useful KBs--and for the KB on the Office source engine. That situation
probably occurs not infrequently. I wish there were a way to know when it
had to be on so I guess the answer there is to let it start automatically.
I like to keep every service off I can to protect CPU--if I don't have
Outlook open, then I shut off the two out of three services ass. with BCM
(SQL) that are needed for BCM to open only and nothing else but show up as
processes at the trough in TM.

Best,

Chad Harris