The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event! Join us in Stockholm, Sweden from September 24-27, 2024.
2-for-1 sale on June 20 only!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
Edits: Accidentally edited the wrong post, then undid the edit, then edited to add edits note.
I don't have a lot of experience with pipelines but didn't find this issue on a skim of the troubleshooting documentation or in a google search. I don't know how to begin to resolve this, it seems like the failure occurs before my pipeline activities even start.
Issue: The scheduled refreshes are all failing. Running the pipeline manually provides a little notification that the pipeline successfully started and immediately provides a notification that the pipeline failed. Looking into the error simple provides "internalServerError executing request". The first couple of steps of the pipeline are lookup activities, but it doesn’t even look like those are initiating before the run fails.
Occurrence: The pipeline was working well on a 15-minute schedule and didn't stop working after I made a copy of the pipeline to test with a refactored notebook. Running the pipeline copy is the first time I saw the error. I couldn’t resolve it and ended up altering the original working pipeline. The updated pipeline continued to work without issue for approximately a week.
Solved! Go to Solution.
Hi @JP_Wisco
Apologies for the delay in response from my end.
Following up to see whether the issue got resolved or still you are facing the issue?
The error "Internal Server Error - Executing requests." could be a transient network issue.
If the issue still persists. Please reach out to our support team so they can do a more thorough investigation on why this it is happening. It's difficult to tell what could be the reason for this performance. If its a bug, we will definitely would like to know and properly address it.
Please go ahead and raise a support ticket to reach our support team:
https://support.fabric.microsoft.com/support
After creating a Support ticket please provide the ticket number as it would help us to track for more information.
Thank you.
Hi @JP_Wisco
Thanks for using Microsoft Fabric Community.
Apologies for the inconvenience that you are facing here.
Could you please share below details to troubleshoot the issue:
Thanks.
Thank you for the response. I hopped into the pipeline to provide a detailed response and initiated a manual run while I was at it. The run kicked off without issue and fully succeeded 20 minutes later. After three straight days of scheduled fails, I have a manual success and was able to restart the schedule without issue. I haven't made any changes to the pipeline, sourcess or destinations beyond unpublishing the in-development Power BI reporting that was built on this data. I guess I'm cured until it happens again?
Hi @JP_Wisco
Apologies for the delay in response from my end.
Following up to see whether the issue got resolved or still you are facing the issue?
The error "Internal Server Error - Executing requests." could be a transient network issue.
If the issue still persists. Please reach out to our support team so they can do a more thorough investigation on why this it is happening. It's difficult to tell what could be the reason for this performance. If its a bug, we will definitely would like to know and properly address it.
Please go ahead and raise a support ticket to reach our support team:
https://support.fabric.microsoft.com/support
After creating a Support ticket please provide the ticket number as it would help us to track for more information.
Thank you.
Hi @JP_Wisco
We haven’t heard from you on the last response and was just checking back to see if you've had a chance to submit a support ticket. If you have, a reference to the ticket number would be greatly appreciated. This will allow us to track the progress of your request and ensure you receive the most efficient support possible.
Thanks
Thank you for the follow-up. I haven't created a ticket, and haven't run into any persistent or even frequent disruptions since this event.
I've never seen a transient network issue persist for a full weekend, but I haven't had any problems with it since I halted the schedule, gave it half a day to rest, and then restarted the schedule.
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Ask questions in Eventhouse and KQL, Eventstream, and Reflex.
User | Count |
---|---|
15 | |
3 | |
2 | |
1 | |
1 |