Workflow works in Site Collection root, but not subsites.

Due to my OOB workflows not running due to being run by 'System Account' (Failed on Start), I have created a basic custom approval workflow.

If I use this on any list or library within the root of the site collection, it works fantastic.
However, when I apply this to a subsite somewhere, the workflow starts, but when they go in to approve the task, they get the error:

A form template (.xsn) file cannot be accessed. You may not have the required permissions to open the file.

Following the correlation ID, I get the following:

Name=Request (GET:http://t-room:80/functions/ftandt/apar/_layouts/WrkTaskIP.aspx?List=2657d5f1%2Dc0d9%2D4f46%2Da147%2D5870c89a572e&ID=11&Source=http%3A%2F%2Ft%2Droom%2Ffunctions%2Fftandt%2Fapar%2F%5Flayouts%2FWrkStat%2Easpx%3FList%3D2a6fdd7d%2De970%2D47d7%2D8c46%2D499440f3ccfe%26WorkflowInstanceID%3D%257b1EE4594B%252d04A3%252d493C%252d8E90%252d547B3020D5AE%257d&IsDlg=1&Web=cdc186fb%2D3324%2D4f59%2D8a78%2D5c85a6ceeb6d)

Site=/

Setting [Display] as the FormContext.FormMode for the current page

Cannot open file "Workflows/Test Approval/Approval Workflow Task _x0028_en-US_x0029_ Copy.xsn".

The XSN is null and its not a cross server issue. Most likely a permission issue

The XSN is null after attempting to get it from SiteAndWebCache

Leaving Monitored Scope (Request (GET:http://t-room:80/functions/ftandt/apar/_layouts/WrkTaskIP.aspx?List=2657d5f1%2Dc0d9%2D4f46%2Da147%2D5870c89a572e&ID=11&Source=http%3A%2F%2Ft%2Droom%2Ffunctions%2Fftandt%2Fapar%2F%5Flayouts%2FWrkStat%2Easpx%3FList%3D2a6fdd7d%2De970%2D47d7%2D8c46%2D499440f3ccfe%26WorkflowInstanceID%3D%257b1EE4594B%252d04A3%252d493C%252d8E90%252d547B3020D5AE%257d&IsDlg=1&Web=cdc186fb%2D3324%2D4f59%2D8a78%2D5c85a6ceeb6d)). Execution Time=139.885097128266

Open in new window


The permissions looks fine, and it works on the root, I'm thinking that the path "Workflows/Test Approval/Approval Workflow Task _x0028_en-US_x0029_ Copy.xsn" is not checking back to the root, but trying to find the globally published workflow within it's ftandt/apar/ subsite.
LVL 4
techvagabondAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
techvagabondConnect With a Mentor Author Commented:
This may have been due to the workflow being associated with the list within SPD.
I don't recall doing it, but when I duplicated the workflow, and renamed the approval tasks within it, I published globally, and all was well with the world.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.