Ms Sql Error 14274
up Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 2005 » Administering » Error 14274: sp_add_jobserver Cannot Add, Update, Or Delete... Error 14274: Cannot Add, Update, Or Delete Job.... Rate sp_delete_job Topic Display Mode Topic Options Author Message JuanBobJuanBob Posted Friday, September 15, 2006 4:03 PM SSC Veteran Group: General Forum sp_dropserver Members Last Login: Saturday, December 8, 2012 7:21 PM Points: 234, Visits: 269 I am receiving this error on some of my jobs. I can verify that the SQL Server was renamed from SERVERX to SERVER1. I have read the MS article below, but I would like to not have to go through the rename if at all possible. I found the steps below on another forum and wanted to verify whether this will work. The server is Win 2003 Server, SQL 2000.Thanks!http://support.microsoft.com/default.aspx?scid=kb;en-us;2816421. Script out all of the jobs. 2. Update the job source by:USE MSDBUPDATE sysjobsSET originating_server = 'New_Server_Name'3. Rename the jobs to be deleted.4. Delete the jobs. 5. Add back the jobs by running the script generated from step 1. Post #309106 EugeneZ-162636EugeneZ-162636 Posted Saturday, September 16, 2006 1:36 PM Valued Member Group: General Forum Members Last Login: Monday, January 4, 2016 9:43 AM Points: 66, Visits: 562 USE MSDBUPDATE sysjobsSET originating_server = 'New_Server_Name'will do it, no need to delete jobs (unless you'd like)Just review code - DTS packs connections, etc Post #309170 JuanBobJuanBob Posted Monday, September 18, 2006 2:51 PM SSC Veteran Group: General Forum Members Last Login: Saturday, December 8, 2012 7:21 PM Points: 234, Visits: 269 That's great, thanks so much for your post! Post #309471 Cris DBACris DBA Posted Tuesday, September 19, 2006 2:44 PM SSC Veteran Group: General Forum Members Last Login: Tuesday, May 12, 2015 3:59 PM Points: 215, Visits: 34 Had similar problem when our system administrator renamed the production db server (win 2003) without telling me (the DBA).Check out BOL:sp_dropserver sp_addserver Although SqlServer (2000) continues running quite happily - SqlServer Agent got very confused - it carried on running all the scheduled backups etc. but I could not edit any of them (or stop, start, re-schedule them) when logged in as BUILTIN/Adinistrator.Changing the server name at NT admin leve
add, update, or delete a job (or its steps or schedules) that originated from an MSX server. The job was not saved. Reason: SQL Server 2000 supports multi-instances, the originating_server field contains the instance name in http://www.sqlservercentral.com/Forums/Topic309106-146-1.aspx the format server\instance. Even for the default instance of the server, the actual server name is used instead of (local). After the Windows server is renamed, these jobs still reference the original server name and may not be updated or http://jaminquimby.com/servers/93-sql/110-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 deleted by the process from the new server name. It’s a known problem with SQL2000 SP3. Fix --Verify Server Name SELECT @@servername If SQL name is not correct run. -- if no sp_dropserver <'nameReturned'> -- and then sp_addserver <'correctServername'> , 'local' Print 'Your server name has now been changed, restart SQL Service so changes will take effect.' If SQL name is correct run. --check originating_server column SELECT * FROM msdb..sysjobs --if not USE msdb GO DECLARE @server sysname SET @server = CAST(SERVERPROPERTY('ServerName')AS sysname) UPDATE sysjobs SET originating_server = @server WHERE originating_server = '
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 http://www.sqlbackuprestore.com/error14274.htm 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 http://www.sql.ru/forum/10729/error-14274-problemy-s-job 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 ms sql 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 ms sql error 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 Error messages when restoring from different versions of SQL Server. Pending vdi error codes Restore speed details Help, my transaction log file is huge! Mirror or log ship What When you attempt to edit or delete a SQL Server Agent job, you receive the following error: Error 14274: Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server. and you do not have MSX or TSX servers set up. Why This is a known issue as reported here. The recommended approach is to rename the server to its original name, script out your jobs, rename the server back again, and recreate your jobs. There is a f
) [new] Олег Member Откуда: Сообщений: 38 При удалении или изменении Job появляется ошибка "Cannot add,update,Delete a Job that originated from an MSX Server". Как можно изменить job или удалить. Подскажите что такое MSX Server и как избавится от ошибки, и если это возможно, подскажите почему появилась ошибка. 7 авг 02, 08:06 [44179] Ответить | Цитировать Сообщить модератору Re: Error 14274 (Проблемы с Job ) [new] MarchCat Member Откуда: Из Сибири. Сообщений: 1401 Error 14274 - Из BOL - Only a system administrator can view tasks owned by others. 7 авг 02, 08:13 [44181] Ответить | Цитировать Сообщить модератору Re: Error 14274 (Проблемы с Job ) [new] Dikobrazz Member Откуда: Владивосток Сообщений: 81 У меня такое было после переименования сервера (сразу после перехода с SQL Server 6.5). Вылечить удалось только изменением поля originating_server в msdb..sysjobs на новое имя сервера 7 авг 02, 08:44 [44188] Ответить | Цитировать Сообщить модератору Re: Error 14274 (Проблемы с Job ) [new] Олег Member Откуда: Сообщений: 38 БОЛЬШОЕ СПАСИБО Dikobrazz, это как раз то что надо. 7 авг 02, 09:05 [44189] Ответить | Цитировать Сообщить модератору Re: Error 14274 (Проблемы с Job ) [new] Blizzard Guest Спасибо, ребята! Я тоже решила проблему с вашей помощью! 6 июл 03, 20:45 [252490] Ответить | Цитировать Сообщить модератору Между сообщениями интервал более 1 года. Re: Error 14274 (Проблемы с Job ) [new] GiANiC Member Откуда: Сообщений: 2 DikobrazzУ меня такое было после переименования сервера (сразу после перехода с SQL Server 6.5). Вылечить удалось только изменением поля originating_server в msdb..sysjobs на новое имя сервераПодскажите пожал-та как это сделать пошагово! 3 фев 07, 05:40 [3734851] Ответить | Цитировать Сообщить модератору Re: Error 14274 (Проблемы с Job ) [new] tpg Member Откуда: Novosibirsk Сообщений: 23904 GiANiC DikobrazzУ меня такое было после переименования сервера (сразу после перехода с SQL Server 6.5). Вылечить удалось только изменением поля originating_server в msdb..sysjobs на новое имя сервераПодскажите пожал-та как это сделать пошагово!А вы сами то как пробовали? Там вроде ничего военного нет - всё лехко