This documentation is archived and is not being maintained.

Troubleshooting Multiserver Jobs That Use Proxies

New: 14 April 2006

Distributed jobs whose steps are associated with a proxy run under the context of the proxy account on the target server. If job steps that use proxy accounts fail when downloaded from the master server, check the error_message column in the sysdownloadlist table in the msdb database for the following error messages:

  • "The job step requires a proxy account, however proxy matching is disabled on the target server."
    To resolve this error, set the \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.<n>\SQLServerAgent\AllowDownloadedJobsToMatchProxyName registry subkey to 1 (true). By default, this subkey is set to 0 (false). The value of MSSQL.<n> is the instance name; for example, MSSQL.1 or MSSQL.3.
  • "Proxy not found."
    To resolve this error, make sure a proxy account exists on the target server with the same name as the master server proxy account under which the job step runs.
ms366347.Caution(en-US,SQL.90).gifCaution:
Incorrectly editing the registry can severely damage your system. Before making changes to the registry, we recommend that you back up any valued data on the computer.

Show: