Missing %ENV variable

Hello people,

I'm working on 3 new servers with a clean 6.7.1 install, windows 2003 server. One has it's previous custom functionalities assembled and working, so I am busy now copying the changes to the 2nd one.

However, I noticed that some of the custom scripts failed while they were working on the first one. After quite a search I wrote a simple script that outputs the %ENV hash and all send parameters, and I found out the keys iw-home and iw-home/bin were missing from %ENV on the second server (prolly also on the 3rd, but that's for later).

I added them manually to the second system, but they still don't turn up in the output, even after a iwreset-a. Do i need to reboot the whole box for this?

Thx in advance!

*edit*
Oh, just for the record, I didn't do the install myself, so plz be gentle Smiley Very Happy

Find more posts tagged with

Comments

Adam Stoller

Hello people,

I'm working on 3 new servers with a clean 6.7.1 install, windows 2003 server. One has it's previous custom functionalities assembled and working, so I am busy now copying the changes to the 2nd one.

However, I noticed that some of the custom scripts failed while they were working on the first one. After quite a search I wrote a simple script that outputs the %ENV hash and all send parameters, and I found out the keys iw-home and iw-home/bin were missing from %ENV on the second server (prolly also on the 3rd, but that's for later).

I added them manually to the second system, but they still don't turn up in the output, even after a iwreset-a. Do i need to reboot the whole box for this?

Thx in advance!

*edit*
Oh, just for the record, I didn't do the install myself, so plz be gentle

iw-home and iw-home/bin are not (OOTB) environment variables.
In some instances they may be form variables - but if you're depending on them being in %ENV you need to search through all your other customizations and configuration files to see if you can find where they're getting set on the first server so you can replicate it on the second (and third) servers.

That being said - all of the above is in the context of the information (or lack thereof) included in your original post - since we don't know what code you're trying to fix we can only guess at what the actual source of the problem is.

RonH

iw-home and iw-home/bin are not (OOTB) environment variables.

I see, hmm... I thought and expected them to be so, merely because OD has similar ENV's defined on OS level.

That being said - all of the above is in the context of the information (or lack thereof) included in your original post - since we don't know what code you're trying to fix we can only guess at what the actual source of the problem is.

I don't want to bother you right now too much with functionalities, not yet that is Smiley Wink

I kept things short to keep it readable.

I'm not sure what can be wrong now, but at least I know this isn't the source of my problem. Thank you for the answer.

PeerReviewReport.rptdesign

Adam Stoller

I see, hmm... I thought and expected them to be so, merely because OD has similar ENV's defined on OS level.

I don't want to bother you right now too much with functionalities, not yet that is I kept things short to keep it readable.

I'm not sure what can be wrong now, but at least I know this isn't the source of my problem. Thank you for the answer.

Some folks do create system environment variables for IWHOME, and perhaps "IWHOMEBIN" (which seems pointless to me) on their servers - if so, than after doing that and rebooting you should be able to access that information as environment variables.

If that's the case - you need to look at the server level (as opposed to the TeamSite level) to see if these "magic" strings exist in the System environment variables listing on your initial server - and if so, create them on your other two servers.

PeerReviewReport.rptdesign

Migrateduser

Do you have the iw-home and iw-home/bin keys on the first server? Go to the page http://teamsite/iw-bin/show_env.cgi does not have the iw-home and iw-home/bin keys.

RonH

If that's the case - you need to look at the server level (as opposed to the TeamSite level) to see if these "magic" strings exist in the System environment variables listing on your initial server - and if so, create them on your other two servers.

It did, and I created them on the other server as well, without any luck, thats what I ment with my first post Smiley Happy

No idea who initially created them and why, their existence seem pretty folly to me.

Anyway, got it figured out. The failing functionality was a filebrowser cgi application run through IIS. Perl did not had access to the file and complained. The server in turn complained about the absence of HTTP headers by retuning a 502.2 error. First this implied to me something with the code (which is quite complex) was wrong. Because the same code is used on a working server, and the absence of two (imo) important ENV's I thought I had something going.

Eventually I used the nph- prefix and firefox to retrieve the raw data from perl, instead of the server error message. This told me perl could not access the file.

Got a tip from our formal admin to add the account used by the default application pool to the TS preview group, and that gave the **** wings.

For some reason the security setup of one IFS volume differs from the other. on the failing server templatedata did not carry and rights for the Everyone account. For know I stopped wondering why.

In any case, thank you very much for your help and time!