SOLUTION:
The problem is solved by changing the "Host" to the relative path format:
Previously:
"DriveName:\Path"
Currently:
"\ServerName\DriveName$\Path"
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello,
After last night's update, our Self-Hosted Integration Runtime stopped accessing our local files. We are faced with the error "DriveName could not be resolved."
You can see the screenshot below:
All of our File System Linked Services stopped working, and we get the same error after trying to:
Edit: We realized one of our Google BigQuery Linked Service is able to access one of the local drives, which makes me think it's an issue related to File System Linked Service alone.
SOLUTION:
The problem is solved by changing the "Host" to the relative path format:
Previously:
"DriveName:\Path"
Currently:
"\ServerName\DriveName$\Path"
SOLUTION:
The problem is solved by changing the "Host" to the relative path format:
Previously:
"DriveName:\Path"
Currently:
"\ServerName\DriveName$\Path"