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

I've got invalid workflow error

khak

I have got workflow error when i submit my job.

Invalid workflow:
XML parse error in WFworkflow.pm:
no element found at line 1, column 0, byte-1 at c:\iw-home\iw-perl\vendor\lib/XML/Parser.pm line 187

Pls help me.
Thanks

Find more posts tagged with

Comments

ISCBorisB

I have got workflow error when i submit my job.

Invalid workflow:
XML parse error in WFworkflow.pm:
no element found at line 1, column 0, byte-1 at c:\iw-home\iw-perl\vendor\lib/XML/Parser.pm line 187

Pls help me.
Thanks

Your WFT File is mal-formed

nipper

You can also get that error if you put an & in the comment
and are not encoding the comment as you insert it in the XML

kaalraa

I have got workflow error when i submit my job.

Invalid workflow:
XML parse error in WFworkflow.pm:
no element found at line 1, column 0, byte-1 at c:\iw-home\iw-perl\vendor\lib/XML/Parser.pm line 187

Pls help me.
Thanks

Either post your WFT or try to debug the parsing error by using any GUI tool or Internet explorer.

ACheethayil

XML parse error in WFworkflow.pm
no element found at line 1, column 0, byte -1 at c:\iw-home\\iw-perl\site\lib/XML/Parser.pm line 185

Then it may be because the directory / tmp/cci has been deleted.

The solution is to re-create the directory cci directory under /tmp.
You should also create an empty file called cci-OK- under /tmp/cci.

In Windows, the group Everyone should have full control to this directory and
the file. In Unix, the directory should have a mode of 1777 and the file 0666.

Another reason for this error might be because you do not have <%SystemRoot%\system32;%SystemRoot%> in the system environment. Add this as the first argument in the PATH variable.

ISCBorisB

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

Do you really think that every and all WFT Instantiation problems are caused by deleted temp/cci Directory?
This particular one is Parser notification of malformed Job Specs XML. It *may* had been caused by unavailable cci
directory but it is much more probable that it was simply bad XML.

Besides, this whole thread is more than a year old.

jagadesh

Do you really think that every and all WFT Instantiation problems are caused by deleted temp/cci Directory?
This particular one is Parser notification of malformed Job Specs XML. It *may* had been caused by unavailable cci
directory but it is much more probable that it was simply bad XML.

Besides, this whole thread is more than a year old.

Other than disk space issue what are the constraints will create workflow instantiation error. No code change happen recently(available_templates.cfg,wft .....). Suddenly we are facing this issue.

Is anybody faced this issue before?

Error Message popup window
[html]
Invalid workflow:
XML parse error in WFworkflow.pm:
no element found at line 1, column 0, byte-1 at c:\iw-home\iw-perl\vendor\lib/XML/Parser.pm line 187

[/html]

ISCBorisB

Other than disk space issue what are the constraints will create workflow instantiation error. No code change happen recently(available_templates.cfg,wft .....). Suddenly we are facing this issue.

Is anybody faced this issue before?

Error Message popup window
[html]
Invalid workflow:
XML parse error in WFworkflow.pm:
no element found at line 1, column 0, byte-1 at c:\iw-home\iw-perl\vendor\lib/XML/Parser.pm line 187

[/html]

Set WFT Debug Mode, generate Job Specifications and attach resulting XML to the post.
Something did change. If it's not wft then it may be code, data, environment, access
and whatnot that wft uses to build specs

nipper

Is anybody faced this issue before?

Error Message popup window
[html]
Invalid workflow:
XML parse error in WFworkflow.pm:
no element found at line 1, column 0, byte-1 at c:\iw-home\iw-perl\vendor\lib/XML/Parser.pm line 187

[/html]

Many possibilities.

Run it in debug mode and post the XML

nipper

BTW, I *just* had this happen (all WFTs) openjms was 65GB and filled the disk. Another possibility

jagadesh

BTW, I *just* had this happen (all WFTs) openjms was 65GB and filled the disk. Another possibility

Thanks for all your replies. Problem got resolved. Suddenly most of workflows didnt initiated two days back, now got resolved without doing any fix. We are analysing the root cause of the issue and how it resolved.

Note:
Its Production Environment. Nobody has access. Whatever change in any file will happen through Process. No code change process happened in the last two weeks. My assumption is its not code change issue, may be environment issue but not sure.