The symptom we had was:
Failed to connect to server. Error: 0x800401F0

Digging deeper we saw WMI issues logged in the install log.
We saw errors logged in the WMI logs also, but service was otherwise
functioning and the articles on this error on Symantec were not
applicable, or didn't work.

Symantec support gave us this brute force fix which did the trick, but
you might want to look at any 3rd party apps you have installed that set
up their own stuff in WMI.


Here was the rebuild procedure we used.

    At the command line, typed "net stop winmgmt"
    Opened Explorer and wemt to the folder called
    %SystemRoot%\System32\WBEM\Repository.
    Deleted that folder and everything in it.
    Rebooted the system normally.
    On the next login, opened a command prompt and typed the following
    commands in this order:
    winmgmt /clearadap
    winmgmt /kill
    winmgmt /unregserver
    winmgmt /regserver
    winmgmt /resyncperf

     

     

 



On 2/21/2010 1:42 AM, David Stanaway wrote:
> I just had a problem with this same error on a windows 2000 client. This
> was on a new 6.5 install.
>
> At the very end of the install, the installer connected to the windows
> event logs through WMI I think but this failed due to WMI repository
> being corrupted somehow. The install rolls back at this point.
>
> The problem was with the WMI Registry which needed to be rebuilt. I can
> send you instructions if you need. It was relatively painless but needed
> a reboot of the client.
>
> On 2/19/2010 5:57 PM, zimmy00 wrote:
>   
>> I have over 300 clients out there and out of those I can't seem to get a 
>> handful of them upgraded past 6. Now I know that unlike 6 and before, 6.5 
>> requires communication with the server, however there are no firewalls in 
>> the way. And the servers backup with no problem with the older clients 
>> installed. The only error I see in the logs is "Failed to connect to server. 
>> Error: 0x800401F0" and of course during the install the app says 
>> "Installation was interupted". 
>>
>> I know it's not the master servers since they have no problem getting to 
>> other clients. DNS is not an issue because the master is a unix server and I 
>> use the hosts table. And as stated there are no firewalls in between. Anyone 
>> have any idea's because I can't think of anything else.
>>
>> This is happening on both 2000 and 2003 clients, I have ran it locally and 
>> tried to push it from another client.  I have ran it as administrator (run 
>> as) and as an adminstrator account.  There is no UPS software on these 
>> servers (only article I could find on it).
>>
>> +----------------------------------------------------------------------
>> |This was sent by steve.s...@compucom.com via Backup Central.
>> |Forward SPAM to ab...@backupcentral.com.
>> +----------------------------------------------------------------------
>>
>>
>> _______________________________________________
>> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
>> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>>   
>>     
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>   

_______________________________________________
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Reply via email to