ODBCBCP Driver Mismatch

Hello,
I am receiving the following error message whenever I try to replicate using Snapshot repl. (or any type of replication) from the snapshot agent:
Error Message: The process could not bulk copy out of table '[dbo].[syncobj_xxxxxxxx]'.
Error Details: ODBCBCP/Driver version mismatch
(Source: ODBC SQL Server Driver (ODBC); Error number: 0)
I have checked the versions of the odbcbcp.dll on both of my SQL Servers (both of which are win2k3 w/ SQL Server 2000 sp3) and they are both 2000.85.1022.0. The version number of sqlsrv32.dll and sqlsrv32.rll are 2000.85.1025.0. Do all three have to mat
ch, is that my problem? Please HELP!! I can't replicate at all!
there are some reports that this problem can be solved by upgrading to a
consistent MDAC versions on both machines.
"Paul Pelletier" <anonymous@.discussions.microsoft.com> wrote in message
news:3E372B82-39B2-4A93-B7DE-5B7740527F13@.microsoft.com...
> Hello,
> I am receiving the following error message whenever I try to replicate
using Snapshot repl. (or any type of replication) from the snapshot agent:
> Error Message: The process could not bulk copy out of table
'[dbo].[syncobj_xxxxxxxx]'.
> Error Details: ODBCBCP/Driver version mismatch
> (Source: ODBC SQL Server Driver (ODBC); Error number: 0)
> I have checked the versions of the odbcbcp.dll on both of my SQL Servers
(both of which are win2k3 w/ SQL Server 2000 sp3) and they are both
2000.85.1022.0. The version number of sqlsrv32.dll and sqlsrv32.rll are
2000.85.1025.0. Do all three have to match, is that my problem? Please
HELP!! I can't replicate at all!
|||Hillary,
I have, I re-applied MDAC 2.7 on both SQL Servers and still the same problem. Any other possible solutions?
Do all there files have to have the same version numbers?
Thanks,
Paul
|||Check the version of the ODBC32.dll. It could be the one that is
mismatched. It should be version 3.525.1022.0.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||It is mismatched in a sense. The odbcbcp.dll is version 2000.85.1022.0. The sqlsrv32.dll is 2000.85.1025.0. The sqlsrv32.rll is 2000.85.1025.0. So really the one that is mismatched is the sqlsrv32.dll, but which version should be the correct version f
or all three, the 1025 or 1022?
Thanks again,
Paul
|||Sorry about the previous post, I did not completely read your post and I missed the fact that you were talking about a completely different dll, I'm a tard! Anyway both of the odbc32.dll do match on both machines and they are in fact 3.525.1022.0. Where
now?

ODBC inserting against open cursor

Im receiving 'HY000 Connection is busy with results for another hstmt' when trying to insert. The reason is down to another hstmt with a cursor still open (as not all results have been fetched) against the same connection handle. My current design is one connect handle per file, with multiple statement handle depending on sql issued so i dont need to rebind.
I'm guessing, but is there a sqlsetconnectattr/sqlsetstmtattr setting to which will allow me to insert/update/delete to a file with a open cursor that may include the result ?

sqlserver version 8So more like you've locked the rows...

Look at sp_lock...|||doesnt seem like a locking issue, as cant insert. sp_lock shows one new process with a lock mode S (presume shared, to which insert should be ok)

my sql generated ..

DECLARE KSQL$001_00 CURSOR FOR SELECT ROWID,KEY_1A,KEY_5A,KEY_NUM
BER,SOMETHING FROM A2R.DBO.CJS ORDER BY KEY_5A,KEY_NUMBER,KEY_1A

OPEN KSQL$001_00

FETCH KSQL$001_00

INSERT INTO A2R.DBO.CJS(KEY_1A,KEY_5A,KEY_NUMBER,SOMETHING) VALUES (?,?,?,?)

[Microsoft][ODBC SQL Server Driver]Connection is busy with results for another h
stmt
****************************
HY000

The above is fine via SQLQuery (note: ? are sqlbindparameter), but not ODBC?|||In RDO it used to be rdOpenForwardOnly resultset qualifier that would allow you to issue action queries on the same connection while the resultset mentioned above is open.|||Cheers for pointing me in the right direction,
I needed to issue the following, which now allows insert etc with open cursors.

SQLSetStmtAttr(vsql_area.current_logon->stmt_current>hstmt,
SQL_ATTR_CURSOR_SENSITIVITY,
SQL_INSENSITIVE,
1);

Regards,
Carl.