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

Question

Question

Save to Repository Task - Invalid Settings / Form No Longer Exists

asked on June 12, 2017

Hello,

I'm experiencing an issue where my Save to Repository tasks display an error when the activity is opened. 

When initially set up, the repository is verified successfully and all archiving works as designed.  When I attempt to update the task (to direct archiving to a live folder, and not a testing folder) it displays the error.  This requires me to completely re-establish the archiving (file name, location, metadata). There doesn't seem to be any reason why it's displaying this error, the repository verifies again immediately, without making any changes.

I don't understand what's causing the issue - the form does still exist, so the error doesn't seem to be accurate.

What's causing this?

LF Error.jpg
LF Error.jpg (37.14 KB)
0 0

Replies

replied on January 5, 2021

Hi all - I just came across this issue today, and found that nothing above fixed it for me. 

 

My use case was the same as Melissa's above - the same error message when trying to use the Forms 'Save to Repository' task, with the same message when attempting to set the connection profile.

 

My issue turned out to be that I'd accidentally set the 'forms' service account user in LFDS to have a password expiry, and it had expired (so LF was thinking that 'user' had to change passwords). Removing that (or alternatively changing the password!) caused it to work perfectly again.

 

Just thought I'd post this here in case others have this issue.

2 0
replied on June 12, 2017 Show version history

I haven't run into this in Forms, but I've seen something similar happen in Workflow where it occasionally thinks an activity no longer exists.

Try setting it to a different form/step, saving the changes, then setting it back to the one you want.

Random thought, does the account you're using in the connection profile have the same permissions in both folders?

0 0
replied on August 11, 2017

What version of Forms are you using? Did you run into same issue again? If you can recall the actions that you did after load the process diagram page and before the error appear, then it will help us to trouble shooting what may cause this.

0 0
replied on June 26, 2019

I had this same issue and it was driving me nuts.

The resolution, for anyone else seeing this post, was just what @████████ suggested. 

Most of our permissions in our repository are inherited from the folders above, and our system user that is used by Workflow and Forms is granted full permissions at the highest level folder, so that inherits all the way down to everything - or I thought it was everything.  Turns out that this one particular folder had been flagged to NOT inherit permissions, and instead set them individually, and the system user hadn't been granted access.

That wasn't apparent by the errors I was receiving, the suspended task was telling me it failed to authenticate; and when setting up the process, I was getting a similar error to what @████████reported.

Once I'd granted full permissions for that folder to the system user, the process worked as expected.

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

Sign in to reply to this post.