Invalid workflow: XML parse error \iw-home\iw-perl\vendor\lib/XML/PArser.pm line 187

Hi,

When we are trying to execute the submit workflow the workflow is not getting instantiated and it throws the error:- Invalid workflow: XML parse error in WFworkflow.pm no element found at line1, column 0, byte -1 at \iw-home\iw-perl\vendor\lib/XML/PArser.pm line 187.lution:- I have also attached the error screenshot.

We followed the below solution but there is no luck to get the issue resolved. Has anyone have an idea how this can be fixed.

Solution proposed in old postings:-

Then it may be because the directory <iw-home>/ tmp/cci has been deleted.

The solution is to re-create the directory cci directory under <iw-home>/tmp.

You should also create an empty file called cci-OK-.txt under <iw-home>/tmp/cci.

Find more posts tagged with

Comments

Adam Stoller

This could be due to errors in your code that are causing compilation problems and bubling up with that error message.

Is this a WFT or a WFM?

I'm guessing WFT with embeded perl code - you'll have to spend time trying to debug your code - try to cut out as much of it as possible to see if you can get the workflow to instantiate, and then start adding it back in, in little steps, to see if you can identify when it breaks and then focus on that code.

adi_adi

Hi Ghoti,

Thanks for your time in going through this. This is just a normal "submit" workflow that comes up with the TS7 installation. If there were errors with code I wonder how the same submit workflow was running fine and stopped working suddenly. This is also not a newly built workflow. This issue was there yesterday both in Stage and Dev environments, Assumption is that in staging the issue got resolved (probably due to creation of "cci" directory and cci-ok text file). But in dev - the issue still is existing. There is an existing "cci" directory and txt file in Dev. I do not really want to conclude that this is the deciding parameter for the issue but it is the observation. There can also be difference between the environments. We have thought of approaching Autonomy support soon as this is not a developed workflow. Want to see if the issue gets fixed across devnet forum.Thoughts?

Thanks and regards,

Naveen

ghoti wrote:
This could be due to errors in your code that are causing compilation problems and bubling up with that error message.

Is this a WFT or a WFM?

I'm guessing WFT with embeded perl code - you'll have to spend time trying to debug your code - try to cut out as much of it as possible to see if you can get the workflow to instantiate, and then start adding it back in, in little steps, to see if you can identify when it breaks and then focus on that code.

Adam Stoller

Okay - I wasn't sure if this was an OOTB workflow or custom.

Did you check the permissions on:

IWHOME
IWHOME/tmp
IWHOME/tmp/cci

in comparison to the other server?

adi_adi

[tshost]/Users has access to read and execute. Is this sufficient or do we have to give Everyone read and execute (we are not comfortable though). What is the recommended permission setting on iw-home directory in windows.

Please advise.

ghoti wrote:
Okay - I wasn't sure if this was an OOTB workflow or custom.
Did you check the permissions on:
IWHOME
IWHOME/tmp
IWHOME/tmp/cci
in comparison to the other server?

Adam Stoller

You said that it's working on one server and not the other.

I said "in comparison to the other server" - i.e.: Compare the permissions on those folders on bother servers and identify the differences, if any. If there are differences, attempt to make those changes on the server where it is not currently working to see if that fixes the problem. If there are multiple permission differences between the two servers I would suggest that first you implement all the changes to see if that fixes the problem; if it does, then you have the option to back out individual changes and re-test to see if you can reduce the number of changes needed.

Frankly, giving Everyone read-execute permissions on those folders makes sense to me - for IWHOME/tmp (and below) they should probably have FULL permissions - it's a tmp directory, they should be able to write into it.

shameem

Ghoti,

we both work for same project.

We are on windows 2008, TS 7.3. I believe, Its a mere permissions issue. Few reasons

1. Workflow is teamsite default submit workflow (wft)

2. CCI solution provided in previous posts may not be valid as the our other environment does not have this at all but still working fine.

3. I am the master and having full permissions on the directory structure able to submit with the same workflow.

4. Tested with one user with full permissions on iw-home, submit workflow works

5. Tested with same user having read and exeecute only on iw-home, submit workflow doesnot work.

Being said that, requesting your inputs on the recommended permissions to set up on iw-home folder or any sub folders. I have seen posts asking to give everyone full permissions to folders which I believe is not a good solution from security point of view. But if thats way it works no other go.

Currently we have the following

Administrators - Full permissions,

[hostname]/Users with read permissions

I have added a test user with full permissions, submit workflow started working.

Downgraded the test user to readonly (read and execute) permissions, submit workflow NOT working.

so, what is expected by teamsite to run error free, please advise.

1. Which group I need to give permissions to have only teamsite users gets execute permissions. is [hostname]/Users not sufficient.

2. What is the receommended permissions is generally given on folders [iw-home]

3. Do I have to give permissions to whole iw-home and subdirs (or) any specific directories (lib/bin etc)so that they donot have any of these execute issues.

Basically I donot want to give all permissions on iw-home folder. If no standards, I have to do trail and error (each time I set it takes ~10mins). Please let me know if any standard is there.

nipper

You should not mess with the permissions as they were when they were installed. I see people do that and it is a mistake.

I suspect someone tried cleaning out iwhome/tmp and removed the cci folder. That must be restored with full control to everyone. Actually iwhometmp should have full control for everyone.

People change the permissions to allow developers to change files. That is a bad model. There are better ways to control things, I use a config branch and use OD to move files to iwhome. No permission changes are necessary

Rick Poulin

(echoing nipper's comments)

I don't know why you're repeating the questions of your coworker, because ghoti already gave you the answer. R+X should be fine on iw-home (Interwoven/TeamSite) except that all users need to be able to write to iw-home/tmp (Interwoven/TeamSite/tmp) and subfolders of that. And again, as ghoti already told you, if that doesn't work then just do the leg work and compare with the server that works!

The "recommended" perms is whatever it sets at install time. You shouldn't have had to mess with them in the first place, especially on a Windows box.

adi_adi

Thanks Ghoti/all for your kind interest to getting this resolved.

Thanks and regards,

Naveen

Adam Stoller

You're welcome - though I'm a tad bit upset that @rpoulin got the mark for solution instead of me :-)

shameem

Ghoti is right Naveen. Rpoulin scolded me well rather (just kidding) for giving extra details. Naveen, with the soution I found below, may be you can change the solution to my reply too :-).

Nopes change it to Ghoti, he deserves.

Any way here is the solution which worked (for future readers)

1. No need to give "Everyone" access any where. This is security issue as per my org security team.

2. There is a group [host]/Users which means only authenticated/authorized users of the system which should be given Read and execute permissions.

3. In addition to this there is special permissions given. You can edit the special permissions by going in to advanced section of the folder secutiry. Here allow "create files/write data"/"create folders/append data". Without these special permissions nothing works and I didnot investigate how much it differs from giving write permissions on the folder.

Hope this helps.

Rick Poulin

@ghoti I guess it's all in the formatting? Your answer had a distinct lack of bold text. Smiley Tongue

bkpark

it must Disable UAC AND REBOOT SYSTEM in windows 2008 r2 x64.

thanks
BK