A MID Server issues record for "User X with mid_server role not associated with a MID Server. No login attempts within reporting period." is likely to be created between creating the User and before installing the MID Server.
In Quebec Patch 1
- Create a new user in the instance, and add the mid_server role
- Intend to install a MID Server within the next hour or so, but don't just yet
- After a short while (which will depend on when the MIDUserConnectivity sysauto-script runs), a MID Server Issues record will be created for the following:
"User X with mid_server role not associated with a MID Server. No login attempts within reporting period."- Install a MID Server using that user
- The issues record remains until the MIDUserConnectivity sysauto-script runs again.
There is no issue.
This is the normal order in which the MID Server user is to be created beforehand and then the install is done, as per the docs.
The issue record does get automatically cleared once the MID Servers are installed, but the MIDUserConnectivity job that creates and clears this runs only every 4 hours, and so there time when this error can cause confusion