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

New Job Error

cliffhanger

Hi,
I was trying to create a new job by clicking File>New Job, then it gave me some error, I am attaching an screen shot of that error message. If anybody has any idea of what it means, please help me out.
Thanks
-cliffhanger

Find more posts tagged with

Comments

Migrateduser

I've seen this problem... what is the ownership / permission on available_templates.cfg? Also, what OS is TS on?

Dave

Dwayne

The most likely cause is that iw-home/local/config/wft/available_templates.cfg has been corrupted in some way, such that it's no longer valid XML.

--

Current project: TS 5.5.2/6.1 W2K

cliffhanger

Permission on the file is RWX for everyone, and it's running on a Windows2000 machine.

cliffhanger

Hi,
How do I check if available_templates.cfg is corrupted?
-Cliffhanger

Dwayne

Try running iwmxl_validate.ipl -well iw-home/local/config/wft/available_templates.cfg (where iw-home is replaced with wherever it is that you have TeamSite installled, of course)

--

Current project: TS 5.5.2/6.1 W2K

Migrateduser

Okay, I think the problem I was thinking of is more often for Unix, but -- as Dwayne said -- your available_tempaltes.cfg could be corrupted. Probably 99% of the time, this is a result of:

1. Careless omission of slashes when editing the file, although we've all done that, or
2. The file was edited using a Windows-based editor which may have left DOS characters (linefeeds) in the file that are both invisible when viewing the file in most editors and causes the TS XML parser to barf when it reads the file.

I've done both, and as I've read this board, most people have done one or both of those, also.

There's a script called $iwhome/bin/iwxml_validate.ipl that will let you know if the file is corrupted or not.

Dave

cliffhanger

checked that already, but doesn't give any error there Smiley Sad

Migrateduser

Hmm... okay, well, what I would do -- and this doesn't take a whole lot of time or effort -- is back up the existing configuration and then try stripping out entries in your available_templates.cfg to see if there's an entry in there it doesn't like.

Also, just for the **** of it, try saving the file in Wordpad (text-only, of course) and see if it works from there. That'll alleviate concerns that it's got some funky DOS characters in it. You may want to try this first.

Dave

Dwayne

The error message that you attached showed 'error 2'. It's been a while, but I think that error code 2 is "file not found." So it COULD be that some system file is missing for some reason.

You've already verified iw-home/local/config/available_templates.cfg. What about iw-home/local/config/available_templates.ipl? That's actually a Perl fragment that parses iw-home/local/config/available_templates.cfg. Don't run it through iwxml_validate.ipl, but make sure it's present and readable.

Also check to see if iw-home/lhttpd/iw-bin/iwwft_available.ipl exists, and is readable.

--

Current project: TS 5.5.2/6.1 W2K

cliffhanger

didn't find iwwft_available.ipl in iw-home/httpd/iw-bin/, but found it in iw-home/bin; copied it from iw-home/bin and put it in iw-home/httpd/iw-bin/, yet it doesn't show any change in the error message
-cliffhanger

Migrateduser

Aren't those ipl files only part of TS 6.x?

Dave

cliffhanger

I don't think so, because I am seeing them in 5.x installation

Migrateduser

I'm also seeing those files in $iwhome/bin under TS 6.1 SP1, so perhaps that was a typo.

Dave

Dwayne

I have to admiit that I made an assumption, without verifying it, that the file should be in httpd/iw-bin. It sounds like I was wrong.

I think we're back to posting your available_templates.cfg, to see if something "jumps out" at one of us.

--

Current project: TS 5.5.2/6.1 W2K

Adam Stoller

Things to check - IWHOME/bin/iwwft_available.ipl exists, and is readable/executable by all.

Paths leading from the drive (e.g. C Smiley Happy

up-to-and-including IWHOME/bin are readable/executable to all (there have been weird problems in the past when some part of that path is restricted to something like Administrators group where various things won't work for users unless they too are in the Administrators group).

IWHOME/tmp/cci/ exists and is readable/executable by all -- workflow tends to use this directory for temporary files and behaves badly when it isn't there (or is inacessible).

Aside from the above - and the ideas others have already posted, that's about all I can think of at this time.

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

Migrateduser

You can set DEBUG to 1 in available_templates.ipl and it will output additional information in /IWHOME/tmp/cci.