he My Site Cleanup Job is also enabled and set to run every hour as set by default.

Once an account is deleted or deactivated within Active Directory, this correctly flags a profile for deletion
If the user had a My Site, the manager will receive a notification that it will be deleted in 14 days.

However the My Site is deleted immediately and there is no delay.

Its jobs must runs User Profile Incremental Synchronization 

Please refer this below link

https://blogs.technet.microsoft.com/scottstewart/2014/09/15/disableloopbackcheck-when-routing-through-a-load-balancer-powershell-sample-included/

• stsadm -o execadmsvcjobs on the server running Central Admin
• Install-SPSolution has only the -Force, 
• Check for Sharepoint 2013 Timer service

In this article ,When user trying to add content type return s error,"null reference exception"

SPContentType test = web.AvailableContentTypes["Employee Details"];
newList.ContentTypesEnabled = true;
newList.Update();
newList.ContentTypes.Add(test);

Question:

 I have a site where the publishing feature was turned on. There are no file under Pages All web pages are under Site Pages. I have files under documents and the image folders. If I deactivate the publishing feature will anything break.


Solution:

down vote

If you enable the SharePoint Server Publishing feature and attempt to restore a backed up site with this feature having been turned on once (even if you disable it before a backup), there will be issues with restoring that site

down votefavorite

In a SharePoint 2013 Site Collection and in its Subsites the SharePoint Publishing Features are enabled: SharePoint Server Publishing Infrastructure Feature (Site Collection Level) SharePoint Server Publishing Feature (Site Level)

1. What happens to the Sites, Document Libraries, Content Types that were created by the SharePoint Publishing Features? Will they be deleted by deactivating the Publishing Features?
2. What will happen to the the sites, document libraries, content types, master pages if customizations were made?
3. What will happen to the Sites, Document Libraries, Content Types, Content, ... when reactivating the Publishing Features? Will they be overwritten by reactivating the Publishing Features?
4. Will creating a backup of the content database(s) provide a sufficient fallback option if data loss is a risk?

Please add attribute  this

disable-output-escaping="yes"


<xsl:value-of select="@Designation" />

Try  like this:


<xsl:value-of select="@Designation" disable-output-escaping="yes" />

 OWSTIMER getting below error

Use PowerShell to enable the 'ParserEnabled' property for the web site

$web = Get-SPWeb <url of web>
$web.ParserEnabled = $true
$web.Update()


#listtemplate missing

when trying to check-in a document in a document library



SharePoint Designer to navigate to the site / Document library. Select all files that need checking in and select Check-in from the Edit menu.

Following things must happen after above policy was set and before your documents are moved to recycle Bin:

• Information management policy completed successfully
• Expiration Policy completed successfully.

Both jobs are by default scheduled to run on a "Weekly" basis.

To Quickly test whether it is working (or any change in policy you made), perform following actions for above jobs in order in which mentioned above:

Go to Central Admin > Monitoring > Review Job Definition. Filter the list by your Web Application

Locate the job and select Run Now

Monitor the job history and make sure the job was run successfully on your web application

You might have figured out now, first jobs calculates the expiry date for the documents based on the policy. The second job actually deletes the documents marked to be deleted by the first job.

Add the below lines in the MasterPage in SharePoint

<!--SPM:<SharePoint:AjaxDelta id="DeltaPlaceHolderLeftNavBar" BlockElement="true" runat="server">-->
<!--SPM:<asp:ContentPlaceHolder id="PlaceHolderLeftNavBar" runat="server">-->
<!--SPM:</asp:ContentPlaceHolder>-->
<!--SPM:</SharePoint:AjaxDelta>-->
<!--SPM:<SharePoint:AjaxDelta id="DeltaPlaceHolderPageTitleInTitleArea" runat="server">-->
<!--SPM:<asp:ContentPlaceHolder id="PlaceHolderPageTitleInTitleArea" runat="server">-->
<!--SPM:</asp:ContentPlaceHolder>-->
<!--SPM:</SharePoint:AjaxDelta>-->

We have facing this issue unable to display webpart.

When we have create more than 120 columns in our list Its shows error in our page

Default setting is 1 second. The PowerShell code below changes it to 2 seconds which should be sufficient for your farm.  So,we will choosing 4 seconds timeout. 



Powershell Script:

$farm = Get-SPFarm
$farm.XSLTTransformTimeout = 4
$farm.Update()



Effects:

If you backup/restore a site collection, you get this error when displaying All Items views.
I created a view loading 20 items at a time instead of all and it fixed the issue.