iwpt_compile.ipl command run from tpl not seeing iwperl on new server

Hello,

I'm testing our current installation on a new server and have a problem with one of the templates which calls iwpt_compile from an <iw_perl> block.

I'm running windows 2003 and TS 6.5 sp2

Basically on the working system everything works as expected. Here I can run a command like below.

E:/Interwoven/Teamsite/bin/iwpt_compile.ipl.............................

On the new system iwpt_compile is not being run unless I do the following.

E:/Interwoven/Teamsite/iw-perl/bin/iwperl E:/Interwoven/Teamsite/bin/iwpt_compile.ipl.............................

I need to figure this out so that I can update any other templates affected by this in the correct way. I cant figure out why this would break. The only difference between the systems is that Teamsite is installed in a different location and the drive letter is different?

Find more posts tagged with

Comments

stefanmaier

Hi,
is it possible, that you registered the filetype ipl on your old system to the iwperl.exe
and you didn't do that on your new system?
What does windows do if you do an doubleclick on a ipl-script on each of your two servers?

Adam Stoller

In addition, check the System environments on both servers.
- PATH
- PATHEXTS

RonaldV

On windows ipl-scripts MUST be registrered to run iwperl (like when .doc extension open Word) since, unfortunately, even Teamsite requires this (in fact, they are simply being lazy not to prefix the command with iwperl.exe).

Tim__D

When I click on the .ipl it runs the script. Same is true if I run it from the command line.

Tim__D

In addition, check the System environments on both servers.
- PATH
- PATHEXTS

I've never had to do that before can you specify the method to check this.

Tim__D

When I click on the .ipl it runs the script. Same is true if I run it from the command line.

Tim__D

In addition, check the System environments on both servers.
- PATH
- PATHEXTS

Here is the output of %ENV

NEW SERVER

PATHEXT - ('PATHEXT')
.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH - ('.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH')
PROMPT - ('PROMPT')
$P$G - ('$P$G')
NUMBER_OF_PROCESSORS - ('NUMBER_OF_PROCESSORS')
4 - ('4')
COMPUTERROLE - ('COMPUTERROLE')
SERVER - ('SERVER')
HOMEPATH - ('HOMEPATH')
\ - ('\')
PATH - ('PATH')
C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\wbem;c:\program files\common files\interwoven\lib;e:\interwoven\teamsite\bin;c:\program files\common files\interwoven\lib;c:\program files\diskshare\ - ('C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\wbem;c:\program files\common files\interwoven\lib;e:\interwoven\teamsite\bin;c:\program files\common files\interwoven\lib;c:\program files\diskshare\')

OLD SERVER

PATHEXT - ('PATHEXT')
.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH - ('.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH')
PROMPT - ('PROMPT')
$P$G - ('$P$G')
NUMBER_OF_PROCESSORS - ('NUMBER_OF_PROCESSORS')
2 - ('2')
HOMEPATH - ('HOMEPATH')
\ - ('\')
PATH - ('PATH')
C:\WINNT\system32;C:\WINNT;C:\WINNT\system32\wbem;c:\program files\common files\interwoven\lib;d:\iw-home\bin;c:\program files\common files\interwoven\lib;c:\program files\diskshare\ - ('C:\WINNT\system32;C:\WINNT;C:\WINNT\system32\wbem;c:\program files\common files\interwoven\lib;d:\iw-home\bin;c:\program files\common files\interwoven\lib;c:\program files\diskshare\')

Adam Stoller

Okay - well you eliminated PATH and PATHEXT from being the source of the issue - sometimes a negative can be a good step forward to a positive ...

Can you post the line(s) from the <iw_perl> block that makes this call? (wrap it in [html]...[/html] tags so that it shows up correctly)

Tim__D

Ok here is the code. This is actually a part of a subroutine. Basically I've got replicant fields in my dcr to allow someone to enter a list of documents that are langauage specific. The template then generates these language pages as separate files and links the main page to them.

[html]
my $langName = iwpt_dcr_value('language.Language');
use TeamSite::Config;
my $iwhome = TeamSite::Config::iwgethome();
my $dcrFilePath = iwpt_get_dcr_name();
my $filePath = iwpt_get_ofile_name();
my $dirName = iwpt_get_ofile_name('dirname');
my $fileName = iwpt_get_ofile_name('basename');

# User selects generate
my $param = iwpt_get_flag_param('-oprefix');
if ($param eq "") {
my $extattpdt = `iwextattr -g TeamSite/Templating/PrimaryDocumentType $filePath`;
my $extattpdcr = `iwextattr -g TeamSite/Templating/PrimaryDCR $filePath`;

# Create directory if needed.
if(!(-e "$dirName/language")) {
mkdir "$dirName/language", 0755;
}

# Buid new file command
$fileName =~ s/([^\/]+)\.jsp/$1_$langName.jsp/;
$fileName = lc($fileName);
my $ofile = "$dirName/language/$fileName";
my $command = "$iwhome/bin/iwpt_compile.ipl ";
$command .= "-pt $vpath\\templatedata\\Marketing_Tools_Extranet\\Product\\presentation\\language.tpl ";
$command .= "-iw_pt-dcr $dcrFilePath ";
$command .= "-iw_pt-arg lang=$langName extattpdcr=$extattpdcr extattpdt=$extattpdt ";
$command .= "-smartwrite ";
$command .= "-ofile $dirName/language/$fileName ";
$command .= "-iw_include-location $vpath";

# Generate new file
my $result = `$command`;
}
[/html]

Adam Stoller

Ok here is the code. This is actually a part of a subroutine. Basically I've got replicant fields in my dcr to allow someone to enter a list of documents that are langauage specific. The template then generates these language pages as separate files and links the main page to them.

[html]
...
# Generate new file
my $result = `$command`;
}
[/html]

Add some debugging to print out the value of $command and $result to a temporary file - and post the results.
My guess - there are various places within $command that you are using single-back-slashes (\) without realizing it - and those are getting interpolated such that the command line isn't actually valid.

Tim__D

Add some debugging to print out the value of $command and $result to a temporary file - and post the results.
My guess - there are various places within $command that you are using single-back-slashes (\) without realizing it - and those are getting interpolated such that the command line isn't actually valid.

Ok. Thanks for the feedback. The main reason for this post was to see if this was a symptom of a bad installation on the new machine or like we covered above, some environment variable which may have been wrong. Since posting this I have seen calls to iwpt_compile.ipl in other .tpl files that do not reference iwperl directly and do work. At least I know through your comments that this does not appear to be an environment issue but an issue with this particular command.

Thanks!

- Tim