%3CLINGO-SUB%20id%3D%22lingo-sub-509927%22%20slang%3D%22en-US%22%3ESharePoint%20Designer%202013%3A%20Unexpected%20Error%20on%20server%20associating%20the%20workflow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-509927%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20TECHNET%20on%20Sep%2010%2C%202014%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CP%3EThis%20post%20is%20a%20contribution%20from%20Raghavendra%20Nanjaiah%2C%20an%20engineer%20with%20the%20SharePoint%20Developer%20Support%20team%3C%2FP%3E%0A%20%20%3CP%3E%3CB%3E%20What%20is%20the%20issue%3F%20%3C%2FB%3E%3C%2FP%3E%0A%20%20%3CP%3EWhen%20you%20try%20to%20publish%20the%20SharePoint%202010%20reusable%20or%20list%20workflow%20on%20SharePoint%202013%20platform%20using%20SharePoint%20designer%202013%20you%20will%20get%20following%20exception%20in%20UI%3C%2FP%3E%0A%20%20%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F111564iB79F7D3253802E48%22%20%2F%3E%3C%2FP%3E%0A%20%20%3CP%3EIf%20you%20carefully%20observe%20the%20ULS%20logs%3C%2FP%3E%0A%20%20%3CP%3E08%2F22%2F2014%2016%3A17%3A53.40%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20w3wp.exe%20(0x2610)%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%200x05D4%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20SharePoint%20Foundation%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Legacy%20Workflow%20Infrastructure%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20xmfh%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Medium%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Workflow%20Compile%20Failed%3A%20Could%20not%20find%20a%20part%20of%20the%20path%20'C%3A%5CUsers%5Cdevapppool%5CAppData%5CLocal%5CTemp%5Ccjjkiult.tmp'.%20b118b19c-3fad-30ad-ac8b-ed8c02395742%3C%2FP%3E%0A%20%20%3CP%3E%3CB%3E%20Why%20we%20face%20this%20issue%3F%20%3C%2FB%3E%3C%2FP%3E%0A%20%20%3CP%3EDuring%20the%20workflow%20publishing%20phase%2C%20SharePoint%20will%20create%20couple%20of%20temporary%20files%20under%20the%20temp%20folder%20(of%20the%20app%20pool%20service%20account).%20As%20part%20of%20clean-up%20process%20w3wp%20process%20will%20delete%20this%20files%20later.%3C%2FP%3E%0A%20%20%3CP%3ESometimes%2C%20instead%20of%20deleting%20content%20inside%20temp%20folder%20w3wp%20process%20deletes%20the%20temp%20folder.%20Because%20of%20which%20workflow%20publishing%20fails%20with%20%E2%80%9CCould%20not%20find%20a%20part%20of%20the%20path%E2%80%9D%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3CB%3E%20How%20to%20work%20around%20this%20issue%3F%20%3C%2FB%3E%3C%2FP%3E%0A%20%20%3CP%3ECreate%20a%20text%20file%20and%20provide%20read%20only%20access%20to%20file.%20This%20will%20stop%20process%20from%20deleting%20temp%20folder.%3C%2FP%3E%0A%20%20%3CP%3E1.%20Navigate%20to%20C%3A%5CUsers%5C%3CSERVICE-ACCT%3E%5CAppData%5CLocal%5CTemp%20on%20both%20the%20server%20(WFE1%20and%20WFE2)%3C%2FSERVICE-ACCT%3E%3C%2FP%3E%0A%20%20%3CP%3E2.%20Create%20a%20text%20file%20inside%20the%20temp%20folder%20and%20in%20the%20properties%20check%20read-only%20option.%3C%2FP%3E%0A%20%20%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F111565i23B6BFFF12FE2595%22%20%2F%3E%3C%2FP%3E%0A%20%20%3CP%3E3.%20Reset%20iis%20%2Fnoforce%3C%2FP%3E%0A%20%20%3CP%3E4.%20Publish%20the%20workflow.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%0A%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-509927%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20TECHNET%20on%20Sep%2010%2C%202014%20This%20post%20is%20a%20contribution%20from%20Raghavendra%20Nanjaiah%2C%20an%20engineer%20with%20the%20SharePoint%20Developer%20Support%20team%20What%20is%20the%20issue%3F%20When%20you%20try%20to%20publish%20the%20SharePoint%202010%20reusable%20or%20list%20workflow%20on%20SharePoint%202013%20platform%20using%20SharePoint%20designer%202013%20you%20will%20get%20following%20exception%20in%20UI%20If%20you%20carefully%20observe%20the%20ULS%20logs%2008%2F22%2F2014%2016%3A17%3A53.%3C%2FLINGO-TEASER%3E
Microsoft
First published on TECHNET on Sep 10, 2014

This post is a contribution from Raghavendra Nanjaiah, an engineer with the SharePoint Developer Support team

What is the issue?

When you try to publish the SharePoint 2010 reusable or list workflow on SharePoint 2013 platform using SharePoint designer 2013 you will get following exception in UI

If you carefully observe the ULS logs

08/22/2014 16:17:53.40          w3wp.exe (0x2610)      0x05D4            SharePoint Foundation      Legacy Workflow Infrastructure           xmfh    Medium           Workflow Compile Failed: Could not find a part of the path 'C:\Users\devapppool\AppData\Local\Temp\cjjkiult.tmp'. b118b19c-3fad-30ad-ac8b-ed8c02395742

Why we face this issue?

During the workflow publishing phase, SharePoint will create couple of temporary files under the temp folder (of the app pool service account). As part of clean-up process w3wp process will delete this files later.

Sometimes, instead of deleting content inside temp folder w3wp process deletes the temp folder. Because of which workflow publishing fails with “Could not find a part of the path”

How to work around this issue?

Create a text file and provide read only access to file. This will stop process from deleting temp folder.

1. Navigate to C:\Users\<service-acct>\AppData\Local\Temp on both the server (WFE1 and WFE2)

2. Create a text file inside the temp folder and in the properties check read-only option.

3. Reset iis /noforce

4. Publish the workflow.