Announcement

Collapse
No announcement yet.

Policy "Applied Failed"

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Policy "Applied Failed"

    1. What is your Company Name? DaGint Computer Support
    2. What is your email? dagint@gmail.com
    3. If it is related with Endpoints, Device OS details: Endpoints, Windows 7 Pro/Windows 10 Pro. Admin Console running Windows 7 Pro
    4. Time Stamp of the problem 11/15/2015
    5. What you did: Tried to apply policy to device. Tried 2 different policies all return "Apply Failed"
    6. What actually happened or you actually saw: Selected apply and nothing really happened within a couple seconds refreshed MMC and Status "Apply failed" was seen.
    7. What you expected to happen or see: Expected to see policy apply successfully or give me some more information as to why it was unable to apply. Applying a policy has never worked for me yet.
    8. Whether you can make the problem happen again, and if so exact steps to make it happen: Yes, repeatable. I've tried this on multiple computers/devices with no success.
    9. Any other information (eg your guess regarding the cause, with reasons): Seems like there might be something wrong with the platform or the agent installation.



    Logs from the MMC Console:
    [15.11.2015 11:41:57:4157|UTC-5|INFO|Tid:4476|LN:323|policy_controller.cpp|FCT:Q PolicyController::OnDispatchMessage]Success
    [15.11.2015 11:41:57:4157|UTC-5|INFO|Tid:4476|LN:366|policy_controller.cpp|FCT:Q PolicyController::OnDispatchMessage]Success
    [15.11.2015 11:41:57:4157|UTC-5|INFO|Tid:4476|LN:280|policy_controller.cpp|FCT:Q PolicyController::OnDispatchMessage]Success
    [15.11.2015 11:41:57:4157|UTC-5|INFO|Tid:4476|LN:366|policy_controller.cpp|FCT:Q PolicyController::OnDispatchMessage]Success
    [15.11.2015 11:41:57:4157|UTC-5|INFO|Tid:4476|LN:286|policy_controller.cpp|FCT:Q PolicyController::OnDispatchMessage]Success
    [15.11.2015 11:41:57:4157|UTC-5|INFO|Tid:4476|LN:366|policy_controller.cpp|FCT:Q PolicyController::OnDispatchMessage]Success
    [15.11.2015 11:42:06:426|UTC-5|INFO|Tid:4476|LN:1968|policy_controller.cpp|FCT: QPolicyController::OnSelectCaAlertResponse]Success
    [15.11.2015 11:42:06:426|UTC-5|INFO|Tid:4476|LN:310|policy_controller.cpp|FCT:Q PolicyController::OnDispatchMessage]Success
    [15.11.2015 11:42:06:426|UTC-5|INFO|Tid:4476|LN:366|policy_controller.cpp|FCT:Q PolicyController::OnDispatchMessage]Success
    [15.11.2015 11:42:09:429|UTC-5|INFO|Tid:4476|LN:304|policy_controller.cpp|FCT:Q PolicyController::OnDispatchMessage]Success
    [15.11.2015 11:42:09:429|UTC-5|INFO|Tid:4476|LN:366|policy_controller.cpp|FCT:Q PolicyController::OnDispatchMessage]Success
    [15.11.2015 11:42:09:429|UTC-5|INFO|Tid:4476|LN:286|policy_controller.cpp|FCT:Q PolicyController::OnDispatchMessage]Success
    [15.11.2015 11:42:09:429|UTC-5|INFO|Tid:4476|LN:366|policy_controller.cpp|FCT:Q PolicyController::OnDispatchMessage]Success
    [15.11.2015 11:42:15:4215|UTC-5|INFO|Tid:4476|LN:1968|policy_controller.cpp|FCT: QPolicyController::OnSelectCaAlertResponse]Success
    [15.11.2015 11:42:15:4215|UTC-5|INFO|Tid:4476|LN:310|policy_controller.cpp|FCT:Q PolicyController::OnDispatchMessage]Success
    [15.11.2015 11:42:15:4215|UTC-5|INFO|Tid:4476|LN:366|policy_controller.cpp|FCT:Q PolicyController::OnDispatchMessage]Success
    [15.11.2015 11:42:15:4215|UTC-5|INFO|Tid:4476|LN:304|policy_controller.cpp|FCT:Q PolicyController::OnDispatchMessage]Success
    [15.11.2015 11:42:15:4215|UTC-5|INFO|Tid:4476|LN:366|policy_controller.cpp|FCT:Q PolicyController::OnDispatchMessage]Success
    [15.11.2015 11:42:15:4215|UTC-5|INFO|Tid:4476|LN:286|policy_controller.cpp|FCT:Q PolicyController::OnDispatchMessage]Success
    [15.11.2015 11:42:15:4215|UTC-5|INFO|Tid:4476|LN:366|policy_controller.cpp|FCT:Q PolicyController::OnDispatchMessage]Success

    Logs From the Agent(happens to be the same machine as the MMC):
    [15.11.2015 11:41:57:4157|UTC-5|ERROR|Tid:1396|LN:132|cdynamiccomponentlibrary.c pp|FCT:CDynamicComponentLibrary::Load]Unsuccessful (1)
    [15.11.2015 11:41:57:4157|UTC-5|ERROR|Tid:1396|LN:132|cdynamiccomponentlibrary.c pp|FCT:CDynamicComponentLibrary::Load]Unsuccessful (1)
    [15.11.2015 11:41:58:4158|UTC-5|ERROR|Tid:1396|LN:132|cdynamiccomponentlibrary.c pp|FCT:CDynamicComponentLibrary::Load]Unsuccessful (1)
    [15.11.2015 11:41:58:4158|UTC-5|ERROR|Tid:1396|LN:1313|ccomponentmanager.cpp|FCT :CComponentManager::Unmarshal]FileNotFound (16)
    [15.11.2015 11:41:58:4158|UTC-5|INFO|Tid:1396|LN:690|downloadmgr.cpp|FCT:CDownlo adMgr::getNetworkTimeout]Temp folder: C
    [15.11.2015 11:41:58:4158|UTC-5|ERROR|Tid:1396|LN:1313|ccomponentmanager.cpp|FCT :CComponentManager::Unmarshal]FileNotFound (16)
    [15.11.2015 11:41:58:4158|UTC-5|ERROR|Tid:1396|LN:1428|ccomponentmanager.cpp|FCT :CComponentManager:ownloadAndUnmarshal]FileNotFound (16)
    [15.11.2015 11:41:58:4158|UTC-5|ERROR|Tid:1396|LN:1838|ccomponentmanager.cpp|FCT :CComponentManager::BuildManifestWithDependencyTre e]FileNotFound (16)
    [15.11.2015 11:41:58:4158|UTC-5|ERROR|Tid:1396|LN:2277|ccomponentmanager.cpp|FCT :CComponentManager::LoadComponent]FileNotFound (16)
    [15.11.2015 11:41:58:4158|UTC-5|ERROR|Tid:1380|LN:3050|listener.cpp|FCT:CCSPMCon trollerListner::OnLoadComponent]FileNotFound (16)

    I would be happy to supply any additional information to help get to the bottom of this.

  • #2
    Hello,
    Thank you for the feedback, we will analyse the logs and get back to you on the matter!

    Comment


    • #3
      Hello,
      Related to the same issue, just to make sure, you're mentioning that the issue occurs on the same machine which has the RMM Console installed on?
      If that is the case then please email us the logs from two locations:

      * For console Logs:
      1. Navigate to: C\Program Files (x86)\COMODO\RMM Administration Console or to C\Program Files\COMODO\RMM Administration Console
      2. Edit dbg_config.ini: change Level=7 to Level=15
      3. Wait for the issue to reproduce (stop and re-apply the Policy) and then collect Logs from: C:\Program Files (x86)\COMODO\RMM Administration Console\logs or C:\Program Files\COMODO\RMM Administration Console\logs

      * For agent Logs:
      1. Navigate to: C\Program Files (x86)\COMODO\Rmm Agent Service or to C\Program Files\COMODO\Rmm Agent Service
      2. Edit dbg_config.ini: change Level=7 to Level=15
      3. Wait for the issue to reproduce (stop and re-apply the Policy) and then collect Logs from: C:\Program Files (x86)\COMODO\Rmm Agent Service\logs or C:\Program Files\COMODO\Rmm Agent Service\logs

      Please email these logs to c1-support@comodo.com with the same mention as this post and we will get back to you with news once the analysis completes.

      Comment


      • #4
        I found for me the issue is related to a specific monitor in my policy. The "Disk Health Monitor" and I configured it twice once with a value of 12 and once with a value of 24. In both cases when applying the Disk Health Monitor I get this "Apply Failed". Removing this one monitor I'm able to successfully apply the policy.

        Comment


        • #5
          Is there a way to modify a Policy rather than deleting an d recreating a policy? Would seem like a simple request.

          Comment


          • #6
            Hello dagint ,

            If you want to edit a policy, you can select it and use the "Create from" option. You will be able to add add / remove monitors and rules - after saving the changes the old policy will still be available.

            Comment


            • #7
              Hi,

              I'm having the same problem but i need the Disk Health monitor so not willing to remove it.

              Comment


              • #8
                Marveltec regarding these issues, please provide the same logs as above, and send them to c1-support@comodo.com, so we can have them analyzed. Thank you

                Comment


                • #9
                  I need it as well but missing that one monitor is better than having no monitors at all.

                  Comment


                  • #10
                    The issue with applying a policy that includes the Disk Health Monitor should be fixed now. Please let us know if everything is ok now.

                    Comment


                    • #11
                      I confirmed the Policy will apply successfully now with the "Disk Health Monitor". Thanks for the prompt resolution.

                      Comment

                      Working...
                      X