Troubleshoot Azure Data Factory UX Issues

APPLIES TO: Azure Data Factory Azure Synapse Analytics

This article explores common troubleshooting methods for Azure Data Factory UX.

ADF UX not loading

Note

The Azure Data Factory UX officially supports Microsoft Edge and Google Chrome. Using other web browsers may lead to unexpected or undocumented behavior.

Third-party cookies blocked

ADF UX uses browser cookies to persist user session and enable interactive development and monitoring experiences. It is possible your browser blocks third-party cookies because you are using an incognito session or have an ad blocker enabled. Blocking third-party cookies can cause issues when loading the portal, such as being redirected to a blank page, 'https://adf.azure.com/accesstoken.html', or getting a warning message saying that third-party cookies are blocked. To solve this problem, enable third-party cookies options on your browser using the following steps:

Google Chrome

Allow all cookies

  1. Visit chrome://settings/cookies in your browser.

  2. Select Allow all cookies option

    Allow All Cookies in Chrome

  3. Refresh ADF UX and try again.

Only allow ADF UX to use cookies

If you do not want to allow all cookies, you can optionally just allow ADF UX:

  1. Visit chrome://settings/cookies.

  2. Select add under Sites that can always use cookies option

    Add ADF UX to allowed sites in Chrome

  3. Add adf.azure.com site, check all cookies option, and save.

    Allow all cookies from ADF UX site

  4. Refresh ADF UX and try again.

Microsoft Edge

  1. Visit edge://settings/content/cookies in your browser.

  2. Ensure Allow sites to save and read cookie data is enabled and that Block third-party cookies option is disabled

    Allow all cookies in Edge

  3. Refresh ADF UX and try again.

Only allow ADF UX to use cookies

If you do not want to allow all cookies, you can optionally just allow ADF UX:

  1. Visit edge://settings/content/cookies.

  2. Under Allow section, select Add and add adf.azure.com site.

    Add ADF UX to allowed sites in Edge

  3. Refresh ADF UX and try again.

Connection failed on ADF UX

Sometimes you would see "Connection failed" error on ADF UI similar to the screenshot below after clicking Test Connection, Preview, etc. It means ADF failed to perform the operation because it cannot connect to the ADF service from your machine.

Connection failed

To resolve the issue, you can first try the same operation with InPrivate browsing mode in your browser.

If it’s still not working, find the server name from the error message (in this example, dpnortheurope.svc.datafactory.azure.com), then type the server name directly in the address bar of your browser.

  • If you see 404 in the browser, it usually means your client side is ok and the issue is at ADF service side. File a support ticket with the Activity ID from the error message.

    Resource not found

  • If you don't see 404 or you see similar error below in the browser, it usually means you have some client-side issue. Further follow the troubleshooting steps.

    Client-side error

To troubleshoot further, open Command Prompt and type nslookup dpnortheurope.svc.datafactory.azure.com. A normal response should look like below:

Command response 1

  • If you see a normal DNS response, further contact your local IT support to check the firewall settings on whether HTTPS connection to this host name is blocked or not. If the issue could not be resolved, file a support ticket with the Activity ID from the error message.

  • If you see anything else than this, it usually means there is something wrong with your DNS server when resolving the DNS name. Usually changing ISP (Internet Service Provider) or DNS (for example, to Google DNS 8.8.8.8) could be a possible workaround to try. If the issue persists, you could further try nslookup datafactory.azure.com and nslookup azure.com to see at which level your DNS resolution is failed and submit all information to your local IT support or your ISP for troubleshooting. If they believe the issue is still at Microsoft side, file a support ticket with the Activity ID from the error message.

    Command response 2

Change linked service type in datasets

File format dataset can be used with all the file-based connectors, for example, you can configure a Parquet dataset on Azure Blob or Azure Data Lake Storage Gen2. Note each connector supports different set of data store related settings on the activity, and with different app model.

On ADF authoring UI, when you use a file format dataset in an activity - including Copy, Lookup, GetMetadata, Delete activities - and in dataset you want to point to a linked service of different type from the current (for example, switch from File System to ADLS Gen2), you would see the following warning message. To make sure it’s a clean switch, upon your consent, the pipelines and activities, which reference this dataset will be modified to use the new type as well, and any existing data store settings, which are incompatible with the new type will be cleared as it no longer applies.

To learn more on which the supported data store settings for each connector, you can go to the corresponding connector article -> copy activity properties to see the detailed property list. Refer to Amazon S3, Azure Blob, Azure Data Lake Storage Gen1, Azure Data Lake Storage Gen2, Azure Files, File System, FTP, Google Cloud Storage, HDFS, HTTP, and SFTP.

Warning message

Could not load resource while opening pipeline

When the user accesses pipeline using ADF GUI authoring tool, the error message says, "Could not load resource 'xxxxxx'. Please ensure no mistakes in the JSON and that referenced resources exist. Status: TypeError: Cannot read property 'xxxxx' of undefined, Possible reason: TypeError: Cannot read property 'xxxxxxx' of undefined."

The source of the error message is JSON file that describes the pipeline. It happens when customer uses Git integration and pipeline JSON files get corrupted for some reason. You will see an error (red dot with x) left to pipeline name as shown below.

Pipeline JSON error

Solution is to fix JSON files at first and then reopen the pipeline using Authoring tool.

Next steps

For more troubleshooting help, try these resources: