01-13-2016, 01:31 PM
Hi Joeri,
Service accounts are/can be used in several linked systems and possibly syncs in authorisation can take some time. In general this is why you do not want to change service account passwords ; )
The service account for Scense is only used on the server-side, which is a good thing. Have you restarted the server (or IIS, or at least give the application pool a recycle)? This should solve it.
For Scense in version 10 there are now 2 databases, and corresponding systems (Scense engine, Live Profiles and *new-new* reporting). Possible some service still thinks it needs to use the old credentials? Same is for the database connectivity (however: you see items in the DB, so this should be ok).
Warning:
Be carefull to ever change the ODS password, as this one is used on the endpoints and it might need some reboots to be able to change this!
Good luck and please keep us informed if you found what triggered the issues (what you needed to reboot/restart to fix it).
Kind regards,
Michael Baars
Service accounts are/can be used in several linked systems and possibly syncs in authorisation can take some time. In general this is why you do not want to change service account passwords ; )
The service account for Scense is only used on the server-side, which is a good thing. Have you restarted the server (or IIS, or at least give the application pool a recycle)? This should solve it.
For Scense in version 10 there are now 2 databases, and corresponding systems (Scense engine, Live Profiles and *new-new* reporting). Possible some service still thinks it needs to use the old credentials? Same is for the database connectivity (however: you see items in the DB, so this should be ok).
Warning:
Be carefull to ever change the ODS password, as this one is used on the endpoints and it might need some reboots to be able to change this!
Good luck and please keep us informed if you found what triggered the issues (what you needed to reboot/restart to fix it).
Kind regards,
Michael Baars