SQL 2005 Agent Configuration Problems

• Vendoran

  SSC Veteran

  Points: 217

  More actions

  April 26, 2006 at 10:09 am

  #114451

  Hello,

   

  I've got two problems when attempting to set up SQL Server 2005 Agent.  Any help on either of these would be greatly appreciated.

   

  1.) When I go into properties of SQL Server Agent and then to history.  I check the Automatically remove agent history checkbox and set the time delay, but it doesn't stay checked when I exit and look again.  Does anyone know how to fix this or even better the specific registry key I can change to force it?  I believe it is in HKLM\Software\Microsoft\Microsoft SQL Server\(Instance)\SQLServerAgent\

   

  2.) On SQL Server Agent properties in General I have changed the location of the log file so instead of D:\Program Files\Microsoft SQL Server\MSSQL\LOG\SQLAGENT.OUT it is E:\SQLLogs\SQLAGENT.OUT  However when I go through Management Studio to view them it says "Unicode File Expected", even though SQL Server is creating the files and automatically rolling them over (I do have Write OEM error log and include execution trace messages checked and am logging Errors, Warnings and Information). 

   

  Any help would be greatly appreciated.

   

  Thanks,

   

  Aaron Lowe

• May 1, 2006 at 8:00 am

  This was removed by the editor as SPAM

• peterhe

  SSChampion

  Points: 11469

  More actions

  May 2, 2006 at 7:43 am

  #635298

  1) This sounds a bug. The "Automatically remove agent history checkbox and set the time delay" is not set as an agent property. Check the set agent properties system SP in msdb, it does not have the property:

  CREATE PROCEDURE [dbo]

  .[sp_set_sqlagent_properties]

  @auto_start

  INT = NULL, -- 1 or 0

  -- Non-SQLDMO exposed properties

  @sqlserver_restart

  INT = NULL, -- 1 or 0

  @jobhistory_max_rows

  INT = NULL, -- No maximum = -1, otherwise must be > 1

  @jobhistory_max_rows_per_job

  INT = NULL, -- 1 to @jobhistory_max_rows

  @errorlog_file

  NVARCHAR(255) = NULL, -- Full drive\path\name of errorlog file

  @errorlogging_level

  INT = NULL, -- 1 = error, 2 = warning, 4 = information

  @error_recipient

  NVARCHAR(30) = NULL, -- Network address of error popup recipient

  @monitor_autostart

  INT = NULL, -- 1 or 0

  @local_host_server

  sysname = NULL, -- Alias of local host server

  @job_shutdown_timeout

  INT = NULL, -- 5 to 600 seconds

  @cmdexec_account

  VARBINARY(64) = NULL, -- CmdExec account information

  @regular_connections

  INT = NULL, -- obsolete

  @host_login_name

  sysname = NULL, -- obsolete

  @host_login_password

  VARBINARY(512) = NULL, -- obsolete

  @login_timeout

  INT = NULL, -- 5 to 45 (seconds)

  @idle_cpu_percent

  INT = NULL, -- 1 to 100

  @idle_cpu_duration

  INT = NULL, -- 20 to 86400 seconds

  @oem_errorlog

  INT = NULL, -- 1 or 0

  @sysadmin_only

  INT = NULL, -- not applicable to Yukon server, for backwards compatibility only

  @email_profile

  NVARCHAR(64) = NULL, -- Email profile name

  @email_save_in_sent_folder

  INT = NULL, -- 1 or 0

  @cpu_poller_enabled

  INT = NULL, -- 1 or 0

  @alert_replace_runtime_tokens

  INT = NULL -- 1 or 0

  AS

  ...

  Instead, SSMS generates the script

  EXEC msdb.dbo.sp_purge_jobhistory @oldest_date='a time'

  to purge the log.

  2) If you remove OEM checkbox, you should not have the error. The log file in OEM fomat does not accept unicode.