EntitySyncFailure: Could not find stored procedure SP_CDSVirtualEntityGetPageRangesV2 for Synapse Link for Dataverse D365FO

Alexander O'Reilly 40 Reputation points

Our team was able to create Synapse Link for Dataverse D365FO select tables to sync. However now I have noticed all the tables are empty in synaspe workspace and the EntitySyncFailure folder is populated with logs of each entity having a message similar to the below indicating that SP_CDSVirtualEntityGetPageRangesV2 could not be found. Has anyone encountered this?

Australia East region

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.SqlClient.SqlException: Could not find stored procedure 'SP_CDSVirtualEntityGetPageRangesV2'.

👁 SP_CDSVirtualEntityGetPageRangesV2

0 comments No comments
Sign in to comment

2 answers

  1. Pilladi Padma Sai Manisha 10,190 Reputation points • Microsoft External Staff • Moderator

    Hey Alexander,

    This is not something you need to fix in the Finance & Operations database, and it’s also not related to Purview.

    The error Could not find stored procedure 'SP_CDSVirtualEntityGetPageRangesV2' comes from the Synapse Link for Dataverse backend process, not from any stored procedures in your Synapse workspace or F&O database. These procedures are managed internally by the service.

    Based on your symptoms (tables created but empty, and all entities failing with the same error in the EntitySyncFailure folder), this usually means the Synapse Link sync pipeline didn’t initialize correctly.

    In most cases this happens due to:

    • A partially initialized or corrupted Synapse Link profile
    • Backend metadata or version mismatch in the Dataverse environment
    • Occasionally a service-side issue in the region

    What I’d recommend trying:

    • Disable and re-enable a few affected tables in the Synapse Link profile
    • If that doesn’t help, delete and recreate the Synapse Link profile completely

    If the issue continues even after recreating the link, then it’s likely a service-side/backend issue, and you should raise a support request under Azure Synapse Analytics > Synapse Link for Dataverse so it can be investigated further.

    In short, nothing needs to be fixed in the database itself,this is a Synapse Link service sync issue.

    1. Alexander O'Reilly 40 Reputation points

      Thanks @Pilladi Padma Sai Manisha . We have recreated the Synapse Link and experiencing the same behaviour as before. Interestingly the below 6 tables sync (which is the same as the first time we setup the Synapse Link):

      • TargetMetadata 1 row
      • StateMetadata 1 row
      • StatusMetadata 1 row
      • OptionsetMetadata 1 row
      • userinfo_partitioned 62 rows
      • GlobalOptionsetMetadata_partitioned 3,869 rows

      All others fail with the "System.Data.SqlClient.SqlException: Could not find stored procedure 'SP_CDSVirtualEntityGetPageRangesV2'" error in the EntitySyncFailure folder.

      Some additional information that might assist with troubleshooting is that we have 4 Synapse Links:

      1. D365 Dataverse for Customer Service (UAT) -> Storage Account A / Synapse Workspace A (working)
      2. D365 Dataverse for Customer Service (PROD) -> Storage Account A / Synapse Workspace A (working)
      3. D365 Dataverse for Finance and Operations (UAT) -> Storage Account A / Synapse Workspace A (working)
      4. D365 Dataverse for Finance and Operations (PROD) -> Storage Account A / Synapse Workspace A (failing)

      Can you confirm if we are only allowed a single FnO Synapse Link per storage account as per this line in the online documentation:👁 User's image

      https://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-select-fno-data

      We also had two spark pools in Synapse workspace A:

      1. Spark Pool v3.5
      2. Spark Pool v3.4 - we have now removed this one today (6 June 2026) to see if that is a factor
    2. Pilladi Padma Sai Manisha 10,190 Reputation points • Microsoft External Staff • Moderator

      Thank you for the additional details.

      Based on what you've shared, I don't think the storage account or Spark pool configuration is the cause. Since the same storage account and Synapse workspace are already working for your other Dataverse and F&O Synapse Links, and only the F&O PROD link is affected, the issue appears to be specific to that environment.

      The fact that the metadata tables are syncing successfully also suggests that the Synapse Link connection itself is working. The failure seems to occur when the service starts processing the F&O entity data, where it encounters the missing SP_CDSVirtualEntityGetPageRangesV2 procedure.

      Regarding the documentation note, my understanding is that F&O data cannot be added to an existing Synapse Link profile already configured with Azure Synapse Link. However, having multiple separate Synapse Link profiles that use the same storage account is generally supported, which aligns with your working UAT environments.

      Since recreating the Synapse Link resulted in the same behavior, and the issue is isolated to the PROD F&O environment, this may require further investigation by the product team. Could you confirm whether the affected entities are standard entities, custom entities, or a mix of both?

      Thanks.

    3. Deleted

      This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    4. Pilladi Padma Sai Manisha 10,190 Reputation points • Microsoft External Staff • Moderator

      Hi Alexander,

      Following up to see if the below answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

    Sign in to comment
  2. Ravi Kiran Pagidi 80 Reputation points

    Hi Alexander,

    This does not look like an issue with the Synapse workspace tables themselves. The error is happening during the Finance and Operations/Dataverse export process before the data is successfully written for consumption in Synapse.

    SP_CDSVirtualEntityGetPageRangesV2appears to be an internal stored procedure used by the Synapse Link / Finance and Operations virtual entity export process to calculate page ranges while extracting data. It is not something you would normally create manually in Synapse.

    When this procedure is missing, it usually points to one of these areas:

    • The required Finance and Operations platform/application update is not fully applied.

    The virtual entity / Synapse Link metadata in the environment is not fully initialized.

    Finance and Operations entities were enabled, but the required backend setup for Synapse Link did not complete correctly.

    The environment was recently restored, copied, upgraded, or moved, and the Synapse Link configuration needs to be reinitialized.

    There is a regional/service-side issue that Microsoft needs to validate.

    I would not recommend creating this stored procedure manually. Since it is part of the product-managed integration, manually adding or modifying backend objects can create unsupported behavior.

    A few things I would check:

    Confirm the Finance and Operations environment is on a supported platform/application version for Synapse Link with F&O data.

    Confirm Finance and Operations virtual entities are enabled correctly.

    Confirm row version change tracking is enabled for the selected entities, if you are using F&O entities.

    Try removing and re-adding one affected table/entity to the Synapse Link profile, or reinitializing the link if this is a non-production environment.

    Check whether this started after an environment restore, database refresh, or platform update.

    If the issue continues across multiple entities, open a Microsoft support ticket, because the missing stored procedure likely needs backend/service-side investigation.

    In short, the empty tables are expected as a result of the sync failure. The root cause is not that Synapse cannot read the data, but that the F&O/Dataverse export process is failing while trying to retrieve page ranges for the selected entities.

    I would start by validating the F&O version/prerequisites and then reinitialize the Synapse Link profile. If the procedure is still missing after that, Microsoft Support will likely need to check the environment provisioning or service metadata for the Australia East region.Hi Alexander,

    This does not look like an issue with the Synapse workspace tables themselves. The error is happening during the Finance and Operations/Dataverse export process before the data is successfully written for consumption in Synapse.

    SP_CDSVirtualEntityGetPageRangesV2 appears to be an internal stored procedure used by the Synapse Link / Finance and Operations virtual entity export process to calculate page ranges while extracting data. It is not something you would normally create manually in Synapse.

    When this procedure is missing, it usually points to one of these areas:

    The required Finance and Operations platform/application update is not fully applied.

    The virtual entity / Synapse Link metadata in the environment is not fully initialized.

    Finance and Operations entities were enabled, but the required backend setup for Synapse Link did not complete correctly.

    The environment was recently restored, copied, upgraded, or moved, and the Synapse Link configuration needs to be reinitialized.

    There is a regional/service-side issue that Microsoft needs to validate.

    I would not recommend creating this stored procedure manually. Since it is part of the product-managed integration, manually adding or modifying backend objects can create unsupported behavior.

    A few things I would check:

    Confirm the Finance and Operations environment is on a supported platform/application version for Synapse Link with F&O data.

    Confirm Finance and Operations virtual entities are enabled correctly.

    Confirm row version change tracking is enabled for the selected entities, if you are using F&O entities.

    Try removing and re-adding one affected table/entity to the Synapse Link profile, or reinitializing the link if this is a non-production environment.

    Check whether this started after an environment restore, database refresh, or platform update.

    If the issue continues across multiple entities, open a Microsoft support ticket, because the missing stored procedure likely needs backend/service-side investigation.

    In short, the empty tables are expected as a result of the sync failure. The root cause is not that Synapse cannot read the data, but that the F&O/Dataverse export process is failing while trying to retrieve page ranges for the selected entities.

    I would start by validating the F&O version/prerequisites and then reinitialize the Synapse Link profile. If the procedure is still missing after that, Microsoft Support will likely need to check the environment provisioning or service metadata for the Australia East region.

    1. Alexander O'Reilly 40 Reputation points

      Thanks Ravi for your detailed response. I have checked all those components and they meet the requirements. We've logged an MS ticket a few days ago but I don't know how get these escalated. Thanks anyway.

    Sign in to comment
Sign in to answer

Your answer