vRanger backups to SmartDisk fail with: "Failed to acquire the shared resources. Unable to connec (97960)

Any attempt to backup or restore to/from SmartDisk or creating a SmartDisk repository will fail with the above vRanger error.

Verifying the SmartDisk status, shows it is started with the "percolator slave" process listening.
"smartdisk.bat stats" or "smartdisk.bat config --show" return normal outputs.
Testing SmartDisk access and webdav authentication via web browser (http://<localhost_IP>:<port>/proc/dedupe/stats.stnz) works as expected, pointing to a vRanger issue rather than SmartDisk.

Note: In this particular instance, vRanger and SmartDisk are both installed on the same physical machine, which is not supported as per the vRanger/NVSD Integration guide:
As per http://us-downloads.quest.com/Repository/support.quest.com/vRanger/5.5/Documentation/E/vRanger_5.5_NVSDIntegration.pdf"

The error message above, can be broken up in 2 parts:

1) The “Failed to acquire the shared resources. Unable to connect to repository” error message is returned when vRanger fails to connect to a repository to verify read/write access, before a backup or restore operation.
2) The "File exists" error message is a Windows System IOException error, typically seen when the local user's %TEMP% directory is full and has reached the maximum 65535 items.
In the vRanger case the %TEMP% folder would be the one belonging to the user vRanger is running as.
Depending on your group Policy settings %TEMP% could for instance point to:
- "C:\Users\vranger\AppData\Local\Temp\"
- "C:\Users\vranger\AppData\Local\Temp\1"
- "C:\Users\vranger\AppData\Local\Temp\2"
and so on...see: http://technet.microsoft.com/en-us/library/cc759190%28WS.10%29.aspx

It is important to note that %TEMP% isn't exclusively used by vRanger but it is shared with any other applications called by the local user.
While temporary locations should normally be cleared by the applications using them, it can never be guaranteed a program will successfully manage to perform its post operation clean up tasks.
Fault report FB14458 has been opened to investigate whether vRanger could be leaving any temorary files and folders in %TEMP%

- Navigate to the vRanger user's %TEMP% folder
- Depending on where %TEMP% points to, clear its content without deleting the parent subdirectories.
Example:
If %TEMP% points to "C:\Users\vranger\AppData\Local\Temp\2" delete its content without deleting the ..\2