Troubleshooting Dataverse Table Data Export Failure in Different Environments

[dexit]

Hello Community,

I am facing a challenging issue with exporting Dataverse table data across different environments and seeking your insights or suggestions.

Here's the situation:

Enviroment	Import	Export
Environment A (Original Environment)	Success	Success
Environment B (Copy of Environment A)	failed	failed
Environment C (Newly created environment with solutions imported from Environment A)	failed	failed

In both problematic environments (B and C), I encounter the following error when attempting to export data: "Connection to Dataverse failed. Please check the link below on how to fix this issue." The link provided with the error message is: Troubleshoot Connection Issues. However, the connection status appears as 'connected', and even after deleting and recreating the connection, the issue persists.

Additional details:

• The security role in all environments is set to System Administrator.
• The issue occurs with both custom and standard tables, indicating that it's not limited to custom configurations.

Could there be specific settings or configurations that need to be adjusted when creating these environments? Has anyone experienced similar issues or have any suggestions on what might be causing this discrepancy and how to resolve it?

Any advice or guidance would be greatly appreciated.

Thank you in advance for your help.

Best regards,

[Jmanriquerios]

Hi @dexit 

In recent weeks MSFT has been adding managed solutions where it is adding new components, in this case many times this occurs when the environments are not aligned correctly.

To solve it if you still do not have data in the two source environments, I recommend restoring it and starting from 0, you can even copy the DEV environment to the other environments with only the components or with the data

This has happened to me and it was very complex to resolve because the connection was not from an unmanaged component

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
You can accept more than one post as a solution

[dexit · Accepted solution]

Thank you for your answer, and I apologize for the late response.
I contacted Microsoft and was able to confirm that it was a fault. I tried checking the consistency of the environment several times on my end, but it was unsuccessful.
It now seems to have been restored. Sorry for the trouble caused.