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

inline callout command to connect database

JohnsonTjang

Hi,

I use inline callout command in the datacapture.cfg to called the perl script to connect to the database to retrieve the data for testing:

<item name="product_name" pathid='product'>
<label>Product Name</label>
<description>The Product Name will be read from database by inline callout</description>
<select required="t">
<inline command="C:\iw-home\iw-perl\bin\iwperl.exe C:\iw-home\custom\bin\iw_solution_inlinecallout.ipl"/>
</select>
<database data-type="VARCHAR(100)" />
</item>

The script "C:\iw-home\iw-perl\bin\iwperl.exe C:\iw-home\httpd\iw-bin\iw_solution_inlinecallout.ipl" work well when I run it in the command prompt, but it failed to run when I select the 'New Form Entry' in the ContentCenter. The following is the error message:

Root cause:
DBI connect('driver={SQL Server};server=10.4.0.83;databasename=template;Trusted_Connection=no','fusionadmin',...) failed: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied. (SQL-08001) [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()). (SQL-01000) [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute (SQL-01S00)(DBD: db_login/SQLConnect err=-1) at C:\iw-home\custom\bin\iw_solution_inlinecallout.ipl line 102 Unable to open database connection at C:\iw-home\custom\bin\iw_solution_inlinecallout.ipl line 102.

If Anyone can help I'd appreciate it.

Thanks and Regards,

Johnson

Find more posts tagged with

Comments

jbonifaci

There have been many similar posts to this over the years. Odds are this has to do with your environment variables. Log all of the environment variables when you run the script from the command line and from the TeamSite UI. Then manually set the necessary variables that are different between the two (use trial and error if needed). I believe the two environment variables you need to set for SQL Server though are $ENV{TEMP} and $ENV{SYSTEMROOT}.

~Jeff

JohnsonTjang

Thanks for your reply first, but I would like to know more about the method to get the environment variables of the Teamsite UI.

jbonifaci

Log them in your perl script, they are stored in the %ENV hash.

~Jeff

Migrateduser

I get the following error.
Root cause:
DBI connect('TS_DB','tsuser',...) failed: [Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or access denied. (SQL-08001) [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen (Connect()). (SQL-01000)(DBD: db_login/SQLConnect err=-1) at d:/iw-home/TeamSite/iw-perl/site/lib/BHD/Database.pm line 72 .

Setting the following variables as well.
$ENV{'TEMP'} = "C:\\Temp";
$ENV{'SYSTEMROOT'} = "C:\\WINNT";

Teamsite is on Win2000.
SQL Server2000SP4 is on Win2003.
Any Clue?

nipper

can you connect to this server via Control Panel ODBJ ?

Migrateduser

Yeah, I can connect.

Migrateduser

same .IPL runs successfully from command line.Getting an error when running as inline.

Migrateduser

Since you are using ODBC...

When you set up the DSN, did you make it a system dsn or a user dsn?

Migrateduser

I am using System DSN. I found the resolution for this problem.
Thanks to all.By changing "Client Configuration - Network Libraries" to TCP/IP.

waikong

I am using System DSN. I found the resolution for this problem.
Thanks to all.By changing "Client Configuration - Network Libraries" to TCP/IP.

I am facing the same problem, I'm using System DSN, and my Client Configuration is TCP/IP (by default).

any solution for me?

RonaldV

Did you create User- or system-dns entries in the odbc-window? I believe the User-dns's are not accessible from within an inline.

If not, it is an environment issue.