Recent changes to bugs

ODBTP Libraries no longer work after applying updates

2012-05-20T01:21:10Z

Example code attached executed perfectly before applying windows 7/2008 normal updates

The call to the libraries results in a valid column name, but no data. The same query used in the odbtpcli produces

Version: ODBTP/1.1
Execute Failed: [HY010][0][Microsoft][ODBC Driver Manager] Function sequence error

However, the php plugin works as desired with the same sql syntax using the same target odbtp server and sql server.

A sample response to the query used is: 1) -1 test=(null) Error 0

I tested this on a Windows 2008 Box and a Windows 7 Box as target and sql host, and used the Windows 2008 as a remote using the CLI, C Libs, and PHP

ODBTP Fails to build on PHP 5.4

2012-04-19T21:05:01Z

When compiling ODBTP on a server that is running PHP 5.4, the build fails. I installed Ubuntu 12.04 Final Beta on our testing server, and upgraded it to 5.4 using https://launchpad.net/~ondrej/+archive/php5 and ODBTP no longer builds.

Uninstalling 5.4 and removing the PPA, then going back to the default 5.3.10 installation of PHP allows ODBTP to be built once again.

Integer value not always correct

2011-07-29T06:27:46Z

The correct integer value isn't always returned.

For example:
select 1 as test

75% of the time, this returns 1. The rest of the time is returns a random number, i.e. 19946824975

Everything else works fine, but integers are flakey

OS: OpenSUSE 11.4 x64
PHP 5.3
ODBTP 1.1.4
SQL Server 2000

Microsoft SQL Server 2005 SP3 cannot connect with LogODBC=1

2011-03-09T03:31:55Z

odbtp_connect fails when LogODBC=1 is set in odbtpsrv.in with Microsoft SQL Server 2005 SP3. The error message received is “[ODBTPERR][0]Unable to read from server (Success).” This is not a problem with Microsoft SQL Server 2005 SP2. We verified this with the PHP extension and the odbtpcli program compiled in Ubuntu Linux.

odbtp_connect succeeds with Microsoft SQL Server 2005 SP3 with LogODBC=0.

Unix-shared Extension Dumps Core on Ubuntu

2010-03-25T02:28:26Z

The php_odbtp.so (1.1.4) dumps core in apache2.

I performed a gdb backtrace on the apache2 core file. Here is the function call list:

#1 0xb6af2b00 in odbFetchRowEx () from /usr/lib/php5/20060613+lfs/php_odbtp.so
No locals.
#2 0xb6aea175 in php_odbtp_fetch_hash () from /usr/lib/php5/20060613+lfs/php_odbtp.so
No locals.
#3 0xb711e2d1 in execute_internal () from /usr/lib/apache2/modules/libphp5.so
No symbol table info available.
#4 0xb6ba163e in ?? () from /usr/lib/php5/20060613+lfs/dbg-php-5.2.so
No symbol table info available.
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb)

Environment:

Apache: 2.2.11
PHP: 5.2.12-0
Ubuntu: 9.0.4
ODBTP: 1.1.4 Attached to this email is the make log output. We compiled with MSSQL support.

I have been using ODBTP 1.1.4 for 3 years connecting to Foxpro/MSSQL on Windows/PHP. It is extremely stable. We brought our code to the Ubuntu linux environment and are experiencing the core dumps. We compiled the extension with -Wall and are seeing many errors. Any ideas? Thank you for creating ODBTP.

MS SQL INSERT FROM EXEC sp fails

2007-03-12T14:08:08Z

Hi.

I have a stored procedure in Microsoft SQL Server 2005 that uses the following statements
/////////////////////////////////////
CREATE TABLE #tmpResumenVentasEjecutivoPromotor
(
idUsuario INT NOT NULL,
strNombrePromotor VARCHAR(64) NOT NULL,
nVisitasEfectuadas FLOAT NOT NULL,
nVisitasEfectivas FLOAT NOT NULL,
SUMdblValorEfectivo FLOAT NOT NULL
)

INSERT INTO #tmpResumenVentasEjecutivoPromotor
EXEC [procResumenVentasEjecutivoPromotorDatosBasicos]
@idPromotor = @idPromotor,
@nHoraReporteInicio = @nHoraReporteInicio, -- DATEPART(hh, DATEADD(hh, -1, GETDATE()))
@nHoraReporteFinal = @nHoraReporteFinal, -- DATEPART(hh, DATEADD(hh, -1, GETDATE()))
@dtmFechaReporteInicio = @dtmFechaReporteInicio, -- dbo.EXTRACTDATE(GETDATE())
@dtmFechaReporteFinal = @dtmFechaReporteFinal; -- dbo.EXTRACTDATE(GETDATE())

SELECT top 10 * FROM #tmpResumenVentasEjecutivoPromotor
return
////////////////////////
The sp does not return anything.

I run the SP inside management and it works flawlessly.

The code for executing in php is
//////////////////////
<?php
include("includes/dbase.php");
try {
$rs1 = $DB->Execute("EXEC [procResumenVentasEjecutivoPromotorUltimaHora] @idPromotor = 941");
if ($rs1->EOF)
{
echo "No ha efectuado visitas" . "<br/>";
}
else
{
rs2html($rs1);
}
}
catch (exception $e) {
fnMostrarError("temp2.php", "DatosInsert<br/>", $e, true, false);
}
?>
//////////////////////

Thanks for your product. It works great.

MRamirez

Return value from stored procedure is inaccesible

2007-01-31T21:14:03Z

Hi and thanks for a very nice piece of software. Today, I discovered you and today it has been implemented successfully. The only problem found so far is about return values from stored procedures in Microsoft SQL Server.

We are using AdoDB in PHP and the following piece of code:

# @RETVAL = SP_RUNSOMETHING @myid,@group
$stmt = $db->PrepareSP('SP_RUNSOMETHING');
# note that the parameter name does not have @ in front!
$db->InParameter($stmt,$id,'myid');
$db->InParameter($stmt,$group,'group',64);
# return value in mssql - RETVAL is hard-coded name
$db->OutParameter($stmt,$ret,'RETVAL');
$db->Execute($stmt);

Variable $ret doesn't contain any value at all at exit.

Is there a problem? Thanks in advance.

Mauricio Ramirez
MV Ltda.

Connection Problems

2006-08-15T14:48:43Z

Hallo,
I'm using your example files and get this error:

Warning: [ODBTPERR][0]Invalid Response
in /srv/www/htdocs/test/odbtp/query.php on line 16

The Connect itself is okay:

[15/Aug/2006:16:29:53] SERVER[Started]
[15/Aug/2006:16:46:11] OPEN 172.16.1.167 1
[15/Aug/2006:16:46:26] CLOSE 172.16.1.167 1
[15/Aug/2006:16:46:35] OPEN 172.16.1.167 2
[15/Aug/2006:16:46:36] CLOSE 172.16.1.167 2

I have added the needed part in the php.ini and have
created a interface file.

Can you help?

Multiple queries of a reserved connection

2006-06-21T10:18:57Z

Using reserved connection:

// creating connection
odbLogin(hCon, SVR,2799, ODB_LOGIN_RESERVED, szDbConn);
odbLogout(hCon, FALSE);

...

odbLogin(hCon, SVR, 2799, ODB_LOGIN_RESERVED, szConn)
odbExecute (hQry, SQL);
qid = odbGetQueryId (hQry);
// qid = 0 - OK
odbLogout(hCon, FALSE);

...

// then again

odbLogin(hCon, SVR, 2799, ODB_LOGIN_RESERVED, szConn)
odbExecute (hQry, NEW_SQL_STATEMENT);
qid = odbGetQueryId (hQry);
// qid egual 0 again !
odbLogout(hCon, FALSE);

Conclusion: the reserved connection does not restore
properly its queries.

vlad

Initialization in odbAllocateQuery()

2006-06-15T11:14:05Z

Function odbAllocateQuery do not initialize some
members of odbHCONNECTION, for example
pbySavedRowDataEndByte. This leads to segmentation
fault in function odbRestoreRowDataBytes().