Interwoven Web Daemon won't start

Just finished upgrading to TeamSite 5.5.2 with all the requires SPs and mandatory patches and now my web daemon won't start up. I get an ERROR:2140: An internal Windows NT error has occurred. Any ideas? I searched the KB and found only a reference if the servlet engine wasn't starting, but that is up and running fine.

Let me also add that this was working fine untril I edited the iw.cfg file and added a custom menu item. I then got an error that the browser failed to get session ID and after I stopped an restarted the browser this connection error started. another user in another building was also using 5.5.2 on this test server and she was booted off.

Edited by Paul on 04/01/03 10:47 AM (server time).

Find more posts tagged with

Comments

Paul

OK I found why the Web Daemon won't start. There are corrupt lines in the httpd.conf file. It seem that every time I run am iwreset -ui this file gets corrupted. It appears that it also gets rewritten because the date/time stamp is the same as the reset. Once I fix those lines up, I can manually start the service but then I get a 400 error BAD Request in the browser. Something funky is going on here.

Gregg Faus

What does your httpd.conf.template file look like? The http.conf is built from the template every time you do a reset.

Paul

which template? and the section of the httpd.conf file in question looks like this: extra space inserted where the ^ symbol is

# For fullproxy mode, use iwproxy as our proxy server for all requests
ProxyRemote * http://localhost^:1080^

# Except for requests that are to bui2 or iwproxy
NoProxy localhost

NoProxy localhost

# Rewrite the Location header of redirects created by bui2, so that the
# browser comes back to us, instead of trying to contact bui2 directly.
# Note that iwproxy takes care of rewriting redirects created by the
# customer's web server.
ProxyPassReverse / http://localhost^:8080^/

... further down ...

gwen1

In the same directory as the httpd.conf is another file httpd.conf.template. (iw-home\iw-webd\conf) Any changes/fixes need to be made to this file not the httpd.conf. The httpd.conf file is recreated based on the template file every time the iw-webd service/process is restarted.

Paul

The httpd.conf.template was fine in the sections that were mucking up the works. However what I did was go back to the iw.cfg file and delete the hard returns and put in soft returns <shift>+<enter> in the section where the template grabs the variables. I then did an IWRESET -ui and the web daemon started without incident. I still had the 400 error so I renamed the wep.xml to web.xml.orig and renames the web_no_jsp.xml to web.xml and did another iereset -ui and all was well.