Microsoft R Server / DeployR Documentation Errors RRS feed

  • General discussion

  • Thought I would share some clear errors in the Deploy R documentation I have come across to help others.

    I've installed onto two servers Microsoft R Server (from SQL Server 2016 ISO) + Deploy R (8.0.5).  Both installations followed the installation process currently documented on the Micrososft site at:

    One server was Windows Server 2012 R2, the other Windows Server 2016.

    The first issue is that the DeployR default node fails to start.  The status "Inactive" is shown in red for the default node on the landing page.  In the diagnostics the following message is seen:

    CHECKING: DeployR Script Execution
    Script execution failed

    Trying to run Rserve from the command prompt returns:

    R_HOME must be set in the environment or Registry

    The documentation errors are on the following page:

    Under the heading “Inactive Grid Node” it states this only happens on Windows 7.  It has occurred for me on both Windows Server 2012 R2 and Windows Server 2016.

    The documentation page states in the event of the above error, the environment variable R_HOME should be set to: C:\Program Files\Microsoft SQL Server\130\R_SERVER\bin\x64

    This is wrong.  If you set the env. variable to this, when attempting to run Rserve manually, the following error is encountered:
    “Unable to read base package”. 

    Further, when running the server normlly, the Repository Manager in DeployR is unable to run any RScripts and fails with:
    “Error in file(file, ifelse(append, "a", "w")) : cannot open the connection”

    The R documentation for R_HOME notes this folder contains: "bin", "doc", "etc", "include", "modules" and "share". 

    So, the correct path for the environment variable should be: C:\Program Files\Microsoft SQL Server\130\R_SERVER

    Once the above env. variable is added and the system rebooted, the default grid node starts up and repository manager functions again.

    Thursday, December 8, 2016 5:16 PM

All replies

  • Thanks for your report, Chris. The documentation has been updated. 



    Friday, December 9, 2016 2:45 PM