Hi All,
Can any one please help to find out the source of the problem?. why the
event category says printer?. Job does not deal with any printing
actions?.
please do the needful
Event Type:Warning
Event Source:SQLAgent$NODEB
Event Category:Printers
Event ID:208
Date:1/2/2007
Time:10:45:56 PM
User:N/A
Computer:NCVR1
Description:
The description for Event ID ( 208 ) in Source ( SQLAgent$VS1 ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: POC086_00:05_Check ,
0xF0CA7025DFA0654F89BF36923FB9F050, Failed, 2007-01-02 22:45:21, The
job failed. The Job was invoked by Schedule 10 (PEY_Check). The last
step to run was step 1 (PEY_Check_)..
thanks!
Hi
"Praveen" wrote:
> Hi All,
> Can any one please help to find out the source of the problem?. why the
> event category says printer?. Job does not deal with any printing
> actions?.
> please do the needful
> Event Type:Warning
> Event Source:SQLAgent$NODEB
> Event Category:Printers
> Event ID:208
> Date:1/2/2007
> Time:10:45:56 PM
> User:N/A
> Computer:NCVR1
> Description:
> The description for Event ID ( 208 ) in Source ( SQLAgent$VS1 ) cannot
> be found. The local computer may not have the necessary registry
> information or message DLL files to display messages from a remote
> computer. You may be able to use the /AUXSOURCE= flag to retrieve this
> description; see Help and Support for details. The following
> information is part of the event: POC086_00:05_Check ,
> 0xF0CA7025DFA0654F89BF36923FB9F050, Failed, 2007-01-02 22:45:21, The
> job failed. The Job was invoked by Schedule 10 (PEY_Check). The last
> step to run was step 1 (PEY_Check_)..
> thanks!
>
An Event Id 208 has been raised for which it can't find a specific message.
But it was raised because the job has failed. Have you looked at the job
history to find out what caused the job to fail?
John
Showing posts with label source. Show all posts
Showing posts with label source. Show all posts
Monday, March 12, 2012
Job Failure
Hi All,
Can any one please help to find out the source of the problem?. why the
event category says printer?. Job does not deal with any printing
actions?.
please do the needful
Event Type: Warning
Event Source: SQLAgent$NODEB
Event Category: Printers
Event ID: 208
Date: 1/2/2007
Time: 10:45:56 PM
User: N/A
Computer: NCVR1
Description:
The description for Event ID ( 208 ) in Source ( SQLAgent$VS1 ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: POC086_00:05_Check ,
0xF0CA7025DFA0654F89BF36923FB9F050, Failed, 2007-01-02 22:45:21, The
job failed. The Job was invoked by Schedule 10 (PEY_Check). The last
step to run was step 1 (PEY_Check_)..
thanks!Hi
"Praveen" wrote:
> Hi All,
> Can any one please help to find out the source of the problem?. why the
> event category says printer?. Job does not deal with any printing
> actions?.
> please do the needful
> Event Type: Warning
> Event Source: SQLAgent$NODEB
> Event Category: Printers
> Event ID: 208
> Date: 1/2/2007
> Time: 10:45:56 PM
> User: N/A
> Computer: NCVR1
> Description:
> The description for Event ID ( 208 ) in Source ( SQLAgent$VS1 ) cannot
> be found. The local computer may not have the necessary registry
> information or message DLL files to display messages from a remote
> computer. You may be able to use the /AUXSOURCE= flag to retrieve this
> description; see Help and Support for details. The following
> information is part of the event: POC086_00:05_Check ,
> 0xF0CA7025DFA0654F89BF36923FB9F050, Failed, 2007-01-02 22:45:21, The
> job failed. The Job was invoked by Schedule 10 (PEY_Check). The last
> step to run was step 1 (PEY_Check_)..
> thanks!
>
An Event Id 208 has been raised for which it can't find a specific message.
But it was raised because the job has failed. Have you looked at the job
history to find out what caused the job to fail?
John
Can any one please help to find out the source of the problem?. why the
event category says printer?. Job does not deal with any printing
actions?.
please do the needful
Event Type: Warning
Event Source: SQLAgent$NODEB
Event Category: Printers
Event ID: 208
Date: 1/2/2007
Time: 10:45:56 PM
User: N/A
Computer: NCVR1
Description:
The description for Event ID ( 208 ) in Source ( SQLAgent$VS1 ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: POC086_00:05_Check ,
0xF0CA7025DFA0654F89BF36923FB9F050, Failed, 2007-01-02 22:45:21, The
job failed. The Job was invoked by Schedule 10 (PEY_Check). The last
step to run was step 1 (PEY_Check_)..
thanks!Hi
"Praveen" wrote:
> Hi All,
> Can any one please help to find out the source of the problem?. why the
> event category says printer?. Job does not deal with any printing
> actions?.
> please do the needful
> Event Type: Warning
> Event Source: SQLAgent$NODEB
> Event Category: Printers
> Event ID: 208
> Date: 1/2/2007
> Time: 10:45:56 PM
> User: N/A
> Computer: NCVR1
> Description:
> The description for Event ID ( 208 ) in Source ( SQLAgent$VS1 ) cannot
> be found. The local computer may not have the necessary registry
> information or message DLL files to display messages from a remote
> computer. You may be able to use the /AUXSOURCE= flag to retrieve this
> description; see Help and Support for details. The following
> information is part of the event: POC086_00:05_Check ,
> 0xF0CA7025DFA0654F89BF36923FB9F050, Failed, 2007-01-02 22:45:21, The
> job failed. The Job was invoked by Schedule 10 (PEY_Check). The last
> step to run was step 1 (PEY_Check_)..
> thanks!
>
An Event Id 208 has been raised for which it can't find a specific message.
But it was raised because the job has failed. Have you looked at the job
history to find out what caused the job to fail?
John
Job failure
I have a job that runs every evening that calls 2 stored
procedures. The first sp inserts new records from a
source database.table into a destination database.table
the second job updates the records that were changed at
the source and updates them at the destination.
This job has run successfully without problems for 2+
years. Now for the past two days the second step is
blowing up the transaction log to more than 7GB (it's
limit). Any idea what could cause this new behaviour?
Any suggestions as to what I need to look at would be
most appreciated.
Thanks,
MarcIs the recovery model of the destination database changed recently? Are the
backup jobs running successfully?
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Marc" <anonymous@.discussions.microsoft.com> wrote in message
news:244ad01c45f4f$3aef6880$a501280a@.phx.gbl...
I have a job that runs every evening that calls 2 stored
procedures. The first sp inserts new records from a
source database.table into a destination database.table
the second job updates the records that were changed at
the source and updates them at the destination.
This job has run successfully without problems for 2+
years. Now for the past two days the second step is
blowing up the transaction log to more than 7GB (it's
limit). Any idea what could cause this new behaviour?
Any suggestions as to what I need to look at would be
most appreciated.
Thanks,
Marc|||Could be that the recovery model was changed from simple
to full, but I'm not 100% as this isn't my server.
The backups that are scheduled after this job runs fail
as there is no longer adequate disk space.
>--Original Message--
>Is the recovery model of the destination database
changed recently? Are the
>backup jobs running successfully?
>--
>HTH,
>Vyas, MVP (SQL Server)
>http://vyaskn.tripod.com/
>Is .NET important for a database professional?
>http://vyaskn.tripod.com/poll.htm
>
>"Marc" <anonymous@.discussions.microsoft.com> wrote in
message
>news:244ad01c45f4f$3aef6880$a501280a@.phx.gbl...
>I have a job that runs every evening that calls 2 stored
>procedures. The first sp inserts new records from a
>source database.table into a destination database.table
>the second job updates the records that were changed at
>the source and updates them at the destination.
>This job has run successfully without problems for 2+
>years. Now for the past two days the second step is
>blowing up the transaction log to more than 7GB (it's
>limit). Any idea what could cause this new behaviour?
>Any suggestions as to what I need to look at would be
>most appreciated.
>Thanks,
>Marc
>
>.
>|||Hi,
Execute the below command to get the recovery model.
select databasepropertyex('dbname','recovery')
If the recovery model is FULL or BULK_LOGGED, you need to perform a
trasnaction log backup inbetween your back job.
Currently to reduce the trasnaction log file size you have backup the
transaction log shrink the file
Steps to shrink the Log file.
1. Backup the transaction log (Use command:- BACKUP Log dbname to
disk='c:\backup\dbname.tr1' (or use enterprise manager) or (if you do need
the trasaction log backup execute below command)
backup log <dbname> with truncate_only
2. Indetify the log file for shrinking:-
use <dbname>
go
sp_helpfile
Based on the name column for the transaction log file execute the dbcc
shrinkfile
3. Shrink the transaction log file.
DBCC SHRINKFILE('logical_transaction_log file name','truncateonly')
Have a look into the below article,
INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
http://support.microsoft.com/default.aspx?scid=kb;en-us;272318
Thanks
Hari
MCDBA
"Marc" <anonymous@.discussions.microsoft.com> wrote in message
news:2415501c45f52$18baf880$a301280a@.phx.gbl...
> Could be that the recovery model was changed from simple
> to full, but I'm not 100% as this isn't my server.
> The backups that are scheduled after this job runs fail
> as there is no longer adequate disk space.
> >--Original Message--
> >Is the recovery model of the destination database
> changed recently? Are the
> >backup jobs running successfully?
> >--
> >HTH,
> >Vyas, MVP (SQL Server)
> >http://vyaskn.tripod.com/
> >Is .NET important for a database professional?
> >http://vyaskn.tripod.com/poll.htm
> >
> >
> >"Marc" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:244ad01c45f4f$3aef6880$a501280a@.phx.gbl...
> >I have a job that runs every evening that calls 2 stored
> >procedures. The first sp inserts new records from a
> >source database.table into a destination database.table
> >the second job updates the records that were changed at
> >the source and updates them at the destination.
> >
> >This job has run successfully without problems for 2+
> >years. Now for the past two days the second step is
> >blowing up the transaction log to more than 7GB (it's
> >limit). Any idea what could cause this new behaviour?
> >
> >Any suggestions as to what I need to look at would be
> >most appreciated.
> >
> >Thanks,
> >Marc
> >
> >
> >.
> >|||Thanks for the info Hari, but I've done all that.
There are transaction log backups every two hours.
What I'm trying to resolve is the offending job that
unexplainably filling up the log to capacity every
evening and then subsequently failing out.
Thanks,
Marc
>--Original Message--
>Hi,
>Execute the below command to get the recovery model.
>select databasepropertyex('dbname','recovery')
>If the recovery model is FULL or BULK_LOGGED, you need
to perform a
>trasnaction log backup inbetween your back job.
>Currently to reduce the trasnaction log file size you
have backup the
>transaction log shrink the file
>Steps to shrink the Log file.
>1. Backup the transaction log (Use command:- BACKUP Log
dbname to
>disk='c:\backup\dbname.tr1' (or use enterprise
manager) or (if you do need
>the trasaction log backup execute below command)
> backup log <dbname> with truncate_only
>2. Indetify the log file for shrinking:-
> use <dbname>
> go
> sp_helpfile
>Based on the name column for the transaction log file
execute the dbcc
>shrinkfile
>3. Shrink the transaction log file.
> DBCC SHRINKFILE('logical_transaction_log file
name','truncateonly')
>
>Have a look into the below article,
>INF: Shrinking the Transaction Log in SQL Server 2000
with DBCC SHRINKFILE
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;272318
>
>--
>Thanks
>Hari
>MCDBA
>"Marc" <anonymous@.discussions.microsoft.com> wrote in
message
>news:2415501c45f52$18baf880$a301280a@.phx.gbl...
>> Could be that the recovery model was changed from
simple
>> to full, but I'm not 100% as this isn't my server.
>> The backups that are scheduled after this job runs fail
>> as there is no longer adequate disk space.
>> >--Original Message--
>> >Is the recovery model of the destination database
>> changed recently? Are the
>> >backup jobs running successfully?
>> >--
>> >HTH,
>> >Vyas, MVP (SQL Server)
>> >http://vyaskn.tripod.com/
>> >Is .NET important for a database professional?
>> >http://vyaskn.tripod.com/poll.htm
>> >
>> >
>> >"Marc" <anonymous@.discussions.microsoft.com> wrote in
>> message
>> >news:244ad01c45f4f$3aef6880$a501280a@.phx.gbl...
>> >I have a job that runs every evening that calls 2
stored
>> >procedures. The first sp inserts new records from a
>> >source database.table into a destination
database.table
>> >the second job updates the records that were changed
at
>> >the source and updates them at the destination.
>> >
>> >This job has run successfully without problems for 2+
>> >years. Now for the past two days the second step is
>> >blowing up the transaction log to more than 7GB (it's
>> >limit). Any idea what could cause this new behaviour?
>> >
>> >Any suggestions as to what I need to look at would be
>> >most appreciated.
>> >
>> >Thanks,
>> >Marc
>> >
>> >
>> >.
>> >
>
>.
>
procedures. The first sp inserts new records from a
source database.table into a destination database.table
the second job updates the records that were changed at
the source and updates them at the destination.
This job has run successfully without problems for 2+
years. Now for the past two days the second step is
blowing up the transaction log to more than 7GB (it's
limit). Any idea what could cause this new behaviour?
Any suggestions as to what I need to look at would be
most appreciated.
Thanks,
MarcIs the recovery model of the destination database changed recently? Are the
backup jobs running successfully?
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Marc" <anonymous@.discussions.microsoft.com> wrote in message
news:244ad01c45f4f$3aef6880$a501280a@.phx.gbl...
I have a job that runs every evening that calls 2 stored
procedures. The first sp inserts new records from a
source database.table into a destination database.table
the second job updates the records that were changed at
the source and updates them at the destination.
This job has run successfully without problems for 2+
years. Now for the past two days the second step is
blowing up the transaction log to more than 7GB (it's
limit). Any idea what could cause this new behaviour?
Any suggestions as to what I need to look at would be
most appreciated.
Thanks,
Marc|||Could be that the recovery model was changed from simple
to full, but I'm not 100% as this isn't my server.
The backups that are scheduled after this job runs fail
as there is no longer adequate disk space.
>--Original Message--
>Is the recovery model of the destination database
changed recently? Are the
>backup jobs running successfully?
>--
>HTH,
>Vyas, MVP (SQL Server)
>http://vyaskn.tripod.com/
>Is .NET important for a database professional?
>http://vyaskn.tripod.com/poll.htm
>
>"Marc" <anonymous@.discussions.microsoft.com> wrote in
message
>news:244ad01c45f4f$3aef6880$a501280a@.phx.gbl...
>I have a job that runs every evening that calls 2 stored
>procedures. The first sp inserts new records from a
>source database.table into a destination database.table
>the second job updates the records that were changed at
>the source and updates them at the destination.
>This job has run successfully without problems for 2+
>years. Now for the past two days the second step is
>blowing up the transaction log to more than 7GB (it's
>limit). Any idea what could cause this new behaviour?
>Any suggestions as to what I need to look at would be
>most appreciated.
>Thanks,
>Marc
>
>.
>|||Hi,
Execute the below command to get the recovery model.
select databasepropertyex('dbname','recovery')
If the recovery model is FULL or BULK_LOGGED, you need to perform a
trasnaction log backup inbetween your back job.
Currently to reduce the trasnaction log file size you have backup the
transaction log shrink the file
Steps to shrink the Log file.
1. Backup the transaction log (Use command:- BACKUP Log dbname to
disk='c:\backup\dbname.tr1' (or use enterprise manager) or (if you do need
the trasaction log backup execute below command)
backup log <dbname> with truncate_only
2. Indetify the log file for shrinking:-
use <dbname>
go
sp_helpfile
Based on the name column for the transaction log file execute the dbcc
shrinkfile
3. Shrink the transaction log file.
DBCC SHRINKFILE('logical_transaction_log file name','truncateonly')
Have a look into the below article,
INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
http://support.microsoft.com/default.aspx?scid=kb;en-us;272318
Thanks
Hari
MCDBA
"Marc" <anonymous@.discussions.microsoft.com> wrote in message
news:2415501c45f52$18baf880$a301280a@.phx.gbl...
> Could be that the recovery model was changed from simple
> to full, but I'm not 100% as this isn't my server.
> The backups that are scheduled after this job runs fail
> as there is no longer adequate disk space.
> >--Original Message--
> >Is the recovery model of the destination database
> changed recently? Are the
> >backup jobs running successfully?
> >--
> >HTH,
> >Vyas, MVP (SQL Server)
> >http://vyaskn.tripod.com/
> >Is .NET important for a database professional?
> >http://vyaskn.tripod.com/poll.htm
> >
> >
> >"Marc" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:244ad01c45f4f$3aef6880$a501280a@.phx.gbl...
> >I have a job that runs every evening that calls 2 stored
> >procedures. The first sp inserts new records from a
> >source database.table into a destination database.table
> >the second job updates the records that were changed at
> >the source and updates them at the destination.
> >
> >This job has run successfully without problems for 2+
> >years. Now for the past two days the second step is
> >blowing up the transaction log to more than 7GB (it's
> >limit). Any idea what could cause this new behaviour?
> >
> >Any suggestions as to what I need to look at would be
> >most appreciated.
> >
> >Thanks,
> >Marc
> >
> >
> >.
> >|||Thanks for the info Hari, but I've done all that.
There are transaction log backups every two hours.
What I'm trying to resolve is the offending job that
unexplainably filling up the log to capacity every
evening and then subsequently failing out.
Thanks,
Marc
>--Original Message--
>Hi,
>Execute the below command to get the recovery model.
>select databasepropertyex('dbname','recovery')
>If the recovery model is FULL or BULK_LOGGED, you need
to perform a
>trasnaction log backup inbetween your back job.
>Currently to reduce the trasnaction log file size you
have backup the
>transaction log shrink the file
>Steps to shrink the Log file.
>1. Backup the transaction log (Use command:- BACKUP Log
dbname to
>disk='c:\backup\dbname.tr1' (or use enterprise
manager) or (if you do need
>the trasaction log backup execute below command)
> backup log <dbname> with truncate_only
>2. Indetify the log file for shrinking:-
> use <dbname>
> go
> sp_helpfile
>Based on the name column for the transaction log file
execute the dbcc
>shrinkfile
>3. Shrink the transaction log file.
> DBCC SHRINKFILE('logical_transaction_log file
name','truncateonly')
>
>Have a look into the below article,
>INF: Shrinking the Transaction Log in SQL Server 2000
with DBCC SHRINKFILE
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;272318
>
>--
>Thanks
>Hari
>MCDBA
>"Marc" <anonymous@.discussions.microsoft.com> wrote in
message
>news:2415501c45f52$18baf880$a301280a@.phx.gbl...
>> Could be that the recovery model was changed from
simple
>> to full, but I'm not 100% as this isn't my server.
>> The backups that are scheduled after this job runs fail
>> as there is no longer adequate disk space.
>> >--Original Message--
>> >Is the recovery model of the destination database
>> changed recently? Are the
>> >backup jobs running successfully?
>> >--
>> >HTH,
>> >Vyas, MVP (SQL Server)
>> >http://vyaskn.tripod.com/
>> >Is .NET important for a database professional?
>> >http://vyaskn.tripod.com/poll.htm
>> >
>> >
>> >"Marc" <anonymous@.discussions.microsoft.com> wrote in
>> message
>> >news:244ad01c45f4f$3aef6880$a501280a@.phx.gbl...
>> >I have a job that runs every evening that calls 2
stored
>> >procedures. The first sp inserts new records from a
>> >source database.table into a destination
database.table
>> >the second job updates the records that were changed
at
>> >the source and updates them at the destination.
>> >
>> >This job has run successfully without problems for 2+
>> >years. Now for the past two days the second step is
>> >blowing up the transaction log to more than 7GB (it's
>> >limit). Any idea what could cause this new behaviour?
>> >
>> >Any suggestions as to what I need to look at would be
>> >most appreciated.
>> >
>> >Thanks,
>> >Marc
>> >
>> >
>> >.
>> >
>
>.
>
job fails
I have a DTS job that runs every hour.
it truncates destination table and copies from the source table.
it has failed with the following error in view job history
"error-214721900(80040E14);provider error 14262.(37B6)"
error source Microsoft ole db provider error
pls help in this
how can i solve this, i tried restarting the job but its failing again.look here
http://support.microsoft.com/default.aspx?scid=kb;en-us;223758
Originally posted by aadil
I have a DTS job that runs every hour.
it truncates destination table and copies from the source table.
it has failed with the following error in view job history
"error-214721900(80040E14);provider error 14262.(37B6)"
error source Microsoft ole db provider error
pls help in this
how can i solve this, i tried restarting the job but its failing again.|||Also
http://search.microsoft.com/search/results.aspx?st=b&na=83&qu=80040E14&View=en-us
Originally posted by aadil
I have a DTS job that runs every hour.
it truncates destination table and copies from the source table.
it has failed with the following error in view job history
"error-214721900(80040E14);provider error 14262.(37B6)"
error source Microsoft ole db provider error
pls help in this
how can i solve this, i tried restarting the job but its failing again.|||Also this KBA http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q269074 to schedule DTS as job and resolve the issue.
it truncates destination table and copies from the source table.
it has failed with the following error in view job history
"error-214721900(80040E14);provider error 14262.(37B6)"
error source Microsoft ole db provider error
pls help in this
how can i solve this, i tried restarting the job but its failing again.look here
http://support.microsoft.com/default.aspx?scid=kb;en-us;223758
Originally posted by aadil
I have a DTS job that runs every hour.
it truncates destination table and copies from the source table.
it has failed with the following error in view job history
"error-214721900(80040E14);provider error 14262.(37B6)"
error source Microsoft ole db provider error
pls help in this
how can i solve this, i tried restarting the job but its failing again.|||Also
http://search.microsoft.com/search/results.aspx?st=b&na=83&qu=80040E14&View=en-us
Originally posted by aadil
I have a DTS job that runs every hour.
it truncates destination table and copies from the source table.
it has failed with the following error in view job history
"error-214721900(80040E14);provider error 14262.(37B6)"
error source Microsoft ole db provider error
pls help in this
how can i solve this, i tried restarting the job but its failing again.|||Also this KBA http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q269074 to schedule DTS as job and resolve the issue.
Subscribe to:
Posts (Atom)