CAPI.AllocConnect() issue

Hi,

I have a project here to migrate some modules from Livelink 9.2 to Content Server 10. The both tools use Oracle as main RDBMS. But I have a customized table where it will receive some data from a MSSQL database. In the actual version (9.2), I use CAPI.AllocConnect() to gather the table and write it to the customized table. However, the same code doesn't work with CS10. I receive the following message:

E661979139:No Sql channel has been established. The required database
drivers are not available.

I believe there is necessary to install a MSSQL driver, or to setup the Content Server 10 to understand the MSSQL connection. Is there someone who can help me ?

Thanks.

Find more posts tagged with

Comments

Appu_Nair

http://msdn.microsoft.com/en-us/library/ms131321.aspx

That article explains how one would

Install sqlserver client on the livelink

Appserver computer.Also if you install the

Sqlserver express you can check if you

Can communicate to the master db using

Client protocols.Installing management

Studio one can use the GUI and avoid

Cmd line tools such as tsql.

Dbwizapi is another package very similar

To capi but in your case without the sqlserver

Driver you will get the same error

Sent from my iPhone

On Aug 8, 2011, at 4:44 PM, "eLink Entry: Content Server Development Forum" <development@elinkkc.opentext.com> wrote:

CAPI.AllocConnect() issue Posted by carlos.takata@br.bnpparibas.com (Takata, Carlos)On 2011/08/08 17:40

Hi,I have a project here to migrate some modules from Livelink 9.2 to Content Server 10. The both tools use Oracle as main RDBMS. But I have a customized table where it will receive some data from a MSSQL database. In the actual version (9.2), I use CAPI.AllocConnect() to gather the table and write it to the customized table. However, the same code doesn't work with CS10. I receive the following message: E661979139:No Sql channel has been established. The required database
drivers are not available. I believe there is necessary to install a MSSQL driver, or to setup the Content Server 10 to understand the MSSQL connection. Is there someone who can help me ? Thanks.
[To post a comment, use the normal reply function]
Forum: Content Server Development Forum
Livelink Server: knowledge-wlweb01

Carlos_Takata

Hi Appu,

Thanks, but it doesn't worked.

In fact, if the Livelink 9.2 works WITHOUT this installation, why Livelink 9.7.1 needs this independent package? I believe the driver SHOULD be installed inside the Livelink 9.7.1, and this solution looks to be in some hidden place of OpenText website. Or maybe it needs to be bought.

Carlos

Appu_Nair

I am afraid I do not know why a 9.2 livelink server can connect to without having a sql client files.

"Livelink ECM - Enterprise Server Installation Guide" can be accessed via the following link: https://knowledge.opentext.com/knowledge/llisapi.dll/Properties/13621454

Page 44 of the above has this info.

• If Microsoft SQL Server resides on its own host, you must install a Microsoft SQL

Server client on the Livelink host.

Maybe time to open a ticket with KB or put logging on the capi layer and see what it is really complaining about…

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Tuesday, August 09, 2011 11:03 AM
To: eLink Recipient
Subject: Re CAPI.AllocConnect() issue

Re CAPI.AllocConnect() issue

Posted by carlos.takata@br.bnpparibas.com (Takata, Carlos) On 2011/08/09 11:58

Hi Appu,

Thanks, but it doesn't worked.

Carlos

[To post a comment, use the normal reply function]
Topic:	CAPI.AllocConnect() issue
Forum:	Content Server Development Forum
Livelink Server:	knowledge-wlweb01

Carlos_Takata

Hi Appu,

This is the evidence where I can see the SQL Client is not important to execute CAPI commands.

In my LL 9.2 environment, which is working, I made a simple test, removing the "LLSQLSERVER.dll" from the "/opentext/bin" folder. Then, when run the code, it returns the same error message, which is the missing driver.

So, can you check into your Livelink 9.7.1 installation, if there is something similar to this file name ? This is in fact, the driver missing for the Livelink 9.7.1 installation. I'll also contact support if they have any clue about this missing file.

Thanks in advance,

Carlos

Carlos_Takata

For who is interested:

In contact with the OpenText support, they told me the Livelink 9.7.1 and CS10 are not compatible anymore with MSSQL (?). So, I had created a solution using ODBC.

The very strange is, if you look at the CAPI help topic, it says you can use MSSQL, ORACLE and ODBC to connect to datasources. I think they want to sell customized solutions instead trying to find out why there is no more DLL available in the new versions.

Carlos

Kyle_Swidrovich

Quoted Carlos Takata (carlos.takata@br.bnpparibas.com) on 2011/08/10 17:47:

For who is interested:

In contact with the OpenText support, they told me the Livelink 9.7.1 and CS10 are not compatible anymore with MSSQL (?). So, I had created a solution using ODBC.

Carlos

Hi Carlos,

I would like to clarify your comments above.

What Customer Support communicated to you was that although 9.7.1 and 10 can use an MSSQL or Oracle database to store its data, the communication method via Oscript to an MSSQL database requires that an MSSQL Client is installed on the machine.

The lloci10 binary is used for Oracle communication and the llodbc binary is used for MSSQL communication.

I suspect that the Builder documentation has an error, which can be corrected.
David Templeton can probably comment more here on this.

Kyle

Carlos_Takata

Hi Kyle,

Thanks, I appreciate your assistance.

However, I tried to install MSSQL Client (the support provided a link to download and install it) from a microsoft website, but it doesn't worked.

Also, I'm pretty sure the problem IS NOT the lack of client installation, it is a problem with the installation of the newer version of Livelink, where this driver doesn't exist anymore.

Again: I tested Livelink 9.2 WITHOUT client and it worked, and this can't be applied with the Livelink 9.7.1 or CS10. They don't have the drivers.

Rgds,

Carlos

Kyle_Swidrovich

Hi Carlos,

The client is what is needed for ODBC use.

Livelink 9.5.0.1 was the last version to include a custom SQL DLL.

ODBC is now used for communication with SQL Server.

You can see this by looking at the Oscript code in DBWIZAPI : DBWizAPIRoot : APIs : SybaseAPI : MsSQLAPI . Init().

.fDBType = CAPI.CT_ODBC

This is the option chosen by Content Server on startup, as seen in the DB Upgrade code in llweb_startup.lxe:

// If the DB needs upgrading; do it.

if ( retVal.OK && NeedsDbUpgrade() )

String dftConnection = $Kernel.SystemPreferences.GetPrefGeneral( 'dftConnection' )

Assoc cnctParams = $Kernel.SystemPreferences.ListValues( "dbconnection:" + dftConnection )

switch ( cnctParams.servtype )

case 'MSSQL'

temp = OS.NewTemp( $DBWizAPI.MssqlAPI )

temp.BringUpToDate()

end

I would recommend you examine how Content Server establishes its connections and use that as a guide for your own use.

Regards,

Kyle

Carlos_Takata

Hi Kyle,

Thanks for your tips.

I'll take a look at the DBWIZAPI module to understand how it works.

In fact, the sad thing in this history, is that the Builder's help is not updated to fit with these changes. I spent a lot of time to figure out and to create, at the end, the same code using ODBC.

Thanks anyway.

Carlos

Kyle_Swidrovich

It looks like that was missed in the updates to the Oscript documentation.
I've entered this into our issue tracking system.
The reference number for this issue is LPAD-26748.

Thanks for letting us know.

Regards,
Kyle

Carlos_Takata

Hi to everyone,

Finally, I found why there is no driver to MSSQL. There is a patch to install (pat100000172_CS64_WIN) where the driver comes with.

Carlos