When starting 2.0-beta2 for the first time, without having the unlimited crypto policy files installed, the startup procedure will error out, but not before writing an empty keystore file. Even after correcting the issue, this empty file will prevent the server from starting up correctly ever again.
The logged error message confused me, and I had to encounter it once more before I realized what to do to fix the problem. It ought to be possible to handle this scenario more gracefully, no?