Error 14274 Sql Server 2000
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more sp_add_jobserver about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered sp_delete_job Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and sp_dropserver learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Can't do any changes to a job in SQL 2000 up vote 1 down vote favorite I have a job in my SQL 2000 server, this job is used to execute a DTS, i want to change the schedule of this job. but every time i try to change of delete or stop this job i get the error message ERROR 14274: Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server. The job was not saved. i have a system shutdown coming up in the weekend and i cant stop this job... sql-server-2000 jobs share|improve this question edited May 31 '12 at 12:18 Leigh Riffel 18.4k1053127 asked May 31 '12 at 7:30 AmmarR 1,94921225 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote accepted It sounds like you might be facing this issue ... http://support.microsoft.com/kb/281642 After the Windows server name been changed, when trying to update or delete the jobs previously created in a SQL Server 2000 instance, you may receive the following error message: Error 14274: Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server. The job was not saved. Here are the suggested steps to workaround the issue ... The best way to handle this problem after the rename process is to follow these steps: Rename the server back to the original name. Script out all of the jobs and then delete them. Rename the server to the new name. Add back the jobs by running the script generated from step 2. Additionally you can find more discussion/suggestions here ... http://blog.sqlauthority.com/2006/12/20/sql-server-fix-error-14274-cannot-add-update-or-delete-a-job-or-its-steps-or-schedules-that-originated-from-an-msx-server-the-job-was-not-saved/ share|improve this answer answered May 31 '12 at 7:39 Justin Jenkins 33115 Thanks, i just applied the script "update sysjobs set originating_server = 'thenewservername';" and it worked, i didnt want to change my
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and http://dba.stackexchange.com/questions/18612/cant-do-any-changes-to-a-job-in-sql-2000 rise to the top Can't do any changes to a job in SQL 2000 up vote 1 down vote favorite I have a job in my SQL 2000 server, this job is used to execute a DTS, i want to change the schedule of this job. but every time i try to change of delete or stop this job i get the error message ERROR 14274: Cannot add, update, or delete a job (or its http://dba.stackexchange.com/questions/18612/cant-do-any-changes-to-a-job-in-sql-2000 steps or schedules) that originated from an MSX server. The job was not saved. i have a system shutdown coming up in the weekend and i cant stop this job... sql-server-2000 jobs share|improve this question edited May 31 '12 at 12:18 Leigh Riffel 18.4k1053127 asked May 31 '12 at 7:30 AmmarR 1,94921225 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote accepted It sounds like you might be facing this issue ... http://support.microsoft.com/kb/281642 After the Windows server name been changed, when trying to update or delete the jobs previously created in a SQL Server 2000 instance, you may receive the following error message: Error 14274: Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server. The job was not saved. Here are the suggested steps to workaround the issue ... The best way to handle this problem after the rename process is to follow these steps: Rename the server back to the original name. Script out all of the jobs and then delete them. Rename the server to the new name. Add back the jobs by running the script generated from step 2. Additionally you can find more discussion/suggestions here ... http://blog.sqlauthority.com/2006/12/20/sql-server-fix-error-14274-cannot-add-update-or-delete-a-job-or-its-steps-or-schedules-that-originated-from-an-msx-server-the-job-was-not-saved/ share|improve this answer answered May 31 '12 at 7:39 Justin Jenkins 33115 Thanks, i just applied the
SQL Server experts to answer whatever question you can come up with. Our new SQL Server http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=186495 Forums are live! Come on over! We've restricted the ability to http://www.sqlbackuprestore.com/error14274.htm create new threads on these forums. SQL Server Forums Profile | ActiveTopics | Members | Search | ForumFAQ Register Now and get your question answered! Username: Password: Save Password Forgot your Password? All Forums SQL Server 2008 Forums Transact-SQL (2008) Cannot add, update, or delete a job error 14274 (or its steps Reply to Topic Printer Friendly Author Topic rosetulip Starting Member 15 Posts Posted-06/28/2013: 23:58:43 I have a trouble to merge two jobs into a master script file by sharing the same globalization declaration. If I run separately, it works fine.The two jobs are testdbname jobtestnewdb jobIt comes up with the following errorsI error 14274 sql got many these messageMsg 14274, Level 16, State 1, Procedure sp_add_job, Line 132Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server.Msg 14274, Level 16, State 1, Procedure sp_add_job, Line 132Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server.Msg 14274, Level 16, State 1, Procedure sp_add_job, Line 132 Here is two job scriptUSE [msdb]GODECLARE @LLC_DATABASE_NAME NVARCHAR(100) = N'LLC'DECLARE @LLC_LOG_IN_NAME NVARCHAR(100) = N'LLC'DECLARE @Roll_Back_Server NVARCHAR(100) = N'(local)'IF EXISTS (SELECT job_id FROM msdb.dbo.sysjobs_view WHERE name = N'testdbname')EXEC sp_delete_job @job_name = N' testdbname' , @delete_unused_schedule=1IF EXISTS (SELECT job_id FROM msdb.dbo.sysjobs_view WHERE name = N'testnewdb')EXEC sp_delete_job @job_name = N'testnewdb' , @delete_unused_schedule=1/****** Object: Job [testdbname] Script Date: 06/25/2013 16:41:15 ******/BEGIN TRANSACTIONDECLARE @ReturnCode INTSELECT @ReturnCode = 0/****** Object: JobCategory [Database Maintenance] Script Date: 06/25/2013 16:41:15 ******/IF NOT EXISTS (SELECT name FROM msdb.dbo.syscategories WHERE name=N'Database Maintenance' AND category_class=1)BEGINEXEC @ReturnCode = msdb.dbo.sp_add_category @class=N'JOB', @type=N'LOCAL', @name=N'Database Maintenance'IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollbackEND-- testdbname jobDECLARE @jobId BINARY(16)EXEC @ReturnCode = msdb.dbo.sp_add_job
transaction log Backing up the tail Inside the transaction log So, what's in a backup file? Test: A full backup does not contain deleted data Verifying backup files Verifying backup files on a budget Cumulative backups Recovering individual tables Backup and restore history details Backup reads and writes Speeding up backups Backup speed details Speeding up restores Restore state affects speed too Backup and restore rights Log shipping Log shipping in SQL Server 2000 Setting up log shipping using Enterprise Manager Checking the set up Failover Log shipping in SQL Server 2005 Setting up log shipping using Management Studio Checking the set up Log shipping status report Failover Log shipping in SQL Backup Using the CopyTool utility Failover 3rd party backup applications VDI VDI versions VDI errors SQL Backup - beyond compression Restoring a chain of transaction log backups Restoring to the latest possible state Backing up multiple databases Backup retention Making a copy of the backup file Backup file naming conventions Restoring the latest backup set Network resilience Encryption Integrated database verification Database file relocation Improved backup retention RESTORE HELP High-availability group support Common SQL Backup issues Installation checklist Setting up rights Configuring service rights Backup data Hanging issues Common backup and restore errors Error 3201 - when performing a backup to a network share Full database backup file is larger than database size Error 3205 - Too many backup devices specified for backup or restore Error 4305 - an earlier transaction log backup is required Bringing a database that is in recovery or read-only mode online Using bulk-logged recovery model but transaction log backup is still large Error 14274 - unable to delete SQL Server Agent job