Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 208 Source: SQLSERVERAGENT
SQL Server Scheduled Job "<job name>" (0xAC8952C0A18BEA4FABCD341D3D982CC6) - Status: Failed - Invoked on: <date and time> - Message: The job failed. The Job was invoked by Schedule 2 (<job name> 2). The last step to run was step 1 (<job name> 2).
|English: This information is only available to subscribers. An example of English, please!|
As per ME970231, a supported hotfix is available from Microsoft (for Microsoft BizTalk Server).
This message simply states that the backup job failed - it does not provide the reason for the failure but rather the "step" where the failure happened. Look for other event log messages that may provide more specific information. Also, you can use the SQL Server Management interface to lookup that particular job history (see Managment, Jobs).
In our case, we got this message after event id 17055 from MSSQLSERVER complaining that the backup device (a "file"-type device) was not formatted properly. We removed the old backup device and created a new one and the backup worked. In another instance, this message was generated when the database was dismounted but a backup job for it was still scheduled. To fix it we removed the database from the backup schedule.
* * *
Another instance when this may occur is when a database included in a backup plan is taken offline.
This problem happens on our web server if IIS is running when the maintenance plan tries to execute. This is due to IIS being connected to one of the databases. A workaround is to stop IIS, run the maintenance plan, and then restart IIS. See ME290622 for more details.
In my case, I moved all the *.bak and *.trn files from the backup destination folder into another folder. I do not know why, but after that the job worked again.
I had this problem when I uninstalled WEBSENSE because the uninstallation procedure left two scheduled processes made by the sqlserveragent. I opened the enterprise manager, deleted these two processes and now it seems to work fine.
In the Job History for the failed job, tick "Show Step Details" for helpful information about the problem. In my particular instance, the job was trying to run Full-Text Indexing, but Full-Text Search was not enabled for the database. To enable full text search, run the following query:
USE <Insert Name of Target Database>
EXEC sp_fulltext_database "enable"
To resolve this error go into SQL Enterprise Manager, expand Management/SQL Agent/Jobs. You will have a list of maintenance jobs and their last run status. On the failed job, select properties and change the owner to an account with correct permissions to the database.
- Job: Optimizations Job for DB Maintenance Plan '<name>' - See ME902388 for information on how to fix the problem.
After having set up an operational Maintenance Plan a database was deleted from the server but not removed from the Maintenance Plan. This error appeared as a consequence. I resolved the problem by removing the deleted database from the Maintenance Plan. Only applies to Maintenance Plan setup by manual selection of databases listed.
- Job: Backup BizTalk Server - As per Microsoft: "The Backup BizTalk Server SQL job fails if you elect not to install all the following components when you install BizTalk Server 2004". See ME839626 for information on how to fix this problem.
- Job: MessageBox_Message_Cleanup_BizTalkMsgBoxDb - See ME872809 for a hotfix applicable to Microsoft BizTalk Server 2004.
- Job: PLUS: Register Server Agent - See Novell Support TID10093879.
The problem would occur upon Integrity Checks. We used ME290622 to resolve the problem.
Right click the database you want to back up and select Properties->Options. Under recovery model, select “Full” or “Bulk-Logged”.
I got a similar error from a transaction log backup job created by a Database Maintenance Plan. Problem was that the Recovery Model of the database in question was set to ''simple'' which would not allow transaction log backups. I switched the Recovery Model to ''full'' and the problem was solved. See ME303229 for more details.
Problem caused by SQL job being run by a user without required permissions. Modified (elevated) user permisions on the SQL and the job run fine.
See ME308988 link below.
|Private comment: Subscribers only. See example of private comment|
|Links: Event id 17055 from MSSQLSERVER, Novell Support TID10093879|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (1) - More links...|
Send comments or solutions
- Notify me when updated