Workflow does not start automatically when items are created by a Web Application in SharePoint 2010

We had a Users list in SharePoint 2010 to which a workflow was attached. This workflow fires off when a item is created in the Users list. The Users list was getting populated through a web application which would let the users enter the data and then save the data to the Users list using the ClientContent object.
        During testing, we made the application pool for the custom web application run under the same user as that of the SharePoint 2010 web application. This caused a wierd behaviour in that the items were getting written the User list but the workflow was not firing. There were no errors in the application logs, SharePoint logs or anywere else.
       Turns out that SharePoint 2010 has a security feature that will prevent the workflow from starting automatically when items are created in a list from a custom Web Application which has the same Application Pool credentials as the SharePoint Application Pool. Once we changed the user on the Custom Web Application Pool everything started to work okay.

Comments

Post a Comment

Popular posts from this blog

Print from WPF using ReportViewer Control

Came across a requirements in a project that i was working on were we had to show SQL reports from inside of a WPF application(that WPF does not have a way to show SQL Reports requires another post). Could not find a complete solution that will give the user the code to add and show SQL Reports from WPF. The environment that i have used for this solution is Visual Studio 2010, SQL 2008  R2 deployed on a remote server Below is the complete code using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Windows; using System.Windows.Controls; using System.Windows.Data; using System.Windows.Documents; using System.Windows.Input; using System.Windows.Media; using System.Windows.Media.Imaging; using System.Windows.Navigation; using System.Windows.Shapes; namespace ReportViewer { /// /// Interaction logic for MainWindow.xaml /// public partial class MainWindow ...
Read more

Printing SSRS 2008 R2 Reports from C#.

While working on a code for sending a SSRS report straight to the printer, ran into a interesting issue where the Render method was not giving back the StreamId's for the reports which had more than one page. This is known bug in SSRS 2008 R3 MS Link . To  get around this issue, you have to modify the element value in the element and call the Render method multiple times  in a Do while loop to get all the pages for the report. The method RenderReport contains the code in which we iterate and call the Render method multiple times. Another bug, which i have not been able to resolve at the time of writing this post, is that the Fonts get somewhat strange when the report is published. Make sure that the you have the elements PrintDpiX and PrintDpiY present and thier values set to 96 in the element otherwise you might see the report printed out in oversize font. To call the class PrintSSSRSReport use the code below  PrintSSRSREport printReport = new PrintSSRSREport(); p...
Read more

Using IOptions class in .Net Core Unit Testing.

When implementing unit testng for a interface that was using a IOptions class, we were getting an null exception when trying to access the value using _mockMyconfig!.Object.Value . To resolve this error this, you have to manually create the MyConfig class and then assign it to the Value property. MyConfig myConfig = new MyConfig() { BaseURL = "https://mocktest.com" }; _mockMyconfig = new Mock >(MockBehavior.Loose); // We need to set the Value of IOptions to be the Myconfig Class, if this step is not done, then we get null exception when we try to use the value like this _mockMyconfig!.Object.Value _mockMyconfig.Setup(ap => ap.Value).Returns(myConfig); Once you have done this, then we use this in the unit testing like without getting the null exception. _mockHttpClient!.Setup(repo => repo.GetPWSHttpClient(_mockMyconfig!.Object.Value)).Returns(new HttpClient()).Verifiable(); The Main NuGet packages that have been used for th...
Read more