Post reply

Just migrated from 2008 to 2014... SQL Service keeps failing

  • July 3, 2015 at 9:20 am

    #318658

    So I just moved from a Windows 2003 / SQL 2008 server to a Windows 2012 R2 / SQL 2014 server.

    The past 2 days the SQL service seems to crash multiple times a day. I have checked in the event logs / SQL logs and I can't seem to find any smoking guns - but - I am not a DBA, nor am I any bit of a SQL expert.

    Our company is just cycling through the last of our Windows 2003 boxes - many of them already migrated have SQL on them. This is the only one thus far with this issue.

    I see this in the event log - but I don't really know what to do about it -

    Faulting application name: sqlservr.exe, version: 2014.120.4100.1, time stamp: 0x5535c7e7

    Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54505737

    Exception code: 0xc0000005

    Fault offset: 0x0000000000008b9c

    Faulting process id: 0x10e8

    Faulting application start time: 0x01d0b5970747d415

    Faulting application path: E:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Binn\sqlservr.exe

    Faulting module path: C:\Windows\system32\KERNELBASE.dll

    Report Id: 81894c90-2191-11e5-80c7-0050568c1782

    Faulting package full name:

    Faulting package-relative application ID:

    Any help is appreciated.

    Thanks

    sb

  • July 3, 2015 at 10:42 am

    #1810235

    What's in the SQL error log?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • July 6, 2015 at 5:11 am

    #1810393

    As my colleague said SQL Server error log should give more hints.

    The c0000005 error is a memory access violation error caused during service start up. Error log may point to the faulting module. Here is an example of a similar case:

    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/042824a3-05e6-47a2-baff-cb32a2235e96/sql-2008-hungs?forum=sqldatabaseengine

  • July 6, 2015 at 9:47 am

    #1810500

    Thank you for the responses. After looking through the event log, I see that the SQL service had been dying long before I moved this server into production. Because of this, I fired up a new server to move this instance to. This new server already has the database and agent jobs on it. It isn't in production yet, but the SQL service hasn't died once since Saturday. The other server has died 15 times in that time frame.

    Hopefully this will do the trick.

    -sb

  • July 13, 2015 at 10:25 am

    #1812072

    UPDATE -

    I rolled the new server into production - and had the same issue for 2 days. After some searching and reading blog posts - I found the issue to be with two of the linked servers. We have 2 ODBC DSNs configured on this server that point to Intersystems Cache databases.

    I modified the provider setting for the MSDASQL provider so that the linked servers do not run in process. This seemed to clear up the issue.

    This is what pointed me in the right direction:

    SQL Server crashes due to Link Server failure

    Thanks again for the involvement!

    sb

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply