SharePOint 2013: Updating an Item in SPD workflow by item ID

Dear all,
I have a scenario where I have to update another Item in another library using SPD.
How can i perform this, if i know the item ID of the target Item that i need to update.
Any help/guide would be greatly appreciated.
I am using sharepoint 2010 wflow.
Many Thanks & Regards
Vinay

Hi Vinay
 Whenever you are updating or using an item of some other list (on which the workflow is not running), then you need to have a column in that list whose value will match with the column of the item, on which the workflow is running. Now in your case,
both the lists (list1 and list2) must have a common column value for each list item
 Therefore, for that you need to use a column of an item in the other list whose value equals any of the column value of the item on which the workflow is running.
Please look into below link
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/MS-SharePoint/Q_28111331.html
Please mark it as answer if it has helped you
Amit Kotha

Similar Messages

  • Workflow in SharePoint 2013: Update item in list

    I have a task list where anyone can post a suggestion for a blog. There is a string field for the status.
    I have a library where the author can upload the blog article when ready to send for review. Uploading the document triggers the workflow to start. This document is reviewed twice and when the author is satisfied it will go for translation and then for web
    publication.
    All of this is worked out in the workflow except for one thing: I would like to update the task list at each stage of the process to the current status. Since it can all be done programmatically, I don't need to use a "choice" field. The string
    field would be just fine. One of the things I saw in my research is that "choice" fields won't update.
    I have put a lookup field in the blog article library to correspond with the title in the task list to create a relationship.
    First of all, is it possible to do to update a task from a document library, or am I just spitting in the wind? If so, why doesn't it work?

    which specific field you want to update after task approval. Did you create a content type based on workflow task (SharePoint 2013) and associated that particular content type with your task list?
    I repeat my question - do you want to update task list after the task execution or just after assignment?
    If its just after assignment then I think its not possible OOB and if its after the execution of the task then its doable OOB since there are two variables set as task out i.e. task outcome and TaskID (guid of the current task list item) and from that TaskID
    you can lookup the task list item and update any field.

  • SharePoint 2013 Update Workflow Manager problems after Service Pack 1

    Hello guys,
    I've installed the service pack 1 for SharePoint 2013 and then I tried to update the workflow manager, but I always get an error message that the workflow manager could not be updated!
    Is the installing order wrong? should I first install the update for the worklfow manager and then the update for SharePoint 2013?
    Best regards
    Matthias

    The error message see below for "Cumulative Update for Workflow Manager 1.0 (KB2799754)
    "One of the custom actions failed. The installation cannot continue. See log for details!"
    [06/06/14 09:48:44] Performing install.
    [06/06/14 09:48:44] At least one of the product packages has been detected.
    [06/06/14 09:48:44] preReqUpdateDisplayName is :
    [06/06/14 09:48:44]
    [06/06/14 09:48:44] Wizard mode on.
    The following products will be enhanced:
    Workflow Manager 1.0
    Attempting to open cached Msi package for product code: {04A7199E-565D-4654-88A3-80A9A7BADDD9}
    Successfully opened cached Msi package.
    [06/06/14 09:48:48] Opening Service Control Manager...
    [06/06/14 09:48:48] Operation succeeded.
    [06/06/14 09:48:48] Copying files...
    [06/06/14 09:48:48] Checking and creating target directory C:\ProgramData\Microsoft\E-Business Servers Updates\Updates\Uninstall2799754.
    [06/06/14 09:48:48] Package Workflow Manager Client 1.0 is not installed. Skipping it.
    [06/06/14 09:48:48] Package Workflow Manager Client 1.0 is not installed. Skipping it.
    [06/06/14 09:48:48] Package Workflow Manager 1.0 is installed.
    [06/06/14 09:48:49] Copying file AppServerV1-WorkflowManagerpatch30.msp ...
    [06/06/14 09:48:49] Operation succeeded.
    [06/06/14 09:48:49] Copying file AppServerV1-WorkflowManagerpatch30.msp ...
    [06/06/14 09:48:49] Operation succeeded.
    [06/06/14 09:48:49] Copying file TargetWFVersion.txt ...
    [06/06/14 09:48:49] Operation succeeded.
    [06/06/14 09:48:49] Copying file UnifiedWFHotfixUpgrade.PS1 ...
    [06/06/14 09:48:49] Operation succeeded.
    [06/06/14 09:48:49] Copying file Setup.xml ...
    [06/06/14 09:48:49] Operation succeeded.
    [06/06/14 09:48:49] Copying file Setup.exe ...
    [06/06/14 09:48:49] Operation succeeded.
    [06/06/14 09:48:49] Package Workflow Manager 1.0 is installed.
    [06/06/14 09:48:49] Package code is {04A7199E-565D-4654-88A3-80A9A7BADDD9}.
    [06/06/14 09:48:49] Executing preinstall custom actions. 1 actions to execute.
    [06/06/14 09:48:49] Starting process "C:\Windows\system32\..\sysnative\windowspowershell\v1.0\powershell.exe" -NoLogo -NonInteractive -NoProfile -WindowStyle Hidden -ExecutionPolicy RemoteSigned -File UnifiedWFHotfixUpgrade.PS1 -HotfixType "CS" -PackageType
    "server" -opcode "PatchBefore" -platform "x64" ...
    [06/06/14 09:48:50] Process exit code is -1.
    get-itemproperty : Cannot find path 'HKLM:\Software\Microsoft\Service Bus\1.0'
    because it does not exist.
    At C:\ProgramData\Microsoft\E-Business Servers
    Updates\Updates\Uninstall2799754\UnifiedWFHotfixUpgrade.PS1:971 char:21
    +   $sbinstallpath = (get-itemproperty "HKLM:\Software\Microsoft\Service
    Bus\1.0"  ...
    That's the log file
    Best regards
    Matthias

  • Javascript error after last sharepoint 2013 update : unable share single list element

    After yesterday update of SharePoint 2013 using Windows update we receive a JavaScript error when we try to share a single list element. Our IE is Italian the error is "Properties or field not inizialized"
    This is the user interface "hanged" and wait ....
    The problem not exist if we share an entire list or website.
    LSo Lorenzo Soncini Trento TN - Italy

    Hi Lorenzo,
    Glad that you solved the issue and thanks for sharing, this will benefit others who have similar issue.
    Regards,
    Daniel Yang
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Sharepoint 2013 - Group task assignment from a workflow

    I have designed a workflow, that can be started manually on a folder in SharePoint documents on a team site.
    I would like the workflow to start, assign a task to a SharePoint group, and then have that task show up in the members of that groups Outlook. 
    I am able to assign tasks to a single user and have the task show up in an outlook task list.
    However, when assigning to a SharePoint group, the tasks do not seem to show up in the outlook task lists.
    Is this an impossibility, or is there a way to make this work?
    Thanks,
    Products in Use:
    SharePoint Designer 2013
    Visio 2013
    (If needed I have visual studio, but would rather avoid it if possible. I am a programmer, but new to visual studio)

    Hi Brandon,
    If you are using “Start a task process” in workflow, please make sure that the “ExpandGroup” is Set to yes. Then the task will be generated for every member in the group. Please check if the task has been generated with members.
    Here are some settings you should ensure:
    All members have mailbox enabled in Exchange side.
    The setting for “task show up in an Outlook task list” is the same for all members.
    If it still doesn’t work, try it on SharePoint 2010 workflow. And also provide more information about your workflow and settings.
    Regards,
    Rebecca Tu
    TechNet Community Support

  • SharePoint 2013: Update User Profile Properties is giving error

    Hello all SharePoint Gurus - I am trying to update the User Profile Properties. The update I am trying is to
    Property Mapping for Synchronization.  Mapping mobile property of AD to the User Profile Property Mobile Phone.
    It is giving error "An Error occurred when updating a property". Check ULS is not showing any error. 
    The FIM Service, USer Profile Services and Synchronization Services all are in Started mode. Properly synchronizing with AD. 
    Please throw some light on this. 
    Regards,
    Khushi

    Hi Khushi,
    According to your description, my understanding is that you got an error when you make "Mobile Phone" map to "mobile" from AD properties.
    I did a test as your description, in my testing, everything worked well.
    Please try to stop User Profile Synchronization service and User profile service, then restart them, compare the result.
    There are some similar posts about this issue, pease check if they are useful for you:
    https://social.technet.microsoft.com/Forums/sharepoint/en-US/32937e1d-830e-4553-bdfc-23d3ee7f6d07/why-mapping-of-user-profile-property-fails
    http://sharepoint.stackexchange.com/questions/34634/mapping-user-properties-fails
    If this issue still exists, please check Windows Event Viewer to check there is something about this issue:
    How to use Windows Event Viewer:
    http://blog.credera.com/technology-insights/microsoft-solutions/troubleshooting-sharepoint-errors/
    Best Regards,
    Wendy
    Wendy Li
    TechNet Community Support

  • SharePoint 2013 Workflow Not Updating on Deployment

    Developing a 2013 Workflow on SharePoint 2013 using Visual Studio 2012, deploying workflow changes does not update the workflow that runs. This has already been posted on the SP 2013 dev forum, but I wanted to check here with the workflow folks. Anyone run
    into this issue before and/or have tips for solving?
    Thanks.
    http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/cd543a00-f3ab-4a4a-8682-b81d8330b677
    http://blog.randomdust.com

    This issue is reported and I'll post about it once I have an update.  For now to workaround this issue, you can try these steps
    Change the default deployment option to “No Activation”
    Retract the solution using Visual Studio
    Deploy the solution. This time feature will not be activated by default as we have changed to “No Activation”
    Open the SharePoint designer and click on the “Workflow”  section. You will see your workflow already present there. Delete the workflow which you have created.
    Activate the feature manually.
    Now you should see your updated version.
    Chandrasekar Natarajan

  • Fetching workflow status from Extended Properties in SharePoint 2013 sequential workflow (Farm solutions) option

    HI,
    I am using VS 2012, I have selected the option "sharepoint sequential workflow (Farm solution) option and not the workflow App model.
    Earlier in SharePoint 2010, the approver status column can be got from ExtendedProperties["TaskStatus"] and which contained either "#" or "@" as its value.
    However, in SharePoint 2013, the ExtendedProperties does not contain the "TaskStatus" key. In the quickwatch, i was able to see the value as "#" associated to some guid key. In the debug mode,i can see the below:
    (new System.Collections.Hashtable.HashtableDebugView(TaskPropertiesForManagerAfter.ExtendedProperties)).Items[12]
    But I’m not sure how to get to it from the code?
    How to retrieve the Task Status using ExtendedProperties in SharePoint 2013?
    Thanks

    Having problems getting SPD 2013 installed on my laptop because of a trial of O365, but I know in SPD 2010 you could find the BCC fields, etc... in the Advanced properties, it wasn't directly available via the common interface.  I know 2013 is very
    different from 2010, and if I can get it to install correctly, I will update, but look for an advanced property, or an XML view where you can find the FROM: field.

  • Button or checkbox to start a workflow in sharepoint 2013

    In my first project for SharePoint 2013, I want a workflow to be manually started by the user due to the way I am using the default buttons generated by SharePoint 2013.
    I would like the user manually be able to start a workflow by doing one of the following:
    1. click a button, or
    2. click a check box, or
    3. select an option button.
    Thus can you tell me how to 'wire together', connect one of the options I listed above to start a workflow manually?

    Midnight,
    THIS IS HOW WORKFLOW CAN BE STARTED MANUALLY
    Create a multiple value radio button column and name it WFStart
    Create a SPD workflow on item add and edit autometically
    Check WFStart value at to as Workflow start condition.
    If Yes, proceed with next stage
    If no stop the workflow
    See this link: Workflow
    conditions in SharePoint Designer : A quick reference guide
    Idea is to start workflow every time but only proceed when radio button column (WFStart) value if yes. No code implementation!
    Please 'propose as answer' if it helped you, also 'vote helpful' if you like this reply.

  • What Has Happened to Workflow in SharePoint 2013

    I am at a loss to get workflow 2013 to work with SharePoint 2013. I am astonished that workflow (other than the broken and buggy 2010 version) is not part of SharePoint 2013. What on earth were they thinking. as if that is not bad enough they have managed
    to break the installation of WorkFlow 2013. This has been reported numerous times by numerous people and needless to say the response from Microsoft has been complete silence.
    In desperation I have just created a virtual machine with 2012R2 standard edition. I have installed (using the SharePoint 2013 +sp1 disk) the SharePoint Prerequisites. Next I follow the link they have provided to "optional software" where it
    lists workflow manager. Instead of running an MSI or EXE they run the Web Platform Installer 5.0. After a bit of downloading and installing it tells me: "We're sorry. The following products have failed to install.
    Microsoft Windows Fabric V1 RTM
    This product did not install successfully: Invalid command line argument"
    So SharePoint 2013 doesn't have workflow and this bug has been present since it came out and the web is filled with people asking about it.
    Does anyone know how to fix this?

    Thank you for that. You missed my point. I don't care whether it is embedded in SharePoint or a separate system. What I care about is that the installation/configuration is not included in the SharePoint installation. It is an optional extra.
    We don't have to create the individual tables and databases in SQL and that is also a separate system. We don't have to configure IIS and that is a separate system so why is the installation and configuration of workflow not treated in the same way? That
    is what I was getting at.
    I most certainly have followed their instructions. Lets be honest they are very straight forward.
    Microsoft's instructions are clear:
    1. Download and run the Microsoft Web Platform Installer
    2. Type "workflow" in the search box.
    3. Click "Add" for the Workflow Manager V1 RTM
    4. Click "Install"
    Even if you download the workflowmanager.msi that just runs the web platform installer and searches for "workflow". Regardless of which you choose; now all you have to do is wait for the error message which comes shortly after this. I have just
    typed this from memory after several hours in the pub so it is not that difficult. If you would care to point out where I have not "specifically follow[ed] the directions" I would be most grateful.
    Now let me tell you what I have found. If I create a virtual machine with Windows 2012R2 and follow the instructions as outlined above it installs perfectly well. If I create another machine and install the SharePoint pre-requisites and then follow the instructions
    as outlined above it does not install at all. Do you think this is because I am not running the web platform installer correctly? My latest experiment is to install it first and then install SharePoint. That seems to hold some promise of actually working
    but if that works then the Microsoft installation instructions are wrong because they don't mention any of this until after SharePoint is installed.
    Looking at the response from Dai Webb below it would seem that there is quite a lot that needs to be done that isn't mentioned in any Microsoft instructions or anywhere else that I have found. Perhaps that is the problem but if it is how come all those organizations
    you mentioned have installed it? Did they know about this or is there yet another way of installing it?

  • Association Columns in Sharepoint 2013 Reusable Workflow

    at http://msdn.microsoft.com/en-us/library/jj728659.aspx it says Association columns are not available in Sharepoint 2013 Workflow 
    But http://msdn.microsoft.com/en-us/library/dn292551.aspx#bkm_07 is suggesting to use Association columns in Sharepoint Server 2013. Doesn't Sharepoint Server 2013 uses Sharepoint 2013
    Workflows?
    Cheers, IXI solution

    Hi,
    According to your description, my understanding is that you want to know if the Association Columns can be used in SharePoint 2013 workflow.
    Per my knowledge, the Association Columns feature is available only on the SharePoint 2010 Workflow platform.
    The article in the link
    http://msdn.microsoft.com/en-us/library/dn292551.aspx#bkm_07 introduces the best practices for developers using Visual Studio to create workflows in SharePoint 2013.
    We can create 2010 workflows in SharePoint 2013 and we can use the
    Association Columns feature in SharePoint 2010 workflows.
    We can also integrate features from the SharePoint 2010 Workflow platform into the new SharePoint 2013 Workflow platform.
    To do this, create a SharePoint 2010 Workflow by choosing the SharePoint 2010 Workflow platform; create a SharePoint 2013 Workflow by choosing the SharePoint 2013 Workflow platform; and then use the
    Start a list workflow and Start a site workflow actions in the SharePoint 2013 Workflow to call the SharePoint 2010 Workflow.
    If you have any questions, please feel free to reply.
    Thanks
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Sharepoint 2007 Sharepoint Designer Workflow migrate to Sharepoint 2013

     SharePoint 2007 sites migration to SharePoint 2013, in SP2007 I have several workflows created using SharePoint Designer. Is it possible to migrate those Workflows to SharePoint 2013? If so,  is SharePoint 2013 Workflow
    Manager needed to run those Workflows?
    BTW, I will be using third party migration tools to migrate SP2007 content to SP2013.

    Hi John
    I know one third party tool which is best in migration and it migrates designer workflows also
    http://en.share-gate.com/sharepoint-migration
    http://en.share-gate.com/
    Please mark it as answer if it helps you finding your answer
    Amit Kotha

  • AD security group issues in SharePoint 2013 Integrated Mode

    Hello,
    Sorry if this is the wrong forum, I'm not sure if this is a SharePoint issue or a Reporting Services configuration issue (or if it should be in a SharePoint forum regardless).
    I have SSRS2012 on SharePoint 2013 in integrated mode. We are doing item level permissions, which means we have an AD security group Reports-All with
    Read to the Reports document library, then each actual report has unique permissions. We have a report with the ProjectManagers AD
    security group on it with Read (plus some other stuff to let them manage subscriptions), and another AD security group ProjectUsers with
    just Read access so they can open the reports. The data source used by this report has the AD security group I mentioned before, Reports-All,
    with Read.
    At a SharePoint level, things appear to work. When a user in ProjectManagers or ProjectUsers browses
    to the library, they see only the 3 reports that those two security groups have permission to see (out of a lot more in the library). That means SharePoint is reading those security group memberships correctly as far as I can tell.
    The issue is when a user in ProjectManagers or ProjectUsers clicks
    on a report, they get a reporting server based error message, and the ULS logs have an error specific to the user trying to run the report.
    Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user 'MyDomain\MyUser' are insufficient for performing this operation. (Fault Detail is equal to Microsoft.ReportingServices.ServiceContract.RsExceptionInfo)
    If I add that specific user with Read permissions to the report and the data source, they are then able to run the report without errors. It seems like some Report Server component is not liking the fact that I'm using security groups. 
    Has anyone seen this behavior with AD security groups? Any ideas on why my environment does not want to work properly with those even though AD security groups are working fine for other non-Reporting Services files?
    Thanks,
    Aaron

    Hi aaronzott,
    According to your description, you configured SSRS 2012 of SharePoint integrated mode. You added read permission to reports and data source to AD security group Reports-All, then added just read permission to ProjectManagers and ProjectUsers groups. When
    users in ProjectManagers or ProjectUsers groups click report, the error message occurred. After you added Read permissions to the report and the data source to the groups, they can preview the report without errors.
    Report definition permissions are defined through List permissions on the library that contains the report, but we can set permissions on individual reports if we want to restrict access. Set properties on a report including data source connection information,
    processing options, and parameter properties. Edit Items on the library that contains the report or on the individual report. We also need to have view permissions on a shared data source (.rsds) to select it for use with the report.
    For more information about Set Permissions for Report Server Operations in a SharePoint Web Application, please refer to the following document:
    http://msdn.microsoft.com/en-us/library/bb326286(v=sql.110).aspx
    If you have any more questions, please feel free to ask.
    Thanks,
    Wendy Fu
    If you have any feedback on our support, please click
    here.

  • Update Column value after current item is Approved and then publish major version using Sharepoint 2013 designer workflow

    Hi,
    We have a requirement to update a column value once the item has been approved.
    Following settings have been made in the publishing articles list:
    Require content approval for submitted items : yes
    Create major and minor (draft) versions
    Who should see draft items in this document library? :Only users who can edit items
    Require documents to be checked out before they can be edited? : yes
    I have createdatu a Sharepoint 2013 workflow to check if Approval sts of current item = 0 i.e. Approved , then check out and update the item and finally checkin the item. Everything works fine till this point except that the minor version of the item is
    checked in. Due to this the updated columns are not published to others.
    Also, I created a Sharepoint 2010 workflow to SET CONTENT APPROVAL = APPROVED and started this workflow from my list workflow above, but the item does not get checked-in and always shows "In Progress" status with comment "The item is currently
    locked for editing. Waiting for item to be checked in or for the lock to be released.".
    Please let me know where I am missing out so that once the item is approved, column value gets updated and current item is still in Approved status.
    Thanks

    Hi,
    According to your post, my understanding is that you want to update Column value after current item is Approved and then publish major version using Sharepoint 2013 designer workflow.
    You will get into this kind of Catch-22 situation trying to set the Content Approval Status in SharePoint Designer workflow:
    - You must check out the document before you can change the Content Approval Status
             - You can't change the Content Approval Status once the document in checked out
    Since you set the Require documents to be checked out before they can be edited=Yes, you will need to check out the document when run the workflow on the item. But you cannot approve a document when it is checked
    out. So the logic in workflow conflicts.
    As a workaround, you can use the Start Another Workflow action to start the normal Approval workflow on the document.  The built-in Approval workflow can work with a document that’s not checked out.
    The designer approval workflow also can work with a document that’s not checked out.
    You can create two workflow using SharePoint Designer 2013.
    First, create a SharePoint 2010 platform workflow.
    Then, create a SharePoint 2013 platform workflow.
    Then when the SharePoint 2013 platform workflow start, it will start the SharePoint 2010 platform workflow to set content approval status, then the SharePoint 2013 platform workflow will update current item value.
    More information:
    SharePoint Designer Workflow Content Approval Issue
    SharePoint 2010 Approval Workflow with Content Approval
    Best Regards,
    Linda Li
    Linda Li
    TechNet Community Support

  • SharePoint 2013 Workflow (SPD 2013) fails for Active Directory Group members

    Hi
    I have a SharePoint 2013 site called "Team Meetings". There are a number of lists and an InfoPath form library.
    The site's SharePoint Group "Team Meeting Members" has two Active Directory groups (All Club Managers and All Club Police) as members. Those two AD groups contain all the people that I want to have  access to the library and list, except for
    a few additional folk who I have made individual members. 
    My PROBLEM:
    I  have created a SharePoint 2013 Workflow using SPD 2013 associated with the  Form Library. Workflow is set to start on new or modified item. The first action is to write to history list, then determine the status (Submitted or Pending) of
    the form and go to different Stages depending on that status.
    The workflow works perfectly for any user who has been added directly to the SharePoint group (Team Meetings Members) BUT FAILS at the very first action for anyone who is a member of one of the AD groups. I know the Workflow is fine because I've tested it
    with numerous people who are direct members of the SharePoint Group, but whenever a person who is a member of the AD group tries it the Workflow just fails.
    Here's a print of the info from the Workflow Status page (I don't have access to server logs):
    RequestorId: 4494760f-92ff-2e8c-90d2-cc7df0e6baa4. Details: System.ApplicationException: HTTP 401 {"Transfer-Encoding":["chunked"],"X-SharePointHealthScore":["0"],"SPRequestGuid":["4494760f-92ff-2e8c-90d2-cc7df0e6baa4"],"request-id":["4494760f-92ff-2e8c-90d2-cc7df0e6baa4"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"MicrosoftSharePointTeamServices":["15.0.0.4420"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1;
    RequireReadOnly"],"Cache-Control":["max-age=0, private"],"Date":["Mon, 10 Mar 2014 01:31:42 GMT"],"Server":["Microsoft-IIS\/8.0"],"WWW-Authenticate":["NTLM"],"X-AspNet-Version":["4.0.30319"],"X-Powered-By":["ASP.NET"]}
    The HTTP response content could not be read. 'Error while copying content to a stream.'. at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance
    instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor 
    Members of the SharePoint Group "Team Meetings Members" have Contribute Access to both the form library and another list that the workflow writes to as well as the Workflow History list (which in SP 2013 uses the credentials of the
    user who started the workflow, unlike 2010 which used System Account).
    All members of the Team Meetings Members group, whether they are individual members or part of one of the AD groups, have no problems opening and saving forms etc. It's just the Workflow that doesn't like them...
    I am stumped. I've spent many hours searching for a reason for this. There are about 200 people in the two AD groups so I really don't want to have to add them all individually - especially when these groups are managed in AD for a whole bunch of other reasons
    and using the AD groups means I'll basically never have to worry about modifying the SharePoint access permissions.
    Does anyone have any ideas why this is happening and what I can try to fix it?
    Mark

    Hi Lars,
    I'm afraid not so far but we are trying a few things today so I will post back with results.
    First thing we are doing is making the AD Group universal because one of our (external provider) gurus remembers seeing something about that. He also sent me a link to a post where they were talking about earlier
    versions but having similar issues and their solution was to make sure the app pool account has sufficient permissions in AD::
    http://social.msdn.microsoft.com/Forums/sharepoint/en-US/27a547da-5cc0-49d7-8056-6eb40b4c3242/failed-to-start-workflow-access-is-denied-exception-from-hresult-0x80070005-eaccessdenied
    This part of that thread looks interesting but we haven't checked it yet as were trying the universal setting first:
    "If the users participating in the workflows have been added to the SharePoint site via Active Directory groups, SharePoint has to update the user’s security token periodically by connecting to
    the domain controller. By default, the token times out every 24 hours. But if the application pool account did not have the right permissions on the domain controller to update the user’s token, user will keep getting the access denied error. The error was
    intermittent because when the user browsed to any page other than the workflow form, the token was getting updated successfully.
    You can try to fix it through granting the application pool account the appropriate permission by adding the account to the group “Windows Authorization Access Group” in Active Directory."
    I'll update when we try these ideas. If you have any luck please do the same.
    Mark
    (sorry about formatting - using my phone....)
    Mark

Maybe you are looking for