.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Workflow History Not Added During Workflow

Posted By:      Posted Date: September 21, 2010    Points: 0   Category :SharePoint

I've created a custom sequential workflow in VS 2008. In the workflow I've added several LogToHistoryList activities, the description for one contains a dynamic value that is a task ID. The workflow histories do not appear in the history list until the workflow is completed. Has anyone else encountered this issue? I've tried including workflowProperties.HistoryList.Update(); to the LogToHistoryList_MethodInvoking with no luck.

Any suggestions?


View Complete Post

More Related Resource Links

Workflow field not being added to list or views when adding a workflow


This problem just started happening in my entire site collection.  Anytime I associate a workflow to any list or doc lib the Workflow column that shows the status and links to the history is not beind added to the list or any views and is nowhere to be found.   Here's exactly what I'm doing:

1.  Go the List settings -> workflow settings -> add a workflow (for this example the OOB approval workflow)

2.  After adding I go to the List, the workflow column doesn't exist.

3.  I go to "modify view", and the workflow column is not listed in the available columns.

Any help is greatly appreciated.

SPField of WorkflowEventType in the Workflow History List has value Workflow Initiated but when i ed


hi all

how are you

i wish anyone could help me in this problem

i have a sharepoint sequential workflow created in visual studio

when the workflow starts i log into the workflow history list that workfow is started using the LogToHistoryListActivity

i entered the hidden workflow history list from the browser for example:


i noticed that an item is created in the above list when i run my workflow

the field Event Type in the item above has the value of Workflow Initiated but when i edit the item i noticed that the field Event Type has a value of 0

so can anyone tells me how this field works and from where it is getting itsvalues

thanks a lot


Workflow history truncated description

Hello When viewing the workflow history for a review workflow, the description field is truncated if it is very long (it appear with ... at the end). Is there a way to see the value of the whole field? Someone already asked this question but the answer given is about using the SharePoint Object Model. I am looking for a solution for end-users. http://social.msdn.microsoft.com/Forums/en-US/sharepointworkflow/thread/5af8d475-149b-45eb-b565-e47ccb71a03b

How to set Workflow History Retention

Hi,How do I set the workflow history retention to be for 5 years using the following command?stsadm -o setproperty -pn job-workflow-autoclean -pv "retention period" -url http://myserverI know the consequences but I need it to happen despite those consequences

Auto-fill fields are racking up the version history whether they are on one workflow or many....SPD


I have a whole batch of fields which trigger an automatic date entry when they are changed: if more than one field is changed then a version is created for each field that is changed. I did some more fiddling to see how many of these workflows I could cram into one (originally built to have one workflow per date trigger) and tested again but although the changes are grouped together now the system automatic updates still trigger another version for each automatically entered date. Anyone know how to get around that? Its not unbearable but it just offends me somehow and it might cause a problem later on.

SharePoint Workflow : Failed to Start when a document is added to library from server-side object mo


When I add a document using my server-side object model code, I get an exception "The type or namespace name 'Office' does not exist in the namespace 'Microsoft'" in the server logs and in the library I can see the Workflow status as "Failed to Start".





Interestingly, when I add a document to the same library from sharepoint site portal, it works just fine, the workflow kicks off with the state : in-progress.

Also, I modified the task form for the Approval workflow template from SharePoint Designer using infopath.(Not sure if that be a problem as adding from portal works fine.)

What am I missing out here??

 Details of the exception:

09/29/2010 18:11:19.15  w3wp.exe (0x2508)                        0x2710 SharePoint Foundation          Workflow Infrastructure        98d8 Unexpected Microsoft.SharePoint.SPException: <Error><CompilerError Line="0" Column="20" Text="The type or namespace name 'Office' does not exist in the namespace 'Microsoft' (a

Workflow History and SQL Error


Like many others who work on SPD 2007 workflows might have encountered the following problem:

That is, When trying to view an item in a list which has workflows run against it, you get an error:

  • Some part of your SQL statement is nested too deeply. Rewrite the query or break it up into smaller queries

Now when I was searching for the solution I stumbled upon a post that suggested the reason we can't access the items is because when SharePoint pulls up the item for edit/view it checks the Workflow History for that item. If there are more than about 200 entries for that item in the Workflow History list, we get the SQL query error.   Now I am aware that the workflow history data is purged from the MOSS Workflow database table after 60 days but I was wondering:

a) Avoid the triggering of unnecessary history events when an item is created (view  link  for details)


b) If there is a way that I am able to control the workflow history list in some w

Workflow Status History


I found out some docs, that were approved over 3 months ago. But now there workflow statuses are clear. And now workflow history inside also.

Is there some mechanism in sharepoint that cleans up workflow history and document approval statuses?


How to delete the contents of the Workflow History List


I'm trying to purge the contents of the workflow history list which has thousands of comments added by the some workflows (I will fix the workflows later!). I'm worried that the huge number of entries in this list is slowing down the site performance. At this stage I do not need any of these entries for any audting or other purpose. I'm not sure of the best way to go about this.

My current strategy is to rely on the workflow autoclean sp timer job, after first running some code to set the AutoCleanupDays property of the SPWorkflowAssociation. I'm hoping that once I have run this on all the document libraries in my site where workflows have been run I will then be able to delete the Workflow History list using the Sharepoint Web UI "Delete this list" hyperlink.

When I do this at them moment I get an error as below:


Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))   at Microsoft.SharePoint.Library.SPRequestInternalClass.DeleteList(String bstrUrl, String bstrListName, UInt32 dwDeleteOp, Guid& pgDeleteTransactionId)
   at Microsoft.SharePoint.Library.SPRequest.DeleteList(String bstrUrl, String bstrListName, UInt32 dwDeleteOp, Guid& pgDeleteTransactionId)

Workflow History list - Huge number of entries.


Hi there,

Does anyone know if there is an issue with having a large number of entries in the workflow history list. I've got 2 sites that have only been in existence for 9months and the workflow history lists are already at 14000 entries?

Is this list size an issue?

Would growing at this rate cause an issue in the future?

Is there anything we could do about it? settings, delete routines..

Any ideas/suggestions gratefully received!



Information Management Policy to clean up the Workflow History List?


I have several InfoPath 2007 forms (with workflows) that are heavily used in my MOSS 2007 environment, and the some of the Workflow History lists are very large need to be cleaned up.  I'm trying to use an (Expiration) Information Management Policy to delete items in the Workflow History list that are Last Modified + X days , but haven't had much success.  Has anyone else had success doing this?


WSS OOB Workflow to send e-mail when item added to List?


I need to the below thing in WSS OOB Workflows . IF please let me know if you know
In WSS I have List with Name Emps. and colmns as EMPName as Single line text and EMPemail1,EMPemail2 as people picker fields.

When An item is added to the List worklfow should start and I need to send mail to EMPemail1 column person.
In the next step mail should send to Email2 person.

Free Series of SharePoint Workflow How-to Videos

This is the series of "How to" Document Workflow with SharePoint using Visual Studio 2008 (using the .NET Framework 3.0 for backward compatibility to Visual Studio 2005). I have created video's that show the most common requests that I have seen around MOSS/SharePoint 2007 workflow & document workflow.

Workflow Services: Visual Design of Workflows with WCF and WF 4


The .NET Framework 4 makes it easier than ever to implement WCF services using WF. We'll demonstrate just how easy it is by modeling a long-running, durable and instrumented workflow based on a real-world business case without having to write any code.

Leon Welicki

MSDN Magazine May 2010

Workflow Essentials: Collaborative Workflow Improvements in SharePoint 2010


In this article, the author covers the new features in SharePoint 2010 geared for workflow developers and then walks the reader through a couple of new user scenarios.

Paul Andrew

MSDN Magazine November 2009

Foundations: Workflow Services for Local Communication


This month's column describes how to use WCF for communication between a workflow and a host application in Windows Workflow Foundation 3. This knowledge should help developers with their efforts using WF3 and prepare them for WF4, where WCF is the only abstraction over queues (referred to as "bookmarks" in WF4) that ships with the framework.

Matthew Milner

MSDN Magazine November 2009

Foundations: Windows Workflow Design Patterns


Design patterns provide a common, repeatable approach to solving software development tasks, and many different patterns can describe how to accomplish a certain goal in code. When developers begin working with Windows Workflow Foundation (WF), they often ask about how to accomplish common tasks with the technology. This month's column discusses several design patterns used in WF.

Matthew Milner

MSDN Magazine August 2009

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend