Saturday, August 15, 2015

Method 'StartWorkflowOnListItem' in type 'Microsoft.SharePoint.WorkflowServices.FabricWorkflowInstanceProvider'

Exception:
Method 'StartWorkflowOnListItem' in type 'Microsoft.SharePoint.WorkflowServices.FabricWorkflowInstanceProvider' from assembly 'Microsoft.SharePoint.WorkflowServices, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' does not have an implementation.

We continuously faced a serious problem in SharePoint 2013 workflow development after installing the hotfix- KB2880998.  This hotfix causes different types of problem in Workflow Manager 1.0. 

Initially we did not identified the root cause. We thought that this was may some server related issue occurred by our last deployment in DEV server. But our Staging server also effected with the same error since we did not deployed our changes to that server. 

Closely observe the ULS logs it seems that this causes by some workflow related dll missing or corrupted. Then investigating the issue based on workflow related issue and found the following link which described the issue clearly

https://social.technet.microsoft.com/Forums/windowsserver/en-US/b189e4b8-bb9e-4ade-a3d5-cd2e0f90e93f/workflow-not-working-after-installing-service-pack-1-and-patches?forum=sharepointadmin

Solution:

Install the security update 2880963 for SharePoint Server 2013 from the following link will fix the issue.


Method 'Upgrade' in type 'Microsoft.SharePoint.WorkflowServices.WorkflowServiceApplicationProxy'

Method 'Upgrade' in type 'Microsoft.SharePoint.WorkflowServices.WorkflowServiceApplicationProxy' from assembly 'Microsoft.SharePoint.WorkflowServices, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' does not have an implementation.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.TypeLoadException: Method 'Upgrade' in type 'Microsoft.SharePoint.WorkflowServices.WorkflowServiceApplicationProxy' from assembly 'Microsoft.SharePoint.WorkflowServices, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' does not have an implementation.

Recently we have installed service pack-1 for SharePoint server  2013. Everything is going well but development team face the above mentioned issue during custom workflow development. 

After investigating we found that Service Pack-1 unstable the Workflow service. Microsoft release a patch to fix the workflow related issue.

Solution:

The workflow upgrade issue required STS and OServer are at the same version. Following update link provide by Microsoft described the issue and fixing.

https://support.microsoft.com/en-us/kb/2880963

Install the following security patch will fix the reported issue.
FYI: No need to restart the SharePoint server 2013 after install the update.

Friday, August 7, 2015

Problem:
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.SharePoint.WorkflowExtensions, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.VisualStudio.SharePoint.WorkflowExtensions, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'

Causes/Solutions:
Our team faced this exception for several scenarios in Development environment. We fixed this problem in different combination for different scenarios.

Development Environment:
Windows server 2012
Visual Studio 2012
SharePoint Server 2013,
SharePoint Workflow 2013

Cause-1:
Workflow Manager Tool was not installed.

Solution-1:
Simply installed the workflow manager tools for SharePoint Workflow 2013.

Cause-2:
Workflow Manager Tool was installed but not updated with corresponding Cumulative update.

Solution-2:
As we know SharePoint workflow is managed by Workflow Manager 1.0 and its depends upon Service Bus 1.0. So need to update both version as well.
These two cumulative updates were working for us.

February 2013 Cumulative Update for Service Bus 1.0: KB2799752
February 2013 Cumulative Update for Workflow Manager 1.0: KB2799754

Cause-3:
Office Developer Tools (OfficeDevToolsforVS2012) was not installed on the DEV box.

Solution-3:
Installed the correct version of Office developer tools. We need to installed the OfficeDevToolsforVS2012 version.

Hopefully this will be helpful for other.

Thursday, June 13, 2013

Technical Reviewer of a new book "Razor View Engine How-to"


Packt Publishing recently released a new book titled – Instant Razor View Engine authored by Abhimanyu Kumar Vatsa. I  have also attached with this process as a technical reviewer.

The main aspect of this book is to made easy for the developers to understand the use of razor view engine in ASP.net MVC. I found this book very helpful for beginner because it shows differences between different scenario with code example. It also covers differences between ASP.net view engine and razor view engine.

This book guide developer a step by step procedure to learn razor view engine quickly and effectively. For advanced developers it also covers the custom model binding,Razor helper extension method,declarative syntax etc.

Friday, November 16, 2012

Observer Design Pattern using Delegates/events

Today I want to discuss with you how to implement Observer design pattern using delegate and event in asp.net /c#.

Observer Pattern

The observer pattern is a software design pattern in which an object, called the subject, maintains a list of its dependents, called observers, and notifies them automatically of any state changes, usually by calling one of their methods. It is mainly used to implement distributed event handling systems. The Observer pattern is also a key part in the familiar Model View Controller (MVC) architectural pattern.(wikipedia).

UML class diagram of Observer pattern(wikipedia)





The Observer Pattern describes the dependence relationship between one object (observable) to many objects (observers). It's also called Model/View, Dependents, or Distributor/Listener pattern.This article introduces an implementation when we can use the Observer pattern to keep all observer objects updated after things have changed.

Case project

In this case, patient is an ObservableObject that needs to send out the notification when the hospital updates his/her physical status. The hospital will determine who will be notified when the patient status is updated.

Thursday, November 15, 2012

A Custom Attribute based approach to write summary on business object

Last day, I have got a mail from a junior developer he needs some help about custom attributes. He has no previous experience about it. I have delivered his some speech or send some link for study. Today I have made an example for him, so that he can understand its usage very easily. Now this also share with you it may also help other friends.


using System;
using

Tuesday, October 9, 2012

MSSQL SERVER 2008 – IntelliSense Does Not Work

Last few months ago I have upgraded Visual Studio 2010 ultimate with service pack 1. But unfortunately my SQL Server Management Studio(SSMS) 2008 intellisense not working. After searching I got that it is a common problem. Please have visit here.

To fix it just install SQL Server 2008 r2 SP1. You can download it from here.

If it is not working please check the following issues it may solve your problem.

  • Verify that the T-SQL Editor does not launch in SQLCMD mode Under Tools->Options->Query Execution->SQL Server->General, make sure “By default, open new queries in SQLCMD mode” is unchecked.

Method 'StartWorkflowOnListItem' in type 'Microsoft.SharePoint.WorkflowServices.FabricWorkflowInstanceProvider'

Exception: Method 'StartWorkflowOnListItem' in type 'Microsoft.SharePoint.WorkflowServices.FabricWorkflowInstanceProvider'...