Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. Visual Basic
  4. how to check if the scheduled task ran successfully on a remote computer with vb.net

how to check if the scheduled task ran successfully on a remote computer with vb.net

Scheduled Pinned Locked Moved Visual Basic
questioncsharptutorial
6 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    MagicGirL83
    wrote on last edited by
    #1

    is there any log files generated with scheduled task? and how can i access it remotely with vb.net? thanks

    D 1 Reply Last reply
    0
    • M MagicGirL83

      is there any log files generated with scheduled task? and how can i access it remotely with vb.net? thanks

      D Offline
      D Offline
      Dave Kreskowiak
      wrote on last edited by
      #2

      The log is kept in a simple text file at C:\WINDOWS\SchedLgU.Txt You can get to it via normal file methods using a UNC path: \\machinename\C$\WINDOWS\SchedLgU.Txt That is, of course, if the target machine is in the same domain as your machine. Authentication to the target machine may become an issue if your not running in a domain environment. You'll have to come up with your own code to parse up the log file into a suitable data structure. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

      M 1 Reply Last reply
      0
      • D Dave Kreskowiak

        The log is kept in a simple text file at C:\WINDOWS\SchedLgU.Txt You can get to it via normal file methods using a UNC path: \\machinename\C$\WINDOWS\SchedLgU.Txt That is, of course, if the target machine is in the same domain as your machine. Authentication to the target machine may become an issue if your not running in a domain environment. You'll have to come up with your own code to parse up the log file into a suitable data structure. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

        M Offline
        M Offline
        MagicGirL83
        wrote on last edited by
        #3

        thanks.. what if the scheduled task didn't run at all? would it still be on the log file?

        D 1 Reply Last reply
        0
        • M MagicGirL83

          thanks.. what if the scheduled task didn't run at all? would it still be on the log file?

          D Offline
          D Offline
          Dave Kreskowiak
          wrote on last edited by
          #4

          Read through the log file to understand it. The log will show that the job was launched, any error that were encountered launching the job, and the jobs return code, if any. If no attempt was ever made to launch the job, then it won't show in the log. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

          M 1 Reply Last reply
          0
          • D Dave Kreskowiak

            Read through the log file to understand it. The log will show that the job was launched, any error that were encountered launching the job, and the jobs return code, if any. If no attempt was ever made to launch the job, then it won't show in the log. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

            M Offline
            M Offline
            MagicGirL83
            wrote on last edited by
            #5

            thanks.. yeah.. i've scanned throught the log and i traced a task that supposed to be run at a given time but it didn't show on the log.. so how can i monitor it? i mean how can i know that the task didn't attempted to start or run at all?

            D 1 Reply Last reply
            0
            • M MagicGirL83

              thanks.. yeah.. i've scanned throught the log and i traced a task that supposed to be run at a given time but it didn't show on the log.. so how can i monitor it? i mean how can i know that the task didn't attempted to start or run at all?

              D Offline
              D Offline
              Dave Kreskowiak
              wrote on last edited by
              #6

              That should be obvious! :confused: If you're monitor already knows the Task Name and it doesn't show up in the log, well, what do you think didn't happen? RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

              1 Reply Last reply
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • World
              • Users
              • Groups