Job with stored proc succeeds with sqlstate 01000

I have a stored procedure that I am executing through the sql server
job scheduler, it executes properly but after each line in the log file
there is a sqlstate message.
procedure name p_document_purge [SQLSTATE 01000]
Archiving records [SQLSTATE 01000]
51 rows archived [SQLSTATE 01000]
Purging duplicate records [SQLSTATE 01000]
51 rows purged [SQLSTATE 01000]
Purge completed successfully [SQLSTATE 01000]
Does anyone know what might cause this? The @.@.ERROR during the
procedure is always 0 or it would rollback the entire transaction. Also
If I run the proc from query analyzer I do not get any negative
feedback regarding it. I tried looking in the documentation, but this
is listed as a general error which doesn't really help.
Thanks
BillPrint statements in the stored procedure can result in the
sqlstate message.
-Sue
.
On 23 Feb 2006 06:30:49 -0800, william_dudek@.yahoo.com
wrote:

>I have a stored procedure that I am executing through the sql server
>job scheduler, it executes properly but after each line in the log file
>there is a sqlstate message.
>procedure name p_document_purge [SQLSTATE 01000]
>Archiving records [SQLSTATE 01000]
>51 rows archived [SQLSTATE 01000]
>Purging duplicate records [SQLSTATE 01000]
>51 rows purged [SQLSTATE 01000]
>Purge completed successfully [SQLSTATE 01000]
>Does anyone know what might cause this? The @.@.ERROR during the
>procedure is always 0 or it would rollback the entire transaction. Also
>If I run the proc from query analyzer I do not get any negative
>feedback regarding it. I tried looking in the documentation, but this
>is listed as a general error which doesn't really help.
>Thanks
>Bill

Job with stored proc succeeds with sqlstate 01000

I have a stored procedure that I am executing through the sql server
job scheduler, it executes properly but after each line in the log file
there is a sqlstate message.
procedure name p_document_purge [SQLSTATE 01000]
Archiving records [SQLSTATE 01000]
51 rows archived [SQLSTATE 01000]
Purging duplicate records [SQLSTATE 01000]
51 rows purged [SQLSTATE 01000]
Purge completed successfully [SQLSTATE 01000]
Does anyone know what might cause this? The @.@.ERROR during the
procedure is always 0 or it would rollback the entire transaction. Also
If I run the proc from query analyzer I do not get any negative
feedback regarding it. I tried looking in the documentation, but this
is listed as a general error which doesn't really help.
Thanks
BillPrint statements in the stored procedure can result in the
sqlstate message.
-Sue
.
On 23 Feb 2006 06:30:49 -0800, william_dudek@.yahoo.com
wrote:
>I have a stored procedure that I am executing through the sql server
>job scheduler, it executes properly but after each line in the log file
>there is a sqlstate message.
>procedure name p_document_purge [SQLSTATE 01000]
>Archiving records [SQLSTATE 01000]
>51 rows archived [SQLSTATE 01000]
>Purging duplicate records [SQLSTATE 01000]
>51 rows purged [SQLSTATE 01000]
>Purge completed successfully [SQLSTATE 01000]
>Does anyone know what might cause this? The @.@.ERROR during the
>procedure is always 0 or it would rollback the entire transaction. Also
>If I run the proc from query analyzer I do not get any negative
>feedback regarding it. I tried looking in the documentation, but this
>is listed as a general error which doesn't really help.
>Thanks
>Bill

Job with stored proc succeeds with sqlstate 01000

I have a stored procedure that I am executing through the sql server
job scheduler, it executes properly but after each line in the log file
there is a sqlstate message.
procedure name p_document_purge [SQLSTATE 01000]
Archiving records [SQLSTATE 01000]
51 rows archived [SQLSTATE 01000]
Purging duplicate records [SQLSTATE 01000]
51 rows purged [SQLSTATE 01000]
Purge completed successfully [SQLSTATE 01000]
Does anyone know what might cause this? The @.@.ERROR during the
procedure is always 0 or it would rollback the entire transaction. Also
If I run the proc from query analyzer I do not get any negative
feedback regarding it. I tried looking in the documentation, but this
is listed as a general error which doesn't really help.
Thanks
Bill
Print statements in the stored procedure can result in the
sqlstate message.
-Sue
..
On 23 Feb 2006 06:30:49 -0800, william_dudek@.yahoo.com
wrote:

>I have a stored procedure that I am executing through the sql server
>job scheduler, it executes properly but after each line in the log file
>there is a sqlstate message.
>procedure name p_document_purge [SQLSTATE 01000]
>Archiving records [SQLSTATE 01000]
>51 rows archived [SQLSTATE 01000]
>Purging duplicate records [SQLSTATE 01000]
>51 rows purged [SQLSTATE 01000]
>Purge completed successfully [SQLSTATE 01000]
>Does anyone know what might cause this? The @.@.ERROR during the
>procedure is always 0 or it would rollback the entire transaction. Also
>If I run the proc from query analyzer I do not get any negative
>feedback regarding it. I tried looking in the documentation, but this
>is listed as a general error which doesn't really help.
>Thanks
>Bill
sql

Job to Backup Log when Full

We have several servers with dozens of databases on each one. We have
elected to group our maintenance jobs so that all database backups are
consolidated into 4 separate jobs (alphabetically). We would like to backup
a log using our standard practices if it gets full. We don't want to call
the 'consolidated' job because if the db is the last alphabetically, it will
have to go through all of the preceeding dbs before it gets to that log. By
that time, I could have gotten up out of bed and backed up the log myself
We would like to be able to read the database name that triggered the alert
and have a job that backs up that log only. Where would I get that database
name? The alert has it, does it store it in a system table in msdb?
Thanks!
There is a group of Alert tokens that you can use...
For instance, you could create a job that has one step
Backup log [A-DBN] to disk = 'c:\[A-DBN].logbak'
When the job is called from an Alert, the token will be replaced (even in
the filename string... and the appropriate database log will be backed up...
But the job can not be run< except from an alert> , because that is the only
time the tokens will be replaced..
For a complete list of Alert tokens, go to Gert Drapers web site
http://www.sqldev.net/sqlagent/SQLAg...ns.htm#Example using TSQL
step
"Michelle" <michelle@.nospam.com> wrote in message
news:eDmu1PNIEHA.3664@.TK2MSFTNGP11.phx.gbl...
> We have several servers with dozens of databases on each one. We have
> elected to group our maintenance jobs so that all database backups are
> consolidated into 4 separate jobs (alphabetically). We would like to
backup
> a log using our standard practices if it gets full. We don't want to call
> the 'consolidated' job because if the db is the last alphabetically, it
will
> have to go through all of the preceeding dbs before it gets to that log.
By
> that time, I could have gotten up out of bed and backed up the log myself

> We would like to be able to read the database name that triggered the
alert
> and have a job that backs up that log only. Where would I get that
database
> name? The alert has it, does it store it in a system table in msdb?
> Thanks!
>
|||This is awesome. I set it up to test and am quite eager to deploy it to
production. Thank you very much.
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:eSpn43UIEHA.2744@.TK2MSFTNGP10.phx.gbl...
> There is a group of Alert tokens that you can use...
> For instance, you could create a job that has one step
> Backup log [A-DBN] to disk = 'c:\[A-DBN].logbak'
> When the job is called from an Alert, the token will be replaced (even in
> the filename string... and the appropriate database log will be backed
up...
> But the job can not be run< except from an alert> , because that is the
only[color=darkblue]
> time the tokens will be replaced..
> For a complete list of Alert tokens, go to Gert Drapers web site
> http://www.sqldev.net/sqlagent/SQLAg...ns.htm#Example using TSQL
> step
>
> "Michelle" <michelle@.nospam.com> wrote in message
> news:eDmu1PNIEHA.3664@.TK2MSFTNGP11.phx.gbl...
> backup
call[color=darkblue]
> will
> By
myself
>
> alert
> database
>

Job to Backup Log when Full

We have several servers with dozens of databases on each one. We have
elected to group our maintenance jobs so that all database backups are
consolidated into 4 separate jobs (alphabetically). We would like to backup
a log using our standard practices if it gets full. We don't want to call
the 'consolidated' job because if the db is the last alphabetically, it will
have to go through all of the preceeding dbs before it gets to that log. By
that time, I could have gotten up out of bed and backed up the log myself
We would like to be able to read the database name that triggered the alert
and have a job that backs up that log only. Where would I get that database
name? The alert has it, does it store it in a system table in msdb?
Thanks!There is a group of Alert tokens that you can use...
For instance, you could create a job that has one step
Backup log [A-DBN] to disk = 'c:\[A-DBN].logbak'
When the job is called from an Alert, the token will be replaced (even in
the filename string... and the appropriate database log will be backed up...
But the job can not be run< except from an alert> , because that is the only
time the tokens will be replaced..
For a complete list of Alert tokens, go to Gert Drapers web site
http://www.sqldev.net/sqlagent/SQLA...ens.htm#Example using TSQL
step
"Michelle" <michelle@.nospam.com> wrote in message
news:eDmu1PNIEHA.3664@.TK2MSFTNGP11.phx.gbl...
> We have several servers with dozens of databases on each one. We have
> elected to group our maintenance jobs so that all database backups are
> consolidated into 4 separate jobs (alphabetically). We would like to
backup
> a log using our standard practices if it gets full. We don't want to call
> the 'consolidated' job because if the db is the last alphabetically, it
will
> have to go through all of the preceeding dbs before it gets to that log.
By
> that time, I could have gotten up out of bed and backed up the log myself

> We would like to be able to read the database name that triggered the
alert
> and have a job that backs up that log only. Where would I get that
database
> name? The alert has it, does it store it in a system table in msdb?
> Thanks!
>|||This is awesome. I set it up to test and am quite eager to deploy it to
production. Thank you very much.
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:eSpn43UIEHA.2744@.TK2MSFTNGP10.phx.gbl...
> There is a group of Alert tokens that you can use...
> For instance, you could create a job that has one step
> Backup log [A-DBN] to disk = 'c:\[A-DBN].logbak'
> When the job is called from an Alert, the token will be replaced (even in
> the filename string... and the appropriate database log will be backed
up...
> But the job can not be run< except from an alert> , because that is the
only
> time the tokens will be replaced..
> For a complete list of Alert tokens, go to Gert Drapers web site
> http://www.sqldev.net/sqlagent/SQLA...ens.htm#Example using TSQL
> step
>
> "Michelle" <michelle@.nospam.com> wrote in message
> news:eDmu1PNIEHA.3664@.TK2MSFTNGP11.phx.gbl...
> backup
call
> will
> By
myself
>
> alert
> database
>

Job to Backup Log when Full

We have several servers with dozens of databases on each one. We have
elected to group our maintenance jobs so that all database backups are
consolidated into 4 separate jobs (alphabetically). We would like to backup
a log using our standard practices if it gets full. We don't want to call
the 'consolidated' job because if the db is the last alphabetically, it will
have to go through all of the preceeding dbs before it gets to that log. By
that time, I could have gotten up out of bed and backed up the log myself :)
We would like to be able to read the database name that triggered the alert
and have a job that backs up that log only. Where would I get that database
name? The alert has it, does it store it in a system table in msdb?
Thanks!There is a group of Alert tokens that you can use...
For instance, you could create a job that has one step
Backup log [A-DBN] to disk = 'c:\[A-DBN].logbak'
When the job is called from an Alert, the token will be replaced (even in
the filename string... and the appropriate database log will be backed up...
But the job can not be run< except from an alert> , because that is the only
time the tokens will be replaced..
For a complete list of Alert tokens, go to Gert Drapers web site
http://www.sqldev.net/sqlagent/SQLAgentStepTokens.htm#Example using TSQL
step
"Michelle" <michelle@.nospam.com> wrote in message
news:eDmu1PNIEHA.3664@.TK2MSFTNGP11.phx.gbl...
> We have several servers with dozens of databases on each one. We have
> elected to group our maintenance jobs so that all database backups are
> consolidated into 4 separate jobs (alphabetically). We would like to
backup
> a log using our standard practices if it gets full. We don't want to call
> the 'consolidated' job because if the db is the last alphabetically, it
will
> have to go through all of the preceeding dbs before it gets to that log.
By
> that time, I could have gotten up out of bed and backed up the log myself
:)
> We would like to be able to read the database name that triggered the
alert
> and have a job that backs up that log only. Where would I get that
database
> name? The alert has it, does it store it in a system table in msdb?
> Thanks!
>|||This is awesome. I set it up to test and am quite eager to deploy it to
production. Thank you very much.
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:eSpn43UIEHA.2744@.TK2MSFTNGP10.phx.gbl...
> There is a group of Alert tokens that you can use...
> For instance, you could create a job that has one step
> Backup log [A-DBN] to disk = 'c:\[A-DBN].logbak'
> When the job is called from an Alert, the token will be replaced (even in
> the filename string... and the appropriate database log will be backed
up...
> But the job can not be run< except from an alert> , because that is the
only
> time the tokens will be replaced..
> For a complete list of Alert tokens, go to Gert Drapers web site
> http://www.sqldev.net/sqlagent/SQLAgentStepTokens.htm#Example using TSQL
> step
>
> "Michelle" <michelle@.nospam.com> wrote in message
> news:eDmu1PNIEHA.3664@.TK2MSFTNGP11.phx.gbl...
> > We have several servers with dozens of databases on each one. We have
> > elected to group our maintenance jobs so that all database backups are
> > consolidated into 4 separate jobs (alphabetically). We would like to
> backup
> > a log using our standard practices if it gets full. We don't want to
call
> > the 'consolidated' job because if the db is the last alphabetically, it
> will
> > have to go through all of the preceeding dbs before it gets to that log.
> By
> > that time, I could have gotten up out of bed and backed up the log
myself
> :)
> > We would like to be able to read the database name that triggered the
> alert
> > and have a job that backs up that log only. Where would I get that
> database
> > name? The alert has it, does it store it in a system table in msdb?
> >
> > Thanks!
> >
> >
>

Job reports failure, but bak file created

The view history of a job created from a maintenance plan reports that it
failed, and the log says that it failed in the backup operation because
"A nonrecoverable I/O error occurred on file
"\\\\BIGPETE\\E\\data\\Backups\\Daily\\MCR_SFPMS\\MCR_SFPMS_backup_200707110001.bak:" 64(The specified network name is no longer available.).
And yet MCR_SFPMS_backup_200707110001.bak does exist, and moreover, it was a
valid backup, as I just confirmed by restoring it to a test database. So why
the error?
Also, this does not happen consistently. The reporting of this apparent
non-error has occured twice out of the last five runs.Does the backup process include a Verify? IF so the error is most likely
occurring on the verify process which is done after the backup is complete.
Backup & Verify is an intensive operation and if you are backing up across
the network there is plenty of time for the network to drop packets etc.
Sounds like you have an unstable network or networks equipment.
--
Andrew J. Kelly SQL MVP
"Bev Kaufman" <BevKaufman@.discussions.microsoft.com> wrote in message
news:AF302871-2972-420D-A932-408F42EA1EA9@.microsoft.com...
> The view history of a job created from a maintenance plan reports that it
> failed, and the log says that it failed in the backup operation because
> "A nonrecoverable I/O error occurred on file
> "\\\\BIGPETE\\E\\data\\Backups\\Daily\\MCR_SFPMS\\MCR_SFPMS_backup_200707110001.bak:"
> 64(The specified network name is no longer available.).
> And yet MCR_SFPMS_backup_200707110001.bak does exist, and moreover, it was
> a
> valid backup, as I just confirmed by restoring it to a test database. So
> why
> the error?
> Also, this does not happen consistently. The reporting of this apparent
> non-error has occured twice out of the last five runs.|||On Jul 11, 9:16 am, Bev Kaufman <BevKauf...@.discussions.microsoft.com>
wrote:
> The view history of a job created from a maintenance plan reports that it
> failed, and the log says that it failed in the backup operation because
> "A nonrecoverable I/O error occurred on file
> "\\\\BIGPETE\\E\\data\\Backups\\Daily\\MCR_SFPMS\\MCR_SFPMS_backup_200707=11=AD0001.bak:" 64(The specified network name is no longer available.).
> And yet MCR_SFPMS_backup_200707110001.bak does exist, and moreover, it wa=s a
> valid backup, as I just confirmed by restoring it to a test database. So= why
> the error?
> Also, this does not happen consistently. The reporting of this apparent
> non-error has occured twice out of the last five runs.
Are you utilizing a third party backup tool? We use RedGate in our
SQL Server 2000 (SP3a - don't ask) environment and have encountered
this on a daily basis. When we used normal backup procedures, no
errors were reported. I have the same issue though, but figured it
might be resolved with a newer service pack. The only thing I can
think of is possibly disk contention of you are utilizing a SAN
environment, but not sure.
Maybe if we put our heads together, we can figure it out. I haven't
put a whole lot of effort into it once I realized that the backups are
working properly (as verified by the restores). I know, terrible, but
sometimes other fires are hotter :)

Job History Logs

Hi,
Maximum Job History Log size is set to 1000 and Maximum Job History Rows
Per Job is set to 100. There are some some jobs that are running every
minute. In less then five minute the Log Size grows to 45 from 0. So I guess
the jobs that are running every minute are filling up the History Log. When
other jobs that run once every night are not able to write in the History
Log. What should be the preferred setting in such scenario that will allow
the nightly jobs to write history in the History Log.
I can think of two options. I can either uncheck the Limit Size of Job
History Log option or change the value of the Maximum Job History Log Size
option. But then I don't know how large the History Log will grow. Can you
give me an idea on that? Also is there a way to automatically clear the
History Log?
Thanks in advance...
If you have n number of jobs then set history log size to (n * 100) +
100.
Set maximum number of rows per job to 100.
Regards
Amish Shah.

Job History Logs

Hi,
Maximum Job History Log size is set to 1000 and Maximum Job History Rows
Per Job is set to 100. There are some some jobs that are running every
minute. In less then five minute the Log Size grows to 45 from 0. So I guess
the jobs that are running every minute are filling up the History Log. When
other jobs that run once every night are not able to write in the History
Log. What should be the preferred setting in such scenario that will allow
the nightly jobs to write history in the History Log.
I can think of two options. I can either uncheck the Limit Size of Job
History Log option or change the value of the Maximum Job History Log Size
option. But then I don't know how large the History Log will grow. Can you
give me an idea on that? Also is there a way to automatically clear the
History Log?
Thanks in advance...If you have n number of jobs then set history log size to (n * 100) +
100.
Set maximum number of rows per job to 100.
Regards
Amish Shah.sql

Job History Logs

Hi,
Maximum Job History Log size is set to 1000 and Maximum Job History Rows
Per Job is set to 100. There are some some jobs that are running every
minute. In less then five minute the Log Size grows to 45 from 0. So I guess
the jobs that are running every minute are filling up the History Log. When
other jobs that run once every night are not able to write in the History
Log. What should be the preferred setting in such scenario that will allow
the nightly jobs to write history in the History Log.
I can think of two options. I can either uncheck the Limit Size of Job
History Log option or change the value of the Maximum Job History Log Size
option. But then I don't know how large the History Log will grow. Can you
give me an idea on that? Also is there a way to automatically clear the
History Log?
Thanks in advance...If you have n number of jobs then set history log size to (n * 100) +
100.
Set maximum number of rows per job to 100.
Regards
Amish Shah.

Job History Log overflow

Hi,
Maximum Job History Log size is set to 1000 and Maximum Job History Rows
Per Job is set to 100. There are some some jobs that are running every
minute. In less then five minute the Log Size grows to 45 from 0. So I guess
the jobs that are running every minute are filling up the History Log. When
other jobs that run once every night are not able to write in the History
Log. What should be the preferred setting in such scenario that will allow
the nightly jobs to write history in the History Log.
I can think of two options. I can either uncheck the Limit Size of Job
History Log option or change the value of the Maximum Job History Log Size
option. But then I don't know how large the History Log will grow. Can you
give me an idea on that? Also is there a way to automatically clear the
History Log?
Thanks in advance...You can set to the job history log size to unlimited. There are no known
issues associated with it -- though it might be a good idea to archive the
data from msdb..sysjobhistory for auditing purposes. Once you set a size
limit, the entire log rows outside the limit can be purged easily.
Anith|||> Also is there a way to automatically clear the History Log?
See sp_purge_jobhistory in BOL.
AMB
"helpful sql" wrote:

> Hi,
> Maximum Job History Log size is set to 1000 and Maximum Job History Row
s
> Per Job is set to 100. There are some some jobs that are running every
> minute. In less then five minute the Log Size grows to 45 from 0. So I gue
ss
> the jobs that are running every minute are filling up the History Log. Whe
n
> other jobs that run once every night are not able to write in the History
> Log. What should be the preferred setting in such scenario that will allow
> the nightly jobs to write history in the History Log.
> I can think of two options. I can either uncheck the Limit Size of Job
> History Log option or change the value of the Maximum Job History Log Size
> option. But then I don't know how large the History Log will grow. Can you
> give me an idea on that? Also is there a way to automatically clear the
> History Log?
> Thanks in advance...
>
>

JOB Failure!

Hi,
I've a question related to JOB failure in the DTS package.
The following is the error from the LOG file.Could some one help me in this
regard,as how i can find the easy way out.
LOG FILE ERROR:
--
Execution Started: 2/24/2005 11:34:06 PM
Execution Completed: 2/25/2005 12:17:56 AM
Total Execution Time: 2629.937 seconds
Package Steps execution information:
Step 'DTSStep_DTSActiveScriptTask_1' failed
Step Error Source: Microsoft Data Transformation Services (DTS) Package
Step Error Description:Error Code: 0
Error Source= Microsoft XML Extensions to SQL Server
Error Description: [DBNETLIB][ConnectionRead (recv()).]General netwo
rk
error. Check your network documentation.
Thanks,
ShyamShyam,
This usually means that there was an actual network problem. A switch or
router may have out of service, a cable disconnected, etc.
RLF
"Shyam" <Shyam@.discussions.microsoft.com> wrote in message
news:25D54BB1-7605-4654-ADBE-7C08CF3901B8@.microsoft.com...
> Hi,
> I've a question related to JOB failure in the DTS package.
> The following is the error from the LOG file.Could some one help me in
> this
> regard,as how i can find the easy way out.
> LOG FILE ERROR:
> --
> Execution Started: 2/24/2005 11:34:06 PM
> Execution Completed: 2/25/2005 12:17:56 AM
> Total Execution Time: 2629.937 seconds
> Package Steps execution information:
> Step 'DTSStep_DTSActiveScriptTask_1' failed
> Step Error Source: Microsoft Data Transformation Services (DTS) Package
> Step Error Description:Error Code: 0
> Error Source= Microsoft XML Extensions to SQL Server
> Error Description: [DBNETLIB][ConnectionRead (recv()).]General net
work
> error. Check your network documentation.
> Thanks,
> Shyam
>

JOB Failure!

Hi,
I've a question related to JOB failure in the DTS package.
The following is the error from the LOG file.Could some one help me in this
regard,as how i can find the easy way out.
LOG FILE ERROR:
--
Execution Started: 2/24/2005 11:34:06 PM
Execution Completed: 2/25/2005 12:17:56 AM
Total Execution Time: 2629.937 seconds
Package Steps execution information:
Step 'DTSStep_DTSActiveScriptTask_1' failed
Step Error Source: Microsoft Data Transformation Services (DTS) Package
Step Error Description:Error Code: 0
Error Source= Microsoft XML Extensions to SQL Server
Error Description: [DBNETLIB][ConnectionRead (recv()).]General network
error. Check your network documentation.
Thanks,
ShyamShyam,
This usually means that there was an actual network problem. A switch or
router may have out of service, a cable disconnected, etc.
RLF
"Shyam" <Shyam@.discussions.microsoft.com> wrote in message
news:25D54BB1-7605-4654-ADBE-7C08CF3901B8@.microsoft.com...
> Hi,
> I've a question related to JOB failure in the DTS package.
> The following is the error from the LOG file.Could some one help me in
> this
> regard,as how i can find the easy way out.
> LOG FILE ERROR:
> --
> Execution Started: 2/24/2005 11:34:06 PM
> Execution Completed: 2/25/2005 12:17:56 AM
> Total Execution Time: 2629.937 seconds
> Package Steps execution information:
> Step 'DTSStep_DTSActiveScriptTask_1' failed
> Step Error Source: Microsoft Data Transformation Services (DTS) Package
> Step Error Description:Error Code: 0
> Error Source= Microsoft XML Extensions to SQL Server
> Error Description: [DBNETLIB][ConnectionRead (recv()).]General network
> error. Check your network documentation.
> Thanks,
> Shyam
>

JOB Failure!

Hi,
I've a question related to JOB failure in the DTS package.
The following is the error from the LOG file.Could some one help me in this
regard,as how i can find the easy way out.
LOG FILE ERROR:
Execution Started: 2/24/2005 11:34:06 PM
Execution Completed: 2/25/2005 12:17:56 AM
Total Execution Time: 2629.937 seconds
Package Steps execution information:
Step 'DTSStep_DTSActiveScriptTask_1' failed
Step Error Source: Microsoft Data Transformation Services (DTS) Package
Step Error Description:Error Code: 0
Error Source= Microsoft XML Extensions to SQL Server
Error Description: [DBNETLIB][ConnectionRead (recv()).]General network
error. Check your network documentation.
Thanks,
Shyam
Shyam,
This usually means that there was an actual network problem. A switch or
router may have out of service, a cable disconnected, etc.
RLF
"Shyam" <Shyam@.discussions.microsoft.com> wrote in message
news:25D54BB1-7605-4654-ADBE-7C08CF3901B8@.microsoft.com...
> Hi,
> I've a question related to JOB failure in the DTS package.
> The following is the error from the LOG file.Could some one help me in
> this
> regard,as how i can find the easy way out.
> LOG FILE ERROR:
> --
> Execution Started: 2/24/2005 11:34:06 PM
> Execution Completed: 2/25/2005 12:17:56 AM
> Total Execution Time: 2629.937 seconds
> Package Steps execution information:
> Step 'DTSStep_DTSActiveScriptTask_1' failed
> Step Error Source: Microsoft Data Transformation Services (DTS) Package
> Step Error Description:Error Code: 0
> Error Source= Microsoft XML Extensions to SQL Server
> Error Description: [DBNETLIB][ConnectionRead (recv()).]General network
> error. Check your network documentation.
> Thanks,
> Shyam
>

Job Failure External Log

Someone in this newsgroup has suggested turning on External Log to see the
job failure information as follow:
Job's properties, choose the step, click 'Edit' then choose 'Advanced' tab.
There would be 'Output file' field. Check if it is set and if it is, then
look at the file.
For a scheduled job failure, I find that there is no external log is
enabled. I would like to know where is the best place to put the external
log ? I don't want to mix it with other logs.
ThanksI would put it with the other logs, but name it differently or put it in a
sub-directory underneath the logs directory. There it will easier to find.
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Jason" <anonymous@.discussions.microsoft.com> wrote in message
news:OtHNrfpZFHA.464@.TK2MSFTNGP15.phx.gbl...
> Someone in this newsgroup has suggested turning on External Log to see the
> job failure information as follow:
> Job's properties, choose the step, click 'Edit' then choose 'Advanced'
tab.
> There would be 'Output file' field. Check if it is set and if it is, then
> look at the file.
> For a scheduled job failure, I find that there is no external log is
> enabled. I would like to know where is the best place to put the external
> log ? I don't want to mix it with other logs.
> Thanks
>

Job Failure External Log

Someone in this newsgroup has suggested turning on External Log to see the
job failure information as follow:
Job's properties, choose the step, click 'Edit' then choose 'Advanced' tab.
There would be 'Output file' field. Check if it is set and if it is, then
look at the file.
For a scheduled job failure, I find that there is no external log is
enabled. I would like to know where is the best place to put the external
log ? I don't want to mix it with other logs.
ThanksI would put it with the other logs, but name it differently or put it in a
sub-directory underneath the logs directory. There it will easier to find.
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Jason" <anonymous@.discussions.microsoft.com> wrote in message
news:OtHNrfpZFHA.464@.TK2MSFTNGP15.phx.gbl...
> Someone in this newsgroup has suggested turning on External Log to see the
> job failure information as follow:
> Job's properties, choose the step, click 'Edit' then choose 'Advanced'
tab.
> There would be 'Output file' field. Check if it is set and if it is, then
> look at the file.
> For a scheduled job failure, I find that there is no external log is
> enabled. I would like to know where is the best place to put the external
> log ? I don't want to mix it with other logs.
> Thanks
>

Job Failure External Log

Someone in this newsgroup has suggested turning on External Log to see the
job failure information as follow:
Job's properties, choose the step, click 'Edit' then choose 'Advanced' tab.
There would be 'Output file' field. Check if it is set and if it is, then
look at the file.
For a scheduled job failure, I find that there is no external log is
enabled. I would like to know where is the best place to put the external
log ? I don't want to mix it with other logs.
Thanks
I would put it with the other logs, but name it differently or put it in a
sub-directory underneath the logs directory. There it will easier to find.
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Jason" <anonymous@.discussions.microsoft.com> wrote in message
news:OtHNrfpZFHA.464@.TK2MSFTNGP15.phx.gbl...
> Someone in this newsgroup has suggested turning on External Log to see the
> job failure information as follow:
> Job's properties, choose the step, click 'Edit' then choose 'Advanced'
tab.
> There would be 'Output file' field. Check if it is set and if it is, then
> look at the file.
> For a scheduled job failure, I find that there is no external log is
> enabled. I would like to know where is the best place to put the external
> log ? I don't want to mix it with other logs.
> Thanks
>

Job failure cannot easily be traced

sql server ver 8... Microsoft Windows 2000
A copy of a database is made using sp_attach sp_detach and the
transaction log backup scheduled for that hour fails ...makes sense !!
There has been subsequent failures at the same time at the application
log but not at the database view history.
No idea what is going on here .....
Your ideas will be more than appreciated
Vince"Vincento Harris" <wumutek@.yahoo.com> wrote in message
news:2fa13ee7.0307110428.6b0d66a@.posting.google.com...
> sql server ver 8... Microsoft Windows 2000
> A copy of a database is made using sp_attach sp_detach and the
> transaction log backup scheduled for that hour fails ...makes sense !!
> There has been subsequent failures at the same time at the application
> log but not at the database view history.
> No idea what is going on here .....
>
> Your ideas will be more than appreciated
If you are detaching, copying and re-attaching the database, the source
database will be unavailable during that time. Possibly contributing to your
job failures.
A far better technique would involve running BACKUP and RESTORE, in that way
the source db does not have to be made unavailable.
Steve

Job fails but no info on why

I'm running a maintenance plan and the job the does the integrity checks
fails, but in the job history log it gives no useful information as to why.
I can guess that there's something wrong with a relationship, index, or
missing data for the relationship, but this is a big db and it would be nice
if its going to fail, it could at least tell me why. For example, when
running a DTS, it there's an integrity issue, it will fail and tell me why.
Is there a stored procedure I can run that would list any issues that would
make this job fail? Any other advise?
Thanks.
moondaddy@.nospam.nospamIn Enterprise Manager, right click on the Maintenance plan (not the job) and
select 'Maintenance plan history' from the context menu.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"moondaddy" <moondaddy@.nospam.nospam> wrote in message
news:OsYC7GHuFHA.1252@.TK2MSFTNGP09.phx.gbl...
I'm running a maintenance plan and the job the does the integrity checks
fails, but in the job history log it gives no useful information as to why.
I can guess that there's something wrong with a relationship, index, or
missing data for the relationship, but this is a big db and it would be nice
if its going to fail, it could at least tell me why. For example, when
running a DTS, it there's an integrity issue, it will fail and tell me why.
Is there a stored procedure I can run that would list any issues that would
make this job fail? Any other advise?
Thanks.
moondaddy@.nospam.nospam|||Look on the job steps under the advanced tab, you are able to put a log
file directory / file name in here to monitor the activity performed by
the job process.
HTH, Jens Suessmeyer.|||Thanks.
moondaddy@.nospam.nospam
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1126623715.659637.295900@.z14g2000cwz.googlegroups.com...
> Look on the job steps under the advanced tab, you are able to put a log
> file directory / file name in here to monitor the activity performed by
> the job process.
>
> HTH, Jens Suessmeyer.
>|||Thanks. that gave me the clue I needed.
moondaddy@.nospam.nospam
"Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
news:u7OpsOHuFHA.1472@.TK2MSFTNGP15.phx.gbl...
> In Enterprise Manager, right click on the Maintenance plan (not the job)
> and
> select 'Maintenance plan history' from the context menu.
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "moondaddy" <moondaddy@.nospam.nospam> wrote in message
> news:OsYC7GHuFHA.1252@.TK2MSFTNGP09.phx.gbl...
> I'm running a maintenance plan and the job the does the integrity checks
> fails, but in the job history log it gives no useful information as to
> why.
> I can guess that there's something wrong with a relationship, index, or
> missing data for the relationship, but this is a big db and it would be
> nice
> if its going to fail, it could at least tell me why. For example, when
> running a DTS, it there's an integrity issue, it will fail and tell me
> why.
> Is there a stored procedure I can run that would list any issues that
> would
> make this job fail? Any other advise?
> Thanks.
> --
> moondaddy@.nospam.nospam
>
>

job failed om the sql server

Hi,

i have a problem when i schedule an agent on the sql server and i log off the sql server ,

the agent failed with this msg' in the event viewr :

Login failed for user 'sa'. [CLIENT: <local machine>].

the account that run the SQL AGENT is NT AUTHORITY\NETWORKSERVICE.

i guess the problem is there but i can't find how to resolve it?

i'll be happy for any help.

10X.

anyone plz...?|||

Hi everyone,

If more info is need i'll be happy to give...

Thanks.

|||I think NT AUTHORITY\NetworkService account is appropriate for MSDTC service but for SQL AGENT you need a domain account if you schedule activities on a network , so change SQL Agent logon account.|||Which service account is the service account running with ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

These resources may help you sort out the service account requirements for SQL Agent.

Configuration -Service Accounts, SQL Server 2005 - Setting Up Windows Service Accounts
http://msdn2.microsoft.com/en-us/library/ms143691.aspx
http://msdn2.microsoft.com/en-us/library/ms143504.aspx

Configuration -Service Accounts, SQL Server or SQL Server Agent service account
http://support.microsoft.com/kb/283811/en-us
http://msdn2.microsoft.com/en-us/library/ms143691.aspx

Configuration -Service Accounts,Selecting an Account for the SQL Server Agent Service
http://msdn2.microsoft.com/en-us/library/ms191543.aspx
http://support.microsoft.com/kb/907557

|||

the service account running with NT AUTHORITY\NetworkService.

(sql server agent service).

|||

As previously indicated, that is NOT a good account for the SQL Agent service.

Refer to the sources I posted for guidelines in setting up a domain account for your SQL Agent Service.