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; } } }

Invalid Workflow..

Rohan_t1

Hi All,

We are facing strange issue here today. None of our Workflows are working. With Submit/new job we get the error as attached. No Workflows have changed today.

We cannot view the Jobs from WorkFlow Tab and just shows a Error screen with no description.
Checking Properties of the asp files show I/O error.

I have checked the support article which indicates the possiblity of corrupted workflow store.

Can some one please suggest?

Thanks,
Rohan

Find more posts tagged with

Comments

Rohan_t1

Forgot to add..I am on TeamSite 6.5 SP1, Windows 2003

CRB

it looks like system resources issue. check disk space and maybe try rebooting the server if you dont see anything wrong.

Rohan_t1

it looks like system resources issue. check disk space and maybe try rebooting the server if you dont see anything wrong.

Since none of the Workflows are working, we took advice from Support and they feel that workflow folder under iw-store might be corrupt. We will carry out the steps so that workflow folder is created again(although we will be loosing the existing workflow jobs).

Will update with the result.

CRB

did u try what i suggested??

Rohan_t1

did u try what i suggested??

We had a check on the system resources and space but all seemed fine. We have just rebooted the server now with fresh workflow folder being created. However no workareas are visible. I checked iwtrace.log and it shows all the local domain groups being scanned.

Is this the reason we dont see any workareas as the information is still read?

CRB

did you delete the WF folder with Teamsite running or stopped?

i dont know why would your workareas not be visible after rebooting, if teamsite is running (able to login) then you should see your workareas unless something is wrong. i hope you have backups of your iwstore.

i wish you rebooted without deleting anything that might have fixed your issue without losing your old jobs.

Rohan_t1

did you delete the WF folder with Teamsite running or stopped?

i dont know why would your workareas not be visible after rebooting, if teamsite is running (able to login) then you should see your workareas unless something is wrong. i hope you have backups of your iwstore.

i wish you rebooted without deleting anything that might have fixed your issue without losing your old jobs.

I have checked iwstat and it shows store and workflow in running but i am not sure why workareas are not visible.

Adam Stoller

I have checked iwstat and it shows store and workflow in running but i am not sure why workareas are not visible.

I suggest you get on the phone with IWOV Support

Rohan_t1

Iw-mount has suddenly disappeared that is the reason we dont see any Workareas. Does it take time to load? iwtrace.log does not report any error. how come it would have disappeared.

I will call support now, but any pointers here are appreciated.

sridharg

The iw-mount sometimes disappears when the CPU goes 100% on the server box. As a result you dont see any Workarea and branch. It would be just blank. You have seek help with your server team to address the CPU issue and if possible add additional memory to your box.

Rohan_t1

The iw-mount sometimes disappears when the CPU goes 100% on the server box. As a result you dont see any Workarea and branch. It would be just blank. You have seek help with your server team to address the CPU issue and if possible add additional memory to your box.

Normal reboot of the server didnt help us here. We ran iwfsck and it reported few errors. Support feels some files might have been corrupted. Although this can be verfied once the xml file generated by running iwfsck is studied thoroughly.

But since it is production box and TS is not available(no workareas) we are thinking of using backup of iw-store which is backed weekly. I understand we might loose some data but this seems to be most feasible option.

Do we need to set the branch/workarea level permissions again? Submitted files will remain submitted as per Support.

Any thing which we need to be careful of?

CRB

Do we need to set the branch/workarea level permissions again? Submitted files will remain submitted as per Support.

i d say it depends how you take your backup and if you do anything with it. if you just take your backup and you never touch it, then all your permissions and history should be there... but if you touched the backup somehow then you might have to reset the permissions.

Any thing which we need to be careful of?

i suggest you save backup of your current iw-store that is giving trouble. that way if the issue turns out to be system issue (not iw-store issue), then you will have your latest work and you wont lose any data. GOOD LUCK!

Rohan_t1

i d say it depends how you take your backup and if you do anything with it. if you just take your backup and you never touch it, then all your permissions and history should be there... but if you touched the backup somehow then you might have to reset the permissions.

i suggest you save backup of your current iw-store that is giving trouble. that way if the issue turns out to be system issue (not iw-store issue), then you will have your latest work and you wont lose any data. GOOD LUCK!

Thanks for the reply..

yes we just take a backup of iw-store and we havent used it in anyway...

Yes we have also planned to take a backup of the existing iw-store so that if needed we can revert back to it again.

Will keep posted with the result.

Rohan_t1

Hi All,

Just to update on this issue, we have successfully restored iw-store from the backup. All the permissions luckily were same as before and we didnt had to reset them again.

We will be reviewing the errors from the output generated from running iwfsck and try to find the root cause of this error with the help of support.
Thanks to all for the suggestions.