You are viewing limited content. For full access, please sign in.

Question

Question

Workflow "Could not find a part of the path "C:\Users\UserName\AppData\Local\Temp\2\........" error

asked on July 10, 2017 Show version history

Hi,

I came across the following issue at one of my clients env. Thankfully it occured while building the 1st workflow.

Error : Workflow "Could not find a part of the path "C:\Users\UserName\AppData\Local\Temp\2\........" error
This was displayed on Rule Manager tab of workflow designer.(Workflows frame as well as scheduler frame)

Initial investigation : 
The folder '2' in the path doesnot exist.
Bad data on forms server manager
 
Workflow Designer Version 10.2

I went about doing the entire exercise of uninstalling existing workflow and re-configuring everything from scratch including creating new workflow database and all the workflow related configurations. It dn't solve the issue thou. 

Issue was resolved by creating a folder named "2" in the path.

It would be great if I could have some information on why this occurred in the 1st place and the steps that I followed (123532) for resolution is correct.

Thank you,

Bipin Nambair

2 0

Replies

replied on July 11, 2017

The Designer uses the TEMP system variable for temporary files. We're not sure at this point why, in some cases, Windows gives that value but does not actually create the folder or allows it to be created on-demand. It's a workstation-side issue so reinstalling Workflow is not expected to make any difference (as you found out).

What does "Bad data on forms server manager" mean?

1 0
replied on July 11, 2017

Thank you for the information Miruna.

"Bad data on forms" error popped up when I tried to configure forms server manager in Laserfiche workflow. My workflow has Retrieve Business Process Variables component in it. Once the "could not find path error" surfaced, I was testing on external data sources and manage servers (forms) on lf workflows. On testing forms manage server, "Bad data on forms" came up.

0 0
replied on July 11, 2017 Show version history

Hi Bipin!

I encountered the same error a couple of days ago when working in the Workflow Administration Console (10.2) and shortly after, encountered an error in SQL Express on the same server.  The reason for the SQL error was due to the temp files being cleaned up by the system and the resolution was to log out of Windows and back in again.  That sorted the issue in SQL and I found I was no longer getting the error in the Workflow Admin Console.  I got the error in Workflow again the following day, so logged out and back in again and it was sorted again.  I'm not sure what's going on with the temp files, but that seemed to be the fix.  Hopefully this helps in your case.

Cheers,

Mike

1 0
replied on July 11, 2017

Thank you for the info, Mike. Now it make sense as few days back I did the same and it worked (login /logout). Again, I had the same come up yesterday and wanted to get to the bottom of it, but couldn't. Then, saw the post of adding that particular folder on Username/appdata/temp path and it worked.

0 0
replied on September 15, 2017

I have 2 customers experiencing this issue. Adding the missing folder corrects the issue, however, the same problem continues to happen, seems to be daily.  Each day , I get the same failure when I try to start Workflow Designer.  The “1” folder that I created the day before is gone.  If I create it again, I can open Designer and get on with life.  So, not a major issue yet, but inconvenient and suggests that something is corrupt or at least buggy.

 

Is there a config or “.ini” entry or something where I can mod the TEMP pointer?  Any other info that suggests it is being fixed in a future build?

1 0
replied on October 14, 2020

I experienced the same issue today on a 10.4 system.  Using the above work around did the trick for today.  We will see if the issue persists.

0 0
replied on September 30, 2024

I had this today on our dev workflow server.  First time ever.  I created the folder as recommended, and it did resolve the issue.

Thanks for this post.

Christine

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.