Application Pools Not Starting After Reboot

IIS Manager > Computer Name > Configuration Editor > Section dropdown > system.applicationhost > application pools > (Collection) > eclipses (…) > select application pool > startMode > AlwaysRunning.

Source:
http://msdn.microsoft.com/en-us/library/ee677285%28v=azure.10%29.aspx

SharePoint 2013 - Sign in as a Different User

/_layouts/closeConnection.aspx?loginasanotheruser=true

Reference:
http://blog.credera.com/technology-insights/microsoft-solutions/how-to-sign-in-as-a-different-user-in-sharepoint-2013/

Copying/Moving SharePoint 2010 Designer Workflows

Consolidated directly from:

http://chanakyajayabalan.wordpress.com/2012/01/02/copyingmoving-sharepoint-2010-designer-workflows/

1. In the first(source) site, create the required workflow and publish it.
2. Now select Export to Visio option which allows you to save the workflow with a .vwi extension. (Refer this workflow hereafter as source workflow).
3. Now go to the destination site where you want the workflow to be copied, and create a new workflow with the same name as the previous one & publish it.
4. Now select Export to Visio option which allows you to save the workflow with a .vwi extension. (Refer this workflow hereafter as Destination workflow).
5. Now you will be having two .vwi files (one of source workflow’s – SourceWorkflowName.vwi and other of the destination workflow’s – DestinationWorkflowName.vwi). Now add .zip extension to both the files. Now your files names should be SourceWorkflowName.vwi.zip & DestinationWorkflowName.vwi.zip.
6. Now open both the zip files, copy workflow.xoml.wfconfig.xml from destination workflow to source workflow. (Its destination to source and not source to destination).
7. From now on, we will not use the file DestinationWorkflowName.vwi.zip. So ignore that file.
8. Remove the .zip extension from SourceWorkflowName.vwi.zip which gives you the SourceWorkflowName.vwi file.
9. Now, go to the destination site, open workflows and click Import from Visio and browse to the SourceWorkflowName.vwi file.
10. That’s it and your workflow is copied. You can publish the workflow and run it.

PS : In case if your list’s GUID’s (for those lists that you have used in workflow – tasks list, history list or any other lists used in workflow steps) have been changed from source & destination site, you may need to update those steps in the workflow.

-----

Instead of creating zip files, just open the source and destination workflows in SPD and overwrite the wfconfig file from source to destination from All files option in SPD and thats it!

Export Multiple Lists into a Single Excel File

This is simply a copy of a clever TechNet Forum answer for reference:

After you click Export to Excel and open the owssvr.iqy for the first list, do not close the Excel file, change the connection name from owssvr to something else in Data->Connections->Properties.
go to the next list and click Export to Excel, choose new worksheet instead of new workbook. And rename the connection to the second list from owssvr to something else as before.
This way, you will get one data connection for each list in the same workbook. Save the workbook back to .xls after finishing the last list.

PowerShell - Get-SPLogEvent

get-splogevent -StartTime "08/26/2014 01:00" -EndTime "08/26/2014 14:00" |?{$_.Correlation -eq "8b49fbf8-7da2-43k7-ad49-5p02277bc598"} | select Timestamp, Area, Category, Level, EventID, Message | Format-List

Blog - Post.aspx - Intermittent Unable to display this Web Part

Intermittent on Blog Post.aspx:

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

-----

$myfarm = Get-SPFarm $myfarm.XsltTransformTimeOut 1

-----

$myfarm.XsltTransformTimeOut = 5 $myfarm.Update()

------

Reference:
http://thechriskent.com/2012/06/18/intermittent-unable-to-display-this-web-part-messages/

ItemStyle.xsl - All Field Names

<xsl:for-each select="@*">
    Field Name :<xsl:value-of select="name()" />
</xsl:for-each>