mf_galberico1 Honored Contributor.
Honored Contributor.
2310 views

odbc error on sqlserver

Jump to solution

hello ...

I have a new error never seen before...

running program compiled with ESQL 32 bit,  after one hour of run I get this error:

Load error : file '_SQLODBC'

error code: 173, pc=0, call=1, seg=0

173     Called program file not found in drive/directory

the mfdebug.log is not generated, what should I look for?

Can you help me please?

Tags (1)
0 Likes
2 Solutions

Accepted Solutions
Micro Focus Expert
Micro Focus Expert

RE: odbc error on sqlserver

Jump to solution

What product and version number are you using?

How are you linking the program, shared, dynamic, static?

So you are stating that the program works OK, connects to the database, runs SQL statements, etc for an hour and then gets this error?

That doesn't make sense as _SQLODBC is an entry point into the OpenESQL run-time system which should already be loaded at that point in time.

Does this problem occur everytime you run the application after about an hour?

Does it occur at any particular location within the program?

You might consider tunring on the ODBC tracing using one of the following directives:

ODBCTRACE=ALWAYS

TRACELEVEL=4

Thanks.

0 Likes
Highlighted
mf_galberico1 Honored Contributor.
Honored Contributor.

RE: odbc error on sqlserver

Jump to solution

Hi,

I have solved the error by installing the latest version of the ODBC driver for MSSQL.

However, after making the ODBC trace I found many lines with message "badmem" like this:

ODBCRUN.EXE LB B4C-c78 EXIT SQLSetStmtAttr with return code 0 (SQL_SUCCESS)
SQLHSTMT 016E7A50
SQLINTEGER 7 <SQL_ATTR_CONCURRENCY>
SQLPOINTER 0x00000001 (badmem)
SQLINTEGER -5

While the ESQL TRACE is not come to end due to lack of disk space, the log written had exceeded 5 Gb, after 7 hours ...

so I decided to upgrade the ODBC driver that solved the fault.

Again, thanks for your time

greetings...

0 Likes
4 Replies
Micro Focus Expert
Micro Focus Expert

RE: odbc error on sqlserver

Jump to solution

What product and version number are you using?

How are you linking the program, shared, dynamic, static?

So you are stating that the program works OK, connects to the database, runs SQL statements, etc for an hour and then gets this error?

That doesn't make sense as _SQLODBC is an entry point into the OpenESQL run-time system which should already be loaded at that point in time.

Does this problem occur everytime you run the application after about an hour?

Does it occur at any particular location within the program?

You might consider tunring on the ODBC tracing using one of the following directives:

ODBCTRACE=ALWAYS

TRACELEVEL=4

Thanks.

0 Likes
mf_galberico1 Honored Contributor.
Honored Contributor.

RE: odbc error on sqlserver

Jump to solution

Thanks...

I'm running the ODBC trace to find the statement that causes the error ,

- i have attached mfsupportinfo.log

- the program is linked shared and this problem occur everytime I run app

- I will also trace with ODBCTRACE= ALWAYS and TRACELEVEL=4

I'll keep you updated, in the meantime, as always, thanks!
peppe
0 Likes
Highlighted
mf_galberico1 Honored Contributor.
Honored Contributor.

RE: odbc error on sqlserver

Jump to solution

Hi,

I have solved the error by installing the latest version of the ODBC driver for MSSQL.

However, after making the ODBC trace I found many lines with message "badmem" like this:

ODBCRUN.EXE LB B4C-c78 EXIT SQLSetStmtAttr with return code 0 (SQL_SUCCESS)
SQLHSTMT 016E7A50
SQLINTEGER 7 <SQL_ATTR_CONCURRENCY>
SQLPOINTER 0x00000001 (badmem)
SQLINTEGER -5

While the ESQL TRACE is not come to end due to lack of disk space, the log written had exceeded 5 Gb, after 7 hours ...

so I decided to upgrade the ODBC driver that solved the fault.

Again, thanks for your time

greetings...

0 Likes
mf_galberico1 Honored Contributor.
Honored Contributor.

RE: odbc error on sqlserver

Jump to solution

this error has come back on another installation...

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.