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 executing ipl script through inline command

motlnt

My env:
TS 6.7.2 on RedHat Linux
DB: MS SQL
ODBC Drivers:unixODBC and freeTDS with DBI

I am trying to populate a drop down list in a form using an inline ipl script which connects to a remote database server. When I run the script on the command line as myself it works fine. When running through inline, the connection fails with the error pasted below.

I am setting the environment variables also properly as shown below.

Has anybody encountered such error?
please provide inputs.

Part of my datacapture.cfg file that calls the ipl script:

< inline command="/Interwoven/TeamSite/iw-perl/bin/iwperl /Interwoven/TeamSite/httpd/iw-bin/connect ToDb.ipl" / >

my perl script connectToDb.ipl

#!/Interwoven/TeamSite/iw-perl/bin/iwperl -w

#This is a program
use strict;

BEGIN {
$ENV{'LANG'} = "en_US";
$ENV{'PATH'} = "/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/joshim/bin";
$ENV{'LD_LIBRARY_PATH'} = "/usr/local:/usr/local/lib:/usr/lib";
$ENV{'ODBCHOME'} = "/usr/local";
$ENV{'ODBCINI'} = "/usr/local/etc/odbc.ini";
};

use CGI;
use DBI;
#use DBI::W32ODBC;

#use DBI: Smiley Surprised

DBC;
#use DBD: Smiley Surprised

DBC;
use TeamSite::Config;

#$ENV{'PATH'} = " /usr/local/openlink/bin:/usr/bin";

# Get Home and mount
(my $iwhome = TeamSite::Config::iwgethome()) =~ tr|\\|/|;
(my $iwmount=TeamSite::Config::iwgetmount()) =~ tr|\\|/|;

#Turn buffering off.
#$| = 1;

my $username = 'username';
my $password = 'password';

my $sql_dbh = DBI->connect( "DBI Smiley Surprised

DBC:MSSQLTestServer",$username,$password ) or die $DBI::errstr;

my $sql = "select dbFName,dbLName,contactId from tblContacts";

# Prepare the statement.
my $sql_sth = $sql_dbh->prepare($sql)
or die "Can't prepare statement: $DBI::errstr";

# Execute the statement.
$sql_sth->execute();

#Generate Option objects for cities/locations in that region.

my $sql_row;

print "\n";

while ( my @sql_row = $sql_sth->fetchrow_array )
{

print " \n";

}
print "\n";

$sql_dbh->disconnect;

exit;

Here is my odbc.ini entry ,
[MSSQLTestServer]
Driver = FreeTDS
Description = SQL database
Trace = No
Server = *.*.*.*
Port = 1433
Database = ***_Teamsite

I get all the values properly when running the IPL through command line.

But when I run the same via DCT, I get this,

DBI connect('MSSQLTestServer','< username >',...) failed: [unixODBC][FreeTDS][SQL Server]Unable to connect to data source (SQL-08001) at /Interwoven/TeamSite/httpd/iw-bin/connectToDb.ipl line 40

I have seen similar posts like this but they all talk about setting the env variables properly which I am doin in IPL.

Please comment.

thx in adv.

Find more posts tagged with

Comments

Migrateduser

You could try to write a log file and print the values of variables you depend on to make sure they really exist when the script runs.

You could also enable some tracing as described here:

http://modperlbook.org/html/20-3-DBI-Debug-Techniques.html

motlnt

The issue is the same script works on the Teamsite dev env w/o any issues via DCT.

I tried printing the env variable using the 'printenv' command and both outputs(from TS dev and prod) are showing similar stuff.

any idea?

pammi

Only i can guess here permission issue to DB connetion.Please check your role and script has execution permission to DB.

Thanks

motlnt

Only i can guess here permission issue to DB connetion.Please check your role and script has execution permission to DB.

Thanks

I dont think there is anything wrong with role/script execution permissions since the same IPL script runs well via command line on the same TS server.

Adam Stoller

I dont think there is anything wrong with role/script execution permissions since the same IPL script runs well via command line on the same TS server.

You may think you're being clear and accurate - but you're not.

How, exactly, do you run the script from the command line?
Who, exactly, do you run the script from the command line as?

How, exactly, does the script get run via the inline?
Who, exactly, does the script get run by via the inline as?

Are you sure you have ALL the needed environment settings?
Is there a DSN directory on the server?
If so - what are the access rights on (and leading upto) it?

motlnt

Here are the inputs...

You may think you're being clear and accurate - but you're not.

How, exactly, do you run the script from the command line?
: /Interwoven/TeamSite/iw-perl/bin/iwperl /Interwoven/TeamSite/httpd/iw-bin/connectToDb.ipl
Who, exactly, do you run the script from the command line as?
: as per log USER = < myself >

How, exactly, does the script get run via the inline?
:in DCT as,
< inline command="/Interwoven/TeamSite/iw-perl/bin/iwperl /Interwoven/TeamSite/httpd/iw-bin/connectTo Db.ipl" / >

Who, exactly, does the script get run by via the inline as?
: the log shows me ,
USER = < myself >
IW_USER = < myself >
IW_ROLE = master
IW_ROLES = Site Manager,admin,master

Are you sure you have ALL the needed environment settings?
: I am setting following in the script,

$ENV{'PATH'} = "/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/< myself >/bin";
$ENV{'LD_LIBRARY_PATH'} = "/usr/local:/usr/local/lib:/usr/lib";
$ENV{'USER'} = "< myself >";
$ENV{'LANG'} = "en_US";
$ENV{'HOME'} = "/home/< myself >";
$ENV{'ODBCHOME'} = "/usr/local";
$ENV{'ODBCINI'} = "/usr/local/etc/odbc.ini";

is there anything else I need to set?

Is there a DSN directory on the server?
: what/where should be the DSN directory?
If so - what are the access rights on (and leading upto) it?

motlnt

I was able to resolve this using a workaround.

Thanks all for help.

gir

Hi ,

I am facing a similar issue using inline command which is calling a perl script to populate values in a drop down, the perl script uses logger (use Log::Log4perl perl module) where it causing the issue. The command inside the inline when executed directly in unix server works fine.
Can you please tell me the workaround you did..

Adam Stoller

Hi ,

I am facing a similar issue using inline command which is calling a perl script to populate values in a drop down, the perl script uses logger (use Log::Log4perl perl module) where it causing the issue. The command inside the inline when executed directly in unix server works fine.
Can you please tell me the workaround you did..

The original problem was related to a script that performs DB interactions - is your problem the same or do you believe your problem is due to the logger functionality?

I've seen issues with the logger in which the permissions on the file being logged to don't get set right (they basically have to be world-writable unless you can identify a sole user or group who will always be the owner of the process running the script).

In such cases - you want to use

Log: Smiley Very Happy ispatch::File

(in addition to

Log::Log4Perl

) and possibly

Log: Smiley Very Happy ispatch::FileRotate

to ensure that the access rights on newly created

Log::Log4perl

log files are set the way you need them to be (and to rotate log files as desired). Read the perldocs for

Log::Log4perl

and the above mentioned

Log: Smiley Very Happy ispatch

modules for more details.