Backup Database is terminated Abnormally Failed

Hi All,
My Database backup is not working in SQL 2014 RTM version. It works fine on SQL Server 2008 R2.
All databases are in Simple recovery model. Not sure what might be the issue. I'm admin for SQL instance and on the box.
DECLARE @BackupFile1
varchar(max)
SET @BackupFile1
= 'E:\MSSQL\Bak\DailyBackups\MSDB\MSDB1_'
+ REPLACE(REPLACE(REPLACE(CONVERT(varchar,GETDATE(),
112),'-',''),':',''),'
+ '.BAK'
BACKUP
DATABASE MSDB TO
DISK
= @BackupFile1
WITH
NOFORMAT,
NOINIT, NAME
= N'MSDB-Full Database Backup',
SKIP,
NOREWIND,
NOUNLOAD, COMPRESSION,MAXTRANSFERSIZE
= 4194304,
STATS = 10
Error:
Msg 3013, Level 16, State 1, Line 25
BACKUP DATABASE is terminating abnormally.

Can you try it again?
Can you try it from SSMS Object Explorer GUI ?
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Similar Messages

BACKUP DATABASE is terminating abnormally

Dear All,
I'm frequently getting the following error message, please provide me detailed description on how to troubleshoot the following issue. I really appreciate everyone to share your valuable information with me.
Issue: At 2014-09-27 21:28:26 the Windows Event Log - SQL 2008 service transitioned from a Normal state
to a Failed state.
Here are the details of the Windows Event Log - SQL 2008 service:
Event Log Module Status: 0
The Last Record Number of the eventlog type that current event entry belongs to: 0
# of duplicate events: 23
Source: SQLWRITER
Category: None
Event ID: 24583
User (If Applicable): N/A
Computer: SERVER.XXX.local
Event Description: Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000,
Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3202
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: Write on "{2BFC2AF2-F73B-48D2-B9D6-6A78271F8800}20" failed: 995(The I/O operation has been
aborted because of either a thread exit or an application request.)
Event Log Name: Application
Event Log Type: error
Event Log Date Time: 2014-09-27 21:02:49
Thanks
DBA

You got no responses because you posted in the wrong forum
Are you backing up to a tape or disk device? This error usually points to a media problem (not a DB problem). Can you backup the DB to disk and see if it works?
Satish Kartan www.sqlfood.com

File name in msdb.dbo.backupset no longer matches the actual file name on the storage media. Error 3013 Restore Database is terminating abnormally.

Thanks in advance for taking the time to read this and comment. Platform: Windows Server 2008 R2 Enterprise Edition SP1 (X64) Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Jun 17 2011 00:54:03 Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)Problem Description: The file name recorded in the msdb.dbo.backupset (sans the extension) no longer matches the actual file name written to the backup media which is
in this case a NETAPP NAS storage share. Example:
Mohave_backup_2014_03_14_233001_1158878.bak      (from NETAPP NAS filer)
Mohave_backup_2014_03_16_233001_4167237             (from MSDB.dbo.backupset), as you can see, the last 7 digits (chars) of the file name are different, although the date and time are identical. The
file names had previously been matching perfectly. The first occurance of this problem occured on 03/13/2014 at 5:00 AM MST. The error generated by the job was:
Date  3/14/2014 10:29:23 AM
Log  Job History (Refresh - Restore Mohave_93_DEV AD HOC)
Step ID  1
Server  OurDevServer
Job Name  Refresh - Restore Mohave_93_DEV AD HOC
Step Name  Restore Mohave_93_DEV
Duration  00:00:01
Sql Severity  0
Sql Message ID  50000
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted  0
Message
Executed as user: OurDomain\OurNetworkServiceLogin. Restore Mohave Prod to Mohave_93_DEV - ERROR: 3013 RESTORE DATABASE is terminating abnormally. [SQLSTATE 01000] (Message 50000). The step succeeded.

Olaf:
Thanks for your reply. Sorry, my bad. I inadvertently copied wrong [name] form the msdb.dbo.backupset. On 3/13 and 3/14, the two file names did not match. In trying to select another example to show you this morning, I found that the names are now matching!
What I was doing was to create dynamic t-sql to retrieve the latest prod backup of the database, and then restore it with move to the development server. This is an ad-hoc job that the developers can run by themselves whenever they require a refresh. Unfortunately,
we only keep 3 days worth of backups for these databases, so the original disk file I was trying to use to restore no longer exists. Researching the original error, one of the error descriptions was that the restore could not find the file requested.
I thought this very strange since I get the file name directly from the backupset table. Further research did indeed show that the file names were different, but unfortunately, I failed to save the details of the file names. Anyway, in looking for a new example
to show you this morning, I have found that the file names are indeed matching exactly again. If this error pops up again, I will be sure to save all details and re-post.
Thanks, regards and best wishes to you and yours,

Backup log is terminating abnormally

Hi Experts
I am unable to take the backup in tape, i am getting a error "sqlstate 42000" operation on device R3DUMP exceeded retry count backup log is terminating abnormally.
Thanks in advance
Regards
Venkat

Hi Experts
I am unable to take the backup in tape, i am getting a error "sqlstate 42000" operation on device R3DUMP exceeded retry count backup log is terminating abnormally.
Thanks in advance
Regards
Venkat

Restore database to azure blob failed

Hi experts,
I create a test db in SQL on Azure VM and backup to my storage account successfully. However, when I delete the database and restore using the T-SQL below, it failed. Please help.
--- query ---
USE [master]
RESTORE DATABASE [test] FROM
URL = N'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014/test_backup_2014_08_18_013128.bak'
WITH CREDENTIAL = N'AzureCredential' , FILE = 1,
MOVE N'test' TO N'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014//test.mdf',
MOVE N'test_log' TO N'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014//test_log.ldf', NOUNLOAD, STATS = 5
GO
--- result ---
Msg 3634, Level 16, State 1, Line 2
The operating system returned the error '50(The request is not supported.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014//test.mdf'.
Msg 3156, Level 16, State 8, Line 2
File 'test' cannot be restored to 'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014//test.mdf'. Use WITH MOVE to identify a valid location for the file.
Msg 3634, Level 16, State 1, Line 2
The operating system returned the error '50(The request is not supported.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014//test_log.ldf'.
Msg 3156, Level 16, State 8, Line 2
File 'test_log' cannot be restored to 'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014//test_log.ldf'. Use WITH MOVE to identify a valid location for the file.
Msg 3119, Level 16, State 1, Line 2
Problems were identified while planning for the RESTORE statement. Previous messages provide details.
Msg 3013, Level 16, State 1, Line 2
RESTORE DATABASE is terminating abnormally.

One has to install Azure Storage Explorer and add Read/Write permissions in Shared Access Key

BACKUP failed to complete the command BACKUP DATABASE. Check the backup application log for detailed messages.

Hi,
We have a back up that is failing.
The error is "BACKUP failed to complete the command BACKUP DATABASE RPS. Check the backup application log for detailed messages.".
As I understand it the backup application log is at C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\LOG. From that all I get is
2014-03-05 14:49:29.41 Backup Error: 3041, Severity: 16, State: 1.
2014-03-05 14:49:29.41 Backup BACKUP failed to complete the command BACKUP DATABASE myDb. Check the backup application log for detailed messages.
The command I am using is
BACKUP DATABASE [MyDb]
TO DISK = N'D:\Domains\SQL_Backup\DB\myDb\Mydb_FullBackup_20140305_1100.bak'
WITH NOFORMAT, NOINIT, NAME = N'mydb-Full Database Backup', SKIP, NOREWIND, NOUNLOAD, STATS = 10
GO
The database is Microsoft SQL Server Standard Edition (64-bit) Version 9.00.1399.06.
The computer is Windows server 2003 R2 Standard Edition SP2
The Db is 191 Gb and there is 227 Gb available on the D drive where it's being backed up to.
Any thoughts as to how I can track down the problem.
Is the 227Gb of spare disk space big enough to back up a 191 Gb database?
If not how much is needed?
Thanks

Hello,
Can you apply latest service pack .I dont know but guess that can be issue.Once faced ,not quite sure.Also can you just make your command like
BACKUP DATABASE [MyDb]
TO DISK = 'D:\Domains\SQL_Backup\DB\myDb\Mydb_FullBackup_20140305_1100.bak'
WITH NOFORMAT, NOINIT, STATS = 10
GO
Just a simple one .Is backup failing immediately or after some time .Error is not so helpful as it does not shows any information
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Backup database fail

hi am trying to do backup using rman but database fail
C:\>rman target sys/pswd@sid NOCATALOG
Recovery Manager: Release 11.2.0.1.0 - Production on Thu Nov 7 17:47:34 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: SMSDEV (DBID=3638300981, not open)
using target database control file instead of recovery catalog
RMAN> backup database;
Starting backup at 07-NOV-13
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=133 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00010 name=C:\APP\TSHIFHIWA\PRODUCT\11.2.0\DBHOME_1\DATABASE\TEST
input datafile file number=00008 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\GATEWAY_TBS.DBF
input datafile file number=00001 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\SYSTEM01.DBF
input datafile file number=00002 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\SYSAUX01.DBF
input datafile file number=00003 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\UNDOTBS01.DBF
input datafile file number=00004 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\USERS01.DBF
input datafile file number=00007 name=C:\APP\TSHIFHIWA\PRODUCT\11.2.0\DBHOME_1\DATABASE\TEMP09
input datafile file number=00009 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\ECADASTRE_TBS.DBF
input datafile file number=00005 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\TEMP06.DBF
input datafile file number=00006 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\TEMP05.DBF
channel ORA_DISK_1: starting piece 1 at 07-NOV-13
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 11/07/2013 17:51:55
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 5218762752 limit
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 07-NOV-13
channel ORA_DISK_1: finished piece 1 at 07-NOV-13
piece handle=C:\APP\TSHIFHIWA\FLASH_RECOVERY_AREA\SMSDEV\BACKUPSET\2013_11_07\O1_MF_NCSNF_TAG2013110
t=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 11/07/2013 17:51:55
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 5218762752 limit

i did this still geting error
SQL> connect /as sysdba
Connected.
SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE=4294967296 SCOPE=BOTH;
System altered.
SQL> commit;
Commit complete.
SQL> shutdown abort;
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 535662592 bytes
Fixed Size                  1375792 bytes
Variable Size             373293520 bytes
Database Buffers          155189248 bytes
Redo Buffers                5804032 bytes
Database mounted.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Pr
oduction
With the Partitioning, OLAP, Data Mining and Real Application Testing options
C:\>rman target sys/pswd@SID NOCATALOG
Recovery Manager: Release 11.2.0.1.0 - Production on Thu Nov 7 19:16:33 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: SMSDEV (DBID=3638300981, not open)
using target database control file instead of recovery catalog
RMAN> delete backup;
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=133 device type=DISK
List of Backup Pieces
BP Key BS Key Pc# Cp# Status      Device Type Piece Name
3       3       1   1   AVAILABLE   DISK        C:\APP\TSHIFHIWA\FLASH_RECOVERY_
AREA\SMSDEV\BACKUPSET\2013_11_07\O1_MF_NCSNF_TAG20131107T182444_97QHXTTS_.BKP
4       4       1   1   AVAILABLE   DISK        C:\APP\TSHIFHIWA\FLASH_RECOVERY_
AREA\SMSDEV\BACKUPSET\2013_11_07\O1_MF_NCSNF_TAG20131107T183949_97QJSS14_.BKP
7       7       1   1   AVAILABLE   DISK        C:\APP\TSHIFHIWA\FLASH_RECOVERY_
AREA\SMSDEV\BACKUPSET\2013_11_07\O1_MF_NCSNF_TAG20131107T191006_97QLKMYL_.BKP
Do you really want to delete the above objects (enter YES or NO)? yes
deleted backup piece
backup piece handle=C:\APP\TSHIFHIWA\FLASH_RECOVERY_AREA\SMSDEV\BACKUPSET\2013_1
1_07\O1_MF_NCSNF_TAG20131107T191006_97QLKMYL_.BKP RECID=7 STAMP=830891603
Deleted 1 objects
RMAN-06207: WARNING: 2 objects could not be deleted for DISK channel(s) due
RMAN-06208:          to mismatched status. Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
RMAN-06212:   Object Type   Filename/Handle
RMAN-06213: --------------- ---------------------------------------------------
RMAN-06214: Backup Piece    C:\APP\TSHIFHIWA\FLASH_RECOVERY_AREA\SMSDEV\BACKUPSE
T\2013_11_07\O1_MF_NCSNF_TAG20131107T182444_97QHXTTS_.BKP
RMAN-06214: Backup Piece    C:\APP\TSHIFHIWA\FLASH_RECOVERY_AREA\SMSDEV\BACKUPSE
T\2013_11_07\O1_MF_NCSNF_TAG20131107T183949_97QJSS14_.BKP
RMAN> backup database;
Starting backup at 07-NOV-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00010 name=C:\APP\TSHIFHIWA\PRODUCT\11.2.0\DBHOME_1\D
ATABASE\TEST
input datafile file number=00008 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\GATEWAY_TB
S.DBF
input datafile file number=00001 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\SYSTEM01.D
BF
input datafile file number=00002 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\SYSAUX01.D
BF
input datafile file number=00003 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\UNDOTBS01.
DBF
input datafile file number=00004 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\USERS01.DB
F
input datafile file number=00007 name=C:\APP\TSHIFHIWA\PRODUCT\11.2.0\DBHOME_1\D
ATABASE\TEMP09
input datafile file number=00009 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\ECADASTRE_
TBS.DBF
input datafile file number=00005 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\TEMP06.DBF
input datafile file number=00006 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\TEMP05.DBF
channel ORA_DISK_1: starting piece 1 at 07-NOV-13
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 11/07/2013 19:20:
10
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 4294967296 limit
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 07-NOV-13
channel ORA_DISK_1: finished piece 1 at 07-NOV-13
piece handle=C:\APP\TSHIFHIWA\FLASH_RECOVERY_AREA\SMSDEV\BACKUPSET\2013_11_07\O1
_MF_NCSNF_TAG20131107T191653_97QLYCJK_.BKP tag=TAG20131107T191653 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 11/07/2013 19:20:
10
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk
space from 4294967296 limit

Backup database; failed

This problem first occurred with the Oracle recommended backup suggested in Enterprise Manager 10g.
After it occurred I went to RMAN and typed:
backup database;
The following (after the error stack) was displayed.
RMAN-03009: failure of backup command on ORA_DISK_1 channel at <date goes here>
ORA-00600: internal error code, arguments: [krbb0ef_inv_blk_2],[], [], [], [], [], [], []
This is essentially the same trace file errors from the Oracle recommended backup failure.
I ran DBV .. nothing corrupted.
No satisfaction from MetaLink/ SR either.
Any ideas ?
Thanks in advance.

I tried as you suggested and no errors where reported.
I attempted the backup again and the same results.
I'm very disappointed with Oracle Support. They have told me
nothing in the last four days.
What am I paying for ??
Thanks for your help.
Brian

1st RMAN backup database plus archivelog fails

Hi
I've just setup RMAN on Oracle 11g within a two node cluster environment.
I have completed the following:
* Created a recovery catalog
* Registed Database
* Configured retention policy window of 7 days
* Configured default device type to disk
* configured controlfile autobackup on;
* configured device type disk backup type to compressed backupset
* configured channel device type disk format
* validated database
* backup database plus archivelog and I received the following error,
RMAN> backup database plus archivelog;
Starting backup at 24/07/2008 17:37:17
current log archived
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 07/24/2008 17:37:20
RMAN-06059: expected archived log not found, lost of archived log compromises re coverability
ORA-19625: error identifying file /u01/app/product/admin/RAC/arc/rac2_2_4_660689 305.arc
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
On node 2 I can list the file:
SQL> !ls -lt
total 4120
-rw-rw---- 1 rac dba 14336 Jul 24 17:18 rac2_2_5_660689305.arc
-rw-rw---- 1 rac dba 4196352 Jul 24 17:13 rac2_2_4_660689305.arc
SQL>

Read the chapter
http://download.oracle.com/docs/cd/B28359_01/rac.111/b28254/rman.htm#i474611
The node that is doing backups must be configured to have access to archivelogs on all the nodes.
See "RMAN Archiving Configuration Scenarios" -> "Noncluster File System Local Archiving Scheme".

How to do backup database in the menu of Oracle XE

Dear all,
When I do database backup selecting from the Oracle XE menu, it output the error as below :
sql statement: create pfile=''C:\ORACLEXE\APP\ORACLE\PRODUCT\10.2.0\SERVER\DATABASE\SPFILE2INIT.ORA'' from spfile
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 08/31/2006 17:14:14
RMAN-20000: abnormal termination of job step
RMAN-11003: failure during parse/execution of SQL statement: create pfile='C:\ORACLEXE\APP\ORACLE\PRODUCT\10.2.0\SERVER\DATABASE\SPFILE2INIT.ORA' from spfile
RMAN-11001: Oracle Error:
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
Best regards,
Simon Wong

Don't duplicate thread:
Cannot do backup database in the startup menu!!
It's also easier to help you if we have all information and
errors regarding this issue on one place.
Thanks!

R12 upgrade patch terminating abnormally

I am applying R12 upgrade patch 6678700 and it is terminating abnormally.The patch session come to command prompt.
The DB is one one node application is on another node.The database version is 11.2.0.3 and it is on linux OEL 5.5 64bit.Please help me to resolve this issue.
Thanks in advance..

Hi,
Please check the patch log for more information and check at which worker it failed and also check the worker log, let us know the information from those log files.

Wait on the Database Engine recovery handle failed. Check the SQL server error log for potential causes in SQL Server 2012 Developer Edition

I m using SQL Server 2012 Developer Edition. Even I tried 2012 express and enterprise edition but all
gave same error. I browsed msdn blog. But nothing help me out.
Below is the error log details--
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2013-10-21 12:58:05
End time: 2013-10-21 13:52:30
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: CROY-TOSH
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: C:\Users\CRoy\Downloads\SQL Server 2012 Developer Edition (x86 and x64) - DVD (English)\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AI
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: CRoy-TOSH\CRoy
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: ROY
CLTRESULTDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: CRoy-TOSH\CRoy
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK, MDS
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: CRoy-TOSH\CRoy
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: SQL Server Data Tools
Status: Passed
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration Services
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: Reporting Services - SharePoint
Status: Passed
Feature: Reporting Services Add-in for SharePoint Products
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\SystemConfigurationCheck_Report.htm

Hi,
This 3rd time I followed this link. But nothing new, same error.
Can you please tell me how to do follow, I cannt do the 1st step, how to change the local system to windows level account, vice-versa. It is shown mine as
Server Configuration Manager(Local)
From here I folllowed the steps ---[I cannt insert link/image :-(]
SQL 2008/R2 setup fails with "Wait on the database engine recovery handle failed"
If I right clicked on SQL Server Service, there is no option to change the account.
Hello,
Thanks for your patience,did you tried stesp mentioned in below article
http://blogs.msdn.com/b/sqljourney/archive/2012/03/16/sql-2008-r2-setup-fails-with-quot-wait-on-the-database-engine-recovery-handle-failed-quot.aspx
To resolve it, follow these steps:-
When the installation throws this error, click on OK and allow it to proceed. It will fail for Database Engine, but the SQL Server service should have
been created. Check the Services console.
If the service is present, perform the following steps:-
1. Go to SQL Server Configuration manager, right click on the SQL Server service, and change the service account (if it is local system, give
it a windows level account, and vice-versa). It might throw a WMI error but you will see the account getting updated anyway. If not, then use the Services console. Change the account for SQL Agent as well.
Use this link to change sql server service account
http://technet.microsoft.com/en-us/library/ms345578.aspx
2. Next, try to start the service. It should come online.
3. However, you will not be able to log in to the SQL Server
4. Now stop the service and start it from the command prompt using -m -c -T3608 parameters.
5. Now try logging in to the server using admin connection from sqlcmd (sqlcmd admin:<server name>\<instance name> ...)
6. Once logged in, use the sp_addsrvrolemember '<domain\username>','sysadmin'.
Also add the builtin/administrators to the sysadmin role
7. Now stop the service from the command prompt and start it from SQL Server configuration manager
You should be able to log in to the server now.
Hope this helps someone.
Please revert if it helps or even if it does not
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Backup Database Task - User Permissions

Hi
I am currently implementing an SSIS package to cater for the backup of our database system. I am using a Back Up Database Task connecting to the database using SQL Authentication. This login has public server rights and db_backupoperator database
role rights.
Having tested the package, it seems to fail on the backup task because of the following error:
[Execute SQL Task] Error: Executing the query "BACKUP DATABASE [CAAP] TO DISK = N'R:\CAAP_Backup..." failed with the following error: "Only users who are members of the following roles can perform this operation: sysadmin fixed server
role; dbowner or dbcreator fixed database role in the current database.
Only users who are members of the following roles can perform this operation: sysadmin fixed server role; dbowner or dbcreator fixed database role in the current database.
Why does it need dbOwner/dbCreator/sysadmin rights to execute a simple backup? Isn't this the point of the dbBackupOperator role?
Thanks.

Hi divvyboy,
I am unable to reproduce the issue in my test environment. The backup script works well in an Execute SQL Task which uses the ADO .NET Connection Manager created by a Back Up Database Task using SQL Server authentication type. Only the Public and db_backupoperator
database roles is okay.
According to the screenshots, the error was thrown by the Execute SQL Task actually. Since the package also contains a Back Up Database Task, there is no need to perform the backup operation from the Execute SQL Task. You can test whether the Back Up Database
Task which doesn’t need us to input a backup script can perform the database backup correctly. If the Back Up Database Task works well, you can remove the Execute SQL Task and go with the Back Up Database Task.
Regards,
Mike Yin
TechNet Community Support

Process Monitor process terminated abnormally

Hi,
I have got the following error on my live oracle8.0 database.
Error Code: ORA-00472 PMON process terminated with error
Cause: The Process Monitor process terminated abnormally.
Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.
I have checked the log files as well as the trace files and I get the message that PMON is terminated.
Kindly, tell me is there any way to recover this PMON process or I have to recreate the whole database?
While recreating the whole database, I may loose the data for 3 - 4 days.
Re-entering the data is not the problem for me, but I want to know how can I recover this process.
Thanks.
Regards,
Mihir

Were there any messages leading up to the PMON termination, explanations of what the problem was, etc?
Assuming that you've been committing transactions along the way, you may be able to simply shut down the database and restart it without losing any data. Re-creating the database would be terribly drastic, and might not accomplish anything if the cause of the PMON termination isn't identified.
Justin
Distributed Database Consulting, Inc.
www.ddbcinc.com/askDDBC

SQL error: Internal database error *** ERROR *** Assertion failed: 201501 (10.0.1.3415)

A SQLA10 production database has been crashing at a customer site.
Here's the error which displayed when I tried to unload the database...
Unloading "DBA"."schedule_profile" into C:\resq\resqprod2\db\unload\719.dat (relative to server)
Unloading "DBA"."schedules" into C:\resq\resqprod2\db\unload\720.dat (relative to server)
***** SQL error: Internal database error *** ERROR *** Assertion failed: 201501 (10.0.1.3415)
Page for requested record not a table page or record not present on page -- transaction rolled back
The database 'C:\resq\resqprod2\db\resqprod2.db' could not be unloaded.
The database 'C:\resq\resqprod2\db\resqprod2.db' could not be unloaded.
I think that backups may also have this error.
Can the database be salvaged?
Thank you,
Doug

Hi Doug,
The error seems to be saying that a pointer is pointing to an invalid page.
Actually, the assertion message is suggesting that we were scanning for a row (record) on a particular page where we expected to find it, and didn't - the table page is likely corrupt.
Does a utility exist which would eliminate all pointers to invalid pages?
No. If the database is corrupted, it is best to move to your database recovery procedure from a valid backup. See KBA 1959391 - How can a SQL Anywhere (stand alone) database be restored from a full or incremental backup?
If you do not have a valid database backup but can still start and connect to the corrupted database (and it seems that you can), you can attempt to salvage the data out of the corrupted database tables manually to extract it to a new database (as Jinwoo suggested). See KBA 1959030 - How To Salvage Data When There are Corrupt Pages in the Database. Using -e to skip tables is appropriate and then trying to select the data that is not contained on invalid pages via the KBA instructions is your best option in this case.
Does sap/sybase offer a recovery service?
No, there is no such "recovery service" underneath SAP and any previous mentions of salvages were one-off contracts underneath Sybase Professional Services, and not a technical support service. These contracts are not available at SAP.
This topic was discussed thoroughly on the SQL Anywhere forum ( http://sqlanywhere-forum.sap.com/ ) previously here and here.
The prevention for this situation is to have properly validated backups, preferably in multiple backup generations to provide many opportunities for recovery. See: http://wiki.scn.sap.com/wiki/x/3QNcFg
Regards,
Jeff Albion
SAP Active Global Support

Backup Database is terminated Abnormally Failed

Similar Messages

Maybe you are looking for