The extension encountered an unexpected error and provided no additional details.

Taavi Kallankari 5 Reputation points
2025-12-13T15:12:02.7066667+00:00

No access to Azure Mysql database. The extension encountered an unexpected error and provided no additional details. Database is stopped and no access to start

Azure Database for MySQL
0 comments No comments
{count} vote

2 answers

Sort by: Most helpful
  1. Q&A Assist
    2025-12-13T15:12:12.8633333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    If you are encountering an unexpected error while trying to access your Azure MySQL database, it could be due to several reasons. Here are some common troubleshooting steps you can take:

    1. Check Firewall Settings: Ensure that your Azure Database for MySQL Flexible Server firewall settings allow connections from your client IP address. You may need to configure the firewall rules accordingly.
    2. Connection Time-out: Verify that there are no network issues causing a connection time-out. Ensure that your network is stable and that you can reach the Azure service.
    3. Incorrect Login Information: Double-check the username and password you are using to connect to the database. An incorrect username or password can lead to access denial.
    4. Maximum Limit Reached: If the maximum limit of connections to the Azure Database for MySQL Flexible Server has been reached, you will need to evaluate and possibly reduce the number of active connections.
    5. TLS/SSL Configuration: Ensure that your connection is using the correct TLS version. Azure Database for MySQL Flexible Server requires TLS 1.2 by default, and connections using TLS 1.0 and TLS 1.1 will be denied.

    If these steps do not resolve the issue, you may want to check the error logs for more details or consult Azure support for further assistance.


    References:


  2. VRISHABHANATH PATIL 3,220 Reputation points Microsoft External Staff Moderator
    2025-12-15T03:05:33.1533333+00:00

    Hi @Taavi Kallankari**
    **
    It looks like you're running into an issue accessing your Azure MySQL database due to an unexpected error. From your description, it seems that the database is stopped, and you're unable to start it.

    Based on what you've described, you might be encountering ERROR 1184 (08S01): Aborted connection 22 to db. This error usually occurs after a successful login but before executing any command if you've set an incorrect value for the init_connect parameter. This can prevent the session from initializing properly.

    Here are some steps you can try to resolve this issue:

    1. Access the Azure Portal: Log in to your Azure Portal.
    2. Navigate to Your MySQL Resource: Go to the specific instance of your Azure Database for MySQL.
    3. Server Parameters: On the Server parameters tab, look for the init_connect parameter.
    4. Reset the Parameter: If you have set a value there, reset it to the default or a supported value. Make sure to only use values that are supported for init_connect.
    5. Restart the Database: Once you've made the changes, attempt to restart your database.

    After resetting the parameter and restarting, try to access your database again.

    If this doesn’t resolve your issue or if you face difficulties with any step, please provide more details:

    • What specific error message are you seeing when trying to access the database?
    • Have you made any recent changes to the database settings or user permissions?
    • Is this issue affecting all users or just specific ones?

    Hope this helps, and I look forward to hearing back from you!

    References:


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.