SharePoint Timer Service terminated with service every 1-2 minutes

I got this error in the event view every minutes or so. I don't know what cause it. I check Job History in central admin and found that not of the job is working. I see following error that i think it might be relate

SPTimerStore.InitializeTimer: SPConfigurationDatabase.RefreshCache returned SPConstants.InvalidRowVersion

The timer service could not initialize its configuration, please check the configuraiton database. will retry later

After googling and decided to try to clear the Configuration Cache, I found out that my cache folder is missing. I decided to recreate the cache folder.

1) Open regedit
2) HKLM->Software->Microsoft->Shared Tools->Web Server Extensions->15.0->Secure->ConfigDB
and look for Id which is a GUID
3) Go to C:\ProgramData\Microsoft\SharePoint\Config create a folder name from guid step 2
4) create a file call Cache.ini, edit and put 1 on the file
5) restart iis and timer service

Now my job is running again. Hope it help someone have same issue.

Change Azure VM Instance Size Powershell

1) download and install Azure Powershell

https://www.windowsazure.com/en-us/downloads/?fb=en-us

2) Export your window azure profile and rename to something you like ex: 'c:\myazureprofile.publishsettings'

https://windows.azure.com/download/publishprofile.aspx

3) Import the setting

Import-AzurePublishSettingsFile 'c:\myazureprofile.publishsettings'

4) Run command in powershell to get current VM you have in asure, this will give you ServiceName, Name and Status 

Get-AzureVM

5) Change VM Size, $cloudSvcName, $vmname are from step 4. $NewSize value = ExtraSmall, Small, Medium...

Get-AzureVM -ServiceName $cloudSvcName -Name $vmname | Set-AzureVMSize $NewSize | Update-AzureVM

JSLink listview webpart not working

I create a field render using JSLink. It work fine on the list ,but when i create a new page add a listview web parts. It not working. It turn out that i have to turn off Server-Side Rendering.

SharePoint 2013 Workflow can't start

I setup and configure workflow manager 1.0 (SharePoint 2013 workflow). The status in central admin show connected. I was able to use SharePoint designer to create and publish workflow. When i try to run the workflow, i got an error. I check SharePoint log without any luck ,but when i check event view under

Applications and Services Logs -> Microsoft-Workflow-> Operation and i got error

Failed SQL command after 1 tries with error '229'. Exception: System.Data.SqlClient.SqlException (0x80131904): The EXECUTE permission was denied on the object 'InsertTrackingAndStatus', database 'WFInstanceManagementDB', schema 'dbo'.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.CompleteAsyncExecuteReader()
   at System.Data.SqlClient.SqlCommand.EndExecuteNonQueryInternal(IAsyncResult asyncResult)
   at System.Data.SqlClient.SqlCommand.EndExecuteNonQuery(IAsyncResult asyncResult)
   at Microsoft.Workflow.Management.ExecuteNonQueryAsyncResult.OnEndExecuteSql(IAsyncResult result)
   at Microsoft.Workflow.Management.ExecuteSqlAsyncResult.EndAsyncResult(IAsyncResult result)
   at Microsoft.Workflow.Common.BackoffRetryAsyncResult.IsolateWithRetry(IAsyncResult result)
   at Microsoft.Workflow.Common.AsyncResult.AsyncCompletionWrapperCallback(IAsyncResult result)
ClientConnectionId:5b1469db-d187-4f8e-aa73-3482aa74a195  Command Details:   SQL Text          : InsertTrackingAndStatus
  SQL Parameters    :
    > @StatusRecords = Microsoft.Workflow.Management.SqlDataAccessProvider+InstanceStatusValuesCollection
    > @MetadataWithInstanceId = Microsoft.Workflow.Management.SqlDataAccessProvider+MetadataValuesWithInstanceIdCollection
    > @Variables = Microsoft.Workflow.Management.SqlDataAccessProvider+VariablesCollection
    > @TrackingRecords =
    > @StatusHistoryRecords =
    > @DebugTraceRecords = Microsoft.Workflow.Management.SqlDataAccessProvider+DebugTraceRecordValuesCollection
    > @RollingStatusHistoryWindowSize = 1000
    > @RollingDebugTraceWindowSize = 5000

I have the workflow service account owner permission to the WFResourceManagment and WFInstanceManagemnet database and it start working again. I don't think owner is needed ,but since this is a dev machine so i give owner to get thing moving.

User Profile Synchonization Service Starting and stop Sharepoint 2013

My User profile synchronization service for some reason stop and it can't start it. I try to manual start (Central Admin -> Services on Server), it say starting and couple minute later will stop. I think my stop because I update SharePoint to March CU.I check and both "Forefront Identity manager Service" and "Forefront Identity Manager Synchronization Service" are both disable and stop. Here what I did that seem to fix. 

• Verify the service account that run timer service is local admin to server. In my case it was not admin so I have to add it local admin and restart server.
• The Sync account have replicate directory change permission.
• I start the User profile synchronization service on central admin
• I do an SharePoint Timer Service Restart
• I wait couple minute and it show started.
• I do another iisreset.
• I now check window service and both "Forefront Identity manager Service" and "Forefront Identity Manager Synchronization Service" started

10 serious mistakes companies make with SharePoint

There are many challenges to implementing SharePoint, both seen and unseen. As a result there are plenty of pitfalls and traps to fall into, and it is very challenging to pick just 10 mistakes.  Poor governance, not having an intranet strategy, or not having an intranet committee are traditional mistakes, but hopefully there is more awareness about these issues now. Marcus Dervin, director of Sydney SharePoint/Office 365 consultancy WebVine. focusses on more specific issues that are are often overlooked, but can derail a SharePoint project team’s best intentions.
It would be great to hear what you consider to be in your top 10, please add a comment.
1.The all or nothing approach
Companies often endeavour to implement a full intranet site including Publishing sites, Team Sites, MySites, InfoPath forms, Business Intelligence and Document Management.  An all or nothing approach. While these are great features, they can be overwhelming for end users when implemented all at once, not to mention the SharePoint team.  And if they are not rolled out in a managed way, their impact falls short and you end up with lots of nothingness in your intranet.
For example, if someone has many deadlines and tasks to deliver, will they really go and update their MySite? Or even tag those documents correctly?  Or even load those documents to the Team Site rather than just email them?
In order to create a successful SharePoint platform in your company, you need to take it step-by-step.
One approach we use in WebVine, is in addition to designing the intranet site, to create a number of small wins for departments also, for example setting up document management for the finance dept. Finance departments are very organised and methodical, and it’s easier to get metadata requirements from them, than from marketing for example. Then when you launch the intranet, showcase the library and have the finance team speak about the benefits of document management. You can do the same for with HR by building an Infopath form for them. And so on.
When people see the results, they become enthusiastic to follow suit, then start working with the remaining departments. You will have a much better chance of user engagement and success.
2.Implementing document management incorrectly
I have seen many SharePoint document libraries and I have rarely seen one that is done well. Often, using a share drive would offer similar benefits, aside from version control and the ability to send links instead of attachments.
If you are using SharePoint, then document libraries can offer tremendous benefits.  However staff are not shown or trained on how to derive to most benefit from document libraries, and end up discarding them.
When you setup a library, the first thing to do is to run a workshop on how to design it. You need to capture the metadata that is applicable to the people using that library. For example, if you are setting up a library for the IT department, it will look different to the Legal department library. You also need to consider using content types and managed metadata in your libraries as these offer tremendous benefits.
With content types you can create a list of templates within a library, so if a user clicks ‘New’ they are presented with a list of predefines templates. If the templates are setup correctly eg a word document called ‘budget report’ then information entered in the word document can be captured as filterable metadata in the library. See below for a good and not so good example of a document library. 

 How not to setup a library – lots of folders, and no useful metadata

A better example of what a library should look like, no folders, filtered by metadata 

3.Just using SharePoint as a CMS
Implement SharePoint as an intranet site takes a lot of work. Especially if engaging a design agency, managing multiple stakeholders and creating a decent site design. Not to mention creating content. Unfortunately, the resources used to create the intranet site end up being the same resources used to maintain and update the intranet.  If resources are limited (intranet resources are usually thin), developing the SharePoint environment further tends not to happen.  So you have an intranet that cost a million dollars in licensing, that could have been delivered much more cheaply on another CMS. If you are not offering any value other than SharePoint being a CMS, what’s the point in using SharePoint?
Team sites, project sites, document management, process improvements, collaboration, reporting and more all need to be on the strategy plan (just not all delivered at once of course).  Otherwise it’s one expensively run website you have sitting there.
To get these projects off the ground, you’ll need a good understanding of what SharePoint can offer your company, and executive level support (see point 8). Ensure you get this support up front and create a SharePoint strategy that delivers decent ROI.
Then you will maximise your SharePoint investment.
4.Lack of SharePoint expertise in the organisation
Making a SharePoint project a success has many facets. Organisations rely completely on their staff to get projects over the line. But what happens when you don’t have enough knowledge in the project team?  Quite possibly the team doesn’t even realise it.
For example, SharePoint is pretty easy to install. But if the administrator doesn’t understand the effect of version control, archiving, records management, and a whole lot more, then the site can come to a grinding halt within 12 months.
Understanding how the SharePoint environment will be used and planning for that up front is crucial.
Also, organisations tend to deploy collaboration features and expect people to use them.  But soon after find empty MySites and discussion groups 1 thread deep. Having SharePoint technical understanding is not enough; you need a plan to ensure adoption in the organisation. Once people see empty pages, they tend not to come back.
Try to find lessons learnt from other companies, attend conferences, do your research, and get external assistance if you need to.
5.Missing out on key features completely
You don’t know what you don’t know.  As a result, there are fabulous gems within SharePoint that are easy to implement, but are often missed.  These features make a real difference to organisations, releasing people from repetitive tasks, so they can actually do productive and enjoyable work.
Custom lists, workflows, content types and forms are awesome and can transform the work culture of a company.
If you are still sending around lots of excel spreadsheets, then it’s likely you are missing out on at least one key feature. Custom Lists are a fantastic way of sharing information and getting rid of those excel documents. You can import an excel document and save it as a list to start with, then you can modify the list. For example setting a date field to default with today’s date. You can set alerts on the list, so if someone updates it, everyone on the alert is notified.
You can create different views of the list, so the manager (on the manager dashboard page if desired), sees the high level information only.
You can easily filter information on the list, for example I only want to see information related to NSW and status of urgent.
You can share information with other lists, for example if I have a column of projects and that appears in 2 different lists, I can create a look-up list to populate both lists.
The possibilities for more collaborative working between people and teams are endless – just using custom lists.
And there is plenty more that SharePoint can offer. So get under the hood, find out how to use these features, and ensure you utilise these in your organisation.

6. The gap between IT and the business
Business users rely on IT to inform them of what they can do with SharePoint.  However, I have spoken to many SharePoint administrators who admit they do not to tell their business users about key features as they don’t have the time to help them use this functionality. IT also rely on the business to give them requirements, however, if the business don't have the information to know what is possible, they won't know what to ask for.  As a result the business may ask for things that are difficult, costly and time consuming to develop.
So there is this information gap. This gap as many people know can lead to frustration, disagreements and a lack of understanding on both sides.
Perhaps a middle ground may have been found if both sides spoke the same language. Configurations to SharePoint can be made without requiring IT's involvement, with the correct knowledge and permissions. Business goals can be created and met if people actually understand what SharePoint can do.
Have knowledgeable SharePoint people in your team that know about SharePoint's features such as InfoPath forms, lists, libraries, search customisation, the many webparts available, personalisation and more. So they can persuade IT to make some of these features available and IT can be relieved of the burden of doing everything.
7. Assuming staff will automatically use SharePoint
Companies that do not engage their staff in how SharePoint is going to benefit them, soon discover a few issues. It's nice to have a nice looking intranet site with news posts and maybe a yammer feed, but is that it? SharePoint is not just a technology solution; it brings about a completely new way of working. People need to be educated in this new way of working together, step by step. Champions need to be found on a grassroots level, and real business benefit needs to be demonstrated. And people won’t get it without guidance and understanding ‘what’s in it for them.
So, in order for people to really appreciate SharePoint, they need to see how it can remove those ‘daily grind’ tasks.  This is where SharePoint really comes into play.
* That report that Jo has to email every week to 20 people and then collate answers into a single document can be easily done in 1/10th of the time without Jo having to move.
* Shelley no longer has to email people when she updates certain documents; they are automatically alerted.
* That list of vendors that is somewhere in the file share is now actually accessible, sortable and easy to get to.
* The Finance manager sees updated live finance data at anytime on his customised home page, without having to request the information.  When you give people back their lives through freeing up their time, they love SharePoint, in addition they are much more productive and happy.
8. Executive level support and understanding is not there
In order to transform how an entire organisation manages information, you need executive level support.  Otherwise you won’t get the funding needed to go the whole way. Key stakeholders and people in roles like sales will not see the benefit to harnessing and accessing knowledge in the organisations. They are more focussed on external results, not streamlining internal processes.
However, you don’t want to let that derail the SharePoint project, as transforming how people work has tremendous benefits to the company.
If the CEO is aware of these benefits and wants the see them realised, then it’s a lot easier to get SharePoint over the line, and delivering tangible results.
After all, who wants to be left in the dark ages using shared drives and email and continuously losing  information. So when the right people can convey a clear message to the executive team of the importance of SharePoint to the organisation, the project has a much better chance of success. Make sure you have those people in your organisation, and if you don’t have them, get some help. For some reason people really value external consultant’s opinions, even if internal staff convey the same message, so consider hiring them even for this pitch alone.
9. Leaving out Search until the last minute
Many SharePoint implementers do not consider SharePoint Search until the launch, like an afterthought.
However, Search is a very important piece in the SharePoint pie, and if it’s not configured well, will not deliver accurate results. The more help you can give SharePoint up front, the more satisfied people will be with the results. And they really do expect Google at their fingertips, after all, that is what they are used to.
Setting up managed metadata or tags so that you can filter results needs to be decided early on, otherwise at the end when you have already configured all of your lists and document libraries, it’s too late.
For example, if someone can filter the results by department, topic, region, job role, or whatever filters are most suited to your content,  that will be incredibly helpful in searching SharePoint. So understand Search from the outset, take it into consideration, create a Search strategy and implement it. You will benefit from the importance of getting Search right in SharePoint.
10. SharePoint sprawl and incorrectly setting up the environment
If SharePoint is not governed well, it can lead to a plethora of Team Sites and even publishing sites in an organisation. This sprawl leads to a very unstructured intranet, which soon becomes unreliable.  People get lost in numerous sites and lose faith in the integrity of the intranet, and this kind of sprawl can lead to deterioration in server performance.
Very often, SharePoint environments are not configured optimally. Someone installs SharePoint, which can be done fairly easily, and away they go. I have seen a number of companies with large SharePoint environments, relied on by thousands of employees, have their environments crippled due to a poor foundation. A lack of understanding at the infrastructure level, and in configuration, can leave SharePoint farms running slowly, giving a poor user experience, a bad name for SharePoint, and even worse, can grind to a halt.
So ensure you have people who know what they are doing when initially setting up SharePoint, who can take into account the volume of data likely to be reached in a number of years, the number of users accessing the system, and many other key factors.

Add Search component to search topology

SharePoint 2013 change search tapology. You cannot change it directly so the way to do it to clone it, modified it and make clone active

Let say you want to add admin component to server P11

1.      Clone current Search Topology

$ssa = Get-SPEnterpriseSearchServiceApplication
$active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active
$clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone –SearchTopology $active

2.      Add new Search component to P11 (server name)

$app2 = Get-SPEnterpriseSearchServiceInstance -Identity "P11"

New-SPEnterpriseSearchAdminComponent -SearchTopology $clone -SearchServiceInstance $app2


3.      Start new search component

Start-SPEnterpriseSearchServiceInstance -Identity $app2


4.      Activate Cloned Topology (this will make clone active)

Set-SPEnterpriseSearchTopology -Identity $clone

Ref: http://stevemannspath.blogspot.com/2013/03/sharepoint-2013-search-moving-query.html

Search Host Controller hung on "Starting" SharePoint 2013

Single Server:

$SA = Get-SPServiceInstance | Where {$_.Status -like “Provisioning”}

$SA -> to check current setup if you want

$SA.Unprovision()

$SA.Provision()

Multiple Server Setup

$SA = Get-SPServiceInstance | Where {$_.Status -like “Provisioning”}

$SA -> to check current setup if you want

$SA.Unprovision()

You may get an error tell you execution code must be run on server name “…”, but if you check in central admin it actually stop service on this server. You will then move to next server to repeat above step for all server.

Go back to first server and run $SA.provision() on all server. You may get error execute next server like above, just follow it until last server and the error is gone.

SharePoint 2013 Helpful link

Show Off Your Style with SharePoint Theming - Theming in SharePoint 2013 makes it easier to drastically change the look of your site and make it your own. That said, the new look of SharePoint sites is great, so why would you want to change it? http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=1043

Certain Microsoft SharePoint Server 2013 installation scenarios are not supported - This article describes Microsoft SharePoint Server 2013 installation scenarios that are not supported.http://support.microsoft.com/kb/2764086

Global Solutions for SharePoint 2013 - This model provides architectural guidance for geographically distributed deployments of SharePoint 2013. http://www.microsoft.com/en-us/download/details.aspx?id=34975

Backup and restore: SharePoint Server 2013 - This model illustrates various ways that you can back up and restore a SharePoint environment. http://www.microsoft.com/en-us/download/details.aspx?id=30365

Databases that support SharePoint 2013 Preview - This model illustrates the databases that that support SharePoint 2013 Preview. http://www.microsoft.com/en-us/download/details.aspx?id=30363

Design Sample: Corporate Portal with Host-named Sites for SharePoint Server 2013 - This design sample illustrates the use of host-named site collections with all sites deployed in a single web application on the farm. This method is highly scalable and is flexible in managing URLs. http://www.microsoft.com/en-us/download/details.aspx?id=30362

Design Sample: Corporate Portal with Path-based Sites for SharePoint Server 2013 - This design sample illustrates the use of path-based site collections with sites organized into dedicated web applications and a single top-level site collection per web application. http://www.microsoft.com/en-us/download/details.aspx?id=30378

Design Sample: Extranet with Dedicated Zones for Authentication for SharePoint 2013 - This design sample illustrates many top-level project sites with vanity URLs by using host-named sites for each project site (instead of organizing project sites underneath a top-level site collection). http://www.microsoft.com/en-us/download/details.aspx?id=30368

Downloadable eBook: Deployment guide for SharePoint 2013 - Download this free ebook to learn how to install and configure SharePoint Server and SharePoint Foundation. http://www.microsoft.com/en-us/download/details.aspx?id=30384

Downloadable eBook: Explore SharePoint 2013 - Download this free eBook to learn more about what's new in SharePoint 2013. http://www.microsoft.com/en-us/download/details.aspx?id=30368

Enterprise search architectures for SharePoint Server 2013 - This design sample shows the search architecture for a variety of sizes of server farms. http://www.microsoft.com/en-us/download/details.aspx?id=30383

Incoming email planning worksheet - This worksheet helps you record information to help you plan for incoming email in a SharePoint deployment.  http://www.microsoft.com/en-us/download/details.aspx?id=34805

Microsoft SharePoint Products and Technologies Protocol Documentation - The Microsoft SharePoint Products and Technologies protocol documentation provides technical specifications for Microsoft proprietary protocols that are 

implemented and used in SharePoint Products and Technologies. http://www.microsoft.com/en-us/download/details.aspx?id=25255

Multi-farm architectures with SharePoint Server 2013 - This model provides architectural guidance for multi-farm deployments of SharePoint Server 2013. http://www.microsoft.com/en-us/download/details.aspx?id=34973

Search architectures for SharePoint Server 2013 - This design sample shows the search architecture for a medium size server farm. http://www.microsoft.com/en-us/download/details.aspx?id=30374

Services in SharePoint Server 2013 - This illustration provides information about services that are available in SharePoint Server 2013. http://www.microsoft.com/en-us/download/details.aspx?id=30402

SharePoint 2013 Upgrade Process - This model explains the process that you use when you upgrade from SharePoint Foundation 2010 or SharePoint Server 2010 to SharePoint Foundation 2013 or SharePoint Server 2013. http://www.microsoft.com/en-us/download/details.aspx?id=30371

SharePoint 2013: App Overview for IT Pro - The app model in SharePoint 2013 enables SharePoint environments to add functionality quickly and securely. http://www.microsoft.com/en-us/download/details.aspx?id=30373

SharePoint 2013: How to Test Upgrade - This model explains how to create a test environment to use when you upgrade from SharePoint Server 2010 or SharePoint Foundation 2010 to SharePoint 2013 Products http://www.microsoft.com/en-us/download/details.aspx?id=30366

Test Lab Guide: Configure SharePoint Server 2010 in a Three-Tier Farm - This paper contains step-by-step instructions for creating a test lab containing a three-tier SharePoint farm. http://www.microsoft.com/en-us/download/details.aspx?id=29420

Topologies for SharePoint 2013 - The versatility of SharePoint 2013 provides opportunities to develop a topology that satisfies your business goals.  http://www.microsoft.com/en-us/download/details.aspx?id=30377

User profile properties and profile synchronization planning worksheets for SharePoint Server 2013 - The following planning worksheets can assist you when planning user profiles or planning and configuring profile synchronization. http://www.microsoft.com/en-us/download/details.aspx?id=35404

White Paper: Office 2013--Access Services Setup for an On-Premises Installation - This white paper provides instructions that will help you configure SQL Server 2012 for Access Services in SharePoint Server 2013. It includes instructions for an on-premises installation and configuration of Access Services on a server that is running SharePoint Server 2013. http://www.microsoft.com/en-us/download/details.aspx?id=30445

KB Articles

Certain Microsoft SharePoint Server 2013 installation scenarios are not supportedhttp://support.microsoft.com/kb/2764086

Sign in as Different User menu option is removed from SharePoint Server 2013http://support.microsoft.com/kb/2752600

Sorry, something went wrong error message when you run a query in SharePoint Server 2013http://support.microsoft.com/kb/2752602

Sorry, something went wrong error message when an anonymous user performs a search on an Enterprise Wiki site in a SharePoint Server 2013 environment http://support.microsoft.com/kb/2755130

Please enable scripts and reload this page error message when you try to open a SharePoint Server 2013 site http://support.microsoft.com/kb/2752584

Method not allowed error message when you use Windows authentication to open the PerformancePoint Dashboard Designer in SharePoint Server 2013 http://support.microsoft.com/kb/2755141

UPA administrator cannot change the synchronization connection settings in SharePoint Server 2013http://support.microsoft.com/kb/2752606

User Profile service application does not function correctly after you restore a SharePoint farm to a SharePoint Server 2013 server http://support.microsoft.com/kb/2752610

How to use SPQuery to query a list in SharePoint Server 2013 http://support.microsoft.com/kb/2755129

PowerPivot gallery is displayed on SharePoint sites after you remove PowerPivot for SharePoint in SharePoint Server 2013 http://support.microsoft.com/kb/2752605

You cannot start Dashboard Designer after you install a language pack for a language that is a variant of Spanish in PerformancePoint Services in SharePoint Server 2013 http://support.microsoft.com/kb/2752603

Only the OU setting is removed when you run the Remove-SPProfileSyncConnection cmdlet in SharePoint Server 2013 http://support.microsoft.com/kb/2758430

Changes to PowerPivot Service application database in SharePoint Server 2013http://support.microsoft.com/kb/2756665

Thanks to IVAN : https://msmvps.com/blogs/ivansanders/archive/2012/11/07/sharepoint-2013-kb-articles-diagrams-ebooks-samples-amp-guidance.aspx

SharePoint 2013 Deploy custom code activity

Deployment in detail

•Workflow Manager box (http://code.msdn.microsoft.com/Defining-and-Using-Custom-d7d87547)

1.Copy activity assembly to following locations:

•%ProgramFiles%\Workflow Manager\1.0\Workflow\Artifacts

•%ProgramFiles%\Workflow Manager\1.0\Workflow\WFWebRoot\bin

2.Add your activity class to the white-list

•Create AllowedType.xml and copy it to above two locations

3.Restart “Workflow Manager backend” service

•SharePoint box (http://msdn.microsoft.com/en-us/library/jj163911.aspx)

1.Copy activity assembly to SharePoint box and GAC it

2.Add a new .actions4 file to %CommonProgramFiles%\Microsoft Shared\Web Server Extensions\15\TEMPLATE\1033\Workflow (need top-level node)

3.Reset IIS

•Client

•Clean up SPD cache (%LocalAppdata%\Microsoft\WebsiteCache)