01-30-2017 12:12 AM
After upgrading M.app Enterprise to the latest version we are getting the below error message on all web pages (Management, Studio, Apps):
Usage statistics cannot be synchronized, because the service is not running or lost connectivity.
Any help getting rid of the message would be much appreciated.
Solved! Go to Solution.
01-30-2017 12:26 AM
never mind I managed to fix it! I manually restarted the 'M.app Service' and logged out and back in to the, Management, Studio and Apps page this cleared the message.
09-27-2017 07:20 AM
Had the same error few minutes ago, after I rebooted my server.
I found out that my "M.App Service" did not start - although it's defined as "automatically".
So I followed your hint an started the service manually - works fine now.
01-14-2018 06:15 AM
I have the same error.
I installed Mapp Enterpries 16.1 for the first time.
In my case the Mapp service is started, still it seems the application is not able to communicate.
I tried restarting and rebooting. Didn't help.
09-28-2018 07:09 AM
Apparently i have had the same problem. Even after installing 16.5 it didn't go away. I guess i'll live with it since my set-up is for demos. But i'd be a little bit happier if it went away.
10-01-2018 10:35 PM
Have you done the checks on the Warehouse user? E.g. if the password has changed or the name is wrong in the services the M.App Service as well as the Tile Service won't start.
If the sync can be done, all used hours gets away from your license package.
10-01-2018 11:20 PM
The M.App Service and the Tile Service are running just fine. At one point the password for the warehouse user was changed and both services restarted. That could be the issue but am not sure how it affects the synchronization service since everything else is working.
10-01-2018 11:26 PM
Have you tried to publish something after the password change? You can just see it there, if the Tile Service is really running and working.
10-01-2018 11:39 PM
I see. Maybe you try to stop and start the service once again + putting in again the password for the Warehouse user in the Services.msc.
Then you also have to logout and login again in the Studio.