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!!

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.

Error when doing site search after 2013 upgrade

I got following error while searching on home page after migration from sharepoint 2010 to sharepoint 2013,
Error:

Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Microsoft SharePoint Foundation-compatible HTML editor such as Microsoft SharePoint Designer. If the problem persists, contact your Web server administrator.

Correlation ID:6474799c-e8bf-80ef-0089-f1547f35a6db

Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Microsoft SharePoint Foundation-compatible HTML editor such as Microsoft SharePoint Designer. If the problem persists, contact your Web server administrator.

I found in ULS log,

Error while executing web part: System.Xml.Xsl.XslLoadException: XSLT compile error. An error occurred at (0,0). ---> System.Xml.XmlException: Root element is missing. at System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res) at System.Xml.XmlTextReaderImpl.ParseDocumentContent() at System.Xml.Xsl.Xslt.XsltInput.ReadNextSibling() at System.Xml.Xsl.Xslt.XsltInput.FindStylesheetElement() at System.Xml.Xsl.Xslt.XsltLoader.LoadDocument() at System.Xml.Xsl.Xslt.XsltLoader.LoadStylesheet(XmlReader reader, Boolean include) - -- End of inner exception stack trace ---

at System.Xml.Xsl.Xslt.XsltLoader.LoadStylesheet(XmlReader reader, Boolean include) at System.Xml.Xsl.Xslt.XsltLoader.Load(Compiler compiler, Object stylesheet, XmlResolver xmlResolver) at System.Xml.Xsl.Xslt.Compiler.Compile(Object stylesheet, XmlResolver xmlResolver, QilExpression& qil) at System.Xml.Xsl.XslCompiledTransform.LoadInternal(Object stylesheet, XsltSettings settings, XmlResolver stylesheetResolver) at Microsoft.SharePoint.WebPartPages.DataFormWebPart.LoadXslCompiledTransform(WSSXmlUrlResolver someXmlResolver) at Microsoft.SharePoint.WebPartPages.DataFormWebPart.GetXslCompiledTransform() at Microsoft.SharePoint.WebPartPages.DataFormWebPart.PrepareAndPerformTransform(Boolean bDeferExecuteTransform)

Solution:

run follwoing command using PS,

$ssa = Get-SPEnterpriseSearchServiceApplication "My Search Service App"

$ssa.Status = "Disabled"

$ssa.Update()

$ssa.Provision()

refresh page or wait for next day sometimes it takes much time to reflect solution.

Cheers.....

installation of Azure AD Connect Azure

I followed this blog and successfully able to synchronize  users from local ad to azure ad.
make sure username and password used to synchronize here while configuring it,

https://azure.microsoft.com/en-us/documentation/articles/active-directory-aadconnect-get-started-custom/

Cheers...

Step-by-Step: Build a FREE SharePoint 2013 Dev/Test Lab in the Cloud with Windows Azure Infrastructure Services

http://blogs.technet.com/b/keithmayer/archive/2013/01/07/step-by-step-build-a-free-sharepoint-2013-lab-in-the-cloud-with-windows-azure-31-days-of-servers-in-the-cloud-part-7-of-31.aspx

Durable Links in SharePoint Server 2016

SharePoint 2016 got new feature called "Durable Links",

http://blogs.technet.com/b/wbaer/archive/2015/09/22/durable-links-in-sharepoint-server-2016-it-preview.aspx

SharePoint 2013 CU Updates

You can find latest updates for SharePoint 2013 here,

https://technet.microsoft.com/en-us/library/dn789211(v=office.14).aspx

SharePoint Online preventing Users to download multiple documents

Error: Users are not prevented to download multiple documents and folders from SharePoint online.
getting following error while doing it,

Solution:
 added https URL into trusted sites under Internet Options/Security tab.
restarted IE browser and it works...Cheers..

Some Users didn't migrate after migration from SharePoint 2010 to 2013

i got following error after migration users from SharePoint 2010 to SharePoint 2013.

Error: i got error from log file,

"SPWebApplication 'QAS Intranet Portal', SPSite '7e4e36d2-6187-4cc5-a95f-d2155e20f2cd', SPUser 'contoso\MS5592': Could not get migration data for user with name 'contoso\MS5592' and identifier 'S-1-5-21-3166358256-3741618376-1075545218-3045' so SKIPPING. 

Checked migration for further logs".

i ran following command to migrate users from SharePoint 2010 to 2013,
$wa = get-SPWebApplication "webappname"
Convert-SPWebApplication -Identity $wa -To Claims –RetainPermissions -Verbose
$wa.MigrateUsers($true)

Solution:

I followed below blog and found it that users are migrated while checking people picket in SharePoint 2013. 
you can run full synchronization to make sure all users are imported properly.
Troubleshoot Database upgrade issue in SharePoint 2013,
https://technet.microsoft.com/en-us/library/cc262967.aspx

Migrate from classic mode to claims based authentication in SP 2013,
https://technet.microsoft.com/en-us/library/gg251985.aspx


That's all....

Database upgrade issues in SharePoint 2013

You have to read this blog before migration from SharePoint 2010 to SharePoint 2013 otherwise you will get error regrading with access issue or user not found in SharePoint or SharePoint sites or AD.

Troubleshoot database upgrade issues in SharePoint 2013

https://technet.microsoft.com/en-us/library/cc262967.aspx

Migrate from classic mode to Claims based authentication in SharePoint 2013,

https://technet.microsoft.com/en-us/library/gg251985.aspx