Backup Failed in SQL 2014

Question

Post reply

Backup Failed in SQL 2014

Viewing 10 posts - 16 through 24 (of 24 total)

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

sri2015 SSCrazy Points: 2780 More actions · Answer 1

sri2015

SSCrazy

Points: 2780

April 20, 2015 at 9:18 am

#1792091

Probably it may help i will check update

sri2015 SSCrazy Points: 2780 More actions · Answer 2

I goggled and found that we can't move resource database.

and i gone through your link, can you give more details about "rebuild performance counters" ?

SQLSlammer Ten Centuries Points: 1045 More actions · Answer 3

I would go the CU2 route first if I were you, I actually hadn't noticed the second page of comments when I wrote my reply.

You only need to rebuild the counters if there are no rows in:

select * from sys.dm_os_performance_counters

sri2015 SSCrazy Points: 2780 More actions · Answer 4

I got 1514 rows when ran above select query.

and we have same setup (Backup in SQL 2014 RTM with Maintenance Plan) in Development server, which is running fine daily without issue.

But same setup in Production Server (also installed RS 2014) backup is getting failed with error message that i posted and its running fine after restart the SQL service for 2 or 3 days.

Diane Rayzer SSC Enthusiast Points: 140 More actions · Answer 5

I'm getting errors that are somewhat similar to the above posts... Backups are failing with the following error: Wanting to open up a case with Microsoft.. Can someone tell me how to do this... Do I call, do you have to have an account? thanks

Memory

MemoryLoad = 83%

Total Physical = 8191 MB

Available Physical = 1384 MB

Total Page File = 16381 MB

Available Page File = 7867 MB

Total Virtual = 8388607 MB

Available Virtual = 8377044 MB

***Stack Dump being sent to E:\MSSQL\SQL2014\MSSQL12.SQL2014\MSSQL\LOG\SQLDump1489.txt

SqlDumpExceptionHandler: Process 10104 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server

is terminating this process.

* *******************************************************************************

*

* BEGIN STACK DUMP:

* 05/05/15 16:25:02 spid 10104

* Private server build.

*

* Exception Address = 000007FEEE3E8D40 Module(sqlmin+0000000002C88D40)

* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION

* Access Violation occurred reading address FFFFFFFFFFFFFFFF

* Input Buffer 510 bytes -

* BACKUP LOG [XXXXXXXX] TO DISK = N'K:\Ba

* ckups\XXXXXXXX\XXXXXX_backup_2015_05_05_162502_0110873.trn'

* WITH NOFORMAT, NOINIT, NAME = N'CouponRequest_backup_2015_05_05_162502_

* 0110873', SKIP, REWIND, NOUNLOAD, STATS = 10

sri2015 SSCrazy Points: 2780 More actions · Answer 6

You need to call Microsoft they will guide you and contact numbers are given in below link.

also when you call they will ask your Subscription ID. make sure to have Subscription ID.

https://msdn.microsoft.com/en-us/subscriptions/aa948875.aspx

Andy sql SSCrazy Eights Points: 9496 More actions · Answer 7

Check if other processes are running at the same time, which could cause blocking on the drive/file. Maybe a separate backup job (nothing to do with MSSQL) is locking files, or AntiVirus, or even VSS.

Diane Rayzer SSC Enthusiast Points: 140 More actions · Answer 8

We don't have a SubscriptionID with Microsoft, we purchase Sql server licenses from a 3rd party vendor.. I'm still receiving the error however my co-worker found the following 5 files to be missing or hidden... Looks to be .Net Framework files... does anyone know if these are really causing my error (the backup failing due to: * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION ) - Process 9720 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. Is there a trace I can take to perhaps tell me more? Can someone tell me the fields I can use for the trace to capture this error?

Any help would be appreciated... (btw - if I restart the instance the errors stop for serveral days)

-- mscorlib.ni.dllC:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\abf62e6545d2802fc60286678a67e6bf\mscorlib.ni.dll4.0.30319.18444

-- System.Configuration.ni.dllC:\Windows\assembly\NativeImages_v4.0.30319_64 \System.Configuration\13bb14bb88e6c577c79001039d678bbd\System.Configuration.ni.dll4.0.30319.18408

-- System.Security.ni.dllC:\Windows\assembly\NativeImages_v4.0.30319_64\System.Security\a6153cf4b7a0d2e5c0f4f3e02de99150\System.Security.ni.dll4.0.30319.18408

-- System.Xml.ni.dllC:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml\fa4b9cda7a89969191429507a934c352\System.Xml.ni.dll4.0.30319.18408

-- System.ni.dllC:\Windows\assembly\NativeImages_v4.0.30319_64\System\4d4a15d5d7968df7dedd4cf853848d90\System.ni.dll4.0.30319.18408

Andy sql SSCrazy Eights Points: 9496 More actions · Answer 9

The .ni in the filenames refers to the "native image" version of the DLL. This is part of standard .NET functionality. Google for NGEN, JIT and MSIL.

Visual Studio can attach listeners to the processes, but this is getting quite involved - above my pay grade 🙂

These compiled system files *could* be doing anything on your system. However, they are not directly linked to MSSQL. I suggest you stop other processes/services on the server and see if that helps the MSSQL backup. It might even be worth re-applying the latest OS service pack (plus subsequent updates), or re-installing .NET.

Diane Rayzer SSC Enthusiast Points: 140 More actions · Answer 10

Thank you Ten Centuries:

Our networking dept. applied some patched to this server 4 days prior to the backups failing. A developer had been using visual studio on this server but he may have been using the incorrect visual studio version (I think he was using VS 2012).. And we've done a repair on the .NET... Perhaps we should reinstall .Net... Thank you I will look into trying what you suggest..