Hi @ssabo,
Are you running a load balanced infrastructure with multiple app servers? If so, this may be that you are connecting to one of the app servers that does not have the replications running on it (only one server should need the replications running). In later versions of FSM this service was moved to reside in the database so you would no longer get this display issue.
If you are only on one app server then the next step would be to check the service itself on the server to see if it is running and this is a display issue or if it is actually stopped. If it is stopped I would suggest checking the logs on the app server to see if there is an error or exception indicating that this service was then stopped by the server. It could be that the service was deemed to be running to often or failing to often and the server stopped it for that reason.
Kind regards,
Lee Pinchbeck