Keith Smith - My Blog

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

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

Problem
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  0x80000000000000  8608  Application  [a SharePoint Server 2010 host]  Microsoft InfoPath Form Services English Language Pack  14.0.7015.1000  1033  0 

Microsoft Corporation   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
   •   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

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

Problem
You encounter the following error appears in the Windows Application event log:
Log Name: Application Source: Microsoft-SharePoint Products-Web Content Management Date:  Event ID: 7362 Task Category: Publishing Cache Level: Warning Keywords:  User:  Computer:  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.

Solution
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 https://[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:

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

-End

0 Comments
Share Post

Failure trying to synch web application Event ID 5555

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

One of the errors I got after upgrading sharepoint that I couldn’t shake until recently.

Failure trying to synch web application , ContentDB Exception message was Microsoft.Office.Server.UserProfiles.UserProfileApplicationNotAvailableException: No User Profile Application available to service the request. Contact your farm administrator. at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.get_ApplicationProperties() at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.get_PerfmonInstanceHandle() at Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer..ctor(ELogType logType, SPContentDatabase cdb, SPJobState jobState) at Microsoft.Office.Server.UserProfiles.WSSProfileSyncJob.Execute()

Run from the sharepoint bin directory in a cmd prompted

Stsadm -o sync -listolddatabases 2 Stsadm -o sync -deleteolddatabases 2

Finally, and I’m not sure if this is necessary, but I read that you should change timer job “Timer Service Recycle” (Central Administration –> Job Definitions) to run at 06:30 PM. This last step can be done through Central Administration. After doing this my errors went away. I did however need to run a full user profile synchronization by going to Central Administration –> Manage Profile Service: SharedServicesSearch_UserProfile –> Start Profile Synchronization

-End

0 Comments
Share Post

Full list of Failure Reasons for event 4625

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

Windows Domain Controller - Event Viewer Security Status and Sub-Status values

SUB_STATUS

	DESCRIPTION
0XC000006D	This is either due to a bad username or authentication information
0XC000006D	This is either due to a bad username or authentication information
0XC000006E	Unknown user name or bad password.
0XC000006E	Unknown user name or bad password.
0XC0000193	account expiration
0XC000006E	Unknown user name or bad password.
0XC000006D	This is either due to a bad username or authentication information
0XC000006D	This is either due to a bad username or authentication information
0XC000018C	The logon request failed because the trust relationship between the primary domain and the trusted domain failed.
0XC000005E	There are currently no logon servers available to service the logon request.
0XC00000DC	Indicates the Sam Server was in the wrong state to perform the desired operation.
0XC0000224	A user is required to change password at next logon
0XC0000192	An attempt was made to logon, but the netlogon service was not started.
0XC0000413	Logon Failure: The machine you are logging onto is protected by an authentication firewall. The specified account is not allowed to authenticate to the machine.