Oftentimes this issue is due to permissions or write access to the repository as per the following solution: https://support.quest.com/SolutionDetail.aspx?id=SOL76689
If the permisons and write access are correct, other things that can cause this issue is the IP and DNS settings.
In one instance, the customer experienced a power failure that seems to have caused the IP for the vRanger machine on which the repository resided to change. A ping by name reported IP 169.x.x.x when10.x.x.x was expected. Also, trying to update the repository through vRanger failed.
Once the DNS settings were corrected, the vRanger machine was rebooted and the correct IP address was assigned back to the vRanger machine. When it came back up, a ping by name showed the correct 10.x.x.x IP and the repository was able to be updated within vRanger.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center