Cannot create and start Extended Events session in Azure SQL Managed Instance

Hi @Ganeshkumar R , going through your steps 1-3, I've found that I can restore database from storage account to MI, but I can not back up database to container. Recreated SAS token and credential at MI. Now I can back up databases from MI to container (with copy_only option). So I can read and write to/from storage account, to MI.

Double-checked credential configuration - it is SHARED ACCESS SIGNATURE.

Tried to recreate the session using your T-SQL code step 4 (and pasting my URL), and then starting it - still - getting same error # 25602.

Please see my SAS config:

Not sure if below helps, but here are storage account details:

Performance - Premium

Replication - Locally-redundant storage (LRS)

Account kind - BlockBlobStorage

West US 2

SQL MI:

General Purpose - no zone redundancy

West US 2

What to troubleshoot further ?

It sounds like you've followed the correct steps to set up your Extended Events session in Azure SQL Managed Instance (MI) and have verified that you can read and write to the storage account. However, you're still encountering error #25602 when trying to create or start the Extended Events session. This error typically indicates a problem with the configuration or permissions.

Here are some additional troubleshooting steps you can take to resolve this issue:

1. Validate the Credential

Make sure the credential in your SQL MI matches the URL and SAS token correctly. Use the following query to verify the credential:

SELECT * FROM sys.credentials WHERE name = 'https://yourstorageaccount.blob.core.windows.net/yourcontainer';

The identity should be 'SHARED ACCESS SIGNATURE', and the secret should match your SAS token.

1. Check Storage Account Firewall Settings

Ensure that your storage account firewall settings allow access from your SQL MI. If the storage account has a firewall enabled, you need to allow access from the SQL MI's IP address range.

1. Go to your storage account in the Azure portal.
2. Navigate to Networking.
3. Ensure that the Selected networks option is configured correctly to allow access from your SQL MI.
4. Review Extended Events Session Configuration

Double-check the T-SQL script for creating the Extended Events session. Ensure that the URL in the filename parameter is correctly formatted and points to the correct container and file name.

Here’s an example of what it should look like:

CREATE EVENT SESSION [ErrorReportingSession] ON SERVER

ADD EVENT sqlserver.error_reported(

    ACTION(sqlserver.sql_text, sqlserver.database_id, sqlserver.nt_username)

    WHERE ([severity] >= 16))

ADD TARGET package0.event_file(

    SET filename = 'https://yourstorageaccount.blob.core.windows.net/yourcontainer/Errors.xel',

    max_file_size = 5, max_rollover_files = 2)

WITH (MAX_MEMORY = 4096 KB, EVENT_RETENTION_MODE = ALLOW_SINGLE_EVENT_LOSS, MAX_DISPATCH_LATENCY = 30 SECONDS, MAX_EVENT_SIZE = 0 KB, MEMORY_PARTITION_MODE = NONE, TRACK_CAUSALITY = ON, STARTUP_STATE = OFF);

ALTER EVENT SESSION [ErrorReportingSession] ON SERVER STATE = START;

5. Check SQL MI Version and Compatibility

Ensure that your SQL MI version supports the Extended Events and the required configurations. You can check the version and update if necessary.

SELECT @@VERSION;

6. Enable Diagnostic Logs

Enable diagnostic logs for your storage account to get more information about the operations being performed. This can help identify any access or permission issues.

7. Check for Any Existing Sessions

Make sure there are no existing Extended Events sessions that might be conflicting. List all the existing sessions and their states:

SELECT * FROM sys.server_event_sessions;

SELECT * FROM sys.dm_xe_sessions;

Example Session Validation

-- Verify Credential

SELECT * FROM sys.credentials WHERE name = 'https://yourstorageaccount.blob.core.windows.net/yourcontainer';

-- Check Extended Events sessions

SELECT * FROM sys.server_event_sessions;

SELECT * FROM sys.dm_xe_sessions;

8. Logs and Error Details

Check the SQL Server error log for more details about the error. You can use the following query to access the error log:

EXEC sp_readerrorlog;

By following these additional troubleshooting steps, you should be able to identify and resolve the issue causing the error #25602. If the problem persists, consider reaching out to Azure support for more detailed assistance, as they can provide insights specific to your environment and configuration.

@Ganeshkumar R

• We have validated the credentials, URL and SAS match. We can backup and restore from that storage.
• Storage account allows public access from all networks, no firewall rules
• URL is correct in T-SQL script
• MI version is regular one, MI supports Extended Events according to documentation
• Enabled diagnostic logs for storage account; no records seen in Insights for log analytics workspace
• Existing Extended Events sessions are system ones (system_health, AlwaysOn_health, etc.) - no user created sessions
• sp_readerrorlog only shows "XE session 'ErrorReportingSession' started.", while in fact it is not started. Error #25602 is not logged because is_event_logged = 0

What to do next ? Do you have anyone who can assist

@Ganeshkumar R What to do next ? The problem is not solved - do you have anyone who can assist ?

Aleksey Vitsko Thank you for reaching out.

Seems like this issue will require some troubleshooting. I would suggest creating a support ticket do we can better assist. Do you have a support plan?

Regards,

Oury