Error Log Archive

Error reading from database

The multi-part identifier "a.Priority" could not be bound. The multi-part identifier "a.CreatedDateTime" could not be bound.

Error reading from database

The multi-part identifier "a.ISN" could not be bound. The multi-part identifier "a.SequenceNumber" could not be bound. The multi-part identifier "a.ValueDate" could not be bound. The multi-part identifier "a.ValueDate" could not be bound. The multi-part identifier "a.InOut" could not be bound. The multi-part identifier "a.InOut" could not be bound. The column prefix 'a' does not match with a table name or alias name used in the query.

One or more errors occurred. (The client has disconnected)

Error reading from database

The multi-part identifier "h.CrDrFlag" could not be bound.

Error reading from database

Ambiguous column name 'MessageType'.

Error reading from database

Ambiguous column name 'MessageType'. Ambiguous column name 'MessageType'.

Error reading from database

Ambiguous column name 'MessageType'.

A second operation was started on this context instance before a previous operation completed. This is usually caused by different threads concurrently using the same instance of DbContext. For more information on how to avoid threading issues with DbContext, see https://go.microsoft.com/fwlink/?linkid=2097913.

A second operation was started on this context instance before a previous operation completed. This is usually caused by different threads concurrently using the same instance of DbContext. For more information on how to avoid threading issues with DbContext, see https://go.microsoft.com/fwlink/?linkid=2097913.

Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

A second operation was started on this context instance before a previous operation completed. This is usually caused by different threads concurrently using the same instance of DbContext. For more information on how to avoid threading issues with DbContext, see https://go.microsoft.com/fwlink/?linkid=2097913.

A second operation was started on this context instance before a previous operation completed. This is usually caused by different threads concurrently using the same instance of DbContext. For more information on how to avoid threading issues with DbContext, see https://go.microsoft.com/fwlink/?linkid=2097913.

A second operation was started on this context instance before a previous operation completed. This is usually caused by different threads concurrently using the same instance of DbContext. For more information on how to avoid threading issues with DbContext, see https://go.microsoft.com/fwlink/?linkid=2097913.

A second operation was started on this context instance before a previous operation completed. This is usually caused by different threads concurrently using the same instance of DbContext. For more information on how to avoid threading issues with DbContext, see https://go.microsoft.com/fwlink/?linkid=2097913.

Error reading from database

Ambiguous column name 'MessageType'.

Error reading from database

Ambiguous column name 'MessageType'.

Error reading from database

Ambiguous column name 'MessageType'.

Neither 'AzureWebJobsStorage' nor 'AzureWebJobsStorage__accountName' is configured.

Neither 'AzureWebJobsStorage' nor 'AzureWebJobsStorage__accountName' is configured.

Value cannot be null. (Parameter 'connectionString')

Value cannot be null. (Parameter 'connectionString')

Value cannot be null. (Parameter 'connectionString')

Unable to Send Message to Queue

Value cannot be null. (Parameter 'connectionString')

Value cannot be null. (Parameter 'connectionString')

Value cannot be null. (Parameter 'connectionString')

Unable to Send Message to Queue

Response status code does not indicate success: 500 (Internal Server Error).

Response status code does not indicate success: 500 (Internal Server Error).

Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.

Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.

Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.

Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.

Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.

Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.

Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.