1 2 Previous Next 20 Replies Latest reply on Jun 14, 2019 5:22 AM by Andrey Gabriel Go to original post
      • 15. Re: "Check OS", OR-step fails since 12.8
        Patrick Halet

        Marvin,

         

        I reviewed the logs provided in the case and it works as expected to me.

         

        An assignment for rule Test Registry Verification is received

         

        OperationalRules                 D   [8184]  Updating rule Test Registry Verification/7ADF552B37416805B4D4F1CDF3436445

         

        So the verification phase starts, and failed

         

        2019/06/10 07:44:38 Test Registry Verification      I   [8084]  Verification Phase: Step 0: registrycheck.chl starting

        2019/06/10 07:44:39 Test Registry Verification      ERR [8084]  Verification Phase: Step 0: registrycheck.chl failed with error : Named Variable = 16299, Expected Value = 17763

         

        Then the verificationphase is performed again every 2 minutes:

         

        07:46:39 Test Registry Verification      I   [8084]  Verification Phase: Step 0: registrycheck.chl starting

        2019/06/10 07:46:39 Test Registry Verification      ERR [8084]  Verification Phase: Step 0: registrycheck.chl failed with error : Named Variable = 16299, Expected Value = 17763

        2019/06/10 07:48:39 Test Registry Verification      I   [8084]  Verification Phase: Step 0: registrycheck.chl starting

        2019/06/10 07:48:39 Test Registry Verification      ERR [8084]  Verification Phase: Step 0: registrycheck.chl failed with error : Named Variable = 16299, Expected Value = 17763

        2019/06/10 07:50:39 Test Registry Verification      I   [8084]  Verification Phase: Step 0: registrycheck.chl starting

        2019/06/10 07:50:39 Test Registry Verification      ERR [8084]  Verification Phase: Step 0: registrycheck.chl failed with error : Named Variable = 16299, Expected Value = 17763

        2019/06/10 07:52:39 Test Registry Verification      I   [8084]  Verification Phase: Step 0: registrycheck.chl starting

        2019/06/10 07:52:39 Test Registry Verification      ERR [8084]  Verification Phase: Step 0: registrycheck.chl failed with error : Named Variable = 16299, Expected Value = 17763

        2019/06/10 07:54:39 Test Registry Verification      I   [8084]  Verification Phase: Step 0: registrycheck.chl starting

        2019/06/10 07:54:39 Test Registry Verification      ERR [8084]  Verification Phase: Step 0: registrycheck.chl failed with error : Named Variable = 16299, Expected Value = 17763

        2019/06/10 07:56:39 Test Registry Verification      I   [8084]  Verification Phase: Step 0: registrycheck.chl starting

        2019/06/10 07:56:39 Test Registry Verification      ERR [8084]  Verification Phase: Step 0: registrycheck.chl failed with error : Named Variable = 16299, Expected Value = 17763

         

        an new assigment is received for this rule (with 'Do not verify' set for this step)

         

        2019/06/10 07:57:47 OperationalRules                 D   [8184]  Updating rule Test Registry Verification/7ADF552B37416805B4D4F1CDF3436445

        ...

        2019/06/10 07:58:39 OperationalRules                 D   [8084]  Check for missing scripts for rule 'Test Registry Verification' (7ADF552B37416805B4D4F1CDF3436445)

        2019/06/10 07:58:39 OperationalRules                 D   [8084]  All needed scripts are available for rule 'Test Registry Verification' (7ADF552B37416805B4D4F1CDF3436445)

        2019/06/10 07:58:39 OperationalRules                 D   [8084]  Start verification phase for rule 'Test Registry Verification' (7ADF552B37416805B4D4F1CDF3436445)

        2019/06/10 07:58:39 OperationalRules                 I   [8084]  Verification phase for rule 'Test Registry Verification'

        2019/06/10 07:58:39 OperationalRules                 I   [8084]  Set RunPhase for rule Test Registry Verification

        2019/06/10 07:58:39 OperationalRules                 I   [8084]  Reset steps status for rule Test Registry Verification

        2019/06/10 07:58:39 OperationalRules                 D   [8084]  Verification phase is OK for rule 'Test Registry Verification' (7ADF552B37416805B4D4F1CDF3436445)

        2019/06/10 07:58:39 OperationalRules                 D   [8084]  Check for missing packages for rule 'Test Registry Verification' (7ADF552B37416805B4D4F1CDF3436445)

        2019/06/10 07:58:39 OperationalRules                 D   [8084]  All needed parts of the OpRule 'Test Registry Verification' are present

        2019/06/10 07:58:39 OperationalRules                 D   [8084]  Dependencies check phase started for rule 'Test Registry Verification' (7ADF552B37416805B4D4F1CDF3436445)

        2019/06/10 07:58:39 OperationalRules                 D   [8084]  Dependencies check phase is OK for rule 'Test Registry Verification' (7ADF552B37416805B4D4F1CDF3436445)

        2019/06/10 07:58:39 OperationalRules                 D   [8084]  Creating Timer for OpRule 'Test Registry Verification' (7ADF552B37416805B4D4F1CDF3436445)

        ...

         

        Now the timer is created, meaning that the rule will be executed:

        2019/06/10 07:58:39 Timer                            I   [8084]  Activating 'OperationalRules_Test Registry Verification_7ADF552B37416805B4D4F1CDF3436445' (immediate)

        2019/06/10 07:58:39 Timer                            I   [8084]  Scheduling 'OperationalRules_Test Registry Verification_7ADF552B37416805B4D4F1CDF3436445' for execution (when: now, eta: 2019/06/10 07:58:39)

        2019/06/10 07:58:39 Timer                            I   [10416] Executing entry 'OperationalRules_Test Registry Verification_7ADF552B37416805B4D4F1CDF3436445' (calling OpRuleProcess)

        2019/06/10 07:58:39 OperationalRules                 I   [10416] Rule execution is queued for rule Test Registry Verification <7ADF552B37416805B4D4F1CDF3436445>

         

         

        Defect DRZKZ-2382 - Workflow is not always correctly handled for verification steps is fixed in both 12.7.00.003 and 12.8.

        2 of 2 people found this helpful
        • 16. Re: "Check OS", OR-step fails since 12.8
          Philipp Ernicke

          Thank you Marvin for pushing this thread.

          • 17. Re: "Check OS", OR-step fails since 12.8
            Marvin Schumacher

            Thank you Patrick for the confirmation. 

            • 18. Re: "Check OS", OR-step fails since 12.8
              Andrey Gabriel

              Same here

               

              Setting the workflow as Yes or No as the same effect

               

              and this for:

               

              • detectfile.chl ("Check for File")
              • checkoperatingsystem2.chl ("Check Operating System")
              • registrycheck.chl ("Registry Key Verification")

               

              I had to corrected the and set to 'Do Not Verify' to not be failed

              https://gitlab.unige.ch/prods/SolutionsUtilisateurs/computer/uploads/6e578831383ee47c6d4616ee62b4c4b0/image.png

               

              I used some SQL to correct it directly in base

              • 19. Re: "Check OS", OR-step fails since 12.8
                Marvin Schumacher

                Andrey,

                 

                Can you share the SQL command you used to correct this in the database?

                 

                Cheers,

                 

                Marvin

                • 20. Re: "Check OS", OR-step fails since 12.8
                  Andrey Gabriel

                  Bonjour Marvin,

                   

                  Sure, here some bits to chew, but I feel I did not catched all stepid's that it bellongs to the problem

                   

                  To find

                  select *

                  FROM OPRULESTEPS

                  WHERE

                  VERIFICATIONACTION = '_DB_STEPACTION_VERIFSTOPONERROR_FAILED_'

                  and (

                  --detectfile.chl

                  steptypeid = 1021

                  --registrycheck.chl

                  or steptypeid = 1133

                  or steptypeid = 1315

                  or steptypeid = 1329

                  or steptypeid = 1460

                  )

                  ;

                   

                  To modify

                  UPDATE OPRULESTEPS
                  SET VERIFICATIONACTION = '_DB_STEPACTION_VERIFNONE_'
                  WHERE
                  VERIFICATIONACTION = '_DB_STEPACTION_VERIFSTOPONERROR_FAILED_'

                  and (
                  --detectfile.chl
                  steptypeid = 1021
                  --registrycheck.chl
                  or steptypeid = 1133

                  or steptypeid = 1315

                  or steptypeid = 1329

                  or steptypeid = 1460
                  )
                  ;


                  For me it did
                  Did 251 changes … in 0.15 sec … not to bad

                   

                  best regards

                  1 of 1 people found this helpful
                  1 2 Previous Next