I had a similar problem. It was caused by the username that the epolicy orchestrator was using to access the sql database having the password changed. run cfgnaims and change the username pword domain to a valid one.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.