• State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 25 subscribers
  • Views 5855 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Discovery errors when editing

steve.depeet
over 6 years ago

Hi,

It seems we are not able to edit existing discovery jobs or to create new discovery jobs...
We receive a different error when trying to adapt the schedule then when we try to edit the scope or other settings.

Every time we try to edit the schedule we end up with the error:

 

 

When we try to edit the settings, we get:

Since it worried me that the db is not reacheable (all roles including db server is installed on the same machine), I had a look at the permissions (which should not have changed) and they seem to be OK...
I still have a feeling that this is got to do with permission problems but I can't seem to find any... Anyone has any ideas...?

Thanks in advance,
Steve.

Parents
  • 0 over 6 years ago
    Hi,

    Thanks for your reply but I seem to have found the problem.
    We were running into a disk space issue where the db file was not able to autogrow...
    I was able to add some storage and now the problem is gone.

    However I have two other questions since I'm a new to this product...:

    Can we cleanup the db because I think there is a lot of old data...?

    We had split out our NTFS discoveries per drive to avoid a discovery task that would run for days but we can only view the discovered data from our last discovery task? Is that normal behaviour?

    Regards,
    Steve.
Reply
  • 0 over 6 years ago
    Hi,

    Thanks for your reply but I seem to have found the problem.
    We were running into a disk space issue where the db file was not able to autogrow...
    I was able to add some storage and now the problem is gone.

    However I have two other questions since I'm a new to this product...:

    Can we cleanup the db because I think there is a lot of old data...?

    We had split out our NTFS discoveries per drive to avoid a discovery task that would run for days but we can only view the discovered data from our last discovery task? Is that normal behaviour?

    Regards,
    Steve.
Children
No Data