XML:Parser.pm error

Has anyone seen this before? When I attempt to start a particular workflow from New_Job I get this error

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 with Debugger on, the workflow XML is valid (tested by opening in IE)

I'm running TeamSite 5.0 on Win2000

Find more posts tagged with

Comments

Migrateduser

Verify that the path to the workflow (in available_templates.cfg) is correct and that the permissions are correct.

The error message (byte -1) suggests a problem while starting to read the workflow, possibly because the file cannot be found our cannot be read.

Brinko Kobrin
Interwoven Staff Engineer

fallinj

The path is correct in available_templates.cfg and the permissions are the same for this workflow as it is for others that do work. It looks like the .wft can be found, b/c if I run debug mode (Where I get the pretty yellow and green output screen) the file is read there.

Migrateduser

Good! Then the problem is not with the reading of the wft file. When you run with debug mode, do you see the job spec XML at the bottom of the page? Is *it* well-formed? (You can copy and paste it into an XML file of its own.)

Brinko Kobrin
Interwoven Staff Engineer

Migrateduser

You can try using the iw_output_file tag in your TAG_info section and save your XML out to a file, then run iwjobc on your XML file. This usually produces better error messages than when you get errors inside the GUI. Why they don't provide more meaningful error messages inside the GUI is a mystery.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

fallinj

I ran iwjobc on the xml file I saved out of the debug window and it returned a job id. I then ran iwinvokejob using the job id. Then the job appeared in my ToDo list

Edited by fallinj on 09/24/02 03:44 PM (server time).

Test.java

Migrateduser

That's freaky. Not that it returned a Job ID (you would need to then run iwinvokejob on that Job ID to actually run the job - that's why it doesn't appear in your ToDo list yet). But because it didn't fail. What the ****?

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Migrateduser

Normally you will only see active task that are assigned to you.

Try View -> All Jobs from WebDesk Pro. If you still don't see your job, try iwgetwfobj on the id that was returned by iwjobc.

But I am still wondering what happened to your XML parse error. Do you still get it if you don't go through iwjobc?

Brinko Kobrin
Interwoven Staff Engineer

fallinj

This is freaky. I've reproduced this twice now.

If I try and instantiate the job from the GUI I get the error "Invalid workflow"

If I run the job in debug mode, copy the xml from the debug window (The green section) 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 ToDo list.

Anyone know what extra steps the GUI uses to instantiate the job?

Edited by fallinj on 09/24/02 03:57 PM (server time).

Migrateduser

That is bizarre. Just for giggles, I would still run the workflow through without debug on, but with iw_output_file and then run iwjobc on the output from iw_output_file (instead of cutting and pasting the XML from the debug window and running iwjobc on that). If that works, you've found a cool new feature - workflows that fix themselves.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Migrateduser

The instantiator essentially does:

1) iwjobc <XML stream>
2) confirm that created job is valid
3) instantiate the job

In all likelihood, you're encountering an error at step #2. The first difference I can think of would relate to the fact that the instantiator/iwjobc depends on the browser/teamsite session for authentication, but I can't immediately see how that would create a problem.

If you're daring, you might try changing one line of code in iwwft_instantiator Perl script:

if ((!defined $wf) || !$wf->IsValid() || $wf->GetError())

to:

if ((!defined $wf) || $wf->GetError() || !$wf->IsValid())

and see if a more informative error message is displayed (it's possible that the IsValid() call is stomping on another error message).

--
Evers Ding
Staff Engineer, Interwoven

fallinj

Good Call

I changed the line of code in iwwft_instantiator.ipl and attempted to start the job from the GUI. I got this error

Invalid workflow:
Could not open C:\iw-home\tmp\cci\workflow908

I must have inadvertantly deleted the dir cci when cleaning out the tmp directory (I had been putting my own debug logs there for quite a while and was just trying to be tidy).

Once I created an empty cci directory in the tmp folder, worked just fine.

Thanks guys for your help.

patrickm

Hey all,
this is a weird one, I'm getting the very same error on Windows 2000 Adv Sever, SP4 with a fresh installation of TS6.5. I'm using the default out of the box workflow solutions. Debugging shows perfect XML is being generated for the workflow, but the instantiation isn't happening due to the XML Parser message. Has anyone seen this on 6.5?
Thanks.