agreed.
Which is why these forums are great.
I experienced the same issue reported as above and the following fixed my issue:
Set user <Data Protector user used for services> with the following privilege inside System Local Policies (secpol.msc > Local Policies > User Rights Assignments):
"Act as part of operating system"
Also…. Change “replace process level token” again in Local Polices!
Then omnisv –stop, omnisv –start.