One of the SharePoint farms we’ve built recently runs on Windows Server 2008 and SQL Server 2008. As usual, the installation is a least privileged account setup, with individual accounts running the various services and app pools. The farm is also patched to the latest level. We’ve experienced one or two issues with …

I've recently been investigating a rather curious problem we've been experiencing with deployment of the Digital Signature ActiveX Control from SharePoint 2007 to browsers. First a little background: A number of workflows we've developed recently make use of the capability of InfoPath forms to incorporate sections that …

This is handy. SharePoint helpfully populates the meta data with the GUID of the list and the ID of the item a WF instance is associated with. These are stored in "ows_WorkflowListId" and "ows_WorkflowItemId" fields on the task list item. An example of using this is from an InfoPath form in the form …

The reason the Office Sharepoint Server Workflow Task is not visible is because it is assigned to a special group named "_Hidden" which precludes it from being displayed in the site collection content type view. As it turns out content types are exposed and manipulable through the Sharepoint OM using the …

We have a workflow that is a mix of simple tasks and MOSS infopath forms server workflow tasks. To that end we remove the TaskListContentTypeId from workflow.xml and use the CreateTaskWithContentType shape to manually set the content type on appropriate tasks. This works fine until we come to deploy on a fresh …