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

Frequent but intermittent problem editing DCRs etc

bjork

Hi everyone,

We are recently having a whole bunch of very annoying problems, all on our production Solaris 5.5.2 TeamSite server. The problems are possibly all related:

When attempting to edit a DCR-created HTML page, TeamSite does not realise that the HTML is created with a DCR, and opens up the raw HTML in the user's HTML editor;
When attempting to edit a DCR directly, TeamSite does not open up the usual Data Capture form, but opens up the raw XML in the user's text editor;
When browsing around the directories in a workarea, the "Regenerate Page" option (and other options) disappear and reappear with no apparent rhyme or reason. I can confirm, for example, that Regenerate Page often disappears even when I am browsing a directory full of DCR-generated HTML pages.

All of these problems are intermittent but frequent, to the extent that I may have to try editing a file up to 20 times before it successfully opens the Data Capture form instead of my HTML editor. It's becoming a big big hassle.

No clues to be found from studying all the server log files. I did find several error refences to a non-existent file:
/usr/local/sys/iw-home/httpd/iw-home/getiwextattr.cgi

That error looks hopeful, and there is actually a file called:
/usr/local/sys/iw-home/httpd/iw-home/getiwextattr.ipl, and looking inside it, I can see that it is a simple CGI script, so I tried copying that file to a cgi extension, and the errors disappeared from the logs but the weird behaviours continue.

Stumped. Really stumped. Our Solaris guys have rebuilt the entire OS from scratch to try and nail this, and our Interwoven resellers are at a dead-end too.

Any thoughts?

thanks heaps,
Lee Borkman

Find more posts tagged with

Comments

Adam Stoller

What service pack / patch level are you with respect to TeamSite and TeamSite Templating?

You say they've rebuilt the OS - have you tried uninstalling / reinstalling TeamSite and TeamSite Templating?

The missing CGI would *seem* to indicate that something went wrong during an installation or upgrade - but I can't say for sure (never seen this problem myself)

--fish
(Interwoven Senior Technical Consultant)

tvaughan

Next time it happens, hop out on the command line, navigate to the exact HTML file the user is trying to open and run

$IWHOME/bin/iwextattr -l file

You should get 3 or 4 extended attributes specifying that the HTML was template generated, which DCR it came from, which category/type, etc.

If you don't see any such extended attributes, it's probably because the pages were copied from another server at some point in the past.

If your pages are opening as raw XML in a text editor or something, (a) make sure there's no file extension on the DCR, and (b) your LaunchPad isn't configured to do what it is doing (i.e., opening all files with Notepad)

If you try editing a file 19 times in a row and are unsucessful in getting it to open in a DCT until the 20th time, I'd call a witch doctor.

Hope that helps,
Tom

bjork

Thanks TV,

I have checked the external attributes repeatedly, even running a script that checks every second for an hour. the external attributes are fine, and the DCR they point to is in place, readable, and perfectly healthy. I have run this little script while trying to open the file, and the external attributes are constant and good, while the UI is failing to open the DCR properly.

;-(

Thanks again,
LeeBB

Adam Stoller

This, again, makes it sound as if something went wrong when installing TeamSite Templating - or that patches may have been applied out-of-order.

I'd recommend backing up the backing store and iw-home, and re-installing TeamSite and TeamSite Templating - it's not much fun, but it's probably the best way to resolve the problem without too much loss of sleep (before or afterwards).

--fish
(Interwoven Senior Technical Consultant)

bteeter

We are having the exact same problem right now. Did you ever find a solution to this problem? If so, what was it?

Thanks - Brian

mdang

Brian,
If you checked the iwextattr as the above post suggested, and it is ok, there is another check you should do:

telnet to the server and login as the TeamSite user who is having the problem.
issue the command:
pkginfo | grep IWOVtst

if the user can not see the package, or there is an error of permission deny, you have found the problem.