Unable to Publsih package when orchestrator is configured

Help
,
1

Scenario: Unable to publish project in Ui Path (Version 2016.2.6274) if orchestrator is configured

Steps to reproduce: Configure Orchestrator & trying to publish

Current Behavior: If orchestrator is connected then unable to publish

Expected Behavior:If orchestrator is connected allow to publish

Studio/Robot/Orchestrator Version: Ui Path (Version 2016.2.6274) Orchestrator Version Version 2016.2.6302

Last stable behavior: Not yet
Last stable version: 2016.1
OS Version: 64 bit
Others if Relevant: (workflow, logs, .net version, service pack, etc):

2

Hi,
could you please attach the snap shot of error .

1 Like
3

Hi,

After Publish it is showing exception as

Publishing the project has failed.
Error: The request was aborted:The request was canceled

4

@badita

5

@vikram Hi! After connecting the Robot to orchestrator, did you check the UiPath.settings file -
NuGetServerUrl parameter to be automatically configured with the URL of the NuGet location?

6

Hi,

yes i check tht too it is showing properly in settings file UiPath.settings (“NuGetServerUrl”: “http://OrchestratorURL/nuget”)

Please let me know , if anything else is required

1 Like
7

Can you publish locally? Or upload the package manually to orchestrator?

8

Hi,

It is allowing me to publish locally, but due to some privacy issue i am unable to upload that package on orchestrator. Is there have any other option?

9

Publishing the project has failed.

Error: Failed to process request. ‘The package size is too large. The feed owner may have to upgrade the MyGet subscription to resolve this issue.’.
The remote server returned an error: (413) The package size is too large. The feed owner may have to upgrade the MyGet subscription to resolve this issue…

System.Exception: Publishing the project has failed.

Error: Failed to process request. ‘The package size is too large. The feed owner may have to upgrade the MyGet subscription to resolve this issue.’.
The remote server returned an error: (413) The package size is too large. The feed owner may have to upgrade the MyGet subscription to resolve this issue… —> System.InvalidOperationException: Failed to process request. ‘The package size is too large. The feed owner may have to upgrade the MyGet subscription to resolve this issue.’.
The remote server returned an error: (413) The package size is too large. The feed owner may have to upgrade the MyGet subscription to resolve this issue… —> System.Net.WebException: The remote server returned an error: (413) The package size is too large. The feed owner may have to upgrade the MyGet subscription to resolve this issue…
at System.Net.HttpWebRequest.GetResponse()
at NuGet.RequestHelper.GetResponse()
at NuGet.HttpClient.GetResponse()
at NuGet.PackageServer.EnsureSuccessfulResponse(HttpClient client, Nullable1 expectedStatusCode) --- End of inner exception stack trace --- at NuGet.PackageServer.EnsureSuccessfulResponse(HttpClient client, Nullable1 expectedStatusCode)
at NuGet.PackageServer.PushPackageToServer(String apiKey, Func`1 packageStreamFactory, Int64 packageSize, Int32 timeout, Boolean disableBuffering)
at NuGet.PackageServer.PushPackage(String apiKey, IPackage package, Int64 packageSize, Int32 timeout, Boolean disableBuffering)
at UiPath.Project.Deploy.ProjectPackageManager.Push(WorkflowProjectPackage pack, Int32 timeout)
at UiPath.Project.Deploy.ProjectPackageManager.PackAndPublish(WorkflowProject project, Int32 timeoutMS)
at UiPath.Project.ProjectManager.Publish(Int32 timeoutMS)
at UiPath.Workflow.ViewModels.MainViewModel.PackAndPush()
— End of inner exception stack trace —

10

hi,
steps to publish a project,

11

hi,
pls follow this,