I'm in the process of testing the restore process for portal users using 1 Click Restore functionality in Enterprise Manager. Select the file, click restore and I get a 'MethodNotFoundException' with a stack showing 'at Jayrock.JsonRpc.JsonRpcDispatcher.ParseRequest(JsonReader input)'.
Tried both Restore > Overwrite and Restore > Keep.
Not finding much on the forum or web with this particular issue. My immediate thought is something to do with permissions, but I could be way off
I'm having the same problem with v9 U1. Only difference is that I'm clicking 'Download' instead of restore. I'll wait and see the outcome of this before logging a ticket myself, so please post back if you find an easy fix.
The files I'm trying to retrieve (for testing) are owned by the user logged into Veeam Enterprise Manager, so it's probably not source file-system permissions, if that's what you mean.
Complete Stack: at Jayrock.JsonRpc.JsonRpcDispatcher.ParseRequest(JsonReader input)
Browsers: Chrome 49.0.2623.87 m / IE 11.0.9600.18230 (on different computers)
Browser OSs: Win 8.1 / 2008 R2 Std (both fully updated)
Veeam Server & Enterprise Manager OS: 2008 R2 Std (fully updated)
I get the same error if I use Download too. The only reason I thought permissions was that I was trying to restore a text file in the C:\Windows folder on the guest. Like I said, it was a SWAG Support have asked for the SVC.VeeamBES.log which I've uploaded, just waiting on a response.
Well, the error turned out to be quite straightforward. I assumed that the same settings that allow for 1 Click FLR from the Veeam console would work the same in BEM, but this is not the case. If guest file system indexing is not enabled, then you get the error we are discussing. I enabled it, configured the correct guest credentials (I'm not worred about VIX access, just RPC) and ran a backup.
BEM lets me now do the restore completely. Happy days.
OP's case was resolved by enabling indexing and using another user account for this operation. I would still suggest to contact our support team to confirm if you're experiencing the same issue or not.