Open GoogleCodeExporter opened 9 years ago
First, is it possible to use a DSN-less connection? I think that is a valid
work around. See here: http://support.microsoft.com/kb/822841
Second, I looked for a way to work around it in the library, but it isn't that
straightforward. It is being reported as an error, not as
SQL_SUCCESS_WITH_INFO. The SQL_SUCCEEDED macro I use everywhere treats both
SUCCESS and SUCCESS_WITH_INFO as success, so I always ignore warnings.
That means the connection probably did fail anyway, so ignoring it won't do any
good.
Notice that the article I linked to mentioned a hotfix is available. Since it
is so old, I suspect one of your servers is not up to date with patches? Is
that something you can look into also?
I'm going to put this on hold until I hear back, but I'm pretty sure that (1)
patches or (2) a DSN-less connection would be the best fixes.
Original comment by mkleehammer
on 21 Nov 2010 at 6:01
Original issue reported on code.google.com by
decal...@laposte.net
on 29 Jul 2010 at 11:58