Hello folks,
I have an issue with ODBCJT32.DLL on a Itenium server that Yukon i64 (April
CTP)running on 64 bit Windows 2003 SP1 server. When we try to run a
distributed query that needs this driver SQL gives the following error:
Msg 7403, Level 16, State 1, Line 1
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
I ran component checker and it found ODBCJT32.DLL as registered to system.
However, I realized that MSJET40.DLL is not registered, didn't see it from
comp checker either. So I tried to install MDAC 2.8 SP8 (KB829558-ia64) but
it returns "There is no need to install this SP because setup has detected
that the system is newer than the update you are applying"
Now, my last card is manually register MSJET40.DLL to system. What do you
think? Any insight would be helpful.
Thanks in advance.
Sunny Jung
Since SQL 2005 is still in beta, you'll want to post this in the Community
Newsgroups:
http://communities.microsoft.com/new...r2005&slcid=us
--Brian
(Please reply to the newsgroups only.)
"SangHunJung" <SangHunJung@.discussions.microsoft.com> wrote in message
news:0270474D-18E6-400F-A5AF-1C3C457A0400@.microsoft.com...
> Hello folks,
> I have an issue with ODBCJT32.DLL on a Itenium server that Yukon i64
> (April
> CTP)running on 64 bit Windows 2003 SP1 server. When we try to run a
> distributed query that needs this driver SQL gives the following error:
> Msg 7403, Level 16, State 1, Line 1
> The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
> I ran component checker and it found ODBCJT32.DLL as registered to system.
> However, I realized that MSJET40.DLL is not registered, didn't see it from
> comp checker either. So I tried to install MDAC 2.8 SP8 (KB829558-ia64)
> but
> it returns "There is no need to install this SP because setup has detected
> that the system is newer than the update you are applying"
> Now, my last card is manually register MSJET40.DLL to system. What do you
> think? Any insight would be helpful.
> Thanks in advance.
> Sunny Jung
>
|||Okay, I posted it there.
However this seems like Win 2003 server 64bit issue. The reason is I don't
see any other ODBC drivers except SQL Native Client and SQL Server.
Normally, when creat a new data source, I would have a list of drivers to
select such as, microsoft excel, access, Fox Pro, etc. I don't see any of
them except two SQL driver. I think this is some thing to do with MDac but
there is no way I can uninstall MDAC and reinstall. Is there any way to do
that?
Thanks,
Sunny
"Brian Lawton" wrote:
> Since SQL 2005 is still in beta, you'll want to post this in the Community
> Newsgroups:
> http://communities.microsoft.com/new...r2005&slcid=us
>
> --
> --Brian
> (Please reply to the newsgroups only.)
>
> "SangHunJung" <SangHunJung@.discussions.microsoft.com> wrote in message
> news:0270474D-18E6-400F-A5AF-1C3C457A0400@.microsoft.com...
>
>
|||Hi
Most of those drivers have not been ported to 64bit, so you won't see them.
All what I've seen is UDB/DB2, Oracle, Sybase and SQL Server 64 bit drivers
for 64 bit Windows.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"SangHunJung" <SangHunJung@.discussions.microsoft.com> wrote in message
news:6C155DA0-52B3-4B82-A5F2-0B949BF64C21@.microsoft.com...[vbcol=seagreen]
> Okay, I posted it there.
> However this seems like Win 2003 server 64bit issue. The reason is I
> don't
> see any other ODBC drivers except SQL Native Client and SQL Server.
> Normally, when creat a new data source, I would have a list of drivers to
> select such as, microsoft excel, access, Fox Pro, etc. I don't see any of
> them except two SQL driver. I think this is some thing to do with MDac
> but
> there is no way I can uninstall MDAC and reinstall. Is there any way to
> do
> that?
> Thanks,
> Sunny
> "Brian Lawton" wrote:
|||Hi Mike,
That is really good to know. I was thinking about that but I could not find
any web-site saying about it. Is there a website that saying that those
drivers are not available to 64 bit except the ones that you listed below?
I have 32bit Windows 2003 and 32bit Yukon, I do have all the ODBC drivers
including Excel and Access on that server. Only different between two
servers are 32bit vs 64 bit.
Thank you in advance.
Sunny Jung
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Most of those drivers have not been ported to 64bit, so you won't see them.
> All what I've seen is UDB/DB2, Oracle, Sybase and SQL Server 64 bit drivers
> for 64 bit Windows.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "SangHunJung" <SangHunJung@.discussions.microsoft.com> wrote in message
> news:6C155DA0-52B3-4B82-A5F2-0B949BF64C21@.microsoft.com...
>
>
Showing posts with label dll. Show all posts
Showing posts with label dll. Show all posts
Monday, March 12, 2012
ODBCJT32.DLL on 64 bit Win 2003 SP1 & Yukon i64 server
Hello folks,
I have an issue with ODBCJT32.DLL on a Itenium server that Yukon i64 (April
CTP)running on 64 bit Windows 2003 SP1 server. When we try to run a
distributed query that needs this driver SQL gives the following error:
Msg 7403, Level 16, State 1, Line 1
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
I ran component checker and it found ODBCJT32.DLL as registered to system.
However, I realized that MSJET40.DLL is not registered, didn't see it from
comp checker either. So I tried to install MDAC 2.8 SP8 (KB829558-ia64) but
it returns "There is no need to install this SP because setup has detected
that the system is newer than the update you are applying"
Now, my last card is manually register MSJET40.DLL to system. What do you
think? Any insight would be helpful.
Thanks in advance.
Sunny JungSince SQL 2005 is still in beta, you'll want to post this in the Community
Newsgroups:
http://communities.microsoft.com/ne...lcid=us
--Brian
(Please reply to the newsgroups only.)
"SangHunJung" <SangHunJung@.discussions.microsoft.com> wrote in message
news:0270474D-18E6-400F-A5AF-1C3C457A0400@.microsoft.com...
> Hello folks,
> I have an issue with ODBCJT32.DLL on a Itenium server that Yukon i64
> (April
> CTP)running on 64 bit Windows 2003 SP1 server. When we try to run a
> distributed query that needs this driver SQL gives the following error:
> Msg 7403, Level 16, State 1, Line 1
> The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
> I ran component checker and it found ODBCJT32.DLL as registered to system.
> However, I realized that MSJET40.DLL is not registered, didn't see it from
> comp checker either. So I tried to install MDAC 2.8 SP8 (KB829558-ia64)
> but
> it returns "There is no need to install this SP because setup has detected
> that the system is newer than the update you are applying"
> Now, my last card is manually register MSJET40.DLL to system. What do you
> think? Any insight would be helpful.
> Thanks in advance.
> Sunny Jung
>|||Okay, I posted it there.
However this seems like Win 2003 server 64bit issue. The reason is I don't
see any other ODBC drivers except SQL Native Client and SQL Server.
Normally, when creat a new data source, I would have a list of drivers to
select such as, microsoft excel, access, Fox Pro, etc. I don't see any of
them except two SQL driver. I think this is some thing to do with MDac but
there is no way I can uninstall MDAC and reinstall. Is there any way to do
that?
Thanks,
Sunny
"Brian Lawton" wrote:
> Since SQL 2005 is still in beta, you'll want to post this in the Community
> Newsgroups:
> http://communities.microsoft.com/ne...lcid=
us
>
> --
> --Brian
> (Please reply to the newsgroups only.)
>
> "SangHunJung" <SangHunJung@.discussions.microsoft.com> wrote in message
> news:0270474D-18E6-400F-A5AF-1C3C457A0400@.microsoft.com...
>
>|||Hi
Most of those drivers have not been ported to 64bit, so you won't see them.
All what I've seen is UDB/DB2, Oracle, Sybase and SQL Server 64 bit drivers
for 64 bit Windows.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"SangHunJung" <SangHunJung@.discussions.microsoft.com> wrote in message
news:6C155DA0-52B3-4B82-A5F2-0B949BF64C21@.microsoft.com...[vbcol=seagreen]
> Okay, I posted it there.
> However this seems like Win 2003 server 64bit issue. The reason is I
> don't
> see any other ODBC drivers except SQL Native Client and SQL Server.
> Normally, when creat a new data source, I would have a list of drivers to
> select such as, microsoft excel, access, Fox Pro, etc. I don't see any of
> them except two SQL driver. I think this is some thing to do with MDac
> but
> there is no way I can uninstall MDAC and reinstall. Is there any way to
> do
> that?
> Thanks,
> Sunny
> "Brian Lawton" wrote:
>|||Hi Mike,
That is really good to know. I was thinking about that but I could not find
any web-site saying about it. Is there a website that saying that those
drivers are not available to 64 bit except the ones that you listed below?
I have 32bit Windows 2003 and 32bit Yukon, I do have all the ODBC drivers
including Excel and Access on that server. Only different between two
servers are 32bit vs 64 bit.
Thank you in advance.
Sunny Jung
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Most of those drivers have not been ported to 64bit, so you won't see them
.
> All what I've seen is UDB/DB2, Oracle, Sybase and SQL Server 64 bit driver
s
> for 64 bit Windows.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "SangHunJung" <SangHunJung@.discussions.microsoft.com> wrote in message
> news:6C155DA0-52B3-4B82-A5F2-0B949BF64C21@.microsoft.com...
>
>
I have an issue with ODBCJT32.DLL on a Itenium server that Yukon i64 (April
CTP)running on 64 bit Windows 2003 SP1 server. When we try to run a
distributed query that needs this driver SQL gives the following error:
Msg 7403, Level 16, State 1, Line 1
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
I ran component checker and it found ODBCJT32.DLL as registered to system.
However, I realized that MSJET40.DLL is not registered, didn't see it from
comp checker either. So I tried to install MDAC 2.8 SP8 (KB829558-ia64) but
it returns "There is no need to install this SP because setup has detected
that the system is newer than the update you are applying"
Now, my last card is manually register MSJET40.DLL to system. What do you
think? Any insight would be helpful.
Thanks in advance.
Sunny JungSince SQL 2005 is still in beta, you'll want to post this in the Community
Newsgroups:
http://communities.microsoft.com/ne...lcid=us
--Brian
(Please reply to the newsgroups only.)
"SangHunJung" <SangHunJung@.discussions.microsoft.com> wrote in message
news:0270474D-18E6-400F-A5AF-1C3C457A0400@.microsoft.com...
> Hello folks,
> I have an issue with ODBCJT32.DLL on a Itenium server that Yukon i64
> (April
> CTP)running on 64 bit Windows 2003 SP1 server. When we try to run a
> distributed query that needs this driver SQL gives the following error:
> Msg 7403, Level 16, State 1, Line 1
> The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
> I ran component checker and it found ODBCJT32.DLL as registered to system.
> However, I realized that MSJET40.DLL is not registered, didn't see it from
> comp checker either. So I tried to install MDAC 2.8 SP8 (KB829558-ia64)
> but
> it returns "There is no need to install this SP because setup has detected
> that the system is newer than the update you are applying"
> Now, my last card is manually register MSJET40.DLL to system. What do you
> think? Any insight would be helpful.
> Thanks in advance.
> Sunny Jung
>|||Okay, I posted it there.
However this seems like Win 2003 server 64bit issue. The reason is I don't
see any other ODBC drivers except SQL Native Client and SQL Server.
Normally, when creat a new data source, I would have a list of drivers to
select such as, microsoft excel, access, Fox Pro, etc. I don't see any of
them except two SQL driver. I think this is some thing to do with MDac but
there is no way I can uninstall MDAC and reinstall. Is there any way to do
that?
Thanks,
Sunny
"Brian Lawton" wrote:
> Since SQL 2005 is still in beta, you'll want to post this in the Community
> Newsgroups:
> http://communities.microsoft.com/ne...lcid=
us
>
> --
> --Brian
> (Please reply to the newsgroups only.)
>
> "SangHunJung" <SangHunJung@.discussions.microsoft.com> wrote in message
> news:0270474D-18E6-400F-A5AF-1C3C457A0400@.microsoft.com...
>
>|||Hi
Most of those drivers have not been ported to 64bit, so you won't see them.
All what I've seen is UDB/DB2, Oracle, Sybase and SQL Server 64 bit drivers
for 64 bit Windows.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"SangHunJung" <SangHunJung@.discussions.microsoft.com> wrote in message
news:6C155DA0-52B3-4B82-A5F2-0B949BF64C21@.microsoft.com...[vbcol=seagreen]
> Okay, I posted it there.
> However this seems like Win 2003 server 64bit issue. The reason is I
> don't
> see any other ODBC drivers except SQL Native Client and SQL Server.
> Normally, when creat a new data source, I would have a list of drivers to
> select such as, microsoft excel, access, Fox Pro, etc. I don't see any of
> them except two SQL driver. I think this is some thing to do with MDac
> but
> there is no way I can uninstall MDAC and reinstall. Is there any way to
> do
> that?
> Thanks,
> Sunny
> "Brian Lawton" wrote:
>|||Hi Mike,
That is really good to know. I was thinking about that but I could not find
any web-site saying about it. Is there a website that saying that those
drivers are not available to 64 bit except the ones that you listed below?
I have 32bit Windows 2003 and 32bit Yukon, I do have all the ODBC drivers
including Excel and Access on that server. Only different between two
servers are 32bit vs 64 bit.
Thank you in advance.
Sunny Jung
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Most of those drivers have not been ported to 64bit, so you won't see them
.
> All what I've seen is UDB/DB2, Oracle, Sybase and SQL Server 64 bit driver
s
> for 64 bit Windows.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "SangHunJung" <SangHunJung@.discussions.microsoft.com> wrote in message
> news:6C155DA0-52B3-4B82-A5F2-0B949BF64C21@.microsoft.com...
>
>
Wednesday, March 7, 2012
ODBC SQLINTEGER & (BADMEM) - Why?
Hi,
I have the ODBC tracing enabled on my development machine using the
"default" tracing DLL.
I thought it was just our applications causing this, but I'm also seeing
this when using isqlw (SQL Query Analyzer).
Is it an issue? The app. seems to have no issues. I know it is indicating
that the memory location is invalid. Why?
I would like to know what the cause is, what other tools are available to
track this down, in the event it is an issue. It doesn't seem like a
"normal" occurrence.
From our app:
12345678.A24 N 95c-cdcEXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS)
SQLHENV 008F1540
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 0x00000003 (BADMEM)
SQLINTEGER 0
12345678.A24 N 95c-cdcEXIT SQLSetConnectAttr with return code 0
(SQL_SUCCESS)
SQLHDBC 008F15E8
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 0x0000003C (BADMEM)
SQLINTEGER 0
From ISQLW:
isqlw edc-9c4EXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS)
SQLHENV 008D1540
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 0x00000003 (BADMEM)
SQLINTEGER -5
isqlw edc-9c4EXIT SQLSetConnectAttrW with return code 0
(SQL_SUCCESS)
SQLHDBC 008D15E8
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 0x0000000F (BADMEM)
SQLINTEGER -5
isqlw edc-9c4EXIT SQLSetStmtAttrW with return code 0
(SQL_SUCCESS)
SQLHSTMT 008D19B8
SQLINTEGER 3 <SQL_ATTR_MAX_LENGTH>
SQLPOINTER 0x0000FC00 (BADMEM)
SQLINTEGER -5
Thanks. Jeff
Hello,
This behavior seems to be normal because some parameters are not used when
calling this method. Also, the SQL_SUCCESS indicate these functions work
fine. For example:
SQLSetConnectAttr Function
http://msdn.microsoft.com/library/de...us/odbc/htm/od
bcsqlsetconnectattr.asp
ValuePtr
[Input]
Pointer to the value to be associated with Attribute. Depending on the
value of Attribute, ValuePtr will be a 32-bit unsigned integer value or
will point to a null-terminated character string. Note that if the
Attribute argument is a driver-specific value, the value in ValuePtr may be
a signed integer.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
I have the ODBC tracing enabled on my development machine using the
"default" tracing DLL.
I thought it was just our applications causing this, but I'm also seeing
this when using isqlw (SQL Query Analyzer).
Is it an issue? The app. seems to have no issues. I know it is indicating
that the memory location is invalid. Why?
I would like to know what the cause is, what other tools are available to
track this down, in the event it is an issue. It doesn't seem like a
"normal" occurrence.
From our app:
12345678.A24 N 95c-cdcEXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS)
SQLHENV 008F1540
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 0x00000003 (BADMEM)
SQLINTEGER 0
12345678.A24 N 95c-cdcEXIT SQLSetConnectAttr with return code 0
(SQL_SUCCESS)
SQLHDBC 008F15E8
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 0x0000003C (BADMEM)
SQLINTEGER 0
From ISQLW:
isqlw edc-9c4EXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS)
SQLHENV 008D1540
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 0x00000003 (BADMEM)
SQLINTEGER -5
isqlw edc-9c4EXIT SQLSetConnectAttrW with return code 0
(SQL_SUCCESS)
SQLHDBC 008D15E8
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 0x0000000F (BADMEM)
SQLINTEGER -5
isqlw edc-9c4EXIT SQLSetStmtAttrW with return code 0
(SQL_SUCCESS)
SQLHSTMT 008D19B8
SQLINTEGER 3 <SQL_ATTR_MAX_LENGTH>
SQLPOINTER 0x0000FC00 (BADMEM)
SQLINTEGER -5
Thanks. Jeff
Hello,
This behavior seems to be normal because some parameters are not used when
calling this method. Also, the SQL_SUCCESS indicate these functions work
fine. For example:
SQLSetConnectAttr Function
http://msdn.microsoft.com/library/de...us/odbc/htm/od
bcsqlsetconnectattr.asp
ValuePtr
[Input]
Pointer to the value to be associated with Attribute. Depending on the
value of Attribute, ValuePtr will be a 32-bit unsigned integer value or
will point to a null-terminated character string. Note that if the
Attribute argument is a driver-specific value, the value in ValuePtr may be
a signed integer.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
ODBC SQLINTEGER & (BADMEM) - Why?
Hi,
I have the ODBC tracing enabled on my development machine using the
"default" tracing DLL.
I thought it was just our applications causing this, but I'm also seeing
this when using isqlw (SQL Query Analyzer).
Is it an issue? The app. seems to have no issues. I know it is indicating
that the memory location is invalid. Why?
I would like to know what the cause is, what other tools are available to
track this down, in the event it is an issue. It doesn't seem like a
"normal" occurrence.
From our app:
12345678.A24 N 95c-cdc EXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS
)
SQLHENV 008F1540
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 0x00000003 (BADMEM)
SQLINTEGER 0
12345678.A24 N 95c-cdc EXIT SQLSetConnectAttr with return code 0
(SQL_SUCCESS)
SQLHDBC 008F15E8
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 0x0000003C (BADMEM)
SQLINTEGER 0
From ISQLW:
isqlw edc-9c4 EXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS
)
SQLHENV 008D1540
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 0x00000003 (BADMEM)
SQLINTEGER -5
isqlw edc-9c4 EXIT SQLSetConnectAttrW with return code 0
(SQL_SUCCESS)
SQLHDBC 008D15E8
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 0x0000000F (BADMEM)
SQLINTEGER -5
isqlw edc-9c4 EXIT SQLSetStmtAttrW with return code 0
(SQL_SUCCESS)
SQLHSTMT 008D19B8
SQLINTEGER 3 <SQL_ATTR_MAX_LENGTH>
SQLPOINTER 0x0000FC00 (BADMEM)
SQLINTEGER -5
Thanks. JeffHello,
This behavior seems to be normal because some parameters are not used when
calling this method. Also, the SQL_SUCCESS indicate these functions work
fine. For example:
SQLSetConnectAttr Function
http://msdn.microsoft.com/library/d...-us/odbc/htm/od
bcsqlsetconnectattr.asp
ValuePtr
[Input]
Pointer to the value to be associated with Attribute. Depending on the
value of Attribute, ValuePtr will be a 32-bit unsigned integer value or
will point to a null-terminated character string. Note that if the
Attribute argument is a driver-specific value, the value in ValuePtr may be
a signed integer.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
I have the ODBC tracing enabled on my development machine using the
"default" tracing DLL.
I thought it was just our applications causing this, but I'm also seeing
this when using isqlw (SQL Query Analyzer).
Is it an issue? The app. seems to have no issues. I know it is indicating
that the memory location is invalid. Why?
I would like to know what the cause is, what other tools are available to
track this down, in the event it is an issue. It doesn't seem like a
"normal" occurrence.
From our app:
12345678.A24 N 95c-cdc EXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS
)
SQLHENV 008F1540
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 0x00000003 (BADMEM)
SQLINTEGER 0
12345678.A24 N 95c-cdc EXIT SQLSetConnectAttr with return code 0
(SQL_SUCCESS)
SQLHDBC 008F15E8
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 0x0000003C (BADMEM)
SQLINTEGER 0
From ISQLW:
isqlw edc-9c4 EXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS
)
SQLHENV 008D1540
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 0x00000003 (BADMEM)
SQLINTEGER -5
isqlw edc-9c4 EXIT SQLSetConnectAttrW with return code 0
(SQL_SUCCESS)
SQLHDBC 008D15E8
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 0x0000000F (BADMEM)
SQLINTEGER -5
isqlw edc-9c4 EXIT SQLSetStmtAttrW with return code 0
(SQL_SUCCESS)
SQLHSTMT 008D19B8
SQLINTEGER 3 <SQL_ATTR_MAX_LENGTH>
SQLPOINTER 0x0000FC00 (BADMEM)
SQLINTEGER -5
Thanks. JeffHello,
This behavior seems to be normal because some parameters are not used when
calling this method. Also, the SQL_SUCCESS indicate these functions work
fine. For example:
SQLSetConnectAttr Function
http://msdn.microsoft.com/library/d...-us/odbc/htm/od
bcsqlsetconnectattr.asp
ValuePtr
[Input]
Pointer to the value to be associated with Attribute. Depending on the
value of Attribute, ValuePtr will be a 32-bit unsigned integer value or
will point to a null-terminated character string. Note that if the
Attribute argument is a driver-specific value, the value in ValuePtr may be
a signed integer.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to:
Posts (Atom)