locked
SQL Server 2019 - Unable to communicate with the runtime for 'R' script for request id:. Please check the requirements of 'R' runtime. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Environment Details:
    OS: Windows Server 2016
    SQL: SQL Server 2019 + CU5

    SQL Service and SQL Agent are running under AD Service Accounts
    Launchpad Service is running  under default account - NT Service\MSSQLLaunchpad
    SQL Service Account & NT Service\MSSQLLaunchpad are already added to local administrators group.

    While running below mention command script in SSMS, I am getting error as mention below. This command executes for 60 seconds every time and then throw same error.

    EXEC sp_execute_external_script
      @language =N'R',
      @script=N'print("Welcome to R in SQL Server")'
    GO

    Error:
    Unable to communicate with the runtime for 'R' script for request id: 3AB7AEB4-AB46-4AC7-9DE5-2B222F7AC003. Please check the requirements of 'R' runtime.

    Log details:
    ------------

    Error in SQL Server Error Log During SQL Service Start time:
    Resource governor reconfiguration encountered an issue (HRESULT code : 0x80040002, reason: Construction of Launchpad Connection failed), while sending active external resource pool ids to launchpad. This will not fail reconfigure.

    Error in SQL Server Error Log During above mention external script:
    Failed to retrieve the connection from satellite {3AB7AEB4-AB46-4AC7-9DE5-2B222F7AC003} after 60000 MilliSeconds. ErrorCode: 0x80040001

    Error in rlauncher log file:
    [Error] Process::TryTerminate failed with error code: 5

    Error in EXTLAUNCHERRORLOG:
    No Error
    Saturday, July 4, 2020 9:00 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    In my case all these protocols were enabled and I has restarted SQL Service and Launchpad services multiple times.

    Finally, I had resolve this issue after:

    uninstall all components of SQL Server 2019 & SQL Server Management Studio.

    Install SQL Server 2019. This time installed all SQL binaries in default location which is under C drive. earlier SQL Server setup was installed on E drive.


    Tuesday, July 7, 2020 3:28 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Prince Rastogi,

    Enable the TCP/IP protocol or Named Pipes protocole in your SSMC,and then restart your SQL Service.

    More helpful information: unable-to-communicate-with-the-runtime-for-r-script-in-sql-server, unable-to-communicate-with-the-runtime-for-r-script-in-sql-server-2017

    BR,

    MIAOYUXI

    Monday, July 6, 2020 3:00 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I'm following this case,is the issue solved?

    Is the reply helpful?

    You can "Mark As Answer" for the helpful reply,and this will benefit for others.

    BR,

    MIAOYUXI

    Tuesday, July 7, 2020 1:31 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    In my case all these protocols were enabled and I has restarted SQL Service and Launchpad services multiple times.

    Finally, I had resolve this issue after:

    uninstall all components of SQL Server 2019 & SQL Server Management Studio.

    Install SQL Server 2019. This time installed all SQL binaries in default location which is under C drive. earlier SQL Server setup was installed on E drive.


    Tuesday, July 7, 2020 3:28 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    OKAY.
    Uninstall and reinstall.
    Time-tested this approach, very easy to use!

    However I have fogotten!

    Wednesday, July 8, 2020 1:22 AM