Unable To Publish Package On NAT Shared Drive

Fix for - Unable to Publish Package on NAT shared drive.

Error Message:

System.UnauthorizedAccessException: Access to the path '\\UKDC12_DATA\cbsuipath\Orchestrator-900e88e3-21e8-425e-8441-0261f5df2cd5\Processes\ROBOT.TO.VM.CONECTION.TEST' is denied.

at void System.IO.FileSystem.CreateDirectory(string fullPath, byte[] securityDescriptor)

at DirectoryInfo System.IO.Directory.CreateDirectory(string path)

at async Task UiPath.Storage.FileSystem.RawFileSystemStorageClient.WriteObjectAsync(StorageLocation location, Stream stream, CancellationToken cancellationToken) in /_/Storage/src/FileSystem/RawFileSystemStorageClient.cs:line 125

at async Task UiPath.Storage.Client.StorageClientExtensions.SafeWriteObjectAsync(IStorageClient storageClient, StorageLocation location, Stream stream, CancellationToken cancellationToken) in /_/Storage/src/Client/StorageClientExtensions.cs:line 37

at async Task

Steps to Check

  1. First of all make sure that in C:\Program Files (x86)\UiPath\Orchestrator\UiPath.Orchestrator.dll.config these lines are filled with data:

<!-- Storage -->

<add key="Storage.Type" value="FileSystem" />

<add key="Storage.Location" value="RootPath=.\Storage" /> ---" Change the Location as per you NAT drive Location"

After checking, adapting based on the requirements, and saved the UiPath.Orchestrator.dll.config file, restart the Orchestrator server from IIS.

  1. On the Orchestrator, try adding everyone in the group and provide full access to everyone in group. Add the Orchestrator user to the access Level.

  1. Check the identity, webhook and Orchestartor need to be run under the same user or create a new service account and add the same under same security group as application pool is not have the access under the share drive access.

22.jpg

If HAA 2 nodes are present, it is recommended to replicate the same steps on both the nodes.

NAT: When NAT is enabled on a network, a NAT IP address is automatically assigned to each VM on a connected network.

For example, if NAT is enabled on Network A and then Network A is connected to Network B, NAT IP addresses are assigned to the VMs connected to Network B. When Network A and B communicate, the VMs in Network B use the NAT IP addresses to send and receive traffic.

Note: One service account can be used on both the nodes in respect the same service account is present in same group as Orchestrator users.