Assets Discovery 7.1.0 fails to scan network

[Mariano]

So, I'm running Assets Discovery on a test VMware SLES server (same server as my test JSM DC), scan settings as per below:

So basically, just scan 10 test VMs in the LAN so I can export that data to a shared folder and upload to JSM.

But the scan is failing, debug logs show the following:

Funny thing is that I am not cancelling anything, just running `Discovery.exe` to trigger a scan.

Do the Assets Discovery files need to be owner by jira user or something like that? Why is my `App run cancelled by user` ?

Any pointers would be greatly appreciated as documentation does not mention this case and this feature seems a bit cryptic.

Thanks in advance!

[Mariano]

@Dorothea Linneweber maybe you can help me understand what's going on? Much appreciated! 😊

[Mariano]

I've noticed that the job quits exactly at 10 second mark.

[Dorothea Linneweber]

Hi @Mariano apologies to play hot potato, but I might suggest for you to please raise a support ticket so that our teams can assess your configurations and route to the best internal teams. https://support.atlassian.com/contact/#/ 

[Mariano]

I've also noticed that the job quits exactly at 10 second mark, any ideas @Volodymyr Batrukh @Volodymyr Batrukh ?

[Mariano]

Also, why is Assets Discovery trying to scan localhost if I specifically provided the IPs and credentials for /24?