This usually occurs when there's an ongoing scan in that network range or provided IP address, or the user does not have the appropriate permissions to run the scan (that is, the user doesn't own the conflicting scan).