nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Submit to STAGING does not work after upgrade to 6.7

jornduff

We just upgraded from TeamSite 6.5 to 6.7. All workflows stopped working as a result. Specifically, files are not being submited to staging. Instead we get this error /default/main//STAGING is not a valid area; backing off locks in task. Is there something we are missing after the upgrade? We are running on a Solaris server. Any one out there with this problem?

Find more posts tagged with

Comments

nipper

That is strange, do you have locks=T after the submit task ?

or during ?

Adam Stoller

We just upgraded from TeamSite 6.5 to 6.7. All workflows stopped working as a result. Specifically, files are not being submited to staging. Instead we get this error /default/main//STAGING is not a valid area; backing off locks in task. Is there something we are missing after the upgrade? We are running on a Solaris server. Any one out there with this problem?

Who is the owner of the submittask in the workflow?
Does that user have the ability to login with Editor or higher privileges?
Did you make use of 6.7's custom roles and perhaps not enable the user to submit to staging?

jornduff

I do not have locks during submit or after submit.

The owner of the submittask is iw_user(translates to current logged in user). This user has all the privilages to log in. TeamSite 6.7 does not let you choose your role at log in like teamsite 6.5. Instead it uses roles that the user has been added to. I did notice thought in the iwevents.log that the role is missing. occasionall it would say master but for the most part it says unknown. This is new since the upgrade. FYI: when we converted, there was a script that TeamSite provided to migrate the old roles into their new format. Does the roles have anything to do with it?

Adam Stoller

I do not have locks during submit or after submit.

The owner of the submittask is iw_user(translates to current logged in user). This user has all the privilages to log in. TeamSite 6.7 does not let you choose your role at log in like teamsite 6.5. Instead it uses roles that the user has been added to. I did notice thought in the iwevents.log that the role is missing. occasionall it would say master but for the most part it says unknown. This is new since the upgrade. FYI: when we converted, there was a script that TeamSite provided to migrate the old roles into their new format. Does the roles have anything to do with it?

I'd assume the roles do have something to do with it - and you should probably go through the Administration tab in CCPro as a 'master' to check out / assign roles to your users. You might contact Support too, as they might be able to provide a better solution (I haven't had an opportunity to really work with 6.7 yet).

jornduff

Thanks. Will Do. Once I get the solution I will post it to the forum.

jornduff

Problem solved. It's a little embarrasing to say that the problem was only a permisions problem. Apparently the upgrade changed a dir within our processes that was out of TeamSite. The workflow was getting hung on this with no adequate error message. Thank all for your help.