Review us!
I've setup a stand alone windows 2008 R2 server (not on a domain). I've installed M-Files v11 (2015) and given a few users remote client access via https. There are no issues using regular vault objects. I just can't get my Report to display. I've followed all instructions in the getting started guide "M-Files Reporting - Getting Started Guide.PDF". I'm using SQL Express 2014 with reporting services.
Since the server is not on a domain, and the M-Files users are not local server accounts, I am using a "Specific Identity" in the the "Specify Report Access Identity" settings of the report setup in M-Files Admin. The specific identity is a local server account which has access to load the SQL report.
As a test outside of M-Files, on the remote workstation I can enter the https report URL directly into my browser. A pop up appears asking me for credentials. I supply the same credentials I used in "Specific Identity" and the report loads. However, when I use the same report URL in the remote M-Files client the report tries to load for a couple seconds and then displays "The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version". My feeling is that M-Files is not passing on the appropriate credentials to load the report even though I have supplied them with my Specific Identity.
(As a side note, the M-Files Client installed right on the server also cannot see the report. Same error.)
Has anyone else experienced an issue with the "Specify Report Access Identity"? Or is anyone actually using it successfully on a non-domain server?
Thanks.
