XML Parse Error

I am kinda frustrated.

I got this error for all the workflows

Invalid workflow:
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

If I run the job in debug mode, copy the xml from the debug window and save that as an .xml file, I can run iwjobc with my .xml file from the command line and I get a job id. Then I can run iwinvokejob using that job id and the workflow will show up in my tasks list in workflow tab.

Actually, I knew someone had the exactly same error in the past, so I looked up the forum.
There suggested, I have to have iw-home\tmp\cci folder if it is happend to be deleted.
However, I did not delete the folder, so the folder stays where it should be.

Is there any other possibility for this error?

TS 6.5
Windows 2000 Server

Find more posts tagged with

Comments

nipper

Many times I have seen this error caused by a special character in the comment, if you
have an & in the WF comment AND you are not using the __TAG__ variable, you will get
bad XML.

Adam Stoller

The error message sounds like there is a problem with the first line in your WFT (either pre- or post- instanation processing) - likely causes:
- white-space before <?xml...?>
- DOS-style EOL (e.g. ^M) at end of <?xml...?>

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

truehero

Thank you for your quick reponse.

The weird thing is, everything was working well two days ago.
But now any workflows are not working including example workflows which were bundled at installation.

Any more suggestions, please?

Edited by jkkim on 08/01/05 11:14 AM (server time).

nipper

Also, when you run it in debug mode, just have it save the file to an XML file instead of cut and paste.

Post that if you like

truehero

Still I am in frustration...

I attached a file. One is a wft file which was bundled at installation.
I just do not understand why suddenly all things are messed up.

Actually, yesterday I installed a jdk 1.5 on the machine, but later I unintalled it.
Do you think this can be a problem?

Thanks.

Edited by jkkim on 08/01/05 01:28 PM (server time).

Adam Stoller

perhaps the problem is in the available_templates.cfg file rather than in the individual wft files?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

truehero

Well, I used an older version of available_template.cfg instead of the current one, but I got the same error.

This is a freaky situation, indeed.

Edited by jkkim on 08/02/05 09:32 AM (server time).

nipper

Change your WFT to save the XMl to a file (do not just cut and paste it).

run it, tell us what happens and post the file that is generated.

mgal

This KB article might be of help

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=48721

Thxs,

Mohammed Gazal.

truehero

As long as I run .wft file with command line tools, it works fine.
However, I found that cgi task is not working even with CLTs.

I attached the job spec file which are "not" just copied and pasted.
The wft file is what was bundled at installation, which means a very simple basic one.

Thank you.

P.S. I changed the extension to .txt.

Edited by jkkim on 08/02/05 11:46 AM (server time).

nipper

So do any workflows work via the CGI task ?

truehero

Interestingly, only cgi tasks are not working.
Every other task before cgi works fine.
If a cgi task is reached, workflow is just stuck.

Weird...

nipper

Do CGI's work in general ? Did someone turn them off ?

can you go to

http://iwserver/iw-bin/sample_cgi_process.cgi (or whatever the name is)

truehero

All cgi's worked well before.

When I try something like http://iwserver/iw-bin/sample_cgi_process.cgi in the browser, the browser tries to find it, but suddenly stops.
I cannot think of anyone who would turn it off.
Hmm...

Can iwproxy be corrupted somehow?

ccprofessional

I know everyone will come after me guns blazing - did you reboot?! ;-)