Keith Smith - Think Ahead. Learn More. Solve Now!

Keith Smith - Think Ahead. Learn More. Solve Now!


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   


SharePoint VersionCheck-PostServicePackSteps

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

sharepoint mgmt shell (get sharepoint version)
(get-spfarm).buildversion

sharepoint mgmt shell (Check to see if psconfig is needed) if true then run the cmd below
(get-spserver $env:computername).NeedsUpgrade


In order to update the SharePoint databases, you must manually run the PSconfig utility. To run the utility:

1. Open an Administrative command prompt.
2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

Sites will be unavailable at this time. Once the above is complete run a iisreset and test your SharePoint sites.

-End
View Comments 0 Comments
Share Post   


Failed to connect to server

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

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:      Application
Source:        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
    (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 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
    0x80000000000000
    
    8608
    Application
    [a SharePoint Server 2010 host]
    
  
  
    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.



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
View Comments 0 Comments
Share Post   


The super user account utilized by the cache is not configured

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

SharePoint: Event ID: 7362: The super user account utilized by the cache is not configured


ProblemAngry
You encounter the following error appears in the Windows Application event log:
Log Name:      Application
Source:        Microsoft-SharePoint Products-Web Content Management
Date:          <date>
Event ID:      7362
Task Category: Publishing Cache
Level:         Warning
Keywords:      
User:          <username>
Computer:      <server>
Description:
Object Cache: The super user account utilized by the cache is not configured. This can increase the number of cache misses, which causes the page requests to consume unnecessary system resources.
To configure the account use the following command 'stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue account -url webappurl'. The account should be any account that has Full Control access to the SharePoint databases but is not an application pool account.
Additional Data:
Current default super user account: [MachineName]\system SharePoint 2010 is hosted on this machine.

SolutionSmile
On new installations, the SharePoint super user account is configured to run under the machine's local System account.  However, this causes complications and thus the warning.  This should be addressed during setup, but isn't included in the setup wizard.  Anyway, resolving it is simple.  There are two ways: using STSADM or using Powershell.  We'll go through both here.

Step 1: Create Super User and Super Reader Domain Accounts
Create super user and super reader domain accounts
Example: DOMAIN\sp_superuser, DOMAIN\sp_superreader

Step 2: Configure Accounts in SharePoint Central Administration
Go to SharePoint CA: Central Admin -> Manage Web Application -> User Policy
Add DOMAIN\sp_superuser – Full Control
Add DOMAIN\sp_superreader – Full Read

Check to make sure these accounts have similar access to the SharePoint databases.  Next, use one of the following steps: A or B.
Step 3A: Using STSADM
Open a command prompt
Execute:
stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue DOMAIN\[sp_superuser] -url [WEBAPPURL]
And
stsadm -o setproperty -propertyname portalsuperreaderaccount -propertyvalue DOMAIN\[sp_superreader] -url [WEBAPPURL]
Step 3B: Using SharePoint Management Shell

Open a shell
Execute the following commands:
1.$wcm = Get-SPWebApplication -Identity http://[webappurl/]
2.$wcm.Properties["portalsuperuseraccount"] = “DOMAIN\sp_superuser”
3.$wcm.Properties["portalsuperreaderaccount"] = “DOMAIN\sp_superreader”
4.$wcm.Update()
Close the shell.

Step 4: Reset IIS
Reset IIS either from the GUI or executing "IISReset" at the command prompt.

Step 5: Test
Open a command prompt
Execute the following:
stsadm -o getproperty -propertyname portalsuperuseraccount -url [WEBAPPURL]
Output should read:
<PropertyExist=”Yes” Value=”DOMAIN\sp_superuser” />


Similarly for the super reader account.  The references below provide good background.

-End
View Comments 0 Comments
Share Post   


Page  <12345...11>