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

deployment fails - workflow errors - production issue

SethHickel

I know this error has been responded to before - but the response is normally "you have a badly formed WFT." I don't think this is the case since we have not changed any WFT files since before this error started occuring.

We get the following error when we start workflows. XML parse error in WFworkflow.pm: no element found at line 1, column 0 byte-1 at

\Interwoven\TeamSite\iw-per\vendor\lib/XMLParser.pm line 187

We do not get this error on all workflows. The TS-Admin workflow does not get this error nor does a WFM created workflow. These workflows complete without error but the deployment log will show that zero files have been deployed.

I made a change to iw.cfg with respect to mail domains however I reverted back to a previous version without that change. The only other change has been to iw_solution_email.ipl used by only one set of workflows. I have also undone that change.

TeamSite 6.7.1 (Not SP1)
Open Deploy 6.1.1

Help Please!

Thanks

Find more posts tagged with

Comments

nipper

Is it possible that someone used an & in a comment ? Something like this & that ? (doubtful but worth asking)

Did available_templates.cfg change recently ?

ISCBorisB

I know this error has been responded to before - but the response is normally "you have a badly formed WFT." I don't think this is the case since we have not changed any WFT files since before this error started occuring.

We get the following error when we start workflows. XML parse error in WFworkflow.pm: no element found at line 1, column 0 byte-1 at \Interwoven\TeamSite\iw-per\vendor\lib/XMLParser.pm line 187

We do not get this error on all workflows. The TS-Admin workflow does not get this error nor does a WFM created workflow. These workflows complete without error but the deployment log will show that zero files have been deployed.

I made a change to iw.cfg with respect to mail domains however I reverted back to a previous version without that change. The only other change has been to iw_solution_email.ipl used by only one set of workflows. I have also undone that change.

TeamSite 6.7.1 (Not SP1)
Open Deploy 6.1.1

Help Please!

Thanks

You may want to switch Debugging on and post the resulting XML ( not wft! XML - eg evaluated Job Specs )

nipper

You may want to switch Debugging on and post the resulting XML ( not wft! XML - eg evaluated Job Specs )

Assuming he gets that far.

SethHickel

switch Debugging on and post the resulting XML ( not wft! XML - eg evaluated Job Specs )

Not sure what logging you are telling me to turn on and what results to send.

Is it possible that someone used an & in a comment ? Something like this & that ? (doubtful but worth asking)

Did available_templates.cfg change recently ?

Checking available_templates.cfg. If someone did use "&" or somthing like it what can I do at this point: kill all jobs?

SethHickel

May 11 was the last edit of available_templates.cfg. This problem surfaced yesterday. Ugh.

ISCBorisB

Not sure what logging you are telling me to turn on and what results to send.

Attach wft, I'll reply with the changes you have to make for debugging (it may be already there)

nipper

Not. If someone did use "&" or somthing like it what can I do at this point: kill all jobs?

What do you mean kill all jobs ? Nothing should have started (per your post)

SethHickel

True - thought perhpas a workflow that was hung ... sorry - just reaching for anything

SethHickel

Attached are four wft files.

Thanks

SethHickel

Sorry - here they are in zip

nipper

You can post your WFT, but you may have a couple lines like this:

# iw_output_file => "...."
# iw_debug_mode => "..."

Those you can remove the perl comments.

One more question, is your repositiory frozen by chance ? The fact that many WFTs are failing is a concern.Check your TS license. It iwll put the backingstore in read only mode if you have a temp license timeout.

SethHickel

Nope - not frozen - iwstat returns ok.

You can post your WFT, but you may have a couple lines like this:

# iw_output_file => "...."
# iw_debug_mode => "..."

Not sure what to do with that comment - was that instruction to look for those in my wft files as a possible issue?

nipper

OK, LowesNet_directsubmit has it turned on already, you can run it and select yes for debug and save the output and post.

NG_expressworkflow.wft change line 15 to true and rerun

Now 2 of the WFT you posted were changed on Monday.

nipper

Not sure what to do with that comment - was that instruction to look for those in my wft files as a possible issue?

They were common approaches, but not what were used in your WFT. I posted a reply.

SethHickel

OK - first time I have done that - attached text is the output that showed in IE. Is this what I need to post? This is for the LowesNet wft

nipper

you reposted the WFTs. Post the debug information

If you change express, there will be a debug file field it will save the output in an XML file and you cn attach that

SethHickel

OK - sorry - fried brain - trying to find where it would log out to

nipper

directsubmit does not save to a file, but the others have a field to save it to a file.

SethHickel

It is my understanding that the log file is not written unless there is an error - the IE screen top is yellow and the bottom is green - the second half starting with something like"
" is the start of the log file for the workflow. It does not appear to have errors.

Very confused.

nipper

It is my understanding that the log file is not written unless there is an error - the IE screen top is yellow and the bottom is green - the second half starting with something like"
" is the start of the log file for the workflow. It does not appear to have errors.

Very confused.

No the log will be created if you select debug=yes. Look for it and post.

SethHickel

My other developer says that he has never been able to get a log file to write. He would see a pop-up (alert box) with an error number and line number.

nipper

Check the path you are writing to. Be certain it is valid and writable.

I do not know if you can cut & paste from the window that is opened.

SethHickel

This next text is from the green section of the IE window that is opened. It is the results of instantiating the workflow.

nipper

Also see if LowesNG_expressworkflow.cfg has been changed recently

I am trying to run this on my server, but it is not working (I think I am missing a PM or something).