1. After Effect Error Crash In Progress . Last Logged Message Was 9160 N
2. After Effect Error Crash In Progress . Last Logged Message Was 9160 10
3. After Effect Error Crash In Progress . Last Logged Message Was 9160 Today
4. After Effect Error Crash In Progress . Last Logged Message Was 9160 J

APPLIES TO: Azure SQL Database Azure SQL Managed Instance

You receive error messages when the connection to Azure SQL Database or Azure SQL Managed Instance fails. These connection problems can be caused by reconfiguration, firewall settings, a connection timeout, incorrect login information, or failure to apply best practices and design guidelines during the application design process. Additionally, if the maximum limit on some Azure SQL Database or SQL Managed Instance resources is reached, you can no longer connect.

Transient fault error messages (40197, 40613 and others)

After effects error: crash in progress, last logged message was:BEEProject::TimestampGetNext ZANZIBAR-3: cannot produce Timestamp,frozen=0, open=0. Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. After Effects error crash in progress fix. If you were working in after effects and you see this message ' After Effects Error: Crash in progress.

The Azure infrastructure has the ability to dynamically reconfigure servers when heavy workloads arise in the SQL Database service. This dynamic behavior might cause your client program to lose its connection to the database or instance. This kind of error condition is called a transient fault. Database reconfiguration events occur because of a planned event (for example, a software upgrade) or an unplanned event (for example, a process crash, or load balancing). Most reconfiguration events are generally short-lived and should be completed in less than 60 seconds at most. However, these events can occasionally take longer to finish, such as when a large transaction causes a long-running recovery. The following table lists various transient errors that applications can receive when connecting to SQL Database

List of transient fault error codes

Steps to resolve transient connectivity issues

1. Check the Microsoft Azure Service Dashboard for any known outages that occurred during the time during which the errors were reported by the application.
2. Applications that connect to a cloud service such as Azure SQL Database should expect periodic reconfiguration events and implement retry logic to handle these errors instead of surfacing application errors to users.
3. As a database approaches its resource limits, it can seem to be a transient connectivity issue. See Resource limits.
4. If connectivity problems continue, or if the duration for which your application encounters the error exceeds 60 seconds or if you see multiple occurrences of the error in a given day, file an Azure support request by selecting Get Support on the Azure Support site.

Implementing Retry Logic

It is strongly recommended that your client program has retry logic so that it could reestablish a connection after giving the transient fault time to correct itself. We recommend that you delay for 5 seconds before your first retry. Retrying after a delay shorter than 5-seconds risks overwhelming the cloud service. For each subsequent retry the delay should grow exponentially, up to a maximum of 60 seconds.

For code examples of retry logic, see:

For additional information on handling transient errors in your application review Troubleshooting transient connection errors to SQL Database

A discussion of the blocking period for clients that use ADO.NET is available in Connection Pooling (ADO.NET).

A network-related or instance-specific error occurred while establishing a connection to your server

The issue occurs if the application can't connect to the server.

To resolve this issue, try the steps (in the order presented) in the Steps to fix common connection issues section.

The server/instance was not found or was not accessible (errors 26, 40, 10053)

Error 26: Error Locating server specified

System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.(provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified)

Error 40: Could not open a connection to the server

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Error 10053: A transport-level error has occurred when receiving results from the server

10053: A transport-level error has occurred when receiving results from the server. (Provider: TCP Provider, error: 0 - An established connection was aborted by the software in your host machine)

These issues occur if the application can't connect to the server.

To resolve these issues, try the steps (in the order presented) in the Steps to fix common connection issues section.

Cannot connect to server due to firewall issues

Error 40615: Cannot connect to < servername >

To resolve this issue, configure firewall settings on SQL Database through the Azure portal.

Error 5: Cannot connect to < servername >

To resolve this issue, make sure that port 1433 is open for outbound connections on all firewalls between the client and the internet.

Unable to log in to the server (errors 18456, 40531)

Login failed for user '< User name >'

Login failed for user '<User name>'.This session has been assigned a tracing ID of '<Tracing ID>'. Provide this tracing ID to customer support when you need assistance. (Microsoft SQL Server, Error: 18456)

To resolve this issue, contact your service administrator to provide you with a valid user name and password.

Typically, the service administrator can use the following steps to add the login credentials:

1. Log in to the server by using SQL Server Management Studio (SSMS).

2. Run the following SQL query in the master database to check whether the login name is disabled:

3. If the corresponding name is disabled, enable it by using the following statement:

4. If the SQL login user name doesn't exist, edit and run the following SQL query to create a new SQL login:

5. In SSMS Object Explorer, expand Databases.

6. Select the database that you want to grant the user permission to.

7. Right-click Security, and then select New, User.

8. In the generated script with placeholders (sample shown below), replace template parameters by following the steps here and execute it:

   You can also use sp_addrolemember to map specific users to specific database roles.

   Note

   In Azure SQL Database, consider the newer ALTER ROLE syntax for managing database role membership.

For more information, see Managing databases and logins in Azure SQL Database.

Connection timeout expired errors

System.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired

System.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=3; handshake=29995;

System.Data.SqlClient.SqlException (0x80131904): Timeout expired

System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

System.Data.Entity.Core.EntityException: The underlying provider failed on Open

System.Data.Entity.Core.EntityException: The underlying provider failed on Open. -> System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. -> System.ComponentModel.Win32Exception: The wait operation timed out

Cannot connect to < server name >

Cannot connect to <server name>.ADDITIONAL INFORMATION:Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=231; handshake=983; [Login] initialization=0; authentication=0; [Post-Login] complete=13000; (Microsoft SQL Server, Error: -2) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476 The wait operation timed out

After Effect Error Crash In Progress . Last Logged Message Was 9160 N

These exceptions can occur either because of connection or query issues. To confirm that this error is caused by connectivity issues, see Confirm whether an error is caused by a connectivity issue.

Connection timeouts occur because the application can't connect to the server. To resolve this issue, try the steps (in the order presented) in the Steps to fix common connection issues section.

Resource governance errors

Error 10928: Resource ID: %d

10928: Resource ID: %d. The %s limit for the database is %d and has been reached. See http://go.microsoft.com/fwlink/?LinkId=267637 for assistance. The Resource ID value in error message indicates the resource for which limit has been reached. For sessions, Resource ID = 2.

To work around this issue, try one of the following methods:

• Verify whether there are long-running queries.

  Note

  This is a minimalist approach that might not resolve the issue. For more thorough information on troubleshooting long running or blocking queries, see Understand and resolve Azure SQL Database blocking problems.

1. Run the following SQL query to check the sys.dm_exec_requests view to see any blocking requests:

2. Determine the input buffer for the head blocker using the sys.dm_exec_input_buffer dynamic management function, and the session_id of the offending query, for example:

3. Tune the head blocker query.

If the database consistently reaches its limit despite addressing blocking and long-running queries, consider upgrading to an edition with more resources Editions.

For more information about database limits, see SQL Database resource limits for servers.

Error 10929: Resource ID: 1

10929: Resource ID: 1. The %s minimum guarantee is %d, maximum limit is %d and the current usage for the database is %d. However, the server is currently too busy to support requests greater than %d for this database. See http://go.microsoft.com/fwlink/?LinkId=267637 for assistance. Otherwise, please try again later.

Error 40501: The service is currently busy

40501: The service is currently busy. Retry the request after 10 seconds. Incident ID: %ls. Code: %d.

This is an engine throttling error, an indication that resource limits are being exceeded.

For more information about resource limits, see Logical SQL server resource limits.

Error 40544: The database has reached its size quota

40544: The database has reached its size quota. Partition or delete data, drop indexes, or consult the documentation for possible resolutions. Incident ID: <ID>. Code: <code>.

This error occurs when the database has reached its size quota.

The following steps can either help you work around the problem or provide you with additional options:

1. Check the current size of the database by using the dashboard in the Azure portal.

   Note

   To identify which tables are consuming the most space and are therefore potential candidates for cleanup, run the following SQL query:

2. If the current size does not exceed the maximum size supported for your edition, you can use ALTER DATABASE to increase the MAXSIZE setting.

3. If the database is already past the maximum supported size for your edition, try one or more of the following steps:

   • Perform normal database cleanup activities. For example, clean up the unwanted data by using truncate/delete, or move data out by using SQL Server Integration Services (SSIS) or the bulk copy program (bcp) utility.
   • Partition or delete data, drop indexes, or consult the documentation for possible resolutions.
   • For database scaling, see Scale single database resources and Scale elastic pool resources.

Error 40549: Session is terminated because you have a long-running transaction

40549: Session is terminated because you have a long-running transaction. Try shortening your transaction.

If you repeatedly encounter this error, try to resolve the issue by following these steps:

1. Check the sys.dm_exec_requests view to see any open sessions that have a high value for the total_elapsed_time column. Perform this check by running the following SQL script:

2. Determine the input buffer for the head blocker using the sys.dm_exec_input_buffer dynamic management function, and the session_id of the offending query, for example:

3. Tune the query.

   Note

   For more information on troubleshooting blocking in Azure SQL Database, see Understand and resolve Azure SQL Database blocking problems.

Also consider batching your queries. For information on batching, see How to use batching to improve SQL Database application performance.

Error 40551: The session has been terminated because of excessive TEMPDB usage

40551: The session has been terminated because of excessive TEMPDB usage. Try modifying your query to reduce the temporary table space usage.

To work around this issue, follow these steps:

1. Change the queries to reduce temporary table space usage.
2. Drop temporary objects after they're no longer needed.
3. Truncate tables or remove unused tables.

Error 40552: The session has been terminated because of excessive transaction log space usage

40552: The session has been terminated because of excessive transaction log space usage. Try modifying fewer rows in a single transaction.

To resolve this issue, try the following methods:

• The issue can occur because of insert, update, or delete operations.Try to reduce the number of rows that are operated on immediately by implementing batching or splitting into multiple smaller transactions.

• The issue can occur because of index rebuild operations. To work around this issue, make sure the number of rows that are affected in the table * (average size of field that's updated in bytes + 80) < 2 gigabytes (GB).

  Note

  For an index rebuild, the average size of the field that's updated should be substituted by the average index size.

  Note

  For more information on troubleshooting a full transaction log in Azure SQL Database and Azure SQL Managed Instance, see Troubleshooting transaction log errors with Azure SQL Database and Azure SQL Managed Instance.

Error 40553: The session has been terminated because of excessive memory usage

40553 : The session has been terminated because of excessive memory usage. Try modifying your query to process fewer rows.

To work around this issue, try to optimize the query.

For an in-depth troubleshooting procedure, see Is my query running fine in the cloud?.

Table of additional resource governance error messages

Elastic pool errors

The following errors are related to creating and using elastic pools:

Cannot open database 'master' requested by the login. The login failed

This issue occurs because the account doesn't have permission to access the master database. But by default, SQL Server Management Studio (SSMS) tries to connect to the master database.

To resolve this issue, follow these steps:

1. On the login screen of SSMS, select Options, and then select Connection Properties.

2. In the Connect to database field, enter the user's default database name as the default login database, and then select Connect.

Confirm whether an error is caused by a connectivity issue

After Effect Error Crash In Progress . Last Logged Message Was 9160 10

To confirm whether an error is caused by a connectivity issue, review the stack trace for frames that show calls to open a connection like the following ones (note the reference to the SqlConnection class):

When the exception is triggered by query issues, you'll notice a call stack that's similar to the following (note the reference to the SqlCommand class). In this situation, tune your queries.

For additional guidance on fine-tuning performance, see the following resources:

Steps to fix common connection issues

1. Make sure that TCP/IP is enabled as a client protocol on the application server. For more information, see Configure client protocols. On application servers where you don't have SQL tools installed, verify that TCP/IP is enabled by running cliconfg.exe (SQL Server Client Network utility).

2. Check the application's connection string to make sure it's configured correctly. For example, make sure that the connection string specifies the correct port (1433) and fully qualified server name.See Get connection information.

3. Try increasing the connection timeout value. We recommend using a connection timeout of at least 30 seconds.

4. Test the connectivity between the application server and the Azure SQL Database by using SQL Server management Studio (SSMS), a UDL file, ping, or telnet. For more information, see Troubleshooting connectivity issues and Diagnostics for connectivity issues.

   Note

   As a troubleshooting step, you can also test connectivity on a different client computer.

5. As a best practice, make sure that the retry logic is in place. For more information about retry logic, see Troubleshoot transient faults and connection errors to SQL Database.

If these steps don't resolve your problem, try to collect more data and then contact support. If your application is a cloud service, enable logging. This step returns a UTC time stamp of the failure. Additionally, SQL Database returns the tracing ID. Microsoft Customer Support Services can use this information.

After Effect Error Crash In Progress . Last Logged Message Was 9160 Today

For more information about how to enable logging, see Enable diagnostics logging for apps in Azure App Service.

Next steps

After Effect Error Crash In Progress . Last Logged Message Was 9160 J

See also