Forum Discussion
Xml processing failed Either the input is invalid or it isn't supported(Internal error:Root element)
- 1 year ago
Hi Devi_AK,
Thank you for reaching out to the Microsoft Fabric community Forum. Please go through the following steps to may resolve your issue.
- Verify Connection: Confirm you can connect to the data source using SQL Server Management Studio or a web browser. Ensure Power BI credentials are valid and have necessary permissions.
- Check Data Source Settings: In Power BI Service > Datasets > select your dataset > Data source settings. Update and authenticate credentials if needed.
- Validate XML Response: If using an XML feed, ensure the response is well-formed. Use Postman or browser tools to check for the root element.
- Fix XML Structure: If the XML structure is invalid (e.g., unclosed tags), adjust the source or transform the data to comply with XML standards.
- Open Power Query Editor: In Power BI Desktop, go to Transform Data. Check each step in the Applied Steps pane for errors that may disrupt data transformation.
- Isolate Transformations: Identify XML-related transformations. Temporarily disable steps to pinpoint where the error occurs.
- Check Data Types: Ensure Power BI's expected data types of matches those from the source. Use Column Quality and Column Distribution in Power Query to find anomalies.
- Verify Gateway Status: Ensure the on-premises gateway is running and up to date. Go to Power BI Service > Settings > Manage gateways to check its configuration.
- Test Data Source Connectivity: In Manage Gateways, test the connection to ensure the data source is accessible. After addressing issues, attempt to refresh the dataset in Power BI Service and monitor the status for new error messages.
I hope my suggestions give you good ideas, if you have any more questions, please feel free to reach out.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
Hi Devi_AK,
Thank you for reaching out to the Microsoft Fabric community Forum. Please go through the following steps to may resolve your issue.
- Verify Connection: Confirm you can connect to the data source using SQL Server Management Studio or a web browser. Ensure Power BI credentials are valid and have necessary permissions.
- Check Data Source Settings: In Power BI Service > Datasets > select your dataset > Data source settings. Update and authenticate credentials if needed.
- Validate XML Response: If using an XML feed, ensure the response is well-formed. Use Postman or browser tools to check for the root element.
- Fix XML Structure: If the XML structure is invalid (e.g., unclosed tags), adjust the source or transform the data to comply with XML standards.
- Open Power Query Editor: In Power BI Desktop, go to Transform Data. Check each step in the Applied Steps pane for errors that may disrupt data transformation.
- Isolate Transformations: Identify XML-related transformations. Temporarily disable steps to pinpoint where the error occurs.
- Check Data Types: Ensure Power BI's expected data types of matches those from the source. Use Column Quality and Column Distribution in Power Query to find anomalies.
- Verify Gateway Status: Ensure the on-premises gateway is running and up to date. Go to Power BI Service > Settings > Manage gateways to check its configuration.
- Test Data Source Connectivity: In Manage Gateways, test the connection to ensure the data source is accessible. After addressing issues, attempt to refresh the dataset in Power BI Service and monitor the status for new error messages.
I hope my suggestions give you good ideas, if you have any more questions, please feel free to reach out.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
- v-kpoloju-msft1 year ago
Community Support
Hi Devi_AK,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.