Hi Guillaume,
The above error is almost certainly due to your SECURITY Configuration settings. You could retry this a couple ways:
1. Try running the Admin Command prompt as another user (One that has command permissions)
2. You could edit your SECURITY Configuration and add an extra entry to give permission to a specific user for COMMANDS
3. You could try running the command from a command file in the Windows Client as per below screenshot. (Doing it this way also gives an advanced option where you can type in a specific user to run it as)
Note: Listing out all dbs (Running and not running) is built into Prognosis Self Monitoring V2.x. I know ScottB offered you this solution some time back (V1.x) and I believe you never did install it. Maybe this new need might tweak your interest in this solution? (It's a support freebie we will install and train you on).
- See https://online.prognosis.com/forum/us-ask-the-experts/prognosis-self-monitoring/