[Version Control] Xlink Check-in Fails Across Different Repositories
Under Audit
Unity 2022.3.x - Unity 2023.2.x
Published Mon, Mar 16
Users encounter a 'repository couldn’t be found' error when attempting to check in changes or create an Xlink between repositories hosted on different servers using Unity Version Control.
An issue has been reported with Unity Version Control (version 11.0.16.8420). The problem occurs when attempting to check in pending changes or create an Xlink between two repositories (A and B) that are hosted on different servers. Despite having administrative rights for both repositories, users encounter the error message: "The specified repository couldn’t be found: .". This error manifests consistently, whether the operation is initiated from the graphical user interface (GUI) or the command line. Other users with similar administrative access to both repositories also encounter this issue when performing Xlink related operations.
- Verify server connectivity and network reachability between the client machine and both repository servers.
- Ensure the repository paths or URLs configured for the Xlink are accurate and accessible.
- Check firewall settings and network configurations to confirm they are not blocking communication with the repository servers.
Editor's Note:
Related Posts Haven't quite found a solution to your problem? We think these posts might help you.
Content inspired by a Unity discussion post.