Slinger's Thoughts

March 4, 2009

Out of the Box workflows don’t work once completed?

Filed under: SharePoint — slingeronline @ 1:25 pm

Well here’s a stumper.  This was first noticed on our development server.  I had set up a document library with the routing workflow feature activated.  And then ran the collect feedback workflow on a document I had uploaded.  It worked great, sending e-mails, notifying users an all.  Once it was completed, however, trouble began.

When a user clicked on the workflow progress link, (you know, the column that has the same name as the workflow that says “In Progress,” “Completed,” “making coffee” or whatever the status of your workflow is to view the history.  I clicked on the item to view the completed workflow.  After all, if I collect feedback from a user, it would be nice to see all of that feedback once completed.  It starts to load and then I get an error message.

ScreenHunter_01 Mar. 04 12.13

Oh, something probably burped, I can try again.  So I click “Try again.”  After clicking it 37 times, it occurs to me that something may be amiss. I try to do the same thing from the server itself and I get one more option. “Show error details.”  That should be helpful.

Then again not so much.  here are the contents of the error details.

‘ows_TaskStatus’ is a duplicate attribute name. Line 35, position 276.

System.Xml.XmlException: ‘ows_TaskStatus’ is a duplicate attribute name. Line 35, position 276.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.AttributeDuplCheck()
at System.Xml.XmlTextReaderImpl.ParseAttributes()
at System.Xml.XmlTextReaderImpl.ParseElement()
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlTextReader.Read()
at System.Xml.XmlReader.MoveToContent()
at Microsoft.Office.Workflow.IPPage.PopulateDataObject(DataSource dataSource, String xml)
at Microsoft.Office.Workflow.WrkTaskIPPage.XmlFormControl_Initialize(Object sender, InitializeEventArgs ea)
at Microsoft.Office.InfoPath.Server.Controls.XmlFormView.OnInitialize(Dictionary`2 intputParameters)
at Microsoft.Office.InfoPath.Server.DocumentLifetime.Document.LoadSolutionAndDocument(HttpContext context, Solution solution, DocumentMetaInformation documentMetaInformation, OnInitializeCallback onInitializeCallback, OpenParameters openParameters)
at Microsoft.Office.InfoPath.Server.DocumentLifetime.Document.OpenDocumentWithSolution(HttpContext context, SPSite contextSite, Solution solution, DocumentMetaInformation documentMetaInformation, OnInitializeCallback onInitializeCallback, OpenParameters openParameters)
at Microsoft.Office.InfoPath.Server.DocumentLifetime.Document.NewFromSolution(HttpContext context, SPSite contextSite, Solution solution, DocumentMetaInformation documentMetaInformation, Boolean disableFirstRequestOptization, OnInitializeCallback onInitializeCallback, OpenParameters openParameters)
at Microsoft.Office.InfoPath.Server.Controls.XmlFormView.DataBindInternal(SolutionMetaInformation solutionMetaInformation, DocumentMetaInformation documentMetaInformation, String absoluteSolutionLocation, Boolean hasCloseHandler, Document& document)
at Microsoft.Office.InfoPath.Server.Controls.XmlFormView.StartNewEditingSession()
at Microsoft.Office.InfoPath.Server.Controls.XmlFormView.EnsureDocument(EventLogStart eventLogStart)
at Microsoft.Office.InfoPath.Server.Controls.XmlFormView.<>c__DisplayClass3.<LoadDocumentAndPlayEventLog>b__1()
at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock)

I google the first line of that, and I see that two other users have had the same issue, but no one has a solution.  I go through the troubleshooting steps I know, including rebuilding the whole damned server from scratch. (Fortunately, being a development server, nothing vital gets stored there.)  And even after all of that, I get the same error.  If I click “Close” then I get the ever helpful message that the form has been closed. Still doesn’t help me as I cannot view the contents of the form which is kind of the point of having the collect feedback and approval workflows to begin with. 

So I’m off into the SharePoint logs.  Nothing. Logging is turned on right? Yes.  Hrrm.  Off into the Event Viewer logs.  There’s a new one. (I filter the view because I really don’t care that everything is working right.)  There is a lone error message.  Contents of which are below.

Event Type:    Error
Event Source:    Office SharePoint Server Error Reporting
Event Category:    None
Event ID:    5000
Date:        3/4/2009
Time:        11:41:07 AM
User:        N/A
Computer:    MOSS-DEV
Description:
EventType ulsexception12, P1 w3wp.exe, P2 6.0.3790.3959, P3 45d6968e, P4 system.xml, P5 2.0.0.0, P6 492b8670, P7 1729, P8 39, P9 xmlexception, P10 8gec.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 006c0075 00650073 00630078 00700065
0010: 00690074 006e006f 00320031 0020002c
0020: 00330077 00700077 0065002e 00650078
0030: 0020002c 002e0036 002e0030 00370033
0040: 00300039 0033002e 00350039 002c0039
0050: 00340020 00640035 00390036 00380036
0060: 002c0065 00730020 00730079 00650074
0070: 002e006d 006d0078 002c006c 00320020
0080: 0030002e 0030002e 0030002e 0020002c
0090: 00390034 00620032 00360038 00300037
00a0: 0020002c 00370031 00390032 0020002c
00b0: 00390033 0020002c 006d0078 0065006c
00c0: 00630078 00700065 00690074 006e006f
00d0: 00380020 00650067 000d0063 000a

Another Google search, and no help there either.  Nothing on technet, MSDN, Microsoft Communities Forums, my yahoo group. Seems that this is rare enough that no one has an answer. I leave it to you, my fellow readers to try and find a solution to this one.  I will keep searching, and rest assured when I find an answer, I will update this post with the solution.

Update:

I found out what the issue was.  On my site I had a tasks list, and the workflows would select this task list to track changes.  It turns out that this is a bad idea.  When using these workflows, go ahead and select “create a new task list” when selecting a task list to track the workflow.  Making this change allows SharePoint to set up an appropriate task list with all of the required columns and no duplicates, which will prevent the issue mentioned above.  Hope this helps.

Advertisements

1 Comment »

  1. I am having the same problem… anyone able to offer any guidance?

    Comment by John — May 8, 2009 @ 1:03 pm


RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Blog at WordPress.com.

%d bloggers like this: