Power BI harvester messages (deprecated)

This message is a reminder to follow all steps to ingest the Power BI metadata in Data Catalog.

This message is always shown after the Power BI harvester successfully uploads the Power BI metadata to the Collibra Data Lineage server. Next, you have to create a lineage harvester configuration file and successfully run the lineage harvester to create Power BI assets and relations in Data Catalog.

An unexpected problem occurred at the local machine. The error can be caused by an invalid path name, not enough storage space or other unexpected issues.

There is a problem with the Power BI harvester configuration file or the source ID configuration file.Make sure that all information in the configuration file(s) and the path to the configuration file(s) is correct.

The Power BI harvester could not retrieve tenant information, because the Microsoft API did not return a response that the Power BI harvester could process.

The Power BI harvester could not communicate with the Collibra Data Lineage server, likely because of one of the following scenarios:

• The remote API did not return a response that the Power BI harvester could process.
• The API call returned a 401 (Unauthorized) error because an invalid userKey token was used.

To solve this problem, we recommend that you:

• Ensure that the Power BI harvester is connecting to the correct Collibra Data Lineage server.
• Check your network settings and rerun the Power BI harvester.

If the issue persists, please contact Collibra support or your customer success manager.

The Power BI harvester could not retrieve Power BI metadata, because the Power BI service did not return a response that the Power BI harvester could process.

Note If the error message indicates that the issue is an internal server error, the problem is caused by the Power BI REST API.

The Power BI harvester could not communicate with a remote server, because the server did not return a response within an expected time interval and, as a result, the Power BI harvester aborted the process.

To solve this problem, we recommend that you do the following:

• Check your network settings.
• Check the amount of metadata that is processed. If it is a large amount, use the --timeout command line option to specify a longer timeout for remote API calls.

If the problem persists or the remote server does not respond within a reasonable time period, create a support ticket or contact your customer success manager.

This problem occurs when the Power BI service returns inconsistent data. As a result, the Power BI harvester cannot successfully process the data to create a consistent result data set.

The Power BI harvester uses multiple API calls to retrieve Power BI metadata. If something in the Power BI service changed during the harvesting process, the metadata can be inconsistent. We recommend to run the Power BI harvester again. If the issue persists, create a support ticket or contact your customer success manager.

The Power BI harvester cannot access XMLA endpoints for some Power BI dedicated capacities with harvested workspaces, because the capacities are currently not running. As a result, the Collibra Data Lineage server cannot create a technical lineage for these workspaces.

To solve this problem, check if the Power BI workspace is part of a running dedicated capacity and you meet the necessary prerequisites to access and export it.

The Power BI authentication failed. This problem can be caused by an error in the Power BI credentials.

To solve this problem, check your Power BI login credentials in the Power BI harvester configuration file or reenter them via command line.

The connection between the Power BI harvester and the Collibra Data Lineage server failed. This problem can be caused by an error in the Collibra Data Intelligence Cloud credentials or Collibra Data Intelligence Cloud host address.

To solve this problem, check your Collibra Data Intelligence Cloud credentials in the Power BI harvester configuration file or reenter them via command line.

The Power BI harvester could not retrieve the tenant domain information.

To solve this problem, check that you have the correct tenant domain ID in the Power BI harvester configuration file.

The Power BI API failed. This can be caused by an error in the syntax of the workspaceFilter field in the Power BI harvester configuration file.

Important The workspace filter operations use OData syntax and are processed by the Power BI service, not the Power BI harvester.

Examples of supported workspace filter operations:

• name eq 'Workspace1' or name eq 'Workspace2' only harvests workspaces with the specified names.
• not endswith(name, 'Test') only harvests workspaces whose names don't end in Test.
• tolower(capacityId) eq '01234567-89ab-cdef-0123-456789abcdef' only harvests workspaces hosted on the specified dedicated capacity.
• reports/any(d:contains(d/name, 'Sales')) only harvests workspaces with reports whose names contain Sales.

If you do not want to filter on specific workspaces, leave the workspaceFilter field in the Power BI harvester configuration file empty.

Tip For more information about the query options to filter Power BI workspaces, see the Microsoft documentation. We cannot guarantee that other group filter operations work correctly. For example, the IN operator is currently not supported.

You do not have the required permissions to harvest the Power BI metadata. Check that the user is a Power BI Administrator and that the Power BI application has all required permissions.

To solve this problem, check that you have correctly registered your Power BI application in Microsoft Azure.

You do not have the required permissions to harvest the Power BI metadata. Enable the Allow service principals to use read-only Power BI admin APIs (preview) option in the Power BI Admin Console.

To solve this problem, check that you meet the prerequisites to use the service principal.

You do not have the required permissions to harvest the Power BI metadata. Enable the Allow service principal to use Power BI APIs option in the Power BI Admin Console.

To solve this problem, check that you meet the prerequisites to use the service principal.

The harvested Power BI workspaces are not assigned to a dedicated capacity. As a result, Data Catalog cannot ingest details about tables and columns and technical lineage are not available.

Note You do not have to assign less important to a dedicated capacity, for example personal workspaces. However, if there are no workspaces on a dedicated capacity, the harvested Power BI metadata is very limited.

The Power BI harvester could not access XMLA endpoints for any Power BI workspaces to retrieve detailed information about data sets. As a result, technical lineage is be available.

To solve this issue, check that you meet the prerequisites to access XMLA endpoints for all Power BI workspaces that you want to ingest in Data Catalog.