Showing posts from 2014

SharePoint 2013 Workflow Errors

SharePoint 2013 Workflow Tips I have learned some gotchas and tricks while creating my first SharePoint 2013 Workflows. Background: These observations were observed while using SharePoint Designer 2013 with Service Pack 1 to create SharePoint 2013 Workflows on an on-premises farm running version 15.0.4665.1000 ​(2013 Service Pack 1 Mark 2).  No custom visual studio actions have been used. Observation 1: Corrupt workflows: DO NOT copy and paste Conditional IF statements from one stage transition to another stage transition. This may cause the workflow to become corrupted.  I have attempted to save the workflow as a template periodically in case it becomes corrupted later.  THIS DID NOT WORK.  It appears that workflows can become corrupt and nothing I could do later helped.  This included exporting the WSP, unpacking it, then trying to copy the XAML from one workflow to another and redeploy to the system.  Basically I tried every workaround I discovered.  Even tried using

PowerShell Scripts

PowerShell Scripts I think it is time I start publishing my SharePoint Scripts.  These are stored in my personal OneDrive and they should always be available.  Please let me know if they are not!  They are read only for public use.  I take no responsibility for their use.  So read them and understand them before using. These apply to the following: Active Directory HyperV IIS Modules NTFS Office 365 SQL Server Reporting Services SharePoint 2007 SharePoint 2010 SharePoint 2013 T-SQL Queries (Mostly for SharePoint purposes) Windows Server I appreciate any and all feedback or help with these.

The Timer Service Failed to Recycle

SharePoint Timer Service Failed to Recycle In the Monitoring section of SharePoint Central Administration a Health Analyzer rule appears warning about: The timer service failed to recycle. Title The timer service failed to recycle. Severity 2 - Warning Category Performance Explanation The last attempt to recycle the timer service failed as have most of the other attempts during the past week. Recycling typically fails because other timer jobs are running when the recycle is scheduled. To view which jobs blocked the recycle view the history for the recycle job and click on the failed status link for more information. The error message for the failed job entry will contain a list of jobs that were still running. Remedy Change the schedule for the timer recycle job so that it does not conflict with other long-running timer jobs. Failing Services SPTimerService (SPTimerV4) Environment SharePoint Server 2010 Enterprise O

SharePoint SQL Queries

My stash of useful SQL queries I use.  Particularly useful when doing migrations as tempdb files can grow out of hand and renaming, fixing databases are needed. View the state and files for a database: exec sp_helpdb [tempdb] View the status of Transaction Log size and usage: dbcc sqlperf(logspace) Shrink a Transaction Log: USE Test_Intranet_Content_Home; GO -- Truncate the log ALTER DATABASE Test_Intranet_Content_Home SET RECOVERY SIMPLE; GO -- Shrinks the log to number of Mb DBCC SHRINKFILE (Test_Intranet_Content_Home_log, 1536); GO -- Reset the recovery model ALTER DATABASE Test_Intranet_Content_Home SET RECOVERY FULL; GO Rename Filenames (I often do this when migrating a content DB to a new farm): -- Get the current database filenames sp_helpdb Test_Technology_Content_Root GO -- Change Logical Filenames  USE [Test_Technology_Content_Root] ALTER DATABASE [Test_Technology_Content_Root]       MODIFY FILE (NAME=N'SharePoint_PortalHome_Content'

Audience Targeting on SharePoint Sites with Anonymous Access

You have a site that is anonymous, but you want to restrict the display of certain content to authenticated users after they sign-in.  This information is a walkthrough of several ways, permissions and audiences, that this can be accomplished.   Anonymous Access Decision: Which sites does the client want to have anonymous as an option? Anonymous is first enabled at the web application level, so this can be a reason to have multiple web applications (and URLs) for different main sites where some need anonymous and others do not. Turning on anonymous at the web application does not actually change any permissions or open up anonymous on site collections.   It simply means you allow it, to give anonymous permissions to a site collection, first navigate to site permissions at the root site collection level.   Here you can choose to give access to the entire site (essentially inherit from the root all the way down) or just lists