This could be an issue with your drm-config.xml file, the file that stores the DRM configuration information defined in the DRM Console. If a drm-config.xml was restored from an old backup or copied from another machine, this could well be the issue.
In this case, you can run the DRM Console to update the file and correct it. You may see a one-time error reported when the DRM Console starts up, but the Console app should correct the file automatically after reporting the error to the user.
If this does not resolve your issue, review the Windows App Event Log, to determine which DRM Server process(es) are also reporting this error (to narrow down any other potential issues with a config file for one of the DRM Server executables). I am guessing this error was observed in just the DRM Batch client, but related Event Log should also be present in the App Event Log.
*** An additional note, if your issue proves to be the one above, you may need re-enter passwords on your defined Database Connections for defined DRM Apps. Try just re-running the DRM Console and re-saving the config initially, but be aware this may be a required additional step, re-entering the DB passwords after the updated encryption has been applied to the stored drm-config.xml file.
Edited by: 680314 on Jan 19, 2013 11:52 AM