To set the pretext
for this post. I've moved on from Applied Information Sciences (who recently
went through a couple rounds of 'down-sizing'), and am now with SM Consulting,
an SAIC owned company.
I've spent a large
part of the past 2 days chasing yet another mystery bug related to a SharePoint
workflow. One of my colleagues here was
trying to test a bit of new functionality in a custom workflow. Unfortunately, he wasn't able to get past the
association step. He was receiving a
"File not found" error message and the stack trace revealed that the
error occurred during the load procedure of some (unknown) assembly.
I still can't come
close to explaining at all why this is happening, but I can share a neat tool
that I used to diagnose the problem.
Perhaps I'm a bit behind the times, but this was my first attempt at
using the Fusion
Log Viewer to figure out what assembly was causing the problem. I spent a few minutes spinning my wheels
trying to get the app to show me anything, and then a came across this very
useful script from Travis
Illig. Using the script I was able
to get the viewer to capture all of the information I was looking for.
As it turns out, the
error was occurring while attempting to load the
Microsoft.Office.Workflow.Pages assembly, which is used in the OOTB custom
workflow association page (CstWrkflIP.aspx).
I have absolutely no idea why this was happening, but since the workflow
wasn't gathering any association data, I
just removed the AssociationUrl attribute from the workflow.xml file, ran an
iisreset, and. magic. We were then able
to associate the workflow without issue.
Feel free to chime
in here if anyone out there has a clue as to why we'd be seeing this problem
with association page…
jesse