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

Error while using show_env.ipl

swatis

Hi,

I have to do filelist deployment by customising menu. I have already cutomised menu and calling an ipl through it. when i try to open show_env.cgi i get to see all the data but when i call show_env.ipl through the customised menu link i get internal server error.

Moreover when i copied show_env.cgi by another name in the same folder and tried to open it through customised menu link its giving me the same error.

Please help me what should i do, i am working on teamsite 7.0.1

Find more posts tagged with

Comments

RonaldV

server errors are most often logged in local/logs/iwui/error.log. Pls check these.

Adam Stoller

Hi,

I have to do filelist deployment by customising menu. I have already cutomised menu and calling an ipl through it. when i try to open show_env.cgi i get to see all the data but when i call show_env.ipl through the customised menu link i get internal server error.

show_env.cgi

is a binary wrapper that runs

show_env.ipl

- if you're getting an internal server error running show_env.ipl directly then it is likely that either (a) someone modified the Perl code incorrectly or (b) the

line at the beginning of the script is incorrect, or (c) if you're on a Unix system - the script isn't marked as being executable.

Moreover when i copied show_env.cgi by another name in the same folder and tried to open it through customised menu link its giving me the same error.

As the CGI is a binary wrapper that attempts to run the same-named IPL script - copying it to an arbitrary name is bound to produce this behavior and really doesn't mean anything.

A little history: The reason the binary wrapper exists is from the days before TeamSite had iwwebd (apache) included to serve the GUI (5.x? 4.x? it's been a while) and most Windows implementations used IIS to do that instead; and IIS had issues running .ipl scripts from the iw-bin directory - especially if the #! line wasn't properly configured. Those days are long-since gone and the binary wrappers should no longer be needed, they just were never removed from the product distribution (probably in the name of backwards-compatibility, though also possibly from sheer laziness ;-)