Metadata inline failing

We are moving to Window2008R2 server so I have a fresh install. I have copied all configs and customizations from our current production installation. We are running TeamSite version 7.4.1.1 on Window 2008R2.

I have an inline in datacapture.cfg:

<item name="contentArea">
<label>Content Area</label>
<description>Please select the proper section for your content</description>
<select required="t">
<inline command="D:\Interwoven\TeamSite\iw-perl\bin\iwperl.exe \Interwoven\TeamSite\local\bin\BCBSNC\Intranet\webform\inline_get_site_section_list_metadata.ipl"/>
</select>
</item>

I get the error below when the inline tries to run:

ERROR /Interwoven/TeamSite/iw-perl/site/lib/BCBSNC/SiteTaxonomy.pm 81 Utility - Can't connect to DB: [IBM][CLI Driver] SQL1336N The remote host "hq1al016" was not found. SQLSTATE=08001

(SQL-08001)(DBD: db_login/SQLConnect err=-1)

Here is a code snippet:

sub new {
my ($class) = @_;
my $self = {};
bless ($self, $class);
if (! $self->{'dbh'}) {
$dbh = DBI->connect("dbi Smiley Surprised DBC:$ODBC_DSN", "$user", "$pw") or $log->error("Can't connect to DB: " . $DBI::errstr );
$self->{'dbh'} = $dbh;
}
if ($self->{'dbh'}) {
return $self;
} else {
return "";
}
}

This is working fine on our current production site and if I run it from the command line it runs just fine. I am using the same version of the DB2 jar files, but I do have an updated version of the DB2 client. All nodes and databases seem to be cataloged correctly and I can connect to the DB w/o issue, except for when this code tries to run from the inline.

Find more posts tagged with

Comments

Adam Stoller

Do you have a TNS / ODBC connection setup on the old server that doesn't [yet] exist on the new server?

ChrisPlunkey

Not that I can see. I see on the old server in the ODBC Admin just 1 System DSN(WADASP) this is the name for the production database. On the new server I have it pointing to our QA resource(WADASQ). They are configured the same and I can connect using either of them.

I also checked the node and database directory frmo the DB2 command line and they match between the old and new servers in that they have the correct values in each, current prod has production info and current QA has qa info. The port numbers are correct and the hostnames are correct and the database is linked to the correct node.

Here is another error from the content_center log:

2015-08-25 09:32:40,268 [http-0.0.0.0-8080-45] ERROR com.interwoven.ui.tagui.LaunchNextGenTagUICommand () - LaunchNextGenTagUICommand caught InlineCalloutException while processing inlines for these files: /default/main/Intranet/WORKAREA/common/wcms_training/testing2.html
com.interwoven.ui.datacapture.core.dct.InlineCallout$InlineCalloutException: DBI connect('WADASQ','das',...) failed: [IBM][CLI Driver] SQL1336N The remote host "hq1al016" was not found. SQLSTATE=08001

I also change the remote host name to the fully qualified name but get the same error.

Adam Stoller

Perhaps it's a DNS (as opposed to DSN) issue - can you ping "hq1al016" and/or it's FQDN from your TeamSite server?

ChrisPlunkey

That was my first thought but I can ping that server all day and if I run the code from the command line(the perl code directly) it works just fine. My 2nd thought was that there is something about the inline and how it executes or who it executes as that seems to be having an issue, but I didn't get anywhere with that.

Adam Stoller

Doh! Inline!

I don't believe inline commands contain the same environment information that your shell does (easily determined by adding code to dump out the environment information into a log file and run it both ways and compare the results) - either environment variables are being passed through explicitly in the iwwebd configuration files on your old server, or somehow or other you incorporated environment informaiton into the running of the script on your old server - in a manner that is eiher not working, or is just using old static information which is now wrong for your new server.

You need to look carefully over the script itself (look for ENV settings) and the iwwebd configuration files (look for environment pass throughs)

ChrisPlunkey

So I added this code to both servers:

foreach my $key (keys(%ENV)) {

$log->error($ENV{$key} . " : " . $key);
}

Both spit out the same info:

[2015/08/28 08:16:52] ERROR /Interwoven/TeamSite/iw-perl/site/lib/BCBSNC/SiteTaxonomy.pm 80 Utility - bcbsnc\u850420 : IW_USER
[2015/08/28 08:16:52] ERROR /Interwoven/TeamSite/iw-perl/site/lib/BCBSNC/SiteTaxonomy.pm 80 Utility - 52616e646f6d495664071e69c6e42433771b9068a32aec3955c0ea81f61c35bf41f81ac982165c00d8c9ea279cd32c7ff899a66e7405106edb9fa7571d73ab24 : IW_SESSIONID
[2015/08/28 08:16:52] ERROR /Interwoven/TeamSite/iw-perl/site/lib/BCBSNC/SiteTaxonomy.pm 80 Utility - /default/main/Intranet/WORKAREA/common : IW_CURRENTNODE
[2015/08/28 08:16:52] ERROR /Interwoven/TeamSite/iw-perl/site/lib/BCBSNC/SiteTaxonomy.pm 80 Utility - C:\WINDOWS : SYSTEMROOT
[2015/08/28 08:16:52] ERROR /Interwoven/TeamSite/iw-perl/site/lib/BCBSNC/SiteTaxonomy.pm 80 Utility - /default/main/Intranet/WORKAREA/common : IW_WORKAREA
[2015/08/28 08:16:52] ERROR /Interwoven/TeamSite/iw-perl/site/lib/BCBSNC/SiteTaxonomy.pm 80 Utility - master : IW_ROLE
[2015/08/28 08:16:52] ERROR /Interwoven/TeamSite/iw-perl/site/lib/BCBSNC/SiteTaxonomy.pm 80 Utility - \Interwoven\TeamSite\local\config\datacapture.cfg : IW_DCT
[2015/08/28 08:16:52] ERROR /Interwoven/TeamSite/iw-perl/site/lib/BCBSNC/SiteTaxonomy.pm 80 Utility - IntranetAuthor,IntranetEditor,admin,master,reviewer : IW_ROLES

The iw-webd\conf\iwwebd.conf.template files are identical(as are the iwwebd.conf files except for the serverName).

Comparing Windows Environment variables now, but they are all looking correct.

Adam Stoller

ChrisPlunkey wrote:
So I added this code to both servers:
foreach my $key (keys(%ENV)) {
$log->error($ENV{$key} . " : " . $key);
}

Might I suggest a slight modification to the above:

foreach my $key (sort keys %ENV) {
   $log->debug("$key : $ENV{$key}");
}

Then compare the results both server-to-server, and command-line-to-DCT.

The sorting makes it easier to compare the results since you aren't guaranteed on the order that un-sorted keys from a hash are presented.

ChrisPlunkey

I compared the ENV's on both the new and old servers, they are the same for the inline, for the command line the only differences were server related, like name. I went ahead and set all the ENV variables that were in the command line in the inline version. Same results.

Adam Stoller

Check the list of DB-related perl modules in IWHOME/iw-perl/site/lib and IWHOME/iw-perl/vendor/lib on both servers - it could be that you're missing a module on the new server.