Error Azure data lake in D365 fno finance and operations

 Error Azure data lake in D365 fno finance and operations

Export to Data Lake feature is not available in your region and/or your environment at this time

This feature is not available in Tier-1 (developer) environments. You need a sandbox environment (Tier 2 or higher) with Platform updates for version 10.0.13 or higher.

This feature is in limited preview and may not be available in all Azure regions where Finance and Operations apps are available, or this feature may not be available for your environment. If you would like to join a future preview, complete the survey. We will contact you when we are ready to include you. You can also join a Yammer group by completing the survey. You can use the Yammer group to stay in contact and ask questions that will help you understand the feature. We are working hard to make this feature available soon.

Export to Data Lake feature is currently being installed for your environment. Please check back later.

Before you can use this feature, you need to configure the export to Data Lake. For more information, see Configure export to Azure Data Lake.

Export to Data Lake add-in is not installed.

Ask your administrator to install this add-in using Dynamics Lifecycle Services (LCS). Before you can use this feature, you need to configure the export to Data Lake. For more information, see Configure export to Azure Data Lake.

Export to Data Lake feature failed to install in Dynamics Life Cycle Services (LCS).

Ask your administrator to re-install the Export to Data Lake add-in. If this issue persists, contact Support. When you configure the Export to Data Lake feature, the system may report an error. Or, there may be an error when you access the data lake after configuration due to a change in your environments. For more information, see Configure export to Azure Data Lake.

Export to Data Lake feature is temporarily unavailable. Please check back later.

If you see this error for a prolonged period of time, contact Support.

Status codes with extended errors

When an error occurs in a table that you added to Export to Data Lake, you may see an error code in the status column. The following error codes provide the cause of the error and how to correct the issue.

Error status codes 4xx indicate an issue with the table

STATUS CODES WITH EXTENDED ERRORS

Error code	Issue	Next steps
400	The table you added doesn't contain a RecID field.	RecID fields are used by the system to index table data. Tables that don't contain a RecID field can't be added to the Data Lake. If this issue is from a table in a Finance and Operations app, contact Microsoft support. If this table was developed by your partner or ISV, contact the developer to include a RecID field.
401	The table you added is missing in the database.	The table you added is no longer available in the database and the system can't continue updating data in the lake. The table may have been removed because of a software or database update. Contact your database administrator or a developer. If this table was developed by your partner or ISV, contact the developer.
402	The RecID field isn't indexed.	The system has detected that the RecID field contained in the table isn't part of an index. This may lead to poor performance in updating the data lake and updates may take longer to reflect in the data lake. If this issue is from a table in a Finance and Operations app, contact Microsoft support. If this table was developed by your partner or ISV, contact the developer.

Error status codes 5xx indicate a system error encountered while exporting data Due to the error, the system has paused data export – data that exists in the lake won’t be updated until the error is resolved. Try to deactivate and activate the table to see if this resolves the issue. Note that deactivating and activating the table may cause the system to re-initialize the data in the lake by taking a full copy. If the issue persists, contact Microsoft support with the table name and the error code.

Error status codes 8xx and 9xx indicate a change to the table or database structure since it was added

TABLE 2

Error code	Issue	Next steps
800	There is a change in the data table schema.	The system found a change in the table structure when adding changed data to the lake. This change is typically the result of a software update or a database modification. For example, when a new field is added to a table, or a field is modified or removed, the data updated in the lake may not be in the same format as the existing data. Because of the error, the system has paused data export. The data that exists in the lake won’t be updated until the error is resolved. Deactivate and activate the table to see if the issue is resolved.
801	There is an issue with the Change data capture feature.	The Export to Data Lake feature uses the Change data capture feature. Change data can’t be exported because the Change data capture feature is disabled in the Finance and Operations apps database. This may be the result of a database maintenance operation. Deactivate and activate the table to see if the issue is resolved. If the issue persists, contact Microsoft support.
802	There is an issue with the Change data capture feature for the table.	The Export to Data lake feature uses the Change data capture feature. Change data can’t be exported because the Change data capture feature isn't enabled for this table in your Finance and Operations apps database. This may be the result of a database maintenance operation. Deactivate and activate the table to see if the issue is resolved.
900	There is an issue with the Change data capture feature in this environment.	The Export to Data lake feature uses the Change data capture feature. Change data can’t be exported because the Change data capture feature isn't enabled for this table in the Finance and Operations apps database. This may be the result of a database maintenance operation. Deactivate and activate the table to see if the issue is resolved. If the issue persists, contact Microsoft support.

 Note

Deactivating and activating the table may cause the system to re-initialize the data in the lake by creating a full copy. If this is a large table, the initialize process may take some time. In the future, the system may automatically update data in the lake to reflect the table structure changes.

Above post from https://docs.microsoft.com//