vacoder
Process Pupil

The file '/_layouts/NintexWorkflow/ConfiguredOutcomePanel.ascx' does not exist

Jump to solution

We started to get this error on our SharePoint 2013 Farm when anyone clicks on a workflow Task item. It is happening on all of our sites. I have confirmed that the file is in the 15/templates/layouts/NintexWorkflow directory.

I attempted to retract and redeploy the solution but this did not change the matter.

Any ideas on how to go about resolving this?

Reply
4 Replies
francois
Forms Fledgling

Re: The file '/_layouts/NintexWorkflow/ConfiguredOutcomePanel.ascx' does not exist

Jump to solution

Do you have in the 14\TEMPLATE\LAYOUTS a Nintex directory?

0 Kudos
Reply
vacoder
Process Pupil

Re: The file '/_layouts/NintexWorkflow/ConfiguredOutcomePanel.ascx' does not exist

Jump to solution

Yes there was a directory there, albeit missing alot. What I ended up doing was removing Nintex completely (First the wsp files then from Programs) and reinstalling. The files were all put back in. Apparently when I retracted and removed a third party branded Nintex solution it removed core Nintex elements but failed to redeploy those bits when I redeployed the third party wsp.

0 Kudos
Reply
francois
Forms Fledgling

Re: The file '/_layouts/NintexWorkflow/ConfiguredOutcomePanel.ascx' does not exist

Jump to solution

Did you try to launch this PowerShell command: Install-SPSolution -Identity <Nintex solution> -GACDeployment -CompatibilityLevel AllVersions (deployement in 14 and 15 hive).

If the deployement failed, you can try to force installation (not the better practice but that can help sometimes to recover a stable plateform): Install-SPSolution -Identity <wsp solution> -GACDeployment -CompatibilityLevel AllVersions -Force.

View solution in original post

Reply
vacoder
Process Pupil

Re: The file '/_layouts/NintexWorkflow/ConfiguredOutcomePanel.ascx' does not exist

Jump to solution

Ah! That's good information and I would have saved me about 90 minutes late last night. Should it ever happen again I'll give that try. The powershell that the 3rd party vendor supplied did have the compatibilityLevel set to 14,15.

Reply