Deleting a rule caused a missing object loop

Started by John C

John C

Deleting a rule caused a missing object loop   19 July 2016, 10:46

hi,

i just installed and started monitoring. with the usage screen open, i was allowed to delete a rule. this caused an endless loop of dialog box saying an object was missing. i had to use task manager to stop band manager.

i suggest an edit to force closing the usage window before allowing a rule to be removed.
SoftPerfect Support forum - Andrew avatar image

Re: Deleting a rule caused a missing object loop   19 July 2016, 12:22

Which usage screen did you have open? Could you perhaps attach some screen shots of how you got this error?
John C

Re: Deleting a rule caused a missing object loop   19 July 2016, 22:27

I setup a tcp rule and a udp rule. i then opened the usage report window. i then decided to use the rule template which combines tcp & udp in one rule. i did this by modifying the tcp only rule. this was reflected by a title change in the usage report window. i then removed the udp rule. at that point the error dialog popped up and i couldn't get past the dialog to close the app.
also, after canceling the app thru task manager, the app won't allow logon without a win10 restart.
SoftPerfect Support forum - Andrew avatar image

Re: Deleting a rule caused a missing object loop   19 July 2016, 22:58

I need to know which 'usage window' you opened please. There is one, two, three.
SoftPerfect Support forum - Andrew avatar image

Re: Deleting a rule caused a missing object loop   21 July 2016, 14:32

Thanks, fixed in the latest build.

Sometimes you can get the answer faster if you try the forum search and/or have a look at the software user manual to see if your question has already been answered.

Our forum rules are simple:

  • Be polite.
  • Do not spam.
  • If possible, check your spelling and grammar.

Author:

Subject

A brief and informative title for your message, approximately 4–8 words:

     

Spam prevention: please enter the following code in the input field below.

 ********   *******   ********        **  ********  
 **        **     **     **           **  **     ** 
 **        **     **     **           **  **     ** 
 ******     ********     **           **  ********  
 **               **     **     **    **  **        
 **        **     **     **     **    **  **        
 ********   *******      **      ******   **        

Message: