Hello,
I'm using Windows SharePoint Services 3 and SharePoint designer 2007. I've set up forms authentication and it works fine however, custom workflows fail now when attempting to set the "assigned to" field when creating a new task. For example, a user fills out a custom list and one of the fields is a person or group. When the user selects a person and submits the form it should create a new task and assign it to the person selected in the previous step. The error logged in the workflow history is "unexpected error". If I remove the "assigned to" field from the workflow then it completes successfully.
Here is the entry from the C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12 log:
System.Workflow.Runtime.Hosting.PersistenceException: Invalid data has been used to update the list item. The field you are trying to update may be read only. ---> Microsoft.SharePoint.SPException: Invalid data has been used to update the list item. The field you are trying to update may be read only. ---> System.Runtime.InteropServices.COMException (0x80020005): Invalid data has been used to update the list item. The field you are trying to update may be read only. at....
I've confirmed that this problem only occurs when trying to assign the task to a person within the custom membership provider. If I modify the workflow to assign the task to a local user then it works fine. Additionally, if I pass the value to a single line text field then the workflow will complete and set the value to membershipprovider:[USER] where [USER] is the username of the correct person. If I edit the newly created task and set the Assigned to field to membershipprovider:[USER] it will assign the task to the correct person.
I googled the error and there was a hotfix released for wss2 that was then distributed with wss sp2. Perhaps the error has been reintroduced in wss3. I downloaded and installed all available patches from MS with no change.
Any help is greatly appreciated (please don't bash me for cross posting - the other post has gotten stale with no answer).
Thanks!
Justin
I'm using Windows SharePoint Services 3 and SharePoint designer 2007. I've set up forms authentication and it works fine however, custom workflows fail now when attempting to set the "assigned to" field when creating a new task. For example, a user fills out a custom list and one of the fields is a person or group. When the user selects a person and submits the form it should create a new task and assign it to the person selected in the previous step. The error logged in the workflow history is "unexpected error". If I remove the "assigned to" field from the workflow then it completes successfully.
Here is the entry from the C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12 log:
System.Workflow.Runtime.Hosting.PersistenceException: Invalid data has been used to update the list item. The field you are trying to update may be read only. ---> Microsoft.SharePoint.SPException: Invalid data has been used to update the list item. The field you are trying to update may be read only. ---> System.Runtime.InteropServices.COMException (0x80020005): Invalid data has been used to update the list item. The field you are trying to update may be read only. at....
I've confirmed that this problem only occurs when trying to assign the task to a person within the custom membership provider. If I modify the workflow to assign the task to a local user then it works fine. Additionally, if I pass the value to a single line text field then the workflow will complete and set the value to membershipprovider:[USER] where [USER] is the username of the correct person. If I edit the newly created task and set the Assigned to field to membershipprovider:[USER] it will assign the task to the correct person.
I googled the error and there was a hotfix released for wss2 that was then distributed with wss sp2. Perhaps the error has been reintroduced in wss3. I downloaded and installed all available patches from MS with no change.
Any help is greatly appreciated (please don't bash me for cross posting - the other post has gotten stale with no answer).
Thanks!
Justin