Self-Hosted Integration Runtime File System Linked Service "could not be resolved."

Arda Ertugrul 6 Reputation points
2022-11-10T09:39:36.56+00:00

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:

259072-image.png

All of our File System Linked Services stopped working, and we get the same error after trying to:

  • Change the drive the linked service tries to access
  • Change the related user trying to access the drive/folder (tried both user@keyman .com, and domain\user for several different users)
  • Restarting the Microsoft Integration Runtime Service.

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"

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
9,896 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Arda Ertugrul 6 Reputation points
    2022-11-10T10:08:12.99+00:00

    SOLUTION:

    The problem is solved by changing the "Host" to the relative path format:

    Previously:

    "DriveName:\Path"

    Currently:

    "\ServerName\DriveName$\Path"

    1 person found this answer helpful.