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 Jun 29, 2019. It is now read-only.
I created a new AzureML workspace in West Central US from new portal. I am trying to operationalize a Python script (that I am able to operationalize on South Central) and facing errors.
ValueError: Failed to publish function: Internal error. The error code has been logged. If you retry and see this error again, report the error code and the request ID to the online forum.
Set azureml.services._DEBUG = True to enable writing predictIris.req/predictIris.res files
I did pass the endpoint parameter in @services.publish() to the management endpoint of West Central US.
For what it is worth, there does seem to be one change in workspace auth token for this new workspace created through new portal. The token seems to be encoded (i.e has a == at the end. The older workspace where it is working does not have this encoding for the tokens. Not sure if there is some decoding I have to do before passing it in @services.publish(). BTW - I tried base64 decode on this token I see in studio and it does not seem to be an ASCII string.
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.
I created a new AzureML workspace in West Central US from new portal. I am trying to operationalize a Python script (that I am able to operationalize on South Central) and facing errors.
ValueError: Failed to publish function: Internal error. The error code has been logged. If you retry and see this error again, report the error code and the request ID to the online forum.
Set azureml.services._DEBUG = True to enable writing predictIris.req/predictIris.res files
I did pass the endpoint parameter in @services.publish() to the management endpoint of West Central US.
For what it is worth, there does seem to be one change in workspace auth token for this new workspace created through new portal. The token seems to be encoded (i.e has a == at the end. The older workspace where it is working does not have this encoding for the tokens. Not sure if there is some decoding I have to do before passing it in @services.publish(). BTW - I tried base64 decode on this token I see in studio and it does not seem to be an ASCII string.
The text was updated successfully, but these errors were encountered: