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

CGI Failing

cocalicious

I am TS 6.7.2 on SP2, for some reason my customized CGI scripts which are part of File menu is throwing an Internal Server Error. It was working success fully till yesterday and when the server got rebooted overnight, it is throwing an internal server error. The error specifies "Apache/2.0.63 (Win32) mod_ssl/2.0.63 OpenSSL/0.9.8e Server at koccm02 Port 80" . Can anyone let me know to resolve this.

Thank

Find more posts tagged with

Comments

nipper

There is not much one can do with as little information as you provide.

You need to do some debugging first and narrow down the issue but one guess is that something did not start up correctly or started on the wrong port.

cocalicious

Here is what i have done to resolve this Andy,

Restart apache checked for the customer_webserver_port=81 in iw.cfg which is correct. Restarted Teamsite service. Rebooted the box. None seem to resolve this issue.

What is Ironic is that we have 3 scripts which provide 3 different Custom Menu items, out of these 2 are throwing Internal Server Error and Third is working fine. IF we assume that the problem was with apache then third script shouldn't work. That being said lets us assume that there is problem with our scripts, so just for giggles I did put in a simple CGI and tested it it still throws an error.

P.S we haven't touched any file VIZ ui_custom.xml or make_toolkit etc.

Thanks

nipper

Have you done an iwreset -a ?

Apache should be running on port 81 but that should not matter, the iwwebd should be running and that should be what is needed for this. DOS or Unix ?

Also, just run the CGI from a shell, do not invoke iwperl, just execute them, make certain something did not happen to them

cocalicious

Have you done an iwreset -a ?

Apache should be running on port 81 but that should not matter, the iwwebd should be running and that should be what is needed for this. DOS or Unix ?

Also, just run the CGI from a shell, do not invoke iwperl, just execute them, make certain something did not happen to them

Andy, the problem was that there was a "iwperl" file create in iw-perl bin directory, this was blocking the cgi to run , once this got deleted everything is back to normal. Seems like it was a know issue.

Thanks