The batch file for starting a MID Server ("start.bat", which then calls "mid.bat start") will always attempt to create a new service for the service name given in the wrapper-override.conf file, if it doesn't already exist. This code does not first check if there is already a existing Windows Service with a different service name for the same installation agent folder.
Due to customer mis-configurations, this commonly causes multiple Windows Services existing for the same agent folder, and both services may even be running simultaneously. This results in a number of symptoms, including running the same jobs multiple times.
A likely scenario for this would be when a customer manually upgrades a MID Server that has become corrupted or failed to upgrade, and forgets to preserve the original wrapper-overrides.conf file created by the installer. If this is overwritten by the file from the full zip file, it will end up with the default service name snc_mid. Often a "snc_mid" and a "snc_mid_<MID Server Name>" service pair are seen.
In this case, the creation of the additional service may happen some time later, perhaps during an auto-upgrade, if the MID Server had not been started using the batch files in the meantime.
Steps to Reproduce
- Install a MID Server using the installer, and start it
- Edit the agent/conf/wrapper-override.conf file, to change the value of wrapper.name parameter, perhaps to the default 'snc_mid' windows service name
- Run start.bat
You will see you now have 2 Windows Services both with the same display name, both running for the same MID Server installation folder, and may see various other symptoms listed in KB0743043
This issue is under review.
To repair you MID Server installation after experiencing this problem, please refer to KB0743043.
Related Problem: PRB1330396