After a successful installation, a user may see that collections are not working as expected. 

If your collections are not running as expected, check the following:

1. Check dbo.Servers:
   1. Have you added SQL Server instances to the dbo.Servers table?
   2. Are those instances marked IsActive = 1?
   3. Is the CollectionZone set to 0 (or, if you have set up Collection Zones, to the appropriate number)?
   4. Check that in the dbo.Servers table, no Port is set to 1433; if a server uses the default port, set Port = NULL.
   5. ​If you have entered more active servers into dbo.Servers than your license covers, all collections will stop. Review the number of servers your license covers, and reduce the number of active servers.
2. Check schedules: It’s possible that some of the collectors simply aren’t scheduled to begin this soon, and/or that the servers in dbo.Servers are ServiceLevel = Silver or Bronze (those collections kick off less often). For a reasonably accurate schedule of collections, see the Automatic Collections and Alerts article on our help center.
3. Check on key collectors: Some collections depend on other, key collections. You can, if you like, manually kick off these key collections; follow the instructions in the Quick Start section "Optional: Jump Start Your Collectors".
4. Check the license: It's possible that your license has expired, or - more rarely - experienced a hiccup. On the repository server:
   1. Open a PowerShell window.
   2. Navigate to c:\MinionByMidnightDBA\Collector
   3. Run the command .\license.exe run. If this returns 1, your license is still active.
   4. If it returns 0, your license has expired or "hiccuped". Run the command .\license.exe install, and repeat step 3 above. If the result is still 0, Support@MidnightDBA.com