"Access to path connection.dill is denied"

Help Studio
, ,
1

image
image989×609 124 KB

Hello, when I try to save dependencies upgrade, I get this error and I’m not sure as to why. Never come across this error , thoughts?

2

Hello @David_Hernandez, try some of these steps and see if it works out for you:

  1. Run UiPath Studio as Administrator: Right-click on the UiPath Studio shortcut and select “Run as administrator.” Running UiPath Studio with administrative privileges can sometimes resolve permission-related issues.
  2. Check Antivirus or Security Software: Your antivirus or security software might be blocking UiPath Studio from accessing or modifying certain files. Try temporarily disabling your antivirus or security software and see if you can save the dependencies upgrade. If it works, you may need to configure your security software to allow UiPath Studio.
  3. Check File/Folder Permissions: Ensure that the folder where your project is stored and the connection.dll file itself have the appropriate read and write permissions. You should have full control over the project folder and the DLL file.
  4. Check for Read-Only Files: Ensure that the connection.dll file is not marked as read-only. Right-click on the file, go to Properties, and make sure the “Read-only” checkbox is not selected.
  5. Check for File Locks: Another application or process might have locked the connection.dll file, preventing UiPath Studio from accessing it. Make sure the file is not open in any other application and that no other process is using it.
  6. Copy to a Different Location: If you’re still facing issues, try copying the project to a different location (e.g., your desktop) and see if you can save the dependencies upgrade there. Sometimes, issues with file permissions are specific to certain directories.
  7. Reinstall UiPath: If none of the above steps work, consider uninstalling and then reinstalling UiPath Studio. This can sometimes resolve issues related to corrupted installations.

Cheers! :slight_smile:

3

Thank you. Do you know the path of the connection.dll file? I can’t seem to find it within the project folder.

4
  1. Open File Explorer.
  2. Navigate to the C:\Program Files (x86)\UiPath\Studio directory if you’re using a 32-bit version of UiPath Studio, or C:\Program Files\UiPath\Studio if you’re using a 64-bit version.
  3. Inside this directory, you’ll find various subdirectories containing UiPath Studio components, including DLLs. Look for the connection.dll file within one of these subdirectories.

Keep in mind that manually interacting with or modifying system-level DLLs is typically not recommended, as it can lead to system instability or compatibility issues. The connection.dll file is managed by UiPath Studio itself, and you should focus on resolving any issues through UiPath Studio’s settings or by following the troubleshooting steps mentioned earlier.

Cheers!

5

Gotcha. Some more background information… we recently switched to the BitBucket repository. This issue seems to be coming up when we clone the project into Server X, do work, push/commit and then try to reclone it in server Y. Server Y has issues with the connect.dll, so I’m guessing Server X is still connected to it somehow.

6

This isn’t a solution. It’s a way to check if the issue is permission related. You shouldn’t just always run it as administrator.

1 Like
7

I have never used that but I asked some of my colleagues and they said this must be a good solution,try some of these steps:

  1. Clean Cloning: When you clone the project to Server Y, ensure that the cloning process is clean and there are no remnants of connections or configurations from Server X. You can do this by cloning the repository into a new directory on Server Y.
  2. Repository Configuration: Check the repository configuration settings within UiPath Studio. Ensure that the repository URL and credentials are correctly set up for Server Y. You can do this by going to Settings > Team > Git > Repository Settings in UiPath Studio.
  3. Local Repository Cleanup: In some cases, conflicts might arise from local cached data. You can try cleaning up the local repository cache on Server Y and then re-clone the project. You can do this by deleting the .git directory in your project folder and then running git clone again.
  4. Git Credential Manager: If you’re using Git as your version control system, ensure that any Git credential manager on Server X is not causing conflicts when cloning on Server Y. You might need to configure Git credentials separately on each server.
  5. Check for Remote Connections: Ensure that there are no remote connections set up in UiPath Studio on Server X that are causing conflicts when trying to clone on Server Y. You can check and manage remote connections in UiPath Studio’s settings.
  6. Authentication and Permissions: Verify that both Server X and Server Y have the necessary authentication and permissions to access the Bitbucket repository. Ensure that SSH keys, if used, are correctly configured on both servers.
  7. Network and Firewall: Confirm that there are no network or firewall restrictions preventing Server Y from accessing the Bitbucket repository. Check the network configuration on both servers.
  8. Bitbucket Configuration: Review your Bitbucket repository settings, especially access controls and permissions. Ensure that both servers have the appropriate access rights to clone and fetch from the repository.
  9. UiPath Studio Version: Ensure that both Server X and Server Y are using the same version of UiPath Studio and that it’s up to date. In some cases, compatibility issues might arise with older versions.
8

Exactly, but once you run it and see if this is the problem we can agree that we reach a solution.