SQL Jobs running after disabled?

  • Hi,

    SQL Jobs running after disabled, what could be issue? where should be troubleshooting?

    I have done as below steps.

    1. Disabled the SQL jobs. -Right click Job-> disabled

    2. remove the schedule that jobs.

    3. exec sp_update_job @job_name= 'myjobname', @disabled = 0

    But still running jobs after done above steps. pl. suggestion me

    thanks

  • the job could be being executed from another job or some application code.

    Script out all your jobs and look for sp_start_job in the output and if necessary run profiler at the time the job runs and look for sp_start_job in the output.

    ---------------------------------------------------------------------

  • You mentioned you disabled the job but what does it do? Has it completed?

    Are there any errors in the logs when disabled it?

    ______________________________
    AJ Mendo | @SQLAJ

  • It could also be the job(s) are being run manually. What does the job log tell you?

  • Job disabled stage run manually, it was run with as below error...

    Executed as user: servername\ExpSQLAgtSvc. 16 percent processed. [SQLSTATE 01000] (Message 3211) 33 percent processed. [SQLSTATE 01000] (Message 3211) 49 percent processed. [SQLSTATE 01000] (Message 3211) 66 percent processed. [SQLSTATE 01000] (Message 3211) 75 percent processed. [SQLSTATE 01000] (Message 3211) 83 percent processed. [SQLSTATE 01000] (Message 3211) 93 percent processed. [SQLSTATE 01000] (Message 3211) Processed 688 pages for database 'EMSEvents', file 'EMSEvents_dat' on file 1. [SQLSTATE 01000] (Message 4035) Processed 32 pages for database 'EMSEvents', file 'EMSEventsIndex_dat' on file 1. [SQLSTATE 01000] (Message 4035) Processed 16 pages for database 'EMSEvents', file 'EMSTimeAndLocalTimeIdx_dat' on file 1. [SQLSTATE 01000] (Message 4035) Processed 16 pages for database 'EMSEvents', file 'EMSLocalDateAndTimeIdx_dat' on file 1. [SQLSTATE 01000] (Message 4035) Processed 16 pages for database 'EMSEvents', file 'EMSLocalDateAndTimeAndLocalTimeIdx_dat' on file 1. [SQLSTATE 01000] (Message 4035) 100 percent processed. [SQLSTATE 01000] (Message 3211) Processed 2 pages for database 'EMSEvents', file 'EMSEvents_log' on file 1. [SQLSTATE 01000] (Message 4035) BACKUP DATABASE successfully processed 770 pages in 2.352 seconds (2.554 MB/sec). [SQLSTATE 01000] (Message 3014) An error occurred in the Microsoft .NET Framework while trying to load assembly id 65536. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error: System.IO.FileLoadException: Could not load file or assembly emsevents, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An error relating to security occurred. (Exception from HRESULT: 0x8013150A) System.IO.FileLoadException: at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at System.Reflection.Assembly.Load(String assemblyString) [SQLSTATE 42000] (Error 10314). The step failed.

  • did you disable in maintenance plan. if you did't disable, disable it from maintenance plan also.

  • Look at your error. There appears to be a security issue.

    An error occurred in the Microsoft .NET Framework while trying to load assembly id 65536.

    The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE.

    Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error:

    System.IO.FileLoadException: Could not load file or assembly emsevents, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or

    one of its dependencies. An error relating to security occurred.

    Are you sure you disable the "Job" and not a "Step" in the job? I would suggest scripting out the job to a new window. Saving and then dropping the job. Then if another job is calling that one it will fail.

    ______________________________
    AJ Mendo | @SQLAJ

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply