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

iwperl vs. ActiveState Perl

PeteOlsen

I recently installed ActiveState Perl on the same server that is running TeamSite and I think that ActiveState may have run over some of the TS iwperl settings. I have since removed ASPerl but TS is still having issues.

I am really only blaming the issue on ASPerl simply because it was the last thing I did to the system.

The specific error is: "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."

Can I re-install iwperl? If not, can I reinstall TS and it's servic packs from scratch without damaging my iw-store and other customizations? Maybe there is a fixiwperl flag for this very issue Smiley Happy

.

Thanks,
Pete.

Find more posts tagged with

Comments

Migrateduser

I'll bet you that it has nothing at all to do with your dual Perl installations. Where did you install AS Perl? Most likely, the two existed independently of each other -- unless you installed it in iw-home/iw-perl or something... which I HOPE you didn't do.

Otherwise, try to parse the workflow you're working with into XML and try to notice any anomalies.

gsundeep

Check the Modules such as XML: Smiley Tongue

arser exists in your iwperl installation.
You can do so my running following command

iwperl -MXML: Smiley Tongue

arser -e 1

PeteOlsen

I agree with you, I think the two perls should have been lived together just fine.

I'll bet you that it has nothing at all to do with your dual Perl installations. Where did you install AS Perl? Most likely, the two existed independently of each other -- unless you installed it in iw-home/iw-perl or something... which I HOPE you didn't do.

Otherwise, try to parse the workflow you're working with into XML and try to notice any anomalies.

So far I hav not found any files with bad XML. I am still looking though. Thanks for the lead.

Pete.

PeteOlsen

Check the Modules such as XML:arser exists in your iwperl installation.
You can do so my running following command

iwperl -MXML:arser -e 1

I have tried this also. There is no return from this command so XML: Smiley Tongue

arser must be installed correctly.

Thanks,
Pete

Adam Stoller

The specific error is: "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."

Check your WFT code - my guess is that you somehow managed to create a WFT in which

Does the workflow die before bring up the instantiation screen, or after you've filled in values and told it to Run Job? If the latter - try enabling workflow debugging and see if you can get a peek at the generated job description file.