‎28-11-2017 11:08 AM
‎30-11-2017 06:37 PM
Hi Andrea,
Ideally yes, you should perform this on all your repositories (including SystemDB) for the enviornment in question.
Let me know if this fixes the issue for you or not.
David
‎30-11-2017 04:27 PM
Hi David,
thanks for your reply.
A question, this cleaning ,do I have to do it on the SystemDB?
Because I have to enable the scheduler on a different scheme from the system.
Andrea
‎29-11-2017 06:35 PM - edited ‎29-11-2017 06:36 PM
Hi Andrea,
Im not sure if you've had a chance to work with Support yet but i saw this post and wanted to chime in as i have just encountered this error recently. Have you run a RDBMS cleanup recently? If not i would recommend running it in Administration as shown in the attached image. I just worked a case where this ended up being the solution for that exact error with the Scheduler service.
Regards,
David
‎29-11-2017 12:36 PM
Hello Jerome,
thanks for you reply.
I turned the case to the support because I keep seeing the error.
Regards
Andrea
‎28-11-2017 06:42 PM
Hello
Check that SSP service is started
Check that scheduler is started (status 'running') in Administration, Scheduler control panel. see image