InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 25 May 2013 05:44:24 GMT20http://www.sqlservercentral.com/Forums/Topic1403750-1550-1.aspxHave you verified that the drive has enough space for the backup to even save? I know files don't always "stick around" if the space to save them doesn't exist.Tue, 08 Jan 2013 04:47:35 GMTBrandie Tarvinhttp://www.sqlservercentral.com/Forums/Topic1403750-1550-1.aspxAre you running this backup task via Maintenance Plan or via your own custom TSQL?If running via a Maintenance Task, simply open up the corresponding SQL Agent job that was created and output the results to a text file or something so you can view the error. Or, you can backup the database via TSQL and view the output generated during runtime.Mon, 07 Jan 2013 12:30:00 GMTMyDoggieJessiehttp://www.sqlservercentral.com/Forums/Topic1403750-1550-1.aspxHello --Thanks for the replies. I'm glad the incorrect email address was not a show-stopper in this scenario. I checked the SQL and and Application log files, and there was no record in either of a problem occurring with the backup. The latter file indicated the backup completed successfully. However, that cannot be true because when I checked the folder for the BAK file that was to be generated by the backup, there was no file at that location.Any ideas on this?Mon, 07 Jan 2013 12:19:35 GMTkaplan71http://www.sqlservercentral.com/Forums/Topic1403750-1550-1.aspxAs GSquared said, check the Windows logs. Application specifically. And the SQL Server Agent log (just in case).Mon, 07 Jan 2013 12:06:11 GMTBrandie Tarvinhttp://www.sqlservercentral.com/Forums/Topic1403750-1550-1.aspxThe "The job was stopped prior to completion by Shutdown Sequence 0" can be attributed to all kinds of things i.e.(server is extremely busy, hardware issues (lack of RAM, etm, errors backing up the DB to a tape device, attached storage, etc...)But to answer your question, No, the incorrect address would not cause your backup to fail.Mon, 07 Jan 2013 11:49:41 GMTMyDoggieJessiehttp://www.sqlservercentral.com/Forums/Topic1403750-1550-1.aspxEmail on SQL 2005 and later is an asynchronous process. Even with a wrong address, that won't stop a job, it just enters an error in a log table in msdb.A stop job request has to initiate from a sys admin, or from software with that kind of privileges. Some server monitoring software, and some antivirus software, can stop a job mid-flight, but the usual culprit is someone doing something like cancelling the job or killing the service.Have you checked the Windows logs?Mon, 07 Jan 2013 11:45:03 GMTGSquaredhttp://www.sqlservercentral.com/Forums/Topic1403750-1550-1.aspxHello --The scheduled Full Backup of one of our databases failed due to a stop job request. The log file had the following entries:[quote]The job was stopped prior to completion by Shutdown Sequence 0. The Job was invoked by Schedule 9 (Backup.Full Backup). The last step to run was step 1 (Full Backup).Executed as user: MGHROSTORAGE2\SYSTEM. The step was cancelled (stopped) as the result of a stop job request.[/quote]The only change that was made recently was the configuration of Database Mail to notify the administrators the results of the backup. The spelling of the e-mail address of intended recipient was incorrect at the time of the backup, and that has since been corrected.Would the incorrect address cause these errors to occur? If not, what would be the culprit, and how can I correct it?Thanks.Mon, 07 Jan 2013 10:37:00 GMTkaplan71