﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 7,2000 / SQL Server Agent  / SQLServerJob failing / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Sat, 25 May 2013 06:35:51 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: SQLServerJob failing</title><link>http://www.sqlservercentral.com/Forums/Topic1342463-110-1.aspx</link><description>See the another thread having resolution..http://www.sqlservercentral.com/Forums/Topic1030483-146-1.aspx</description><pubDate>Wed, 02 Jan 2013 04:32:10 GMT</pubDate><dc:creator>KumarSQLDBA</dc:creator></item><item><title>SQLServerJob failing</title><link>http://www.sqlservercentral.com/Forums/Topic1342463-110-1.aspx</link><description>I have a job that executes fine most of the time but sometimes it fails with the error below. The service for SQLServerAgent is logging on with a windows account and the job is owned by sa. The job has one step executing a maintanenceplan with the following code EXECUTE master.dbo.xp_sqlmaint N'-PlanID 80CB4BBB-AF15-4C7E-AD3B-02CCA9B6F85B -To "Remote DBA" -WriteHistory  -BkUpMedia DISK -BkUpLog "Folderpath" -DelBkUps 3DAYS -BkExt "TRN"'The view history for the job shows the error:Executed as user: DOMAIN\user. ConnectionCheckForData (CheckforData()). [SQLSTATE 01000] (Message 10054)  General network error. Check your network documentation. [SQLSTATE 08S01] (Error 11).  The step failed.The log for SQLServerAgent shows two errors:1. [382] Logon to server 'SERVERNAME' failed (ConnAttemptCachableOp)2. [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]The output from select @@version is:Microsoft SQL Server  2000 - 8.00.760 (Intel X86)   Dec 17 2002 14:22:05   Copyright (c) 1988-2003 Microsoft Corporation  Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4) We have 3 servers one with SQL Server 2005 and two with 2000. The same error occurs in the SQLServerAgent log on all the servers but are very rare on two.</description><pubDate>Thu, 09 Aug 2012 02:55:08 GMT</pubDate><dc:creator>eirik.andersen</dc:creator></item></channel></rss>