Nick--
You may get some additional information at Event Viewer, but odds are it
will be similar and possibly some hex errors or errors written in "Hungarian
notation" not to be confused with the language from Hungary, or some other
language used and I doubt it in this case.
It would be helpful to know what OS (build of XP--SP1 SP2 ect.) you're
running and what application you're trying to update. You didn't say. If
you have Windows XP then upgrading to at least SP1 might help.
*A good first response to any error like this in XP* besides trying to
track the errors down with google or a search engine is to run System File
Checker and try to replace .dlls or files that are damaged with intact files
that are stored as replacements. That might help.
Running SFC would be the first thing I would try given your situation. No
downside and it might restore a missing file or files you need.
http://tinyurl.com/lc0l
Description of the Windows File Protection Feature
Introduction to using scannow sfc (system file checker)
http://www.updatexp.com/scannow-sfc.html
(One of the best articles I have on SFC)
This KB does not name your error messages, but it has more than one way you
might repair your installer. I have not drilled the Install Shield site's
KB because you indicated you have done this.
http://support.microsoft.com/default.aspx?scid=kb;[LN];315346
"Error 1719. The Windows Installer service could not be accessed" error
message when you try to add or remove a program
This has *ways to repair your MSI* although you did not get Error 1719--I
used it in a situation described below when I was gettting different setup
errors for Office.
You may try using this if previous updates of your application are listed to
get rid of files that might not have installed correctly in relation to that
application (previous updates for that particular app is what I mean here).
Windows Installer Cleanup Utility
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301
___________________________________________________________________
There are KBs close to your topic:
http://support.microsoft.com/?id=818234
"Error 1311: Cannot Locate Source File" Error Message During Office
Installation
http://tinyurl.com/5j7an
on Error Code 1603
http://www.rz.fh-ulm.de/rz/docs/msierror.htm
MSI Error Codes
http://support.microsoft.com/default.aspx?scid=kb;EN-US;229683
List of Error Codes Including 1603
http://www.jsiinc.com/SUBP/tip7700/rh7732.htm
JSI Tip on 1603
The last 1603 error I had to contend with was an Office installation error
because I used an app I picked up from the net to get rid of wisptis.exe
which MSFT ridiculously default installs with every Office or Office related
app as does Adobe with their reader. It's to facilitate the pen in a tablet,
and to my knowledge not every Office user is working with a tablet
today--I'd safely say the vast majority of Office deployments, One Note
deployments, Front Page Deployments aren't on boxes using a tablet pen.
Why isn't wisptis.exe an optional install at the MSFT Office site? Good
question.
Why did I want to remove wisptis.exe in the first place--it mimes spyware
and can cause systained CPU runs of 100% which manifest with the symptom of
a freeze for varying amounts of time for a number of users.
hth,
Chad Harris
_________________________________________________________________________________________________________
