You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 28, 2019. It is now read-only.
Hi, after successfully publishing a web service using the publishWebService AzureML function, consuming always result in error below ("cannot open the connection").
I had an identical error using the ml studio execute R script module, which I solved by switching to R Open 3.4.4. question is: how to specify r open 3.4.4 on publishWebService?
tried using like this, but same error, didnt work:
Module execution encountered an internal library error.
The following error occurred during evaluation of R script: R_tryEval: return error: Error in read.dcf(file = tmpf) : cannot open the connection
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, after successfully publishing a web service using the publishWebService AzureML function, consuming always result in error below ("cannot open the connection").
I had an identical error using the ml studio execute R script module, which I solved by switching to R Open 3.4.4.
question is: how to specify r open 3.4.4 on publishWebService?
tried using like this, but same error, didnt work:
options(repos = c(CRAN = "https://mran.revolutionanalytics.com/snapshot/2019-01-01"))
ep <- publishWebService(ws,
fun=xxxxxxx, name="my_model",
inputSchema = df,
data.frame = TRUE,
packages=c("quanteda"),
version="3.4.4")
Error
Error: AzureML returns error code:
HTTP status code : 400
AzureML error code : LibraryExecutionError
Module execution encountered an internal library error.
The following error occurred during evaluation of R script: R_tryEval: return error: Error in read.dcf(file = tmpf) : cannot open the connection
The text was updated successfully, but these errors were encountered: