Share via

InternalServerError on BACPAC import to Azure SQL Database - Multiple attempts failed

Lucas Reine 0 Reputation points
2025-11-24T16:20:09.22+00:00

Problem Description

I'm experiencing persistent InternalServerError when attempting to import a BACPAC file to Azure SQL Database. The error occurs consistently across multiple attempts with different configurations.

Error Details

Error Code: InternalServerError

Error Message: "An unexpected error occurred while processing the request"

Tracking Information

First Attempt:

  • Tracking ID: b3264388-af48-495f-867f-9a4ca34ce41d
  • Service Request ID: 53a3fd2a-452d-4536-80d6-40a53233d888
  • Correlation ID: d7e8c75f-1303-4004-b0cb-dc37653643c8

Second Attempt (with 500GB database):

  • Tracking ID: 38ffe606-380f-4c1f-831f-d9d07d4c9e9f
  • Service Request ID: 30cdf6ae-0c52-4677-89bc-b1c3b2a4a4e7

Environment Details

PII security information

Troubleshooting Steps Already Taken

  1. Firewall Configuration: Successfully configured public access (0.0.0.0 - 255.255.255.255)
  2. Database Cleanup: Deleted all 3 existing databases to start fresh
  3. Increased Storage: Attempted import with 500GB database capacity (previously 250GB)
  4. Result: Same InternalServerError persists in all attempts

Question

What could be causing this persistent InternalServerError during BACPAC import? The error appears to be server-side rather than a configuration issue on my end. How can I resolve this or get further assistance from Azure support team?

Azure SQL Database

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Alberto Morillo 35,506 Reputation points MVP Volunteer Moderator
    2025-11-24T22:35:45.0033333+00:00

    Please make sure the bacpac does not make reference to Windows users, Active Directory users or Azure Entra users that are not valid. If you can recreate the bacpac, make sure you create a copy of the database and remove these types of users, before recreating the bacpac.

    If the bacpac was created on a SQL Server on-premises server, there may be incompatibilities between SQL Server databases and Azure SQL Server. I already mentioned Windows/Entra users as possible causes, but other causes could be:

    • Unresolved reference to objects that reside on other databases.
    • Encrypted objects
    • Three-four part names are not supported on Azure SQL.
    • Cross database queries on SQL programming objects.

    Go to the Import/Export History at the logical Azure SQL Server level (under Data Management) on Azure Portal There you need to click on the import operations you have tried to get the real error. Share with us that error.

    Try also using sqlpackage to have better control over importing bacpacs to SQL Azure.

    Was this answer helpful?

    0 comments

  2. AI answer

    2025-11-24T16:20:21.3366667+00:00

    The persistent InternalServerError you are encountering during the BACPAC import to Azure SQL Database could be caused by several factors, particularly since you mentioned that the error occurs consistently across multiple attempts and configurations. Here are some potential causes and troubleshooting steps you can consider:

    1. Database Size Limitations: Ensure that your Azure SQL Database tier supports the size of the BACPAC file you are trying to import. If you are importing a 500GB database, verify that your selected service tier can accommodate this size.
    2. Disk Space: The machine processing the import request needs sufficient disk space to handle the BACPAC file and any temporary files generated during the import process. It's recommended to have up to three times the size of the database in free disk space. If the machine has insufficient space, it may lead to errors.
    3. Region-Specific Issues: Since you are operating in the Brazil South region, check if there are any known issues or outages in that region that could affect service availability. You can check the Azure status page for any ongoing incidents.
    4. Firewall and Network Configuration: Although you have configured public access, ensure that there are no network restrictions or firewall rules that could be interfering with the import process.
    5. Service Health: Monitor the Azure Service Health dashboard for any alerts or notifications that might indicate service degradation or issues affecting your resources.
    6. Using SqlPackage: If the Azure portal continues to fail, consider using the SqlPackage command-line utility to perform the import. This tool can sometimes handle larger imports more effectively and may provide more detailed error messages.
    7. Contacting Azure Support: Since this appears to be a server-side issue, reaching out to Azure Support with the provided tracking and service request IDs may help you get more specific assistance tailored to your situation.

    By following these steps, you may be able to identify the underlying issue causing the InternalServerError and successfully complete the BACPAC import.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.