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

iwwft_compile.ipl error

BlueWhale

Hello,

I am trying to invoke a workflow from a perl script for which I am using the iwwft_compile.ipl command.
But, when I run the command from the command line, I am getting the following error:

\Programs\Interwoven\TeamSite\bin>iwwft_compile.ipl -i <

\Programs\Interwoven\TeamSite\tmp\test_input.xml

ERROR: miscellaneous error occurred
Error parsing input XML: XML parse error :
no element found at line 1, column 0, byte -1 at

\Programs\Interwoven\TeamSite
\iw-perl\vendor\lib/XML/Parser.pm line 187

But, I have a well-formed test_input.xml as attached.

I did some research and I found the Interwoven support article https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=48721 for this issue but, I am still getting the same error even after going through the steps.

It would be great if any of you can help me in this matter. Thank You.

Environment: TeamSite 6.7.1 Sp1 on Windows 2003

Find more posts tagged with

Comments

Adam Stoller

Hello,

I am trying to invoke a workflow from a perl script for which I am using the iwwft_compile.ipl command.
But, when I run the command from the command line, I am getting the following error:

\Programs\Interwoven\TeamSite\bin>iwwft_compile.ipl -i < \Programs\Interwoven\TeamSite\tmp\test_input.xml

ERROR: miscellaneous error occurred
Error parsing input XML: XML parse error :
no element found at line 1, column 0, byte -1 at \Programs\Interwoven\TeamSite
\iw-perl\vendor\lib/XML/Parser.pm line 187

But, I have a well-formed test_input.xml as attached.

I did some research and I found the Interwoven support article https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=48721 for this issue but, I am still getting the same error even after going through the steps.

It would be great if any of you can help me in this matter. Thank You.

Environment: TeamSite 6.7.1 Sp1 on Windows 2003

Try using a different editor or configure your editor to save files with Unix EOL characters - right now your file has ^M's at the end of each line and these often can cause problems with XML parsers.

I've taken the liberty of making an adjustment to the file posted - so it might work. Of course, since the file says DOMAIN\User - you'll probably need to edit it - and if you do - you may end up putting the ^M's back in - I suggest trying to run with this file as is and see if you at least get a different error message.

BlueWhale

Thanks Ghoti for looking into this. But, I am getting the same error message even with the file you edited (I took the file as is..haven't edited).

I am getting the same error message with any xml file (tried passing DCTs, DCRs, PTLs and other XMLs to the command).

Any help is highly appreciated.

Adam Stoller

Thanks Ghoti for looking into this. But, I am getting the same error message even with the file you edited (I took the file as is..haven't edited).

I am getting the same error message with any xml file (tried passing DCTs, DCRs, PTLs and other XMLs to the command).

Any help is highly appreciated.

Perhaps it's the WFT that's causing problems. I realize you're specifying an OOTB WFT - but (a) it may have been edited and/or (b) it may also have the ^M problem, which while it might not cause problems when processed through the GUI, might still cause problems when processed by the CLT.

That's all I can think of at this time.

It's kind of difficult to debug something like this when you're not in the same environment and able to reproduce the same problem.

Good luck

BlueWhale

Thanks Ghoti for looking into this.

I got this worked by invoking the command as:

\Programs\Interwoven\TeamSite\bin>D:\Programs\Interwoven\TeamSite\iw-perl\bin\iwperl.exe iwwft_compile.ipl -i < WF_input1.xml

(by giving the path to perl interpreter)

pbarua

I had the same issue and prepending path to perl interpreter before the iwwft_compile.ipl call fixed it.

I am on TS 6.7, Windows server 2003 SP1. I invoked iwwft_compile.ipl with and without path to iwperl.exe and monitored it in process explorer. In both cases it actually invokes the script with path to iwperl.exe (i.e. even when I call the script iwwft_compile.ipl without iwperl.exe, it appends path-to-iwperl.exe before that call.)

I compared the environment variables for both calls and they are exactly the same. So, why is this working when we explicitly give path to the perl interpreter? Any ideas?

adapa

Hi I am able to execute query successfully but i am not able to retreive the file name in another perl script by using
@files = $task->GetFiles();

any one can help me to retreive the file name

Migrateduser

Hi I am able to execute query successfully but i am not able to retreive the file name in another perl script by using
@files = $task->GetFiles();

any one can help me to retreive the file name

What does this have to do with the original thread? You've provided no useful information that would allow anyone to help you with this. Perhaps if you attached your entire script that would be helpful. How did you attach files to the job?

nipper

What does this have to do with the original thread? You've provided no useful information that would allow anyone to help you with this. Perhaps if you attached your entire script that would be helpful. How did you attach files to the job?

I thought he was actually using that code to build the WFT, which we know will never work.

this (or the new thread) will be a fun one to watch

Migrateduser

I thought he was actually using that code to build the WFT, which we know will never work.

this (or the new thread) will be a fun one to watch

I'm microwaving the popcorn as we speak....

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.