- Check that the OC Scanner is running correctly.
- Check that the OC Scanner is scheduled correctly, by setting the scheduler configuration on the OC Scanner scan file level, in the OC Configurator. For each new OC Scanner, the OC Scanner must be run manually one time, so it can create the scheduled task on the given OC Scanner server.
- Ensure the OC Scanner is running with the correct privileges – typically this would be defined in the OC Configurator > Scan files > Specific scan file > Servers > Specific server entry > General tab, as the scheduler credentials are automatically taken from the given section (from the username/password field).
- Check that the OC Scanner has network connectivity to your OC Configurator API server. To check the correct network port used by the OC Configurator server, navigate to the IIS Manager on the OC Configurator server, and check the bindings on the OC Configurator website.
Note: The OC Scanners deliver their data to your OC Configurator server first, and then this data is forwarded to the OC Reporter server (in the Octopus Cloud, or on-premises depending on the deployment type). The data is not immediately imported, but automatically after a couple of hours. Manual data import can be initiated by navigating to the OC Reporter website > Data Import > Automation > Click on ‘Import X available files’.