Keith Smith - My Blog

Keith Smith - My Blog


Event ID 6398 and 5586

Wednesday, April 19, 2017 - Posted by Keith A. Smith, in SharePoint

Simple fix for Event ID 6398 and 5586

Disable the Health Analysis Job (Daily, Microsoft SharePoint Foundation Timer, Any Server)  in the central administration

-End
View Comments 0 Comments
Share Post   

Warning 1015- Failed to connect to server Error- 0x80070005

Wednesday, April 19, 2017 - Posted by Keith A. Smith, in SharePoint

Problem

On a daily basis, you see the following warning appear in the SharePoint server host's Application log:
Log Name:      Application
Source:        MsiInstaller
Date:          [date]
Event ID:      1015
Task Category: None
Level:         Warning
Keywords:      Classic
User:          [SharePoint farm account]
Computer:      [a SharePoint Server host]
Description:

Failed to connect to server. Error: 0x80070005
Event Xml:

  
    
    1015
    3
    0
    0x80000000000000
    
    8607
    Application
    [a SharePoint Server host]
    
  
  
    0x80070005
    (NULL)
    (NULL)
    (NULL)
    (NULL)
    (NULL)
    
    
  


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  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
    0x80000000000000
    
    8608
    Application
    [a SharePoint Server ]
    
  
  
    Microsoft InfoPath Form Services English Language Pack
    14.0.7015.1000
    1033
    0
    Microsoft Corporation
    (NULL)
    
    
    ...
  

Each 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.

Solution
1. Add the farm account to the host's local administrator group.
2. Restart the SharePoint 2010 Timer service.
3. Remove the farm account from the host's local administrator group.
4. Run the farm's product Version Job.
5. Check the host's Application Log.

View Comments 0 Comments
Share Post   

People search relevance is not optimized when the Active Directory

Wednesday, April 19, 2017 - Posted by Keith A. Smith, in SharePoint

People search relevance is not optimized when the Active Directory has errors in the manager reporting structure.

People search relevance is not optimized when the Active Directory has errors in the manager reporting structure.

Scenario:
Specify the company leaders explicitly. Use the following PowerShell commands: $upap = Get-SPServiceApplicationProxy [appid]; Add-SPProfileLeader $upap [Domain]\[UserName]. Run ‘Get-SPProfileLeader $upap’ to check whether the leader was successfully added. As a last step, run a full crawl on the content source containing the start address (URL) of the user profile application. For more information about this rule, see “http://go.microsoft.com/fwlink/?LinkID=248249“.
 
Steps:
Run the follow commands in a SharePoint Management shell as administrator:
1) Get-SPServiceApplicationProxy
 
2)  $upap = Get-SPServiceApplicationProxy -Identity c36a7818
-668b-4190-87f9-03aed906e465
3) $upap

4) Add-SPProfileLeader -ProfileServiceApplicationProxy $upap -Name “DOMAIN\Department.Head”
5) Get-SPProfileLeader $upap
6) Run a full crawl on the content source containing the start address (URL) of the user profile application
If you want to check the leadres:
Get-SPProfileLeader
Get-SPProfileLeader -ProfileServiceApplicationProxy $upap
 
If you want to delete the leaders:
Remove-SPProfileLeader
Remove-SPProfileLeader -ProfileServiceApplicationProxy $upap -Name "DOMAIN\user1"

-End
View Comments 0 Comments
Share Post   

The Unattended Service Account Application ID is not specified

Wednesday, April 19, 2017 - Posted by Keith A. Smith, in SharePoint

The Unattended Service Account Application ID is not specified or has an invalid value.

    •    The Unattended Service Account Application ID is not specified or has an invalid value.

1) Go to Central Administration | Application Management | Manage service applications | Visio Graphics Service | Global Settings 
2) Check the Application ID under Unattended Service Account 
3) You should have entered an application Id here, if not create a Secure Store Target Application of type Group and then enter its Target Application ID for Visio Graphics Account.

To create a new secure store target application go to Central Administration | Application Management | Manage service applications | Secure Store Service

This error showed up on the Monitoring > Health Analyzer of my SharePoint 2010 VM.   Apparently after using the wizard to create a new farm, you must double back to supply Visio Services with user credentials for remote data connections.
http://social.msdn.microsoft.com/Forums/en-US/sharepoint2010general/thread/559f72a4-d9ca-4004-b5ca-a0fa6dbad51f was a helpful reference on the steps.

Steps Taken:
    •    Open Health Analyzer and view details
    •    Manage the Visio Graphics Service (SA) and confirm Application ID is empty.
    •    Manage the Secure Store Service (SA) and Generate New Key
    •    Create a New Target Application
    •    Provide a unique ID, name, and contact email. Select Group Type.
    •    Accept default and just click Next
    •    Provide a user name for both fields.  I used “DEMOAdmin” as that is the only user on this machine. Click OK.
    •    Enter the Target Application ID back on the Visio Graphics Service (SA) page and click OK.
    •    Go to the Health Analyzer rule, open it and click Reanalyze Now, then you should be ready to go.

 

-End









View Comments 0 Comments
Share Post   

Timer service keeps terminating unexpectedly

Wednesday, April 19, 2017 - Posted by Keith A. Smith, in SharePoint

For anyone else having this issue. The solution is to give access for the user the timer service is running under to the following SP directory. The Admin group has the rights required which is why the issue is resolved for those people who put the account in the machine's admin group which is a bad practice. Ensure the user has the correct permissions on the following SP directory, and see the error go away.
C:\ProgramData\Microsoft\SharePoint\Config
(create a new account for the timer service in AD, then create sec. Group add the account to that group. Add the group to the file sec permissions and admin etc.)

Also add to SQL security

OR

I've solve this after including account into local admin group. But! this problem happen when i'm change Network service account to local one created especially for this service.

-End
View Comments 0 Comments
Share Post   

Page  <1...7891011...18>