Connect to remote R Services (In-Database) #3361
Comments
Did workaround in #3315 (importing certificate or moving it to the trusted root) work for you? |
I did all steps, suggested by @karthiknadig and also moved cert to trusted root. But now I'm have the following error: [2017-04-04 10:19:54Z] <Microsoft.R.Host.Broker.Interpreters.InterpreterManager> (T): [2017-04-04 10:19:54Z] <Microsoft.R.Host.Broker.Interpreters.InterpreterManager> (W): [2017-04-04 10:19:54Z] <Microsoft.R.Host.Broker.Interpreters.InterpreterManager> (I): [2017-04-04 10:19:54Z] <Microsoft.AspNetCore.Hosting.Internal.WebHost> (D): [2017-04-04 10:19:55Z] <Microsoft.AspNetCore.Hosting.Internal.WebHost> (D): [2017-04-04 10:22:54Z] <Microsoft.AspNetCore.Server.Kestrel> (D): [2017-04-04 10:23:00Z] <Microsoft.AspNetCore.Server.Kestrel> (E): |
Can you check if Network Service has access to the certificate? |
@karthiknadig thanks, it helped me! I did copy cert back to personal, add permission to Network Service and copy back to trusted root. Now problem looks like so in VS: Connecting to R Workspace failed. But I have the R Services (In-Database) from Sql Server 2016 installed |
Due to the way SQL installs R it is sometimes difficult to locate. However, you can configure intepreters manually in the broker config file. In
|
Thanks, it helped! |
Can I connect to remote R Services (In-Database) from my notebook with rtools for visual studio? Log Microsoft.R.Host.Broker is below. It seems like R Services (In-Database) from Sql Server 2016 is not supported. Does it so?
[2017-03-29 11:44:12Z] <Microsoft.R.Host.Broker.Startup.Program> (I):
Certificate issued by CN="FQDN"
[2017-03-29 11:44:12Z] <Microsoft.R.Host.Broker.Startup.Program> (I):
Certificate issued to CN="FQDN"
[2017-03-29 11:44:16Z] <Microsoft.R.Host.Broker.Interpreters.InterpreterManager> (T):
Auto-detecting R ...
[2017-03-29 11:44:16Z] <Microsoft.R.Host.Broker.Interpreters.InterpreterManager> (W):
No compatible R interpreters found
[2017-03-29 11:44:16Z] <Microsoft.R.Host.Broker.Interpreters.InterpreterManager> (I):
0 interpreters configured:
[2017-03-29 11:44:16Z] <Microsoft.AspNetCore.Hosting.Internal.WebHost> (D):
Hosting starting
[2017-03-29 11:44:17Z] <Microsoft.AspNetCore.Hosting.Internal.WebHost> (D):
Hosting started
[2017-03-29 11:48:23Z] <Microsoft.AspNetCore.Server.Kestrel> (D):
Connection id "0HL3MG1DQUR4G" started.
[2017-03-29 11:48:23Z] <Microsoft.AspNetCore.Server.Kestrel> (E):
ConnectionFilter.OnConnection
Exception: System.AggregateException: One or more errors occurred. ---> System.NotSupportedException: The server mode SSL must use a certificate with the associated private key.
at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)
at System.Threading.Tasks.TaskFactory
1.FromAsyncCoreLogic(IAsyncResult iar, Func
2 endFunction, Action1 endAction, Task
1 promise, Boolean requiresSynchronization)--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Server.Kestrel.Https.HttpsConnectionFilter.d__3.MoveNext()
--- End of inner exception stack trace ---
---> (Inner Exception #0) System.NotSupportedException: The server mode SSL must use a certificate with the associated private key.
at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)
at System.Threading.Tasks.TaskFactory
1.FromAsyncCoreLogic(IAsyncResult iar, Func
2 endFunction, Action1 endAction, Task
1 promise, Boolean requiresSynchronization)--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Server.Kestrel.Https.HttpsConnectionFilter.d__3.MoveNext()<---
The text was updated successfully, but these errors were encountered: