Accessing results of event viewer value query in task scheduler action












0















I'm trying to implement a scheduled task in Windows 10. The task is triggered by multiple events, I want to pass the event ID that triggered the task to the action.



So I have the following value query:



      <ValueQueries>
<Value name="eventID">Event/System/EventID</Value>
</ValueQueries>


And the arguments in the ExecAction:



<Arguments>--event $(eventID)</Arguments>


But when the task is triggered, I get an error code: 2147942409



Translating that to Hex is 0x80070009.



Windows error? "Storage control block address is invalid" ?



I don't understand what it's trying to tell me?



The task executes fine without the $(eventID) on the command line (just doesn't do anything useful).










share|improve this question



























    0















    I'm trying to implement a scheduled task in Windows 10. The task is triggered by multiple events, I want to pass the event ID that triggered the task to the action.



    So I have the following value query:



          <ValueQueries>
    <Value name="eventID">Event/System/EventID</Value>
    </ValueQueries>


    And the arguments in the ExecAction:



    <Arguments>--event $(eventID)</Arguments>


    But when the task is triggered, I get an error code: 2147942409



    Translating that to Hex is 0x80070009.



    Windows error? "Storage control block address is invalid" ?



    I don't understand what it's trying to tell me?



    The task executes fine without the $(eventID) on the command line (just doesn't do anything useful).










    share|improve this question

























      0












      0








      0








      I'm trying to implement a scheduled task in Windows 10. The task is triggered by multiple events, I want to pass the event ID that triggered the task to the action.



      So I have the following value query:



            <ValueQueries>
      <Value name="eventID">Event/System/EventID</Value>
      </ValueQueries>


      And the arguments in the ExecAction:



      <Arguments>--event $(eventID)</Arguments>


      But when the task is triggered, I get an error code: 2147942409



      Translating that to Hex is 0x80070009.



      Windows error? "Storage control block address is invalid" ?



      I don't understand what it's trying to tell me?



      The task executes fine without the $(eventID) on the command line (just doesn't do anything useful).










      share|improve this question














      I'm trying to implement a scheduled task in Windows 10. The task is triggered by multiple events, I want to pass the event ID that triggered the task to the action.



      So I have the following value query:



            <ValueQueries>
      <Value name="eventID">Event/System/EventID</Value>
      </ValueQueries>


      And the arguments in the ExecAction:



      <Arguments>--event $(eventID)</Arguments>


      But when the task is triggered, I get an error code: 2147942409



      Translating that to Hex is 0x80070009.



      Windows error? "Storage control block address is invalid" ?



      I don't understand what it's trying to tell me?



      The task executes fine without the $(eventID) on the command line (just doesn't do anything useful).







      xml windows task scheduler






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 22 '18 at 3:37









      mikbmikb

      405




      405
























          1 Answer
          1






          active

          oldest

          votes


















          0














          I found the answer, eventually - and been travelling a while, and not working on this project.



          The script actually asks the task scheduler to trigger on two events, and had a separate trigger definition for each event id in the trigger collection. That works. What doesn't work is using the same name attribute for the value query in each definition. That's what was generating the error - despite it being valid XML, I was effectively declaring the same variable twice, so the scheduler decided to punish me by throwing a meaningless error.



          The solution was to fold the two trigger definitions into one, which means only one value query is defined:



              <EventTrigger>
          <Enabled>true</Enabled>
          <Subscription>&lt;QueryList&gt;&lt;Query Id="0"&gt;&lt;Select Path="Microsoft-Windows-NetworkProfile/Operational"&gt;*[System[(EventID=10000) or (EventID=10001)]]&lt;/Select&gt;&lt;/Query&gt;&lt;/QueryList&gt;</Subscription>
          <ValueQueries>
          <Value name="eventID">Event/System/EventID</Value>
          </ValueQueries>
          </EventTrigger>


          All happy now, and prototype delivered to the client!






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53423532%2faccessing-results-of-event-viewer-value-query-in-task-scheduler-action%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            I found the answer, eventually - and been travelling a while, and not working on this project.



            The script actually asks the task scheduler to trigger on two events, and had a separate trigger definition for each event id in the trigger collection. That works. What doesn't work is using the same name attribute for the value query in each definition. That's what was generating the error - despite it being valid XML, I was effectively declaring the same variable twice, so the scheduler decided to punish me by throwing a meaningless error.



            The solution was to fold the two trigger definitions into one, which means only one value query is defined:



                <EventTrigger>
            <Enabled>true</Enabled>
            <Subscription>&lt;QueryList&gt;&lt;Query Id="0"&gt;&lt;Select Path="Microsoft-Windows-NetworkProfile/Operational"&gt;*[System[(EventID=10000) or (EventID=10001)]]&lt;/Select&gt;&lt;/Query&gt;&lt;/QueryList&gt;</Subscription>
            <ValueQueries>
            <Value name="eventID">Event/System/EventID</Value>
            </ValueQueries>
            </EventTrigger>


            All happy now, and prototype delivered to the client!






            share|improve this answer




























              0














              I found the answer, eventually - and been travelling a while, and not working on this project.



              The script actually asks the task scheduler to trigger on two events, and had a separate trigger definition for each event id in the trigger collection. That works. What doesn't work is using the same name attribute for the value query in each definition. That's what was generating the error - despite it being valid XML, I was effectively declaring the same variable twice, so the scheduler decided to punish me by throwing a meaningless error.



              The solution was to fold the two trigger definitions into one, which means only one value query is defined:



                  <EventTrigger>
              <Enabled>true</Enabled>
              <Subscription>&lt;QueryList&gt;&lt;Query Id="0"&gt;&lt;Select Path="Microsoft-Windows-NetworkProfile/Operational"&gt;*[System[(EventID=10000) or (EventID=10001)]]&lt;/Select&gt;&lt;/Query&gt;&lt;/QueryList&gt;</Subscription>
              <ValueQueries>
              <Value name="eventID">Event/System/EventID</Value>
              </ValueQueries>
              </EventTrigger>


              All happy now, and prototype delivered to the client!






              share|improve this answer


























                0












                0








                0







                I found the answer, eventually - and been travelling a while, and not working on this project.



                The script actually asks the task scheduler to trigger on two events, and had a separate trigger definition for each event id in the trigger collection. That works. What doesn't work is using the same name attribute for the value query in each definition. That's what was generating the error - despite it being valid XML, I was effectively declaring the same variable twice, so the scheduler decided to punish me by throwing a meaningless error.



                The solution was to fold the two trigger definitions into one, which means only one value query is defined:



                    <EventTrigger>
                <Enabled>true</Enabled>
                <Subscription>&lt;QueryList&gt;&lt;Query Id="0"&gt;&lt;Select Path="Microsoft-Windows-NetworkProfile/Operational"&gt;*[System[(EventID=10000) or (EventID=10001)]]&lt;/Select&gt;&lt;/Query&gt;&lt;/QueryList&gt;</Subscription>
                <ValueQueries>
                <Value name="eventID">Event/System/EventID</Value>
                </ValueQueries>
                </EventTrigger>


                All happy now, and prototype delivered to the client!






                share|improve this answer













                I found the answer, eventually - and been travelling a while, and not working on this project.



                The script actually asks the task scheduler to trigger on two events, and had a separate trigger definition for each event id in the trigger collection. That works. What doesn't work is using the same name attribute for the value query in each definition. That's what was generating the error - despite it being valid XML, I was effectively declaring the same variable twice, so the scheduler decided to punish me by throwing a meaningless error.



                The solution was to fold the two trigger definitions into one, which means only one value query is defined:



                    <EventTrigger>
                <Enabled>true</Enabled>
                <Subscription>&lt;QueryList&gt;&lt;Query Id="0"&gt;&lt;Select Path="Microsoft-Windows-NetworkProfile/Operational"&gt;*[System[(EventID=10000) or (EventID=10001)]]&lt;/Select&gt;&lt;/Query&gt;&lt;/QueryList&gt;</Subscription>
                <ValueQueries>
                <Value name="eventID">Event/System/EventID</Value>
                </ValueQueries>
                </EventTrigger>


                All happy now, and prototype delivered to the client!







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 27 '18 at 1:22









                mikbmikb

                405




                405
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53423532%2faccessing-results-of-event-viewer-value-query-in-task-scheduler-action%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

                    Alcedinidae

                    RAC Tourist Trophy