NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

NetBackup status code: 4214

NetBackup status code : 4214
HOWTO91752 | 2013-10-02
How To | CMS-XML

Recieving error when doing the microsoft SQL database Backup using netbackup 7.1 | Symantec Connect

Recieving error when doing the microsoft SQL database Backup using netbackup 7.1 INFO The api was waiting and the timeout interval had elapsed. INFO ODBC return code <-1>, SQL State <37000>, SQL Message < 4214 ><[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG cannot be performed because there is no current database backup.>. INFO SQL Message <3013><[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally.>
Connect Forums | HTML

Backup SQL log error (SQLVDI) | Symantec Connect

CONTINUATION: - The api was waiting and the timeout interval had elapsed. DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message < 4214 ><[Microsoft][SQL Native Client][SQL Server]BACKUP LOG cannot be performed because there is no current database backup.>. DBMS MSG - SQL Message <3013><[Microsoft][SQL Native Client][SQL Server]BACKUP LOG is terminating abnormally.>
Connect Forums | HTML

191 errors on Duplcation Jobs | Symantec Connect

19:56:26.552 [4476.1780] <2> logconnections: BPDBM CONNECT FROM 10.239.51.107. 4214 TO 10.239.53.31.1556 fd = 640
Connect Forums | HTML

Status Code Chart

4213 4214 4215
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

NetBackup messages

snapshot mount failed See NetBackup status code : 4214 snapshot not accessible or invalid snapshot
HOWTO90266 | 2013-10-02
How To | CMS-XML

Backup fails with EC - 2 on SQL 2005 server. | Symantec Connect

Backup fails with EC - 2 on SQL 2005 server. CONTINUATION: - The api was waiting and the timeout interval had elapsed. DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message < 4214 ><[Microsoft][SQL Native Client][SQL Server]BACKUP LOG cannot be performed because there is no current database backup.>. DBMS MSG - SQL Message <3013><[Microsoft][SQL Native Client][SQL Server]BACKUP LOG is terminating abnormally.>
Connect Forums | HTML

SQL jobs randomly failing and locking databases (7.5.0.1) | Symantec Connect

2012/09/06 06:50:04 AM - Info dbclient(pid=4688) CONTINUATION: - The api was waiting and the timeout interval had elapsed. 2012/09/06 06:50:04 AM - Info dbclient(pid=4688) DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message < 4214 ><[Microsoft][SQL Native Client][SQL Server]BACKUP LOG cannot be performed because there is no current database backup.>.
Connect Forums | HTML

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?