Keith Smith - My Blog - Twitter @_KeithIT

Failed to connect to server

Wednesday, April 19, 2017 - by Keith A. Smith

SharePoint: Warning 1015: Failed to connect to server. Error: 0x80070005


ProblemCensored
On a daily basis, you see the following warning appear in the SharePoint server 2010 host's Application log:
Log Name:
ApplicationSource: MsiInstaller
 Date:         
[date]
Event ID: 1015

Task Category: None 
Level:        
Warning Keywords:     
Classic User: [SharePoint farm account]

Computer: [a SharePoint Server 2010 host]


Description:
Failed to connect to server. Error: 0x80070005
Event Xml:
1015 3 0 0x80000000000000 8607 Application [a SharePoint Server 2010 host]0x80070005
    
  
You may see a 100 or so similar warnings appear daily, each one accompanied by a corresponding Information event, such as the following:
Log Name: Application
Source: MsiInstaller
Date: [date]
Event ID:1035 
Task Category: None
Level: Information
Keywords: Classic
User: [SharePoint farm account]
Computer: [a SharePoint Server 2010 host]
Description:
Windows Installer reconfigured the product. Product Name: Microsoft InfoPath Form Services English Language Pack. Product Version: 14.0.7015.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0.
Event Xml:

  1035
    4
    0
   0x800000000000008608
  Application
  [a SharePoint Server 2010 host]Microsoft InfoPath Form Services English Language Pack
    14.0.7015.1000
    1033
    0
  
Microsoft CorporationEach of these pairs corresponds to a different component that can be configured for the farm.

Discussion

These are associated with the farm's Product Version Job, which by default runs daily at 12:45 AM.  Compare the times of these warnings with the time that your farm's Product Version Job runs, and you'll see the association.



SolutionClap
    •    Add the farm account to the host's local administrator group.
    •    Restart the SharePoint 2010 Timer service.
    •    Remove the farm account from the host's local administrator group.
    •    Run the farm's product Version Job.
    •    Check the host's Application Log.


-End
  Share Post   

View Comments Comments


Leave a Comment