I am unable to modify/delete a backup job for master database.
Error 14274: Cannot add, update or delete a job that originated from MSX
server.
??
Help!
Did you recently migrate the msdb database from another server? Are you the
DBA responsible for managing these?
You get that error for one of the two reasons above usually. The second one
happens when someone is using a single server to administer the jobs on
several servers.
If you look at the sysjobs table in the msdb database, you will see a column
called originating_server. That will be a different name then the instance
this msdb and master database reside on. If you update that column, you will
no longer get the error.
MeanOldDBA
derrickleggett@.hotmail.com
http://weblogs.sqlteam.com/derrickl
When life gives you a lemon, fire the DBA.
"docsql" wrote:
> I am unable to modify/delete a backup job for master database.
> Error 14274: Cannot add, update or delete a job that originated from MSX
> server.
> ??
> Help!
>
>
|||Hi,
You may also want to check if you encounter the following known issue:
281642 PRB: Error 14274 Occurs When You Update a SQL Agent Job After
Renaming
http://support.microsoft.com/?id=281642
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: backups
| thread-index: AcXK5VguhZxeuRlgTjiTogE3a78P6A==
| X-WBNR-Posting-Host: 65.69.68.118
| From: "=?Utf-8?B?TWVhbk9sZERCQQ==?="
<MeanOldDBA@.discussions.microsoft.com>
| References: <uPrUdQsyFHA.2072@.TK2MSFTNGP14.phx.gbl>
| Subject: RE: backups
| Date: Thu, 6 Oct 2005 19:18:02 -0700
| Lines: 33
| Message-ID: <7818BB22-C587-47F5-B487-3FC87D0513FD@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:73344
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Did you recently migrate the msdb database from another server? Are you
the
| DBA responsible for managing these?
|
| You get that error for one of the two reasons above usually. The second
one
| happens when someone is using a single server to administer the jobs on
| several servers.
|
| If you look at the sysjobs table in the msdb database, you will see a
column
| called originating_server. That will be a different name then the
instance
| this msdb and master database reside on. If you update that column, you
will
| no longer get the error.
|
| --
| MeanOldDBA
| derrickleggett@.hotmail.com
| http://weblogs.sqlteam.com/derrickl
|
| When life gives you a lemon, fire the DBA.
|
|
| "docsql" wrote:
|
| > I am unable to modify/delete a backup job for master database.
| >
| > Error 14274: Cannot add, update or delete a job that originated from
MSX
| > server.
| >
| > ??
| >
| > Help!
| >
| >
| >
|
|||... and this http://www.karaszi.com/SQLServer/inf...erver_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
news:pjczSIwyFHA.768@.TK2MSFTNGXA01.phx.gbl...
> Hi,
> You may also want to check if you encounter the following known issue:
> 281642 PRB: Error 14274 Occurs When You Update a SQL Agent Job After
> Renaming
> http://support.microsoft.com/?id=281642
> Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> | Thread-Topic: backups
> | thread-index: AcXK5VguhZxeuRlgTjiTogE3a78P6A==
> | X-WBNR-Posting-Host: 65.69.68.118
> | From: "=?Utf-8?B?TWVhbk9sZERCQQ==?="
> <MeanOldDBA@.discussions.microsoft.com>
> | References: <uPrUdQsyFHA.2072@.TK2MSFTNGP14.phx.gbl>
> | Subject: RE: backups
> | Date: Thu, 6 Oct 2005 19:18:02 -0700
> | Lines: 33
> | Message-ID: <7818BB22-C587-47F5-B487-3FC87D0513FD@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.sqlserver.server
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:73344
> | X-Tomcat-NG: microsoft.public.sqlserver.server
> |
> | Did you recently migrate the msdb database from another server? Are you
> the
> | DBA responsible for managing these?
> |
> | You get that error for one of the two reasons above usually. The second
> one
> | happens when someone is using a single server to administer the jobs on
> | several servers.
> |
> | If you look at the sysjobs table in the msdb database, you will see a
> column
> | called originating_server. That will be a different name then the
> instance
> | this msdb and master database reside on. If you update that column, you
> will
> | no longer get the error.
> |
> | --
> | MeanOldDBA
> | derrickleggett@.hotmail.com
> | http://weblogs.sqlteam.com/derrickl
> |
> | When life gives you a lemon, fire the DBA.
> |
> |
> | "docsql" wrote:
> |
> | > I am unable to modify/delete a backup job for master database.
> | >
> | > Error 14274: Cannot add, update or delete a job that originated from
> MSX
> | > server.
> | >
> | > ??
> | >
> | > Help!
> | >
> | >
> | >
> |
>
|||open sysjobs table
find the job that gives the error, the originating server field MUST be
different, change it to the current server name
finished
|||open msdb..sysjobs table
find the job that gives the error, the originating server field MUST be
different, change it to the current server name
finished
|||"docsql" <docsql@.noemail.nospam> wrote in message
news:uPrUdQsyFHA.2072@.TK2MSFTNGP14.phx.gbl...
>I am unable to modify/delete a backup job for master database.
> Error 14274: Cannot add, update or delete a job that originated from MSX
> server.
> ??
> Help!
>
|||http://www.karaszi.com/SQLServer/inf...erver_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"docsql" <docsql@.noemail.nospam> wrote in message news:eVx37BpzFHA.908@.tk2msftngp13.phx.gbl...
> "docsql" <docsql@.noemail.nospam> wrote in message
> news:uPrUdQsyFHA.2072@.TK2MSFTNGP14.phx.gbl...
>
Showing posts with label unable. Show all posts
Showing posts with label unable. Show all posts
Saturday, February 25, 2012
backups
I am unable to modify/delete a backup job for master database.
Error 14274: Cannot add, update or delete a job that originated from MSX
server.
'?
Help!Did you recently migrate the msdb database from another server? Are you the
DBA responsible for managing these?
You get that error for one of the two reasons above usually. The second one
happens when someone is using a single server to administer the jobs on
several servers.
If you look at the sysjobs table in the msdb database, you will see a column
called originating_server. That will be a different name then the instance
this msdb and master database reside on. If you update that column, you wil
l
no longer get the error.
MeanOldDBA
derrickleggett@.hotmail.com
http://weblogs.sqlteam.com/derrickl
When life gives you a lemon, fire the DBA.
"docsql" wrote:
> I am unable to modify/delete a backup job for master database.
> Error 14274: Cannot add, update or delete a job that originated from MSX
> server.
> '?
> Help!
>
>|||Hi,
You may also want to check if you encounter the following known issue:
281642 PRB: Error 14274 Occurs When You Update a SQL Agent Job After
Renaming
http://support.microsoft.com/?id=281642
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: backups
| thread-index: AcXK5VguhZxeuRlgTjiTogE3a78P6A==
| X-WBNR-Posting-Host: 65.69.68.118
| From: "examnotes"
<MeanOldDBA@.discussions.microsoft.com>
| References: <uPrUdQsyFHA.2072@.TK2MSFTNGP14.phx.gbl>
| Subject: RE: backups
| Date: Thu, 6 Oct 2005 19:18:02 -0700
| Lines: 33
| Message-ID: <7818BB22-C587-47F5-B487-3FC87D0513FD@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:73344
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Did you recently migrate the msdb database from another server? Are you
the
| DBA responsible for managing these?
|
| You get that error for one of the two reasons above usually. The second
one
| happens when someone is using a single server to administer the jobs on
| several servers.
|
| If you look at the sysjobs table in the msdb database, you will see a
column
| called originating_server. That will be a different name then the
instance
| this msdb and master database reside on. If you update that column, you
will
| no longer get the error.
|
| --
| MeanOldDBA
| derrickleggett@.hotmail.com
| http://weblogs.sqlteam.com/derrickl
|
| When life gives you a lemon, fire the DBA.
|
|
| "docsql" wrote:
|
| > I am unable to modify/delete a backup job for master database.
| >
| > Error 14274: Cannot add, update or delete a job that originated from
MSX
| > server.
| >
| > '?
| >
| > Help!
| >
| >
| >
||||... and this http://www.karaszi.com/SQLServer/in...server_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
news:pjczSIwyFHA.768@.TK2MSFTNGXA01.phx.gbl...
> Hi,
> You may also want to check if you encounter the following known issue:
> 281642 PRB: Error 14274 Occurs When You Update a SQL Agent Job After
> Renaming
> http://support.microsoft.com/?id=281642
> Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> --
> | Thread-Topic: backups
> | thread-index: AcXK5VguhZxeuRlgTjiTogE3a78P6A==
> | X-WBNR-Posting-Host: 65.69.68.118
> | From: "examnotes"
> <MeanOldDBA@.discussions.microsoft.com>
> | References: <uPrUdQsyFHA.2072@.TK2MSFTNGP14.phx.gbl>
> | Subject: RE: backups
> | Date: Thu, 6 Oct 2005 19:18:02 -0700
> | Lines: 33
> | Message-ID: <7818BB22-C587-47F5-B487-3FC87D0513FD@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.sqlserver.server
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:73344
> | X-Tomcat-NG: microsoft.public.sqlserver.server
> |
> | Did you recently migrate the msdb database from another server? Are you
> the
> | DBA responsible for managing these?
> |
> | You get that error for one of the two reasons above usually. The second
> one
> | happens when someone is using a single server to administer the jobs on
> | several servers.
> |
> | If you look at the sysjobs table in the msdb database, you will see a
> column
> | called originating_server. That will be a different name then the
> instance
> | this msdb and master database reside on. If you update that column, you
> will
> | no longer get the error.
> |
> | --
> | MeanOldDBA
> | derrickleggett@.hotmail.com
> | http://weblogs.sqlteam.com/derrickl
> |
> | When life gives you a lemon, fire the DBA.
> |
> |
> | "docsql" wrote:
> |
> | > I am unable to modify/delete a backup job for master database.
> | >
> | > Error 14274: Cannot add, update or delete a job that originated from
> MSX
> | > server.
> | >
> | > '?
> | >
> | > Help!
> | >
> | >
> | >
> |
>|||open sysjobs table
find the job that gives the error, the originating server field MUST be
different, change it to the current server name
finished|||open msdb..sysjobs table
find the job that gives the error, the originating server field MUST be
different, change it to the current server name
finished|||"docsql" <docsql@.noemail.nospam> wrote in message
news:uPrUdQsyFHA.2072@.TK2MSFTNGP14.phx.gbl...
>I am unable to modify/delete a backup job for master database.
> Error 14274: Cannot add, update or delete a job that originated from MSX
> server.
> '?
> Help!
>|||http://www.karaszi.com/SQLServer/in...server_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"docsql" <docsql@.noemail.nospam> wrote in message news:eVx37BpzFHA.908@.tk2msftngp13.phx.gbl.
.
> "docsql" <docsql@.noemail.nospam> wrote in message
> news:uPrUdQsyFHA.2072@.TK2MSFTNGP14.phx.gbl...
>
Error 14274: Cannot add, update or delete a job that originated from MSX
server.
'?
Help!Did you recently migrate the msdb database from another server? Are you the
DBA responsible for managing these?
You get that error for one of the two reasons above usually. The second one
happens when someone is using a single server to administer the jobs on
several servers.
If you look at the sysjobs table in the msdb database, you will see a column
called originating_server. That will be a different name then the instance
this msdb and master database reside on. If you update that column, you wil
l
no longer get the error.
MeanOldDBA
derrickleggett@.hotmail.com
http://weblogs.sqlteam.com/derrickl
When life gives you a lemon, fire the DBA.
"docsql" wrote:
> I am unable to modify/delete a backup job for master database.
> Error 14274: Cannot add, update or delete a job that originated from MSX
> server.
> '?
> Help!
>
>|||Hi,
You may also want to check if you encounter the following known issue:
281642 PRB: Error 14274 Occurs When You Update a SQL Agent Job After
Renaming
http://support.microsoft.com/?id=281642
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: backups
| thread-index: AcXK5VguhZxeuRlgTjiTogE3a78P6A==
| X-WBNR-Posting-Host: 65.69.68.118
| From: "examnotes"
<MeanOldDBA@.discussions.microsoft.com>
| References: <uPrUdQsyFHA.2072@.TK2MSFTNGP14.phx.gbl>
| Subject: RE: backups
| Date: Thu, 6 Oct 2005 19:18:02 -0700
| Lines: 33
| Message-ID: <7818BB22-C587-47F5-B487-3FC87D0513FD@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:73344
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Did you recently migrate the msdb database from another server? Are you
the
| DBA responsible for managing these?
|
| You get that error for one of the two reasons above usually. The second
one
| happens when someone is using a single server to administer the jobs on
| several servers.
|
| If you look at the sysjobs table in the msdb database, you will see a
column
| called originating_server. That will be a different name then the
instance
| this msdb and master database reside on. If you update that column, you
will
| no longer get the error.
|
| --
| MeanOldDBA
| derrickleggett@.hotmail.com
| http://weblogs.sqlteam.com/derrickl
|
| When life gives you a lemon, fire the DBA.
|
|
| "docsql" wrote:
|
| > I am unable to modify/delete a backup job for master database.
| >
| > Error 14274: Cannot add, update or delete a job that originated from
MSX
| > server.
| >
| > '?
| >
| > Help!
| >
| >
| >
||||... and this http://www.karaszi.com/SQLServer/in...server_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
news:pjczSIwyFHA.768@.TK2MSFTNGXA01.phx.gbl...
> Hi,
> You may also want to check if you encounter the following known issue:
> 281642 PRB: Error 14274 Occurs When You Update a SQL Agent Job After
> Renaming
> http://support.microsoft.com/?id=281642
> Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> --
> | Thread-Topic: backups
> | thread-index: AcXK5VguhZxeuRlgTjiTogE3a78P6A==
> | X-WBNR-Posting-Host: 65.69.68.118
> | From: "examnotes"
> <MeanOldDBA@.discussions.microsoft.com>
> | References: <uPrUdQsyFHA.2072@.TK2MSFTNGP14.phx.gbl>
> | Subject: RE: backups
> | Date: Thu, 6 Oct 2005 19:18:02 -0700
> | Lines: 33
> | Message-ID: <7818BB22-C587-47F5-B487-3FC87D0513FD@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.sqlserver.server
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:73344
> | X-Tomcat-NG: microsoft.public.sqlserver.server
> |
> | Did you recently migrate the msdb database from another server? Are you
> the
> | DBA responsible for managing these?
> |
> | You get that error for one of the two reasons above usually. The second
> one
> | happens when someone is using a single server to administer the jobs on
> | several servers.
> |
> | If you look at the sysjobs table in the msdb database, you will see a
> column
> | called originating_server. That will be a different name then the
> instance
> | this msdb and master database reside on. If you update that column, you
> will
> | no longer get the error.
> |
> | --
> | MeanOldDBA
> | derrickleggett@.hotmail.com
> | http://weblogs.sqlteam.com/derrickl
> |
> | When life gives you a lemon, fire the DBA.
> |
> |
> | "docsql" wrote:
> |
> | > I am unable to modify/delete a backup job for master database.
> | >
> | > Error 14274: Cannot add, update or delete a job that originated from
> MSX
> | > server.
> | >
> | > '?
> | >
> | > Help!
> | >
> | >
> | >
> |
>|||open sysjobs table
find the job that gives the error, the originating server field MUST be
different, change it to the current server name
finished|||open msdb..sysjobs table
find the job that gives the error, the originating server field MUST be
different, change it to the current server name
finished|||"docsql" <docsql@.noemail.nospam> wrote in message
news:uPrUdQsyFHA.2072@.TK2MSFTNGP14.phx.gbl...
>I am unable to modify/delete a backup job for master database.
> Error 14274: Cannot add, update or delete a job that originated from MSX
> server.
> '?
> Help!
>|||http://www.karaszi.com/SQLServer/in...server_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"docsql" <docsql@.noemail.nospam> wrote in message news:eVx37BpzFHA.908@.tk2msftngp13.phx.gbl.
.
> "docsql" <docsql@.noemail.nospam> wrote in message
> news:uPrUdQsyFHA.2072@.TK2MSFTNGP14.phx.gbl...
>
backups
I am unable to modify/delete a backup job for master database.
Error 14274: Cannot add, update or delete a job that originated from MSX
server.
'?
Help!Did you recently migrate the msdb database from another server? Are you the
DBA responsible for managing these?
You get that error for one of the two reasons above usually. The second one
happens when someone is using a single server to administer the jobs on
several servers.
If you look at the sysjobs table in the msdb database, you will see a column
called originating_server. That will be a different name then the instance
this msdb and master database reside on. If you update that column, you will
no longer get the error.
--
MeanOldDBA
derrickleggett@.hotmail.com
http://weblogs.sqlteam.com/derrickl
When life gives you a lemon, fire the DBA.
"docsql" wrote:
> I am unable to modify/delete a backup job for master database.
> Error 14274: Cannot add, update or delete a job that originated from MSX
> server.
> '?
> Help!
>
>|||Hi,
You may also want to check if you encounter the following known issue:
281642 PRB: Error 14274 Occurs When You Update a SQL Agent Job After
Renaming
http://support.microsoft.com/?id=281642
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--
| Thread-Topic: backups
| thread-index: AcXK5VguhZxeuRlgTjiTogE3a78P6A==| X-WBNR-Posting-Host: 65.69.68.118
| From: "=?Utf-8?B?TWVhbk9sZERCQQ==?="
<MeanOldDBA@.discussions.microsoft.com>
| References: <uPrUdQsyFHA.2072@.TK2MSFTNGP14.phx.gbl>
| Subject: RE: backups
| Date: Thu, 6 Oct 2005 19:18:02 -0700
| Lines: 33
| Message-ID: <7818BB22-C587-47F5-B487-3FC87D0513FD@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:73344
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Did you recently migrate the msdb database from another server? Are you
the
| DBA responsible for managing these?
|
| You get that error for one of the two reasons above usually. The second
one
| happens when someone is using a single server to administer the jobs on
| several servers.
|
| If you look at the sysjobs table in the msdb database, you will see a
column
| called originating_server. That will be a different name then the
instance
| this msdb and master database reside on. If you update that column, you
will
| no longer get the error.
|
| --
| MeanOldDBA
| derrickleggett@.hotmail.com
| http://weblogs.sqlteam.com/derrickl
|
| When life gives you a lemon, fire the DBA.
|
|
| "docsql" wrote:
|
| > I am unable to modify/delete a backup job for master database.
| >
| > Error 14274: Cannot add, update or delete a job that originated from
MSX
| > server.
| >
| > '?
| >
| > Help!
| >
| >
| >
||||... and this http://www.karaszi.com/SQLServer/info_change_server_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
news:pjczSIwyFHA.768@.TK2MSFTNGXA01.phx.gbl...
> Hi,
> You may also want to check if you encounter the following known issue:
> 281642 PRB: Error 14274 Occurs When You Update a SQL Agent Job After
> Renaming
> http://support.microsoft.com/?id=281642
> Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> | Thread-Topic: backups
> | thread-index: AcXK5VguhZxeuRlgTjiTogE3a78P6A==> | X-WBNR-Posting-Host: 65.69.68.118
> | From: "=?Utf-8?B?TWVhbk9sZERCQQ==?="
> <MeanOldDBA@.discussions.microsoft.com>
> | References: <uPrUdQsyFHA.2072@.TK2MSFTNGP14.phx.gbl>
> | Subject: RE: backups
> | Date: Thu, 6 Oct 2005 19:18:02 -0700
> | Lines: 33
> | Message-ID: <7818BB22-C587-47F5-B487-3FC87D0513FD@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.sqlserver.server
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:73344
> | X-Tomcat-NG: microsoft.public.sqlserver.server
> |
> | Did you recently migrate the msdb database from another server? Are you
> the
> | DBA responsible for managing these?
> |
> | You get that error for one of the two reasons above usually. The second
> one
> | happens when someone is using a single server to administer the jobs on
> | several servers.
> |
> | If you look at the sysjobs table in the msdb database, you will see a
> column
> | called originating_server. That will be a different name then the
> instance
> | this msdb and master database reside on. If you update that column, you
> will
> | no longer get the error.
> |
> | --
> | MeanOldDBA
> | derrickleggett@.hotmail.com
> | http://weblogs.sqlteam.com/derrickl
> |
> | When life gives you a lemon, fire the DBA.
> |
> |
> | "docsql" wrote:
> |
> | > I am unable to modify/delete a backup job for master database.
> | >
> | > Error 14274: Cannot add, update or delete a job that originated from
> MSX
> | > server.
> | >
> | > '?
> | >
> | > Help!
> | >
> | >
> | >
> |
>|||open sysjobs table
find the job that gives the error, the originating server field MUST be
different, change it to the current server name
finished|||open msdb..sysjobs table
find the job that gives the error, the originating server field MUST be
different, change it to the current server name
finished|||"docsql" <docsql@.noemail.nospam> wrote in message
news:uPrUdQsyFHA.2072@.TK2MSFTNGP14.phx.gbl...
>I am unable to modify/delete a backup job for master database.
> Error 14274: Cannot add, update or delete a job that originated from MSX
> server.
> '?
> Help!
>|||http://www.karaszi.com/SQLServer/info_change_server_name.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"docsql" <docsql@.noemail.nospam> wrote in message news:eVx37BpzFHA.908@.tk2msftngp13.phx.gbl...
> "docsql" <docsql@.noemail.nospam> wrote in message
> news:uPrUdQsyFHA.2072@.TK2MSFTNGP14.phx.gbl...
>>I am unable to modify/delete a backup job for master database.
>> Error 14274: Cannot add, update or delete a job that originated from MSX
>> server.
>> '?
>> Help!
>
Error 14274: Cannot add, update or delete a job that originated from MSX
server.
'?
Help!Did you recently migrate the msdb database from another server? Are you the
DBA responsible for managing these?
You get that error for one of the two reasons above usually. The second one
happens when someone is using a single server to administer the jobs on
several servers.
If you look at the sysjobs table in the msdb database, you will see a column
called originating_server. That will be a different name then the instance
this msdb and master database reside on. If you update that column, you will
no longer get the error.
--
MeanOldDBA
derrickleggett@.hotmail.com
http://weblogs.sqlteam.com/derrickl
When life gives you a lemon, fire the DBA.
"docsql" wrote:
> I am unable to modify/delete a backup job for master database.
> Error 14274: Cannot add, update or delete a job that originated from MSX
> server.
> '?
> Help!
>
>|||Hi,
You may also want to check if you encounter the following known issue:
281642 PRB: Error 14274 Occurs When You Update a SQL Agent Job After
Renaming
http://support.microsoft.com/?id=281642
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--
| Thread-Topic: backups
| thread-index: AcXK5VguhZxeuRlgTjiTogE3a78P6A==| X-WBNR-Posting-Host: 65.69.68.118
| From: "=?Utf-8?B?TWVhbk9sZERCQQ==?="
<MeanOldDBA@.discussions.microsoft.com>
| References: <uPrUdQsyFHA.2072@.TK2MSFTNGP14.phx.gbl>
| Subject: RE: backups
| Date: Thu, 6 Oct 2005 19:18:02 -0700
| Lines: 33
| Message-ID: <7818BB22-C587-47F5-B487-3FC87D0513FD@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:73344
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Did you recently migrate the msdb database from another server? Are you
the
| DBA responsible for managing these?
|
| You get that error for one of the two reasons above usually. The second
one
| happens when someone is using a single server to administer the jobs on
| several servers.
|
| If you look at the sysjobs table in the msdb database, you will see a
column
| called originating_server. That will be a different name then the
instance
| this msdb and master database reside on. If you update that column, you
will
| no longer get the error.
|
| --
| MeanOldDBA
| derrickleggett@.hotmail.com
| http://weblogs.sqlteam.com/derrickl
|
| When life gives you a lemon, fire the DBA.
|
|
| "docsql" wrote:
|
| > I am unable to modify/delete a backup job for master database.
| >
| > Error 14274: Cannot add, update or delete a job that originated from
MSX
| > server.
| >
| > '?
| >
| > Help!
| >
| >
| >
||||... and this http://www.karaszi.com/SQLServer/info_change_server_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
news:pjczSIwyFHA.768@.TK2MSFTNGXA01.phx.gbl...
> Hi,
> You may also want to check if you encounter the following known issue:
> 281642 PRB: Error 14274 Occurs When You Update a SQL Agent Job After
> Renaming
> http://support.microsoft.com/?id=281642
> Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> | Thread-Topic: backups
> | thread-index: AcXK5VguhZxeuRlgTjiTogE3a78P6A==> | X-WBNR-Posting-Host: 65.69.68.118
> | From: "=?Utf-8?B?TWVhbk9sZERCQQ==?="
> <MeanOldDBA@.discussions.microsoft.com>
> | References: <uPrUdQsyFHA.2072@.TK2MSFTNGP14.phx.gbl>
> | Subject: RE: backups
> | Date: Thu, 6 Oct 2005 19:18:02 -0700
> | Lines: 33
> | Message-ID: <7818BB22-C587-47F5-B487-3FC87D0513FD@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.sqlserver.server
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:73344
> | X-Tomcat-NG: microsoft.public.sqlserver.server
> |
> | Did you recently migrate the msdb database from another server? Are you
> the
> | DBA responsible for managing these?
> |
> | You get that error for one of the two reasons above usually. The second
> one
> | happens when someone is using a single server to administer the jobs on
> | several servers.
> |
> | If you look at the sysjobs table in the msdb database, you will see a
> column
> | called originating_server. That will be a different name then the
> instance
> | this msdb and master database reside on. If you update that column, you
> will
> | no longer get the error.
> |
> | --
> | MeanOldDBA
> | derrickleggett@.hotmail.com
> | http://weblogs.sqlteam.com/derrickl
> |
> | When life gives you a lemon, fire the DBA.
> |
> |
> | "docsql" wrote:
> |
> | > I am unable to modify/delete a backup job for master database.
> | >
> | > Error 14274: Cannot add, update or delete a job that originated from
> MSX
> | > server.
> | >
> | > '?
> | >
> | > Help!
> | >
> | >
> | >
> |
>|||open sysjobs table
find the job that gives the error, the originating server field MUST be
different, change it to the current server name
finished|||open msdb..sysjobs table
find the job that gives the error, the originating server field MUST be
different, change it to the current server name
finished|||"docsql" <docsql@.noemail.nospam> wrote in message
news:uPrUdQsyFHA.2072@.TK2MSFTNGP14.phx.gbl...
>I am unable to modify/delete a backup job for master database.
> Error 14274: Cannot add, update or delete a job that originated from MSX
> server.
> '?
> Help!
>|||http://www.karaszi.com/SQLServer/info_change_server_name.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"docsql" <docsql@.noemail.nospam> wrote in message news:eVx37BpzFHA.908@.tk2msftngp13.phx.gbl...
> "docsql" <docsql@.noemail.nospam> wrote in message
> news:uPrUdQsyFHA.2072@.TK2MSFTNGP14.phx.gbl...
>>I am unable to modify/delete a backup job for master database.
>> Error 14274: Cannot add, update or delete a job that originated from MSX
>> server.
>> '?
>> Help!
>
Friday, February 24, 2012
BackupIoRequest::WaitForIoCompletion - Unable to find ryme or reason!
Event Type: Error
Event Source: MSSQLServer
Event Category: (6)
Event ID: 17055
Date: 8/11/2002
Time: 8:00:08 PM
User: xxxxxxxxxx
Computer: xxxxxxxxxx
Description:
18210 :
BackupIoRequest::WaitForIoCompletion: read failure on backup
device 'd:\mssql7\data\Debtors_Data.MDF'. Operating system error 1453
(Insufficient quota to complete the requested service.).
This is the event log view from a SQL7 No service pack server on a W2k server SP2.
The D: drive where the backup file is going has over 13GB free !
Has any one else had this error ? M$ have no information :(
Cheers
DaveRE:
read failure on backup device 'd:\mssql7\data\Debtors_Data.MDF'. Operating system error 1453 (Insufficient quota to complete the requested service.).
This is the event log view from a SQL7 No service pack server on a W2k server SP2.
The D: drive where the backup file is going has over 13GB free !
Has any one else had this error ? M$ have no information
Q1 Has any one else had this error ?
A1 This looks like it may be a disk quota related error.
Q2 The D: drive where the backup file is going has over 13GB free!
A2 Fine, but if disk quotas are enabled, how much is available on the D:\ drive for the service account under which sql server is running?
S1 Are you able to complete any (small) backup dumps? (If not, some DB may have already grown to meet an existing quota limit.)
S2 Try deleteing all existing backup files and then attempt a (very small) backup dump, say for master.|||Hi,
No Quota's are enabled
The 'Job' ran successfully the following morning after the initial error.
This morning (Tuesday) the Job ran successfully.
I am thinking that the Quota reference is 'system resources' rather than disk quota.
I think that even though the source is MSSQLSERVICE i believe its a W2K issue.
OS W2K SP2
1x 1Ghz CPU
Memory 2GB
Hardware RAID
2x Database.
Cataloging 3,2xx,xxx records (manual incremental population)
I have read where people have Service Packed there OS to SP3 but this still doesnt fix [there] problem
Dave|||RE:
Hi, No Quota's are enabled
The 'Job' ran successfully the following morning after the initial error.
This morning (Tuesday) the Job ran successfully.
I am thinking that the Quota reference is 'system resources' rather than disk quota. I think that even though the source is MSSQLSERVICE i believe its a W2K issue.
OS W2K SP2
1x 1Ghz CPU
Memory 2GB
Hardware RAID
2x Database.
Cataloging 3,2xx,xxx records (manual incremental population)
I have read where people have Service Packed there OS to SP3 but this still doesnt fix [there] problem Dave
Q1 [No Quota's are enabled]
A1 That's too bad it would have been an easy fix.
Q2 [I am thinking that the Quota reference is 'system resources' rather than disk quota. I think that even though the source is MSSQLSERVICE i believe its a W2K issue.]
A2 Well yes, kind of (probably); the API likely ends up calling the same lower level drivers in any case.
S1 The issue may also be related to driver corruption, driver coding issues / bugs and / or authentication and / or ACL issues. If you happen to have also very recently updated any disk / array drivers, you might consider either attempting to refresh the driver update(s) and / or undoing them?
As far as I understood there (were / are in 99 / 00?) some issues having to do with "IO set completion" that had / have something to do with switches between different levels of kernel drivers that array controller drivers initiate (maybe related, maybe not?).
As to authentication, I've seen (and experienced) problems with some network domains wherein every now and then the (domain controller?) decides the Sql Server / service account doesn't have the neccessary rights to dump wherever (usually, but not always, also accompanied by logon failures in the event log), which causes similar issues.|||Event Type: Error
Event Source: MSSQLServer
Event Category: (6)
Event ID: 17055
Date: 8/11/2002
Time: 8:00:08 PM
User: xxxxxxxxxx
Computer: xxxxxxxxxx
Description:
18210 :
BackupIoRequest::WaitForIoCompletion: read failure on backup
device 'd:\mssql7\data\Debtors_Data.MDF'. Operating system error 1453
(Insufficient quota to complete the requested service.).
This is the event log view from a SQL7 No service pack server on a W2k server SP2.
The D: drive where the backup file is going has over 13GB free !
Has any one else had this error ? M$ have no information :(
Cheers
Dave
Q1 This is the event log view from a SQL7 No service pack server?
A1 I missed that detail previously. If I read that correctly why is that? You may want to check out MS Q274310 (or "Why you may consider applying Service Pack 3 for Microsoft SQL Server 7.0")?
http://support.microsoft.com/default.aspx?scid=kb;EN-US;274310
Event Source: MSSQLServer
Event Category: (6)
Event ID: 17055
Date: 8/11/2002
Time: 8:00:08 PM
User: xxxxxxxxxx
Computer: xxxxxxxxxx
Description:
18210 :
BackupIoRequest::WaitForIoCompletion: read failure on backup
device 'd:\mssql7\data\Debtors_Data.MDF'. Operating system error 1453
(Insufficient quota to complete the requested service.).
This is the event log view from a SQL7 No service pack server on a W2k server SP2.
The D: drive where the backup file is going has over 13GB free !
Has any one else had this error ? M$ have no information :(
Cheers
DaveRE:
read failure on backup device 'd:\mssql7\data\Debtors_Data.MDF'. Operating system error 1453 (Insufficient quota to complete the requested service.).
This is the event log view from a SQL7 No service pack server on a W2k server SP2.
The D: drive where the backup file is going has over 13GB free !
Has any one else had this error ? M$ have no information
Q1 Has any one else had this error ?
A1 This looks like it may be a disk quota related error.
Q2 The D: drive where the backup file is going has over 13GB free!
A2 Fine, but if disk quotas are enabled, how much is available on the D:\ drive for the service account under which sql server is running?
S1 Are you able to complete any (small) backup dumps? (If not, some DB may have already grown to meet an existing quota limit.)
S2 Try deleteing all existing backup files and then attempt a (very small) backup dump, say for master.|||Hi,
No Quota's are enabled
The 'Job' ran successfully the following morning after the initial error.
This morning (Tuesday) the Job ran successfully.
I am thinking that the Quota reference is 'system resources' rather than disk quota.
I think that even though the source is MSSQLSERVICE i believe its a W2K issue.
OS W2K SP2
1x 1Ghz CPU
Memory 2GB
Hardware RAID
2x Database.
Cataloging 3,2xx,xxx records (manual incremental population)
I have read where people have Service Packed there OS to SP3 but this still doesnt fix [there] problem
Dave|||RE:
Hi, No Quota's are enabled
The 'Job' ran successfully the following morning after the initial error.
This morning (Tuesday) the Job ran successfully.
I am thinking that the Quota reference is 'system resources' rather than disk quota. I think that even though the source is MSSQLSERVICE i believe its a W2K issue.
OS W2K SP2
1x 1Ghz CPU
Memory 2GB
Hardware RAID
2x Database.
Cataloging 3,2xx,xxx records (manual incremental population)
I have read where people have Service Packed there OS to SP3 but this still doesnt fix [there] problem Dave
Q1 [No Quota's are enabled]
A1 That's too bad it would have been an easy fix.
Q2 [I am thinking that the Quota reference is 'system resources' rather than disk quota. I think that even though the source is MSSQLSERVICE i believe its a W2K issue.]
A2 Well yes, kind of (probably); the API likely ends up calling the same lower level drivers in any case.
S1 The issue may also be related to driver corruption, driver coding issues / bugs and / or authentication and / or ACL issues. If you happen to have also very recently updated any disk / array drivers, you might consider either attempting to refresh the driver update(s) and / or undoing them?
As far as I understood there (were / are in 99 / 00?) some issues having to do with "IO set completion" that had / have something to do with switches between different levels of kernel drivers that array controller drivers initiate (maybe related, maybe not?).
As to authentication, I've seen (and experienced) problems with some network domains wherein every now and then the (domain controller?) decides the Sql Server / service account doesn't have the neccessary rights to dump wherever (usually, but not always, also accompanied by logon failures in the event log), which causes similar issues.|||Event Type: Error
Event Source: MSSQLServer
Event Category: (6)
Event ID: 17055
Date: 8/11/2002
Time: 8:00:08 PM
User: xxxxxxxxxx
Computer: xxxxxxxxxx
Description:
18210 :
BackupIoRequest::WaitForIoCompletion: read failure on backup
device 'd:\mssql7\data\Debtors_Data.MDF'. Operating system error 1453
(Insufficient quota to complete the requested service.).
This is the event log view from a SQL7 No service pack server on a W2k server SP2.
The D: drive where the backup file is going has over 13GB free !
Has any one else had this error ? M$ have no information :(
Cheers
Dave
Q1 This is the event log view from a SQL7 No service pack server?
A1 I missed that detail previously. If I read that correctly why is that? You may want to check out MS Q274310 (or "Why you may consider applying Service Pack 3 for Microsoft SQL Server 7.0")?
http://support.microsoft.com/default.aspx?scid=kb;EN-US;274310
Subscribe to:
Posts (Atom)