Endpoint Protection

 View Only
  • 1.  Console error "(minimum <= value <= maximum) is false"

    Posted Apr 03, 2013 07:08 PM

    Hi,

    I recently upgraded my SEPM from 12.1 to 12.1.2 and now I cannot edit my LiveUpdate Settings policy.  When I try to edit the policy I recieve a a console error stating "(minimum <= value <= maximum) is false".  I can edit all of my other policies just fine.  Has anyone else run into this or have any suggestions on how to fix?

    Thank you in advance.



  • 2.  RE: Console error "(minimum <= value <= maximum) is false"

    Posted Apr 03, 2013 07:10 PM

    Can you show a screenshot of the error message? Never seen that before.



  • 3.  RE: Console error "(minimum <= value <= maximum) is false"

    Posted Apr 03, 2013 07:18 PM

    Error.jpg

     



  • 4.  RE: Console error "(minimum <= value <= maximum) is false"
    Best Answer

    Posted Apr 03, 2013 07:54 PM

    Certainly a new one for me. Have you tried deleting and creating a new policy?



  • 5.  RE: Console error "(minimum <= value <= maximum) is false"

    Posted Apr 03, 2013 11:05 PM

    Try this

     

    1. Click Start Control Panel.
    2. Double-click Java.
    3. On the General tab, under Temporary Internet Files, click Settings.
    4. Click Delete Files.
    5. Make sure all boxes are checked, and click OK.
    6. Click OK to close the dialog boxes.


  • 6.  RE: Console error "(minimum <= value <= maximum) is false"

    Posted Apr 04, 2013 01:20 AM

    i agree with Rafreeg.



  • 7.  RE: Console error "(minimum <= value <= maximum) is false"

    Posted Apr 04, 2013 02:17 AM

    High posiblity that policy has been corrupt.

    Could you run the dbvalidaor and confirm if the validation passes.

    Below are the steps to run the Database Validation tool:

    Open a command prompt
    Start > Run > Type: “cmd” (without quotes) > click OK
    Change the directory to:
    <Drive>:\Program Files\Symantec\Symantec Endpoint Protection Manager\Tools
    Type the following command to run the batch file:

    dbvalidator.bat

    One of the following messages is displayed at the command prompt to tell you whether the database has passed or failed validation:

    a)      If the database is valid, you see the following message:

    Database validation passed.

    b)      If the database is invalid, you see the following message:

    Database validation failed. Please check the log file for more details.

    copy of the output this tool creates it can be located in the following location with the filename dbvalidator.log:

    \Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs
     



  • 8.  RE: Console error "(minimum <= value <= maximum) is false"

    Posted Apr 04, 2013 03:24 AM

    Hi

    Delete all files from Liveupdate from Caching and observe the same..

    Regards

     



  • 9.  RE: Console error "(minimum <= value <= maximum) is false"

    Posted Apr 04, 2013 12:07 PM

    Thank you to all who replied.  Here is an update on the issue:

    Brian81- I can successfully create a new policy and edit that new policy after.  I have not tried to delete my current LiveUpdate policy however.

    Rafeeq- I followed your instructions to delete the temp internet files in the Java console, but I am still getting the same error after.

    la ripper- I followed your instructions to run dbvalidator and in the output log states that the database validation has passed.

    SameerU- I opened the LiveUpdate console from the control panel and removed all files from the update cache tab.  After doing so, I am still getting the same console error message when trying to edit my current LiveUpdate policy.

    At this point, I am going to try and just re-create the LiveUpdate policy on both my main and replication partners and see what happens.  I will report back in a few days with an update.



  • 10.  RE: Console error "(minimum <= value <= maximum) is false"

    Posted Apr 10, 2013 02:55 PM

    Deleting and re-creating a new LiveUpdate policy seems to have done the trick.  I have been running a week now on the re-created policy without any issues.