June 18, 2013 at 4:55 am
Hi,
We have a new MSServer 2012 / MSSQLServer 2012 Enterprise Edition, running under VMWare in a datacenter.
Currently we are migrating our customers from the production 2008R2 server.
We came across the following: the server crashed with the following event:
Faulting application name: sqlservr.exe, version: 2011.110.3128.0, time stamp: 0x50deadad
Faulting module name: myodbc5.dll, version: 5.1.12.0, time stamp: 0x51017fd2
Exception code: 0xc0000005
Fault offset: 0x0000000000027ad3
Faulting process id: 0x398
Faulting application start time: 0x01ce56239a757bee
Faulting application path: C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\sqlservr.exe
Faulting module path: C:\Program Files\MySQL\Connector ODBC 5.1\myodbc5.dll
Report Id: cb0ad250-d802-11e2-93fc-005056971d36
Faulting package full name:
Faulting package-relative application ID:
We use the MyODBC5.dll to connect to a number of MySQL databases. We've been doing this the past few years on our 2008R2 server and a crash never happened. We can even reproduce the crashing by connecting to a MySQL database.
Obvious question: what can we do to prevent SQL2012 from crashing?
Thanks,
Raymond
June 18, 2013 at 5:09 am
Are you running the latest version of the MySQL Driver? There are a few closed bugs for this sort of error in the MySQL dev site.
June 18, 2013 at 5:10 am
We noticed that once we remove the tablename (catalog) from the Linked Server, we can't reproduce crashing anymore. Maybe this will solve the issue? Any other feedback, background info etc. is appreciated.
October 6, 2013 at 5:32 am
Sorry to revive an old thread, but I found this in my environment and opened a Connect item on that - https://connect.microsoft.com/SQLServer/feedback/details/804671/sql-server-2012-sp1-build-3128-crashes-unexpectedly-after-creating-a-linked-server-using-odbc-provider, please vote up if you find it's relevant.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply