ODBC error "SQLAllocStmt failed."

Question

Hi,
I have a simple program with three partitions: DBSO, SO and GUI,
querying a master/detail pair of tables in a database. Until
recently this worked fine on my (client) machine, but I couldn't get
it working when I put the SO's on the server. Specifically, it
would return zero rows no matter what it should have got.
We're using MS-SQL Server 6.5 on NT4sp4/i386 with an NT client. The
ODBC versions are: SQL Server driver 3.60.0319, DB library 6.50.252
and net library 6.5.0.0. These are the same on both client and server.
The SQl-Server side is ok, the PowerBuilder app that uses it natively
still works.
My SO throws this exception when run on the server:
USER ERROR: Prepare failed for dynamic SQL statement 3, error from database
is:
ODBC SQLAllocStmt failed.
[Microsoft][ODBC Driver Manager] Driver does not support this function
Class: qqdb_UsageException
Detected at: qqdb_OdbcVendorInfo::DoSQLAllocStmt at 10
Last TOOL statement: method ContactManager.FindContactsDynamic
Error Time: Tue Jul 13 11:04:18
Distributed method called: qqdb_SessionProxy.Prepare!82 (object name
site/contactservices_cl0/contactwindows_cl0-contactdbso0x1d8:0x2) from
partition "ContactWindows_cl0_Part2", (partitionId =
2AE77400-1A1B-11D3-9D87-DC8E0ECEAA77:0x1d9:0x1, taskId =
[2AE77400-1A1B-11D3-9D87-DC8E0ECEAA77:0x1d9.3]) in application "Forte
Runtime", pid 205 on node ERMINTRUDE in environment centrale
ODBC SQLSTATE: IM001, Server: GodzillaDatabase, UserName: sa
Database Statement: select contact_number
"ContactNumber", name "ContactName", street_line1
"StreetLine1", street_line2 "StreetLine2", street_line3
"StreetLine3", suburb "Suburb", state
"State", postcode "PostCode", country
"Country", area_code "AreaCode", industry
"Industry", stage "Stage", comments
"Comments", postal_line1 "PostalLine1", postal_line2
"PostalLine2", postal_line3 "PostalLine3", postal_line4
"PostalLine4", postal_line5 "PostalLine5", invoice_person
"InvoicePerson", pay_nett "PayNett" from contact
where Contact_Number = 5
Exception occurred (remotely) on partition "ContactWindows_cl0_Part1",
(partitionId = 2AE77400-1A1B-11D3-9D87-DC8E0ECEAA77:0x1d2:0x9, taskId
=
[2AE77400-1A1B-11D3-9D87-DC8E0ECEAA77:0x1d8:0x3.26]) in application
"Forte
Runtime", pid 342 on node GODZILLA in environment centrale.
Turning on ODBC tracing shows this is the originating error:
ftexec 156:16b EXIT SQLAllocStmt with return code -1 (SQL_ERROR)
HDBC 0x00938360
HSTMT * 0x00d8e2e4
DIAG [IM001] [Microsoft][ODBC Driver Manager] Driver does
not support this function (0)
During the connect sequence we also get this error:
ftexec 156:16b ENTER SQLSetConnectOption
HDBC 0x00938360
UWORD 112 <SQL_PACKET_SIZE>
UDWORD 8192
ftexec 156:16b EXIT SQLSetConnectOption with return code -1
(SQL_ERROR)
HDBC 0x00938360
UWORD 112 <SQL_PACKET_SIZE>
UDWORD 8192
oft][ODBC SQL Server Driver][SQL Server]The ODBC catalog stored procedures
installed on server godzilla are version 6.50.193; version 07.00.0324 or
later is required to ensure proper operation. Please contact your system
administrator. (0)
Now, until recently the program worked fine when run locally. Unfortunately
while
trying to work out what the problems are we've managed to produce the same
error
on the client, with no idea how exactly we did it. As of now I can't locate
the
SO's back on the client because Forte thinks ODBC is not set up.
USER ERROR: The node ERMINTRUDE is unable to support this partition
(ContactWindows_cl0_Part1). This is because either all of the restricted
projects required by the partition have not been installed on the node or
the
node does not have the external resource or thread package that the
partition
uses. This partition requires the restricted project(s) ODBC and the
external
resource GodzillaDatabase.
In my ODBC configuration I have GodzillaDatabase set as a System DSN, having
just moved it from being a User DSN. Neither fixes that problem.
Does anyone have any ideas on this, or solutions to it?
Thanks
Chris
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/forte>

Answer 1

Hi Steve,
If you open the Report and then click on DataBase, Log on and connect first. Then open your report, then Database, Set Location and once it's done then Verify the Database. Fix any errors or warnings that may pop up.
Lots of changes between 8.5 and 2008. CR detects that the report is the old format and it then goes through an series of internal report upgrade routines to convert all functions to the current format.
Also, all of the database drivers were re-written to take advantage of the updated functionality and Client enhancements. As well as we removed any "custom hacks" that we did back then to fix "issues" int he DB client drivers at the time. All of those "fixes" were removed, to much work to maintain them all, now if there are issues it's usually due to the DB Client not following ANSII 92 Standards.
One issue that does show up from time to time is that the order you inserted the tables can have an affect on how CR generates the SQL, may not be the case for your issue though, just something to watch for.
What happens if you create a new report and use that same SQL, save it, close all, re-open the report and run it. Do you get the same errors?
Also note: you did not say if you also updated the ODBC driver? As of CR 9 we are UNICODE compliant, may be your client needs to be updated also. Also verify it's using ODBC 3 and not ODBC 2 standards.
Thank you
Don
Edited by: Don Williams on May 6, 2010 7:21 AM