Re: Is a solution to the Failed to connect to server/Answer for Sloan
From: Sloan Crayton [MS] (sloanc_at_online.microsoft.com)
Date: 08/08/04
- Next message: Sloan Crayton [MS]: "Re: SP1 Cannot be applied / Installation failed - My fix"
- Previous message: Sloan Crayton [MS]: "Re: Office 2003"
- In reply to: Chad Harris: "Re: Is a solution to the Failed to connect to server/Answer for Sloan"
- Next in thread: Chad Harris: "Re: Is a solution to the Failed to connect to server/Answer for Sloan"
- Reply: Chad Harris: "Re: Is a solution to the Failed to connect to server/Answer for Sloan"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 7 Aug 2004 21:08:30 -0700
I'm afraid that I'm not knowledgeable about Outlook with BCM to be helpful.
I suggest posting that question in one of the Outlook newsgroups.
Sloan Crayton
Microsoft
"Chad Harris" <ddram32_nospam@yahoo.com> wrote in message
news:uXTNWn3eEHA.1724@TK2MSFTNGP10.phx.gbl...
> Sloan--
>
> Actually, *none* of the errors I showed you are during patching. I will
> paste the errors that I had when I couldn't get Office SP1 in (the other
> Office updates released including One Note on 7/27 went in without a
> hitch). These are the repeated install errors I had when I tried to get
> MOS 2004 SP1 in--the ones below are the ones I get when I open up OL and
> Word--but OL and Word work just fine so I don't know how to context those
> errors.
>
> The only patching errors I got were the install problem errors I got with
> only MOS 2003 SP1 were--I understand from you Log Files are not generated
> when you install from Office Update but until I used the full file, I was
> getting these guys below no matter which place I installed from--the
> download page or Office Update:
>
> Error 1336. There was an error creating a temporary file that is needed to
> complete this installation. Folder: C:\Config.Msi\. System error code: 267
> Product: Microsoft Office Professional Edition 2003 - Update 'Office 2003
> Service Pack 1' could not be installed. Error code 1603. Additional
> information is available in the log file
> C:\DOCUME~1\LOCALS~1\Temp\OHotfix\OHotfix(00010)_Msi.log.
>
> Failed to connect to server. Error: 0x800401F0
>
> They occur cyclically (trying that as an adverb and spelling it at the
> same time makes me a little nervous, but even if I were wrong, it
> wouldn't have stopped me from making it up) and consistently when I
> *open up Word or Outlook*using "Wordmail" as the editor for messages. I
> don't get them at each instance of firing up Word or Outlook or Outlook
> and Wordmail. I just opened Word--it said I had recovered from a serious
> error--and if I open up Outlook with BCM and don't start the correct 3
> services that have SQL relationships to the MSDE then I'll get that kind
> of error the next time I open Word--do I want to disable the add-in with
> nothing corresponding to this in event viewer. I'm used to that and it
> only happens if I tried to Open OL with BCM and forget to give BCM the
> required services. I don't keep them on when OL is fired up because I
> don't want the Process SQL entry to gobble CPU.
>
> BTW, some of your collegues from Office or someone else decided that
> everyone needed that intrepid critter wisptis.exe with every Office app
> and MSFT got Adobe to install it with anything they make as well. If
> they don't have a tablet, then they don't need a CPU gobbler called
> wisptis as an adjunct for the tablet pen. It could have been an elective
> MSFT download for those who do need a Tablet pen facillitator or whatever
> wisptis is.
>
> The only EV error I got when I opened Word and told it not to disable any
> add-ins was "Accepted Safe Mode action : Microsoft Office Word." I'm not
> in Safe Mode, but that was a spinoff from trying to open OL last time
> without the requisite services for BCM. When I opened up Outlook, I got
> these, and this is typical but OL opens fine, it works fine, When I fire
> up One Note, Access, Excel, PowerPoint, InfoPath, Publisher they pop up
> immediately and there are no errors in EV or anywhere else. Word takes a
> little longer because of some third party add-ins I have for it. Outlook
> only takes longer because BCM adds a few seconds or it would open up
> immediately but the data base engine needs a little time to get going.
> Accepted Safe Mode action : Microsoft Office Outlook.
>
> Detection of product '{91E30409-6000-11D3-8CFE-0150048383C9}', feature
> 'WORDFiles', component '{1EBDE4BC-9A51-4630-B541-2561FA45CCC5}' failed.
> The resource 'E:\Program Files\Microsoft Office\OFFICE11\WINWORD.EXE' does
> not exist.
>
> Detection of product '{91E30409-6000-11D3-8CFE-0150048383C9}', feature
> 'WORDFiles' failed during request for component
> '{1EBDE4BC-9A51-4630-B541-2561FA45CCC5}'
>
> Office is installed at E:\Program Files\Microsoft Office\OFFICE11 ( and
> just one OS on "C") and when ocassionally an Office patch (like one of
> the excel patches for 03) gives you a choice where to install (self
> extracting zip?), I try to send it to the most specific place possible
> for that patch in the Office 11 folder, although I think you have some
> lattitude there. I have a stereotypical 4 drive setup with Documents on
> "D" and most programs including Office on "E" with the exception of some
> of the large ones like Encarta DVD (3Gb or so) on "F" with some teaching
> programs that take up significant real estate---the objective being to try
> to maintain 20-30% free space on each drive so I'll get a decent defrag.
>
> When I had trouble installing Office 2003 SP1, I got these errors
> consistently and repeatedly and the OX800401F0 error showed up even when I
> used the Full File from the Office Update scanner which went right in with
> no problems, or as I say when I tried to install a downloaded executable.
> I don't think that despite it's failed to connect to server error wording,
> you will tell me it has anything to do with any server connection however.
> I would be glad to send you Event Viewer or any MSI OHotfix verbose logs
> files from the problem,or I can send you Event Viewer's Application
> errors. Once I got it in I didn't want to bother you since you are being
> nice enough to look at so many for people and I don't know how long it
> takes. I also wonder when you all read those, *if you have any additional
> "software tool" you deploy* or it's just in learning how to look at them:
>
> I also meant to ask you about this. I have the Windows Installer Windows
> ® Installer. V 3.00.3790.2162 by virtue of XP SP2's build but there are
> two (probably one is a duplicate somehow instances on "F" of the
> "Installer for the Windows Installer" 2.0.2600.2 one named InstMSIA and
> the other InstMSIW that each take up over 1.6GB, a self extracting cabinet
> MSI 1.30 Version 5.5000 and MSI 1.30 RC1 and RC2 logs on "C." I'm
> presumming the active MSI is version 3 plus that came with SP2 and 2.0
> plus came with SP1. I don't think I need anything but the latest
> actually. Can the others referencing MSI be uninstalled with no downside?
> And if so can I just shift delete them-- or do I have to go after them
> where they are installed plus registry keys. They don't have entries in
> Add/Remove--and I wouldn't expect the native installer for XP to have one.
>
> Thanks much,
>
> Chad Harris
> ________________________________________________________________________
>
> "Sloan Crayton [MS]" <sloanc@online.microsoft.com> wrote in message
> news:ObG$Tt1eEHA.2028@tk2msftngp13.phx.gbl...
> Did these errors occur during patching? It looks like E: is the location
> of your Office installation. Is that correct?
>
> Sloan Crayton
> Microsoft
> "Chad Harris" <ddram32_nospam@yahoo.com> wrote in message
> news:elQ8sRkeEHA.2468@TK2MSFTNGP12.phx.gbl...
> Sloan--
>
> Thanks for this, because even when I finally got SP1 in it's in Event
> Viewer lilterally one minute after, and after last week of SP1 versus me
> for a few days, (although I wonder now had I used the Windows Install
> Repair Utility or LIS if I might have gotten it in sooner), I still got a
> series of those errors right before I ran the Update wizard and I'm still
> seeing it and I'm not trying to install anything. I wonder if for some
> reason just opening OL or Word is evoking it--they are working fine. If I
> had had your explanations from the last two days including the one on the
> Windows Install Repair Utility I would have used it in a heartbeat.
>
> I have never used the LIS tool, but I believe that's not what you
> said--you meant that registry information got corrupted possibly during
> setup regarding the LIS feature not that you would have had to use it
> first to get the error.
>
> And at first I thought (and superficially) on 7/27 when the series of
> SP1s released, that there was a rush on the MSFT servers and they were
> overwhelmed but unless there were an unusual attack on them that impacted
> them (my understanding is that there are upwards of 250,000 attacks on
> MSFT servers or its security system daily) I doubt that would happen.
> *Then it began happening even when I was trying to install a downloaded
> excutable of MOS 03 SP1 so I began to wonder if it was a very short time
> out from my ISP's server until a number of people started showing up with
> this error.
>
> I don't want you to spend much time with these (I'm not trying to ask you
> about every little error I see but I haven't been able to search these
> "detection of product errors down" I've been having since I loaded Office
> 2003 and wanted to show you these(they show up frequently in Event
> Viewer), and if you're able to glance at them and context them for me as
> errors I need to do something about I'd really appreciate it. I wondered
> if it meant I was missing something essential since they say a Word or
> Outlook component failed.
>
> Detection of product '{91E30409-6000-11D3-8CFE-0150048383C9}', feature
> 'OUTLOOKFiles', component '{3CE26368-6322-4ABF-B11B-458F5C450D0F}' failed.
> The resource 'E:\Program Files\Microsoft Office\OFFICE11\OUTLOOK.EXE' does
> not exist.
> Detection of product '{91E30409-6000-11D3-8CFE-0150048383C9}', feature
> 'WORDFiles' failed during request for component
> '{1EBDE4BC-9A51-4630-B541-2561FA45CCC5}'
> Detection of product '{91E30409-6000-11D3-8CFE-0150048383C9}', feature
> 'WORDFiles', component '{1EBDE4BC-9A51-4630-B541-2561FA45CCC5}' failed.
> The resource 'E:\Program Files\Microsoft Office\OFFICE11\WINWORD.EXE' does
> not exist.
> Detection of product '{91E30409-6000-11D3-8CFE-0150048383C9}', feature
> 'WORDFiles' failed during request for component
> '{1EBDE4BC-9A51-4630-B541-2561FA45CCC5}'
> Detection of product '{91E30409-6000-11D3-8CFE-0150048383C9}', feature
> 'WORDFiles', component '{1EBDE4BC-9A51-4630-B541-2561FA45CCC5}' failed.
> The resource 'E:\Program Files\Microsoft Office\OFFICE11\WINWORD.EXE' does
> not exist.
>
> The MOF file created for the Outlook service could not be loaded. The
> error code returned by the MOF Compiler is contained in the Record Data.
> Before the performance counters of this service can be collected by WMI
> the MOF file will need to be loaded manually. Contact the vendor of this
> service for additional information.
> Performance counters for the Outlook (Outlook) service were loaded
> successfully. The Record Data contains the new index values assigned to
> this service.
> User: NT AUTHORITY\NETWORK SERVICE
> Description:
> Detection of product '{91E30409-6000-11D3-8CFE-0150048383C9}', feature
> 'WISPHidden', component '{DCE23ACB-E055-44F1-88BD-2D1A75A8FCB8}' failed.
> The resource 'E:\Program Files\Microsoft
> Office\OFFICE11\1033\PROTTPLN.PPT' does not exist.\
>
> The description for Event ID ( 19011 ) in Source ( MSSQL$MICROSOFTBCM )
> cannot be found.
>
> The local computer may not have the necessary registry information or
> message DLL files to display messages from a remote computer. You may be
> able to use the /AUXSOURCE= flag to retrieve this description; see Help
> and Support for details. The following information is part of the event:
> (SpnRegister) : Error 1355.
>
> The description for Event ID ( 0 ) in Source ( OfficeUpdateV3 ) cannot be
> found. The local computer may not have the necessary registry information
> or message DLL files to display messages from a remote computer. You may
> be able to use the /AUXSOURCE= flag to retrieve this description; see Help
> and Support for details. The following information is part of the event:
> V3_2|511735|INSTALL|MAINSP1_6361_ENG||2004-07-30
> 01:32:17|9|FAIL|00000000|The operation completed successfully.
>
> Thanks,
>
> Chad Harris
> _______________________________________________________________
> "Sloan Crayton [MS]" <sloanc@online.microsoft.com> wrote in message
> news:OBZ1sMeeEHA.3520@TK2MSFTNGP10.phx.gbl...
> We're investigating this error, Chad. Several folks have sent their log
> files to me, and what they have in common is corrupted registry
> information regarding the LIS feature. With the log files we're hopeful
> that we'll be able to fix the problem and provide a workaround for those
> who've already encountered it. We expect that this corruption also
> 'breaks' the LIS Tool.
>
> Sloan Crayton
> Microsoft
> "Chad Harris" <ddram32_nospam@yahoo.com> wrote in message
> news:%23Cqk4SSeEHA.3792@TK2MSFTNGP09.phx.gbl...
> If not, what is this error, and what's the remedy? I'm struck by this
> explanation Sloan Crayton made of the LIS tool:
>
> Do you have a clear understanding of the reason for this Local Install
> Source feature? If you leave the LIS intact (with all of the CAB files
> from
> the CD), it will eliminate the need to connect to the source when updating
> your client.
>
> Frequently Asked Questions About the Local Install Source Feature
> http://support.microsoft.com/default.aspx?scid=kb;en-us;830168
>
>
> A number of people have been posting that they can't get MOS 2003 SP1 in,
> and that they can't use the Office Update tool. The Update tool can be
> bypassed to a downloads page, but the only error they are showing in Event
> Viewer is *Failed to connect to server. Error: 0x800401F0*.
>
> I have tried to figure out what this error means, and googling it
> provides a plethora of engimas enshroweded in a pllentiful supply of
> mysteries--nothing clear even searching error sites.
>
> I got the error on a successful install from the Wizard connected to
> Office Update's scanner using the full file, but I also got it in
> conjunction with the others every time I failed using the client file
> either with the scanner/wizard or using downloaded executables.
>
> Would the LIS tool help this, because somehow it would prevent your
> falling prey to a Fail to Connect to Server problem since LIS "eliminates
> the need to connect to the source?"
>
> Frequently Asked Questions About the Local Install Source Feature
> http://support.microsoft.com/default.aspx?scid=kb;en-us;830168
>
> http://www.microsoft.com/office/ork/2003/journ/LISTool.htm.
> Change the Local Installation Source After the Installation
>
> http://www.microsoft.com/office/ork/2003/two/ch3/DepC06.htmTaking
> Advantage of a Local Installation Source
>
> Other LIS Resources:
>
> http://www.microsoft.com/office/ork/2003/journ/LISupdt.htm
>
> http://www.microsoft.com/office/ork/2003/journ/LISTool.htm
>
> Chad Harris
> _________________________________________________________________
>
- Next message: Sloan Crayton [MS]: "Re: SP1 Cannot be applied / Installation failed - My fix"
- Previous message: Sloan Crayton [MS]: "Re: Office 2003"
- In reply to: Chad Harris: "Re: Is a solution to the Failed to connect to server/Answer for Sloan"
- Next in thread: Chad Harris: "Re: Is a solution to the Failed to connect to server/Answer for Sloan"
- Reply: Chad Harris: "Re: Is a solution to the Failed to connect to server/Answer for Sloan"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|