asked
SQL Server R Services
Can anyone assist with the following Post-Installation Server Configuration in SQL Server R Services![alt text][1] [1]: /storage/temp/3280-screen-shot-2016-03-11-at-134835.png
You have some good answers below. This web site runs by you voting and marking the best answers. For each helpful answer below, indicate this by clicking on the thumbs up symbol next to those answers. If any one answer lead to a solution, indicate this by clicking on the check mark next to that answer. This helps indicate your solution for anyone else with the same question.
R is still under development. You're most likely to get an answer on Connect (
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?category=sqlserver). I'm pretty sure the developers will be keeping an eye on questions there.
I don't Think this is an issue with the R Services. The error message rather indicates some NetBIOS/AD-problems. I'm taking a wild guess here that the name RDATAWAREHOUSE can't be found. Depending on your infrastructure setup, there are a number of things you could try. 1) If RDATAWAREHOUSE is the name of the computer hosting the SQL Server instance, and you are running the post installation scripts from Another computer: I'm thinking the NetBIOS name can't be resolved. If that's the case, you could try with the full DNS name of the host RDATAWAREHOUSE instead. 2) If you are running the post installation scripts locally on the machine hosting SQL Server, and SQL Server is running as the default instance, you can ommit the INSTANCE-parameter to registerRext.exe. 3) If you are running the post installation scripts locally on the machine hosting SQL Server, and the SQL Server instance is a named instance named RDATAWAREHOUSE, the parameter should be /INSTANCE:.\RDATAWAREHOUSE If neither of the above fits your setup, please provide some more details about: - From where are you running the post installation script - Where is the SQL Server instance installed (computer in the same Active Directory or not, name of the instance etc).
Many thanks Magnus, i managed to solve the issue through a Microsoft SQL Server 2016 forum. The problem was that the Workstation services were not running
19 People are following this question.
