Event ID - 17055

Event Id17055
SourceMSSQLSERVER
Description:
Event Information3266 : The backup data in is incorrectly formatted. Backups cannot be appended, but existing backup sets may still be usable. - We encountered this when SQL will not backup a database saying that the backup device is corrupt. We deleted the existing backup device (a file) and created a new one.
17052 : Microsoft SQL Server 2000 - 8.00.818 (Intel X86)[] - It occurs when the SQL server is started.
17122: initdata: Warning: Could not set working set size to 226752.
17148: SQL Server is terminating due to stop request from Service Control Manager. - This may indicate a manual stop of the SQL server service.
18204: [...] Operating system error = 3(The system cannot find the path specified.) - This event is generated when there is an attempt to backup an MSSQL database to a backup device that is corrupted or has not been initialized.
18204: [...] Operating system error = 5 (Access denied.) -See link given below "Unable to Back Up Database to a Network Drive Without Permissions"
18210: [...] Operating system error -2147221164(Class not registered). -See link given below "SQL 7.0 VDI Backup May Fail When SQL Server 2000 Is Installed on the Same Computer"
18210: [...] Operating system error -2147024769 (The specified procedure could not be found.) -See link given below "SQL 7.0 VDI Backup May Fail When SQL Server 2000 Is Installed on the Same Computer"
18265: Log backed up: Database: , , number of dump devices: 1, device information: (). -This is a successful database backup indiaction.
17311: SQL Server is aborting. Fatal exception c0000005 caught - If you have linked the server to an Oracle database, and your SQL account is a domain or a local user account (not member of the admin group), on folder ?ora92? give to the SQL account read and execute, list folder.
Reference LinksPRB: A "Database log truncated" Error is Logged in the Event Log When You Try to Back Up the Transaction Log

INF: Changing Configuration Values When SQL Server Wont Start

PRB: Dumping to a New Dump Device Using INIT Option Causes a Dbsvolopen Error

PRB: Unable to Back Up Database to a Network Drive Without Permissions

FIX: Lock Escalation With Parallel Query May Cause 1203 Error And Server Shutdown

INF: "DBCC TRACEON (208)" Messages in the Error Log When Using MSQuery

BUG: Access Violation Occurs with Non-Updateable Derived Table in UPDATE Statement

PRB: SQL 7.0 VDI Backup May Fail When SQL Server 2000 Is Installed on the Same Computer

INF: MSSQLSERVER or SQLServerAgent Services Fail to Start on a Stand-Alone Server

FIX: DTS Copy Objects Task (DMO) breaks transaction log backup chain by switching recovery mode to Simple during transfer

FIX:

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.