Tag: synapse link

Synapse Link Spark Pool Issue

~ planet_goodwill ~ Leave a comment

Microsoft Azure Synapse Link is a powerful tool that allows you to seamlessly integrate your Azure Synapse Analytics workspace with dataverse. However, like any technology, it can encounter issues during configuration and usage. In this blog post, we’ll address a common problem that users encounter when setting up Synapse Link: tables going into an initial sync and eventually failing, with Spark applications getting canceled. We’ll discuss how to troubleshoot this issue and provide a resolution to get your Synapse Link up and running smoothly.

Problem Statement

After configuring Synapse Link, you may notice that your tables are going through an initial synchronization process, but then they fail. Furthermore, when you check the Synapse monitoring, Spark applications are shown as being in a canceled state, and no logs are created for these jobs. This can be frustrating, but there are reasons behind this issue and steps to resolve it.

Synapse Link Error
Canceled Spark Application

Troubleshoot:

The primary reason for tables failing during the initial sync and Spark applications getting canceled is related to the available resources in your Synapse workspace. Here are some troubleshooting steps to identify the problem

  1. Inadequate Cores: Your Synapse workspace might not have the required number of cores available to process Synapse Link tables effectively. To find out if this is the issue, you can review your Azure Synapse Analytics available cores.
  2. Spark Pool Minimum Requirement: The minimum requirements for a Spark pool in Synapse Link can also lead to this problem. You should check whether your Spark pool configuration meets these requirements.
Minimum requirement for spark pool

Resolution

To resolve the issue and ensure a smooth operation of Synapse Link, you need to make sure that your Synapse workspace has the necessary resources available. Here’s how you can do it:

  1. Spark Cluster Nodes: Synapse Link needs a Spark cluster with 5-10 Spark nodes. If the size of one Spark node is (4 vCores / 32 GB), then your workspace should have 40 total vCores available to process Synapse Link tables effectively. Ensure that your workspace meets this requirement.
  2. Increase Spark Cores: If your Synapse environment falls short of the required number of cores, you can increase the number of Spark cores. To do this, open a support ticket with Microsoft (MSFT) and request an increase in the Spark cores for your environment.

Reference

For more information and detailed recommendations on Spark pool configuration for Azure Synapse Link, you can refer to the official Microsoft documentation here.

Related Synapse Link Issues

Synapse Link Filed to Initialize Storage

Synapse Link Fetching App

Synapse Link Partition Table Issue

Synapse Link failed to initialize storage

~ planet_goodwill ~ 1 Comment

Azure Synapse Analytics is a powerful tool for big data and analytics workloads, but like any complex system, it can encounter issues that need troubleshooting. In this blog post, we will discuss a common problem where Synapse Link Delta Tables are not being created in a Synapse Workspace and how to resolve it. We’ll walk you through the symptoms and provide a step-by-step resolution to get your workflow back on track.

Symptoms

  1. Job Status is in a Failed State in Power Platform: When you’re trying to create Delta Tables in your Synapse Workspace, one of the first symptoms you might encounter is job failures in Power Platform. This is a clear indication that something is not working as expected.
  2. Successful Execution of Spark Application in Synapse Workspace: Oddly, the Spark application itself may run without issues within the Synapse Workspace. This can make the problem seem even more mysterious.
  3. Errors in Spark Application Logs: While the Spark application itself may run successfully, the logs can reveal errors or issues that are preventing the creation of Delta Tables.

Look for the following in the spark application Logs:

ERROR AzureStorageEmitter [SparkObservabilityManager-0]: failed to initialize
com.microsoft.azure.storage.StorageException: Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.

Screenshots:

Synapse Link for dataverse
Spark application logs

Resolution

To resolve the issue of Delta Tables not being created in your Synapse Workspace, follow these steps:

  1. Go to Synapse Studio: Open Synapse Studio, which is your gateway to managing and monitoring your Synapse Analytics workloads.
  2. Open Linked Services: Under the “Manage” section in Synapse Studio, find and open “Linked Services.” This is where you can configure the connections and settings required for various services and resources in your Synapse Workspace.
  3. Test “Azure Data Lake Storage Gen2” Linked Service: Look for the “Azure Data Lake Storage Gen2” linked service, which is used by both Synapse Link and Synapse Studio. This is a critical component, and any issues with this connection can disrupt your Delta Table creation process.
  4. Ensure Successful Connection: Test the connection to the “Azure Data Lake Storage Gen2” linked service. It should be able to connect to your storage successfully. If the test fails, you need to correct the linked service connection. This might involve verifying your access credentials, permissions, or network configurations.
  5. Verify Synapse Link: After successfully establishing a connection with the Azure Data Lake Storage Gen2, verify that your Synapse Link is correctly set up and configured. This link should now be able to create Delta Tables in your Synapse Studio Data Lake after resolving any issues with the linked service.

By following these steps, you should be able to identify and resolve the issues preventing the creation of Delta Tables in your Azure Synapse Workspace. Ensuring that your connections and configurations are correct is crucial for the smooth operation of your analytics workflows.

Conclusion

Troubleshooting issues like Delta Table creation in Azure Synapse Workspace can be a challenging task, but with the right approach, you can quickly identify and resolve the problem. By checking and testing your linked services and verifying your Synapse Link configuration, you can get your data workflows back on track and make the most of Azure Synapse Analytics for your big data and analytics needs. If you encounter further issues, don’t hesitate to reach out to Azure support for additional assistance.

Other Synapse link issues:

Synapse link stuck at fetching app

Reference: Configure Synapse Link for Dataverse

Synapse Link Stuck at Fetching App

~ planet_goodwill ~ 2 Comments

In this blog post, we will address a common issue with Synapse Link, where it gets stuck at “Fetching App.” We will provide a step-by-step guide on how to troubleshoot and resolve this problem.

Issue:

Synapse Link Stuck at Fetching App

Fetching App

Troubleshoot

If you encounter the issue of Synapse Link being stuck at “Fetching App,” follow these troubleshooting steps:

  1. Set Up a New Link from make.powerapps.com:
    • Head to make.powerapps.com.
    • Create new synapse link
    • Select your Synapse workspace and storage
  2. Select Required Tables for Syncing:
    • Choose the tables that you want to sync.
  3. Enable Developer Tools in Your Browser:
    • Press F12 to open the developer tools.
    • Navigate to the “Network” tab.
  4. Look for a 404 Error:
    • Select create synapse link after selecting tables
    • While in the network tab, look for a 404 error that matches the following description or states “app not found.” This error indicates that Synapse Link is unable to set up a Service Principal in Azure.

404 error when trying a GET request https://graph.windows.net/myorganization/servicePrincipalsByAppId/12345678-77a4-5874-2365-12345678c89b/objectId?api-version=1.6

Resolution

To resolve this issue, follow these steps

  1. Launch PowerShell as Administrator with Azure Installed:
    • If you don’t have Azure PowerShell installed, you can follow the installation steps here.
  2. Connect to the Tenant:
    • Run the following command: Connect-AzAccount.
    • Ensure you log in with a user who has privileges to create a Service Principal in the tenant, such as a tenant admin or global administrator.
  3. Add the Principal:
    • Run this command: New-AzADServicePrincipal -ApplicationId ‘12345678-77a4-5874-2365-12345678c89b’.
  4. Try Setting up Synapse Link Again:
    • You should now attempt to set up Synapse Link again. Ideally, this should work without any issues.

By following these steps, you should be able to resolve the “Synapse Link Stuck at Fetching App” issue. If you encounter any further issues, don’t hesitate to seek additional support from your Azure administrators or support team.

Reference: Synapse Link Delta Lake Configuration

Related Article:

Synapse Invalid Object Name

Invalid object name ‘dataverse_.dbo.opportunity_partitioned’

~ planet_goodwill ~ 2 Comments

In this blog post, we will discuss a common issue encountered when trying to access partitioned tables in Azure Synapse Workspace, specifically those created by ingesting tables from Power Platform through Azure Synapse Link for Dataverse. While the snapshot folder and .csv files are typically generated, users face difficulties in accessing these partitioned tables. The problem is characterized by an error message that reads: “Invalid object name ‘dataverse_********.dbo.opportunity_partitioned’.”

Resolution:

  1. Check if Workspace System Assigned Managed identity has Storage Blob Data Contributor access on the Storage Account.
  2. Create a server-scoped credential on the master database for the storage account and container
  3. Partition table should work after creating server-scoped credentials

USE MASTER
CREATE CREDENTIAL [https://storageaccount.dfs.core.windows.net/container]
WITH IDENTITY=’Managed Identity’

Reference: https://learn.microsoft.com/en-us/azure/synapse-analytics/sql/develop-storage-files-storage-access-control?tabs=shared-access-signature#server-scoped-credential