BUG: You receive an "Error 14269" error message when you try to modify the SQL Server Agent job if the combination of the computer name and the instance name is more than 30 characters in SQL Server 2000 (908243)


The information in this article applies to:

  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
BUG #: 472192 (SQL Server 8.0) SQL Server 8.0:472192

SYMPTOMS

In Microsoft SQL Server 2000, you identify a named instance by using a combination of the computer name and the instance name that is specified as computername\instancename. If the combination of the computer name and the instance name is more than 30 characters, you can create a new SQL Server Agent job. Additionally, the SQL Server Agent job runs successfully. However, if the combination of the computer name and the instance name is more than 30 characters, you cannot modify the SQL Server Agent job. When you try to modify the SQL Server Agent job, you receive the following error message:

Error 14269: Job 'YourJob' is already targeted at server
'yourcomputername\yourinstancename'. The job was not saved.
Note In this error message, YourJob is a placeholder for the name of the SQL Server Agent job, and yourcomputername\yourinstancename is a placeholder for the combination of the computer name and the instance name.

CAUSE

This issue occurs because the sp_add_jobserver stored procedure cannot run correctly.

In SQL Server, the computer name and the instance name are stored as the nvarchar (30) data type column in several system tables. Alternatively, the computer name and the instance name are defined as input parameters that have the nvarchar (30) data type for several stored procedures. These stored procedures are needed to modify the SQL Server Agent job. If the combination of the computer name and the instance name is more than 30 characters, the sp_add_jobserver stored procedure cannot run correctly.

WORKAROUND

To work around this issue, use one of the following methods:
  • Reinstall SQL Server, and make sure that the combination of the computer name and the instance name is fewer than 30 characters.
  • If you must use a combination of the computer name and the instance name that is more than 30 characters, delete the SQL Server Agent job. Then, re-create the SQL Server Agent job, and include the changes that you want to make.

    Note If the SQL Server Agent job is not a maintenance plan, you can follow these steps:
    1. Generate a SQL script file for the SQL Server Agent job.
    2. Modify the SQL script in the file to include the changes that you want to make.
    3. Run the SQL script to re-create the SQL Server Agent job.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

REFERENCES

For more information, see the following topics in SQL Server 2000 Books Online:
  • How to create a job (Enterprise Manager)
  • How to create a job (Transact-SQL)
  • sp_add_job
Modification Type:MajorLast Reviewed:10/31/2005
Keywords:kbbug KB908243 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.