Cannot Connect To Packages Feed (#1651)

News Knowledge Base
1

When accessing the packages page, processes page or libraries page in Orchestrator a #1651 error is thrown.

When accessing the packages page, processes page or libraries page in Orchestrator a #1651 error is generated.


This error is generated when there is an issue with location where Orchestrator stores packages.

Diagnosing the issue:

  1. Login to the Orchestrator Server as an Admin.
  2. Open a Run window and type “eventvwr” – This will open the Event Viewer.
  1. In the Event Viewer window, go to “Event Viewer (Local) -> Windows Logs->Application
  2. Click “Filter Current Log…” in the right “Actions” pane window.
  3. In the “Filter Current Log” dialog box, choose the Event Source: “Orchestrator”. Then select “OK”.
  1. Force the error to occur by trying to go to the Orchestrator page that caused the problem.
  2. In “Event Viewer” click “Refresh” in the “Actions” pane in the left menu.
  3. Check to see if a new “Warning” message was generated.
  4. If the following message was generated, go to the Fix File Permissions section. This error message indicates a permission issue.
UiPath.Orchestrator.Core.Exceptions.LocalizedException: Error code - 1651, Message - 'Cannot connect to packages feed, the Deployment Settings may be invalid.' ---> System.UnauthorizedAccessException: Access to the path 'C:\Program Files (x86)\UiPath\Orchestrator\Storage\...
  1. If one of the following errors is generated, go to the Fix Deployment URL. This error indicates that the URL used in the Deployment settings of Orchestrator are not valid.
  • UiPath.Orchestrator.Core.Exceptions.LocalizedException: Error code - 1651, Message - 'Cannot connect to packages feed, the Deployment Settings may be invalid.' ---> System.Net.WebException: The remote server returned an error: (404) Not Found.
  • UiPath.Orchestrator.Core.Exceptions.LocalizedException: Error code - 1651, Message - 'Cannot connect to packages feed, the Deployment Settings may be invalid.' ---> System.Net.WebException: The remote name could not be resolved: 'www.example.com'

Fixing File Permissions:
  1. If the Application Pool Identity that runs Orchestrator does not have read/write access to the folder in which it stores packages, this error will be encountered. The error message will give an indication of the folders with incorrect permissions.
  • For example, looking at the following error message: UiPath.Orchestrator.Core.Exceptions.LocalizedException: Error code - 1651, Message - 'Cannot connect to packages feed, the Deployment Settings may be invalid.' ---> System.UnauthorizedAccessException: Access to the path 'C:\Program Files (x86)\UiPath\Orchestrator\Storage\Orchestrator-0d3c0600-fe03-4e13-9da8-8a2437455101\Processes' is denied.
It can be seen that the folder with incorrect permissions is: 'C:\Program Files (x86)\UiPath\Orchestrator\Storage\Orchestrator-0d3c0600-fe03-4e13-9da8-8a2437455101\Processes’
  1. Depending on the setup, the permissions can usually be fixed by adjusting the permissions on one folder.
    • For Orchestrator instances that are using a Nuget.Repository.Type of “Legacy” change the permissions on the following folder: “C:\Program Files (x86)\UiPath\Orchestrator\NuGetPackages”
    • For Orchestrator instances that are using a Nuget.Repository.Type of “Composite” change the permissions on the following folder: “C:\Program Files (x86)\UiPath\Orchestrator\Storage”
    • For more info about Legacy and composite, see: v2020.4.x or lower, v2020.10.x or higher
  2. Open a Run window and type “inetmgr” to open IIS.
  3. Go to the Application pool settings.
  1. In the “Application Pools” window identify the App pool name used by Orchestrator (Usually it is “UiPath Orchestrator”). Remember this vale.
  2. Navigate to ““C:\Program Files (x86)\UiPath\Orchestrator”
  3. Right click the folder specified in step 2 and select “Properties”.
  4. Go to the “Security” tab and then select the “Edit” button.
  5. Modify the permissions so that the App Pool (“UiPath Orchestrator” by default) has the following permissions:
    • Read & execute
    • Write
    • Modify
    • Or Full Control
  6. It may be required to add the App Pool to the list of Users with access to the file location.
  7. Alternatively, if you installed Orchestrator with a Custom Account instead of using a built in App Pool Identity, you can add the Custom User the permissions mentioned above.
  8. The result should look something like:
  1. Validate that the Package, Processes and Library pages all work in Orchestrator.
    1. If Orchestrator application pool is run on a Custom Account, the Custom Account settings may need to be reset. To reset, select ApplicationPoolIdentity once, and re-configure the Custom Account settings.
  2. If the issue still occurs, open a support request with UiPath.

If the package folder is on a shared folder, Share permission has to be verified as well.
Open the folder's property on the share server if it is a Windows one, and open "Sharing" tab.
Click "Advanced Sharing" and then "Permissions"


Fix Invalid URL
  1. If Event Viewer showed a 404 error or a “name could not be resolved” error in relation to the package feed, it means there is a problem with the server represented by the package deployment URL or that the settings are incorrect.
  2. Open a Browser and go to the Orchestrator site.
  3. Login as an admin user.
  4. Go to the “Settings” page (accessed by click the upper right icon that usually displays a user’s initials).
  5. From the “Settings” click the Deployment tab.
  6. Look at the section “Packages->Deployment”. The value will be set to “External”.
  7. The first step is to verify that the deployment value should be set to “External”. Most instances of Orchestrator use an internal feed, so it is highly likely this value needs to be change to “Internal”.
  8. If the “External” setting is desired, then validate that the “Deployment URL” is correct.
  9. If the error was a “name could not be resolved” this means, there is an issue with DNS. A network admin should be able to help with the issue.
  10. If the error is a 404 error, it most likely means the deployment server did not respond or that the Orchestrator server is not authorized to write to the URL. In this case, contact the admin of the deployment server to verify that the Orchestrator has the correct access.
  11. If local system admins cannot resolve the issue, open a support request with UiPath.