Over the last month we have been getting completely random errors on the SQL jobs. Usually when running the job again, it works without issues. The error is related to staging process. Below is an example:
An unexpected error occured while processing the request. Tracking ID: 'fc59b29b-220b-4e63-90d2-5d528535813d'Status: 500 (Internal Server Error)ErrorCode: InternalServerErrorContent:{"error":{"code":"InternalServerError","message":"An unexpected error occured while processing the request. Tracking ID: 'fc59b29b-220b-4e63-90d2-5d528535813d'"}}Headers:Cache-Control: no-cachePragma: no-cachex-ms-request-id: fc59b29b-220b-4e63-90d2-5d528535813dx-ms-failure-cause: REDACTEDx-ms-operation-identifier: REDACTEDx-ms-ratelimit-remaining-subscription-reads: REDACTEDx-ms-ratelimit-remaining-subscription-global-reads: REDACTEDx-ms-correlation-request-id: REDACTEDx-ms-routing-request-id: REDACTEDStrict-Transport-Security: REDACTEDX-Content-Type-Options: REDACTEDX-Cache: REDACTEDX-MSEdge-Ref: REDACTEDDate: Tue, 24 Jun 2025 01:13:34 GMTContent-Length: 162Content-Type: application/json; charset=utf-8Expires: -1
We have ticket open (Case #07731453) where Veeam Support investigated and concluded it was an issue on MS Azure side. I raised a ticket with MS Support who concluded no SQL errors are visible from their side and insist Veeam to look into it again. So I'm stuck being pinged back and forth.
Just wondered if anyone else has seen this? We currently have 3 different customers affected by it, all with isolated setup.
I can see from the case that these errors keep repeating and they've asked to check with Azure support (maybe share those errors with them) to see what is going on.
Can you tell a bit more about how these SQL jobs/servers are setup? It could be something unique to their setup which explains this.