Monday, March 28, 2016

SharePoint Timer service is stopping - SharePoint 2013 /2010

Error:

Timer service is stopping every weekend. we have been using SP farm account which has all administrative access though timer service is stopping every weekend.
start type is selected automatic but it does not make any sense as well.
Causes:
-Couple of reasons are being come up while digging this issue as following: 
After checking system event viewer, found following error which is occurring often,
"Cannot connect to SQL Server. DSQL not found. Additional error information from SQL Server is included below.
Connection Timeout Expired.  The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.  This could be because the pre-login handshake failed or the server was unable to respond back in time.  The duration spent while attempting to connect to this server was - [Pre-Login] initialization=2; handshake=14985;"
Suggestions to Check to fix this issues are:
Friday evening there's maintenance jobs running which are bringing down the SQL environment. Check server backup schedules, SQL DB backup schedules, full crawl times and SAN backup times.
only one server(in my case) which is being served as web front end and apps server for dev environment and it has only 12 GB RAM. 

Solution:
-it was database back up schedule which caused this issue. 
- if the resources (disk, CPU, or network) consumed by performing that backup are so high, it is possible that the SQL Server isn't able to respond in time for SharePoint's requests.
-we did backup schedule on other day and checked whether it generates error or not and we got same error.
- end of day, after adding memory to RAM of Sql server, it solved the issue and no more timer service is breaking. it is running without error or stopped.
- That's all!!

Friday, March 25, 2016

SharePoint 2010 Cumulative Updates Error: Some farm products and patches were not detected

Error: 
I got error while running SharePoint Products configuration wizard after deploying Feb 2016 CU for SharePoint 2010 servers as following,



Solution:

 1. run Powershell command using sp admin account
2. then run Get-SPProduct -Local
3. (Get-SPServer $env:ComputerName).NeedsUpgrade
4. confirm that you get true as returned at last




5. run SharePoint Products Configuration wizard and it will run be fine.

That's all.