Re: MOS 2003 SP1 - Does NOT install--What's in Event Viewer/App with MSI Source?????
From: Sloan Crayton [MS] (sloanc_at_online.microsoft.com)
Date: 08/01/04
- Next message: Sloan Crayton [MS]: "Re: Can't install Office 2003 SP1 --The Cleanup Utility"
- Previous message: Chad Harris: "Re: MOS 2003 SP1 - Does NOT install--More Install Hints/References"
- Next in thread: Admin: "Re: MOS 2003 SP1 - Does NOT install--What's in Event Viewer/App with MSI Source?????"
- Reply: Admin: "Re: MOS 2003 SP1 - Does NOT install--What's in Event Viewer/App with MSI Source?????"
- Reply: Admin: "Re: MOS 2003 SP1 - Does NOT install--What's in Event Viewer/App with MSI Source?????"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 1 Aug 2004 15:10:06 -0700
Is there an error when Office Update attempts to scan your configuration?
If so, what is that error?
Sloan Crayton
Microsoft
"Admin" <Net*man@yahoo.com> wrote in message
news:0aing0172emds9q65ilrh507vm4fvgu4jv@4ax.com...
> Hi Chad:
>
> There were some error messages in the 'event log', unfortunately I had
> not looked at this log for a while and the log had gotten pretty long
> so, after I posted the verbose logs I deleted the event log, thinking
> it is less meaningful than the specific logs that I posted because
> every time I have followed the link in the event log entry to find
> more info, I have never found anything.
>
> Interestingly, AFTER I have run the Installer cleaner and removed the
> remnants of previous Office (Office XP) installation, the behavior of
> Office 2003 SP1 installer has changed altogether, now the website is
> UNable to scan my Office installation for any need for an update,
> before, it would identify the SP1 and try to install it although
> unsuccessfully.
>
> The same is true about running the downloaded SP1 files ( the Client
> file AND the Full file). Now if I run either of the SP1 package, it
> does not appear to do much except for generating an error message that
> it also wants to send to Microsoft. Before, it would proceed through
> the step of gathering info of the current installation and then fail.
>
> Thanks for your detailed responses.
>
> Matt
> ================================================
>
>
> On Sat, 31 Jul 2004 02:23:44 -0400, "Chad Harris"
> <ddram32_nospam@yahoo.com> wrote:
>
>>Matt--
>>
>>1) I should correct one thing I said. Safe Mode is not an option that
>>will
>>be helpful for the install, because Safe Mode as far as I know does *not*
>>load/access the Windows Installer.
>>
>>2) I want to push on "no error message was encountered"--I saw a number of
>>failed installs of this on different boxes for some different reasons
>>since
>>the 7/27 release of MOS 03 SP1--but I haven't seen any without anxillary
>>useful info in Event Viewer!!!
>>
>> There should be several messages in the Applications section of Event
>>Viewer that can be helpful. During my problem, the box on the desktop
>>that
>>Office gives you was a simple superficial statement of one of my errors.
>>Now that I know what happened, I can use Event Viewer info to put it all
>>together, and in many cases it tells you what KB to consult or which of
>>the
>>tools Rohit referenced might be the appropriate one(s).
>>Please put "eventvwr.msc" in your run box and stretch that puppy out and
>>go
>>to Application and tell me if you see errors that will be labled
>>MSIInstaller under "Source." Click on these and go up and down and you'll
>>have some errors.
>>
>>3) Did you try installing with the *Full installation package--the one on
>>the bottom* that is on the download webpage? The reasoning there is that
>>even if you do have your CD handy, it may supply set up folders that you
>>may
>>need to get the install done, that the enu.exe may not supply. It worked
>>for me like a charm, and has been working for others--and it is one of the
>>"troubleshooting moves" that the Scanning for Updates wizard mentions.
>>
>>http://tinyurl.com/44x62
>>Office 2003 Service Pack 1
>>
>>Files in this Download
>>Below are links to the separate files available for this download.
>>
>> File Name:
>> File Size
>>
>> Office2003SP1-kb842532-client-enu.exe
>> 18396 KB
>>
>> Office2003SP1-kb842532-fullfile-enu.exe
>> 73906 KB
>>
>>
>>
>>4) I appreciate the log you posted, but as you know, special tools are
>>needed to interpret that log. Some of the engineers or developers that
>>monitor this site with Rohit, from MSFT or others have access to them.
>>
>>5) This brings up one of my strongest criticisms-- that MSFT has abdicated
>>a
>>format to convey meaningful error messages in logs and sometimes in Event
>>Viewer for all but a small population of users. Those home users gathered
>>around the Windows Media Center that I saw Jim Alchin on Tech TV promoting
>>aren't speaking in Hex or Hungarian Notation and don't have tools and
>>training to interpret those messages. They are for MSFT, MSFT will say.
>>Fine. We are all for MSFT having the data it needs to improve things on
>>the
>>fly and in the future, but MSFT has hugely abdicated getting useful
>>information on many errors that don't link to clear MSKBs or other KBs or
>>don't readily lend themselves to web searching for info. I think it's
>>time
>>for them to pull some of the ranks back from the SP2 security bandwagon
>>and
>>put some of them on a feature that can convey meaningful info on what
>>steps
>>to take and tools to use. But that's just my opinion.
>>
>>5) As far as multiple versions of Office, there are KBs for both Office XP
>>and Office 2003 and plenty of people run them quite successfully although
>>the official party line in a KB may be that it's not preferred. There
>>are
>>good reasons for some people to do it, but the caveat is to install the
>>oldest version first, because of backwards compatibility issues.
>>
>>6) I'm not trained or don't have the tools to deal with this error data,
>>but
>>some people who monitor this group are. However, if you find numbered
>>errors in Event Viewer's Application Section like for example a 1603 Error
>>and paste what it says--they will not be long--I can go after useful
>>information on those. Mine had an error that referenced the Hotfix Logs
>>in
>>temporary files like the one you put up, but I had no where to go to do
>>anything with that. The Resource kit has some useful tools, and they
>>continue to grow, but many of us need some contexting for those tools and
>>I'll bet Rohit appreciates that as well. I'm just getting acquainted
>>with
>>LIS myself, but I didn't have to use it. There are several resource kit
>>tools that I've been reading about but not used so there are much better
>>people to help with those.
>>
>>
>>
>>7)Microsoft's Convergys phone support as a rule doesn't have the means to
>>deal with it--many of them don't even know what those temporary file
>>hotfix
>>logs are or that they exist--although some do so you'd be playing phone
>>roulette there. There needs to be some continuing education from MSFT for
>>them and quality control monitoring doesn't seem to exist. It seems that
>>only their more senior tech support people have access to tools to analyze
>>them. MSFT--that company in Redmond who has Convergys providing their
>>phone support is another story. But you aren't talking to MSFT when home
>>users and small business call for Tech Support. Most of your calls are
>>channelled to Bangelore or New Delhi India or Nova Scotia Canada and
>>you're
>>talking to Convergys. The support is contracted out by MSFT to vendors.
>>
>>8) MSFT are the people that sell the software, but they don't support it
>>very effectively, particularly on the phone. It is very nice of people
>>like Ronit and Sloan to help here, and I appreciate their links and
>>contexting for the Resource Kit installation adjunct tools. Howver, Rohit
>>knows well that Convergys is the phone support beard out in front of MSFT
>>who talks to the public in phone incidents unless that public is
>>enterprise
>>with big bucks multiple licenses or perhaps a partner who has paid a
>>couple
>>grand for special support.
>>
>>Please tell me/paste what Event Viewer's Application errors say as with
>>MSI
>>as a source during the time when you attempt installation. Hopefully
>>someone else can interpret the info you just put up--again I don't have
>>the
>>tools to do that.
>>
>>Best,
>>
>>Chad Harris
>>____________________________________________________
>>
>>
>>"Admin" <Net*man@yahoo.com> wrote in message
>>news:hu2lg090h3bujp2ai3aigerudiqlhru1hs@4ax.com...
>>>
>>> Hi Chad:
>>>
>>> No error message was encountered as such, the only message was "'the
>>> update cannot be applied'.
>>>
>>> After you replied to my posting, I did the following.
>>>
>>> Please see the steps taken and the logs generated as a result.
>>>
>>> -------------------------------------------------------------------------------------------
>>>
>>> I tried running LisTool, it does NOT run returns an eror message :
>>> 0x80070002, Here is the log:
>>>
>>> === Logging started: 2004/07/30 14:03:06 ===
>>> Executable: C:\MSOCache\LISTOOL.EXE v11.0.6353.0
>>> Computer : xyz
>>> --- logging level: standard ---
>>> loglevel not found
>>> logging set to 1
>>> Checked run type
>>> Claimed mutex
>>> User is an admin.
>>> Claimed mutex
>>> Initialization of OSE Succeeded
>>> Initialized OSE
>>> Tool failed to complete because an error occurred: 0x80070002.
>>> === Logging stopped: 2004/07/30 14:05:19 ===
>>> _____________________________________________________
>>>
>>>
>>> Tried running the Office Setup fix tool, it asks for an ini file, I do
>>> not know where it (the ini file) resides. Here is the log:
>>>
>>> Detected Windows Info:
>>> PlatformId = 2
>>> MajorVersion = 5
>>> MinorVersion = 1
>>> ServicePackLevel = 1
>>> - - - - - - - - - - - - - - - - - - - - - - -
>>> Launch Setup
>>> 7/30/04 1:23:53 PM
>>> Setup path: C:\Downloads\SETUP.EXE
>>> Trying to get version of
>>> C:\Downloads\SETUP.EXE
>>> ...succeeded.
>>> C:\Downloads\SETUP.EXE is version 11.0.6176.0
>>> Current version of Setup.exe: 11.0.6176.0
>>> Searching for .INI file: SETUP.INI
>>> C:\Downloads\FILES\SETUP\SETUP.INI
>>> C:\Downloads\SETUP\SETUP.INI
>>> C:\Downloads\SETUP.INI
>>> Invalid settings file contents: C:\Downloads\FILES\SETUP\SETUP.INI
>>> Settings file C:\Downloads\FILES\SETUP\SETUP.INI is missing or
>>> invalid. Please ensure this file exists and is accessible.
>>> Failed to query chaining key for main task name.
>>> Failed to get path to INI file.
>>> GetTempPath returned: C:\DOCUME~1\ADMINI~1.ALT\LOCALS~1\Temp\
>>>
>>> ______________________________________________________________
>>>
>>> I did run the MS installer clean up tool, it did show some remanents
>>> of Office XP Pro with Front Page and Publisher 2002, I removed them.
>>>
>>> Then I tried to run the SP1 install agin, now it does generate an
>>> error message, here is the log:
>>>
>>> Starting the log on 07/30/2004 at 14:10:07...
>>> Loading the resource .dll...
>>> Reading the settings...
>>> The settings are:
>>> IsNormalUpdate=1
>>> AdminUsesShortFilenames=1
>>> AdminPath=""
>>> MessageTitle="Office 2003 Service Pack 1 (SP1)"
>>> CopyFilesToRerun=1
>>> ShowSuccessDialog=1
>>> RebootInQuietMode=0
>>> RunSetupWatson=1
>>> RequireAllPatchesNeeded=0
>>> RequireAllProductsAtMinVersion=0
>>> MinProductVersion=""
>>> MinMsiVersion="2.0"
>>> UpgradeMsi=1
>>> MsiUpgradeURL="http://go.microsoft.com/fwlink/?LinkId=20610"
>>> OHotfixLogLevel="v"
>>> MsiLogLevel="v"
>>> OHotfixUILevel="n"
>>> MsiUILevel="n"
>>> FeatureToCheck=""
>>> Making sure only this instance of the bootstrapper is running...
>>> Making sure the environment is okay for patching...
>>> Getting the patches...
>>> Getting the products to patch...
>>> Seeing if patch
>>> C:\DOCUME~1\ADMINI~1.ALT\LOCALS~1\Temp\IXP000.TMP\MAINSP1op.msp is
>>> needed...
>>> The update failed.
>>> Finished processing the update on 07/30/2004 at 14:10:07.
>>> Encountered error 1612 while updating.
>>> Launching Setup Watson...
>>> Setup Watson manifest file:
>>> C:\DOCUME~1\ADMINI~1.ALT\LOCALS~1\Temp\OHotfix\DW6CD.tmp.
>>> Setup Watson command line: "C:\Program Files\Common Files\Microsoft
>>> Shared\Office10\dw.exe"
>>> -d"C:\DOCUME~1\ADMINI~1.ALT\LOCALS~1\Temp\OHotfix\DW6CD.tmp"
>>> ______________________________________________________________
>>>
>>> Kindly advise as to how to proceed
>>>
>>> Matt
>>>
>>>
>>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
- Next message: Sloan Crayton [MS]: "Re: Can't install Office 2003 SP1 --The Cleanup Utility"
- Previous message: Chad Harris: "Re: MOS 2003 SP1 - Does NOT install--More Install Hints/References"
- Next in thread: Admin: "Re: MOS 2003 SP1 - Does NOT install--What's in Event Viewer/App with MSI Source?????"
- Reply: Admin: "Re: MOS 2003 SP1 - Does NOT install--What's in Event Viewer/App with MSI Source?????"
- Reply: Admin: "Re: MOS 2003 SP1 - Does NOT install--What's in Event Viewer/App with MSI Source?????"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
