0x80070002 error when running LISTool

Seven Office 2003 updates are failing to install on this system with a 0x52F
error code. Troubleshooting led me to download and run the LISTool.
However, after extracting the two files and trying to run the tool I receive
a 0x80070002 error. I've been unable to find any information related to this
error. HELP!!!

RochSenCompSem wrote:

> Seven Office 2003 updates are failing to install on this system with a 0x52F
> error code. Troubleshooting led me to download and run the LISTool.
> However, after extracting the two files and trying to run the tool I receive
> a 0x80070002 error. I've been unable to find any information related to this
> error. HELP!!!

How to troubleshoot an update installation by using log files in Office 2003
http://support.microsoft.com/kb/884290

Or, since most of the updates are security-related:

> How to obtain help and support for this security update
> For home users, no-charge support is available by calling 1-866-PCSAFETY in the United States and
> Canada or by contacting your local Microsoft subsidiary. For more information about how to contact
> your local Microsoft subsidiary for support issues with security updates,
visit the Microsoft
> International Support Web site:
> http://support.microsoft.com/common/....aspx?rdpath=4
> North American customers can also obtain instant access to unlimited no-charge e-mail support or to
> unlimited individual chat support by visiting the following Microsoft Web site:
> http://support.microsoft.com/oas/def...spx?&prid=7552


MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============

Thanks for the reply MowGreen but I'm looking for a solution to the error
with the LISTool function. This is a tool that is supposed to resolve
problems with the Local Installation Source (LIS) location but when the tool
itself fails, there's not much that can be done. I know I can resolve my
original problem by uninstalling Office and then reinstalling it but I'd like
to see the owner of the LISTool function step forward and resolve the problem
with the tool itself. That's why I made the subject of this discussion the
LISTool rather than the original problem of not being able to install some
Office 2003 updates.
>

RochSenCompSem wrote:

> Thanks for the reply MowGreen but I'm looking for a solution to the error
> with the LISTool function. This is a tool that is supposed to resolve
> problems with the Local Installation Source (LIS) location but when the tool
> itself fails, there's not much that can be done. I know I can resolve my
> original problem by uninstalling Office and then reinstalling it but I'd like
> to see the owner of the LISTool function step forward and resolve the problem
> with the tool itself. That's why I made the subject of this discussion the
> LISTool rather than the original problem of not being able to install some
> Office 2003 updates.
>

0x80070002 The system cannot find the file specified.

" Overview
The Local Installation Source Tool is a wizard to help manage your Local
Installation Source (LIS) on computers running Microsoft Office 2003.
The LIS Tool allows you to enable or disable LIS, and to move the
MsoCache folder to a new volume. This download is intended for use by
customers and network administrators with LIS issues who contact
Microsoft Product Support Services. "

I haven't run LISTool but I *think* it won't help if the MSOCache folder
doesn't contain the installation source files required in order for
updates to install. That's what the error may be referring to.

Still suggest you contact MS for no-charge support in getting the
Security updates installed and see if they recommend the use of LISTool.

I *highly* doubt the owner of LISTool ever frequents MS newsgroups.

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============

I've submitted an incident report (1076747859) for this problem. I'll post
the results of the fix when MS gets it resolved.

RochSenCompSem wrote:

> I've submitted an incident report (1076747859) for this problem. I'll post
> the results of the fix when MS gets it resolved.
>

Thanks, will be looking forward to finding out what's causing the error
code when running the tool.

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============

I submitted the incident report, got it rerouted twice and finally got a new
incident report (SRX1077386702ID). The tech tried many different fixes
(Windows Installer, Repair, etc) but nothing worked. Finally had to
uninstall Office, then reinstall and the updates went on successfully.
Luckily "?", the LIStool is still failing with the same error code. The tech
told me to send an email to his manager, letting him know that I still want
to pursue the problem with the LIStool. Still waiting to hear back from the
manager.


"RochSenCompSem" wrote:

> I've submitted an incident report (1076747859) for this problem. I'll post
> the results of the fix when MS gets it resolved.
>

Thanks for keeping the group updated on this. It doesn't make much sense
to recommend the tool if running it throws an error code.
I wonder which file is missing that is causing the error ?


MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============



RochSenCompSem wrote:

> I submitted the incident report, got it rerouted twice and finally got a new
> incident report (SRX1077386702ID). The tech tried many different fixes
> (Windows Installer, Repair, etc) but nothing worked. Finally had to
> uninstall Office, then reinstall and the updates went on successfully.
> Luckily "?", the LIStool is still failing with the same error code. The tech
> told me to send an email to his manager, letting him know that I still want
> to pursue the problem with the LIStool. Still waiting to hear back from the
> manager.
>
>
> "RochSenCompSem" wrote:
>
>
>>I've submitted an incident report (1076747859) for this problem. I'll post
>>the results of the fix when MS gets it resolved.
>>

"MowGreen [MVP]" <> wrote in message
news:%...
> Thanks for keeping the group updated on this. It doesn't make much sense
> to recommend the tool if running it throws an error code.

> I wonder which file is missing that is causing the error ?


Two fairly simple ways to try to find out:
1. Run... FileMon (or ProcMon) to capture the file accesses the tool use generates.
2. Execute the listool.exe (with whatever command line parameters it needs)
under Dependency Walker (using its Profiling feature.) That could show
the exact call which produced the error which could be more useful by being
more informative, especially if Symbols were provided... ; )

Of course there may also be other diagnostics produced to supplement the
error code, maybe even in the Event Viewer's Application log, is he's lucky.
To find any other diagnostics he could just search his harddrive(s) for any
changes made that day at that time. But running ProcMon could expose
those too, e.g. filtering on WRITE.


; )

Robert
---

Robert Aldwinckle wrote:

> "MowGreen [MVP]" <> wrote in message
> news:%...
>
>>Thanks for keeping the group updated on this. It doesn't make much sense
>>to recommend the tool if running it throws an error code.
>
>
>>I wonder which file is missing that is causing the error ?
>
>
>
> Two fairly simple ways to try to find out:
> 1. Run... FileMon (or ProcMon) to capture the file accesses the tool use generates.
> 2. Execute the listool.exe (with whatever command line parameters it needs)
> under Dependency Walker (using its Profiling feature.) That could show
> the exact call which produced the error which could be more useful by being
> more informative, especially if Symbols were provided... ; )
>
> Of course there may also be other diagnostics produced to supplement the
> error code, maybe even in the Event Viewer's Application log, is he's lucky.
> To find any other diagnostics he could just search his harddrive(s) for any
> changes made that day at that time. But running ProcMon could expose
> those too, e.g. filtering on WRITE.
>
>
> ; )
>
> Robert
> ---
>
>

Hi Robert ... Maybe we should recommend those tools to PSS/CSS since
they also have no clue as to why the error is being thrown <eg>

"RochSenCompSem" wrote:

> The tech tried many different fixes
> (Windows Installer, Repair, etc) but nothing worked. Finally had to
> uninstall Office, then reinstall and the updates went on successfully.
> Luckily "?", the LIStool is still failing with the same error code.
> The tech told me to send an email to his manager, letting him know that I still want
> to pursue the problem with the LIStool. Still waiting to hear back from the
> manager.


MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============