Deadlocked transaction error in AC7 Error Log

[AbleMods]

Anyone ever seen this one or have any sugggestions?

Transaction (Process ID 71) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Several showed up in the event log today during the afternoon. I've seen them before, not sure when though.

[batmike]

I've gotten those before too ... actually a few just this weekend, as well. I've haven't looked into it at this point, though, so I'd be interested if anyone has any ideas too.

Mike

[jmestep]

I haven't seen any in my error log, but I used to get locks in Able 5 where a malicious spider was running the site. I didn't get them much after Able put patches for spider handling. Joe, since the SQL server is on your own box, you might be able to monitor it better than those of us on shared servers.

[WylieE]

I've encountered about a dozen of those in the past week. I had presumed it was because we have our SQL guy, web graphics guy and myself flogging our development server. (With our dev server being a bit antiquated....)

[AbleMods]

I've encountered about a dozen of those in the past week. I had presumed it was because we have our SQL guy, web graphics guy and myself flogging our development server. (With our dev server being a bit antiquated....)

I would blame the web graphics guy. You really can't trust those creative types.....

[Shopping Cart Admin]

Hello All,

From development:

The error shows up in the error log, but this particular error would best be classified as "warning" or "info". The process will be retried at the next maintenance interval. This probably shows up during periods of heavy traffic where user accounts are being created and the delete operation cannot obtain a lock to remove records.

Based on the following information found in the applog:

ERROR 2008-08-20 15:09:01,685 4262499ms Object a
- Error in user maintenance
System.Data.SqlClient.SqlException: Transaction (Process ID 51) was deadlocked on lock | generic waitable object resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult
result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.Practices.EnterpriseLibrary.Data.Database.DoExecuteNonQuery(DbCommand
command)
at Microsoft.Practices.EnterpriseLibrary.Data.Database.ExecuteNonQuery(DbCommand
command)
at CommerceBuilder.Utility.MaintenanceWorker.f()
at CommerceBuilder.Utility.MaintenanceWorker.RunMaintenance(

[WylieE]

Mike,

Can you elaborate on these maintenance processes? We continue to get a few of these deadlock errors every day and cannot afford to have our customers see a big screen full of an error message.

Is there anything we can do to eliminate these?

Here's the most recent error. Copied from the log file:
System.Data.SqlClient.SqlException: Transaction (Process ID 53) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.Practices.EnterpriseLibrary.Data.Database.DoExecuteNonQuery(DbCommand command)
at Microsoft.Practices.EnterpriseLibrary.Data.Database.ExecuteNonQuery(DbCommand command)
at CommerceBuilder.Utility.MaintenanceWorker.f()
at CommerceBuilder.Utility.MaintenanceWorker.RunMaintenance()

[draneb]

Hello,

I have started getting these in my error logs like crazy.

I noticed a customer just tried submitting an order and this came through at the same time:

Unhandled exception during checkout. Transaction (Process ID 119) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Her order status remains Unpaid/Unprocessed

I went into the Payments tab and clicked on "Authorize Payment" and it submitted.

So, it seems to have something to do with checking out. That scares me... Any idea as to what is going on?

Thank you.

[jmestep]

When it happened to us, it was usually when a spider was running the site and the database couldn't handle all the transactions that fast. We didn't have it in 5.5 after some of the performance mods were put in and I'm sure Able would have incorporated those in Able 7. It could have been some kind of problem on your SQL Server and the network.

[Logan Rhodehamel]

I have started getting these in my error logs like crazy.

Can you put that into numbers? Like you get one a day, one an hour, etc?

Unhandled exception during checkout. Transaction (Process ID 119) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Were there any other error messages around it? I assume this error was in the online error log?

[draneb]

Hello,

Here are the last three I have in the admin error log. So these were about 3-4 hours apart. I haven't gotten any today knock on wood. I did email my hosting company this morning and showed them the errors and asked if they could reboot the server (and SQL server)... only because that's usually what fixes things over here


11/26/2008 3:44:12 AM Error Unhandled exception during checkout. Transaction (Process ID 119) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
11/26/2008 12:02:58 AM Error Unhandled exception during checkout. Transaction (Process ID 86) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
11/25/2008 9:42:22 PM Error Unhandled exception during checkout. Transaction (Process ID 58) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

[draneb]

Hello,

I got another one last night. I've never seen one that mentioned adding an order note.

11/27/2008 8:06:16 PM Warn Could not add order note regarding authorization. Transaction (Process ID 99) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

I have no idea what the error means but based on the replies above it doesn't sound serious. Just thought I would share the info.

[mazhar]

11/27/2008 8:06:16 PM Warn Could not add order note regarding authorization. Transaction (Process ID 99) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Well the message means two processes tried to access a resource same time and system killed one of them to avoid dead lock.

[draneb]

Hey guys and gals,

This deadlock victim thing is just annoying and I notice everytime it happens the customer's order gets put under "New". If I go into the order and click on Payments all the credit card information is there. So I click on "Authorize Payment" and I can get it to process.

1) I wonder what kind of screen the customer sees when this happens?
2) Can the Process ID be traced back to anything?
3) It appears most of these happened to customers trying to submit payments. I use Authorize.net...

Any tips or advice would definitely be appreciated. Thanks!

11/30/2008 7:32:21 PM Error Error in user maintenance Transaction (Process ID 151) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

11/30/2008 7:32:19 PM Error Error in user maintenance Transaction (Process ID 164) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

11/30/2008 7:32:14 PM Error Error in user maintenance Transaction (Process ID 82) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

11/30/2008 4:06:36 PM Error Unhandled exception during checkout. Transaction (Process ID 126) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

11/30/2008 12:47:40 PM Error Unhandled exception during checkout. Transaction (Process ID 53) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

11/29/2008 4:19:09 PM Error Unhandled exception during checkout. Transaction (Process ID 134) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

[jmestep]

Are you getting any error emails from about that time? Can you call the customers and find out if they got an error screen?
Did you see any errors from last night/early this morning? (I got 900 error emails from your site caused by a spider with an .ru in the domain name, but I've already deleted them.

[Logan Rhodehamel]

11/30/2008 7:32:21 PM Error Error in user maintenance Transaction (Process ID 151) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Errors during maintenance are no concern, unless they happen consistently and repeatedly. It looks like that particular time around, a new user was being created while the maintenance process wanted to clear out old users. Common causes would be if your site was being spidered while the maintenance was trying to run.

11/29/2008 4:19:09 PM Error Unhandled exception during checkout. Transaction (Process ID 134) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

What kind of daily traffic do you get at your site? Are orders coming in at around the same time as these errors, and is it just the problem order or are there others?

[draneb]

What kind of daily traffic do you get at your site? Are orders coming in at around the same time as these errors, and is it just the problem order or are there others?

Hi Logan,

Well I only have the AC stats in the admin to go by. It shows pretty consistantly around 9,000 to 10,500 page views per day.

All of the ones I have seen today had to deal with the user maintenance, which you mentioned are no concern.
I have noticed that the orders are coming in at the same time as these errors.

It's so strange because when it happens I can go into the admin and the payment information is there, just not authorized.
PS - I use Authorize.net to process payments. I just select "Authorize Payment" in the AC Admin and it changes the order from New to Paid In Full.

Could Authorize.net be causing any of these issues?

Thank you.

[WylieE]

11/30/2008 7:32:21 PM Error Error in user maintenance Transaction (Process ID 151) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Errors during maintenance are no concern, unless they happen consistently and repeatedly. It looks like that particular time around, a new user was being created while the maintenance process wanted to clear out old users. Common causes would be if your site was being spidered while the maintenance was trying to run.


What kind of daily traffic do you get at your site? Are orders coming in at around the same time as these errors, and is it just the problem order or are there others?

We are getting regular deadlock errors on our development site. As this is not accessable outside our building, we can be fairly certain webcrawler and significant orders are not the culprit. We have a small staff and no more than 6 - 8 people at a time are accessing the site.

[Logan Rhodehamel]

We are getting regular deadlock errors on our development site.

Can you post a sample of the errors and indicate the frequency? Are the deadlock errors primarily regarding maintenance?

[WylieE]

The overwhelming majority of the errors have come from user maintenance.

Code: Select all

10/28/2008 12:21:24 PM Error Error in user maintenance Transaction (Process ID 58) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. 

As the number of people using our dev site increase, we are also beginning to see transaction deadlock errors in VisionCore as well. My concern is the errors will only increase as more of our company uses the system. This gives me much concern as we grow closer to rollout.

Thanks,

[Logan Rhodehamel]

The overwhelming majority of the errors have come from user maintenance.

The user maintenance process is trying to delete records - it can't do that if there is other activity going on. Bug 7116 is entered to look at reducing errors during this process. I have updated it to note that user maintenance is a specific concern.

[Logan Rhodehamel]

For anyone that has a full installation of SQL server, don't hesitate to use SQL profiler and the database tuning wizard to check for any indexes that the server thinks would help. Depending on your data the tool may have different suggestions that can improve situations like this.

[WylieE]

For anyone that has a full installation of SQL server, don't hesitate to use SQL profiler and the database tuning wizard to check for any indexes that the server thinks would help. Depending on your data the tool may have different suggestions that can improve situations like this.

We'll check it out. Logan, since I have only a basic familiarity with SQL Profiler, can you make any suggestions to things to trace or not trace?

Thanks.

[bhill]

We are getting these constantly, here is just a piece of hundreds of the errors. Heavy traffic too 27,000 page views perday:
12/9/2008 10:35:06 PM Error Error in user maintenance Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
12/9/2008 10:35:04 PM Error Error in user maintenance Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
12/9/2008 10:35:04 PM Error Error in user maintenance Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
12/9/2008 10:34:59 PM Error Error in user maintenance Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
12/9/2008 10:34:48 PM Error Error in user maintenance Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
12/9/2008 10:34:30 PM Error Error in user maintenance Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
12/9/2008 10:34:29 PM Error Error in user maintenance Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
12/9/2008 10:34:29 PM Error Error in anonymous checkout maintenance Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
12/9/2008 10:34:28 PM Error Error in anonymous checkout maintenance Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
12/9/2008 10:33:56 PM Error Error in user maintenance Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
12/9/2008 10:33:55 PM Error Error in user maintenance Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
12/9/2008 10:27:18 PM Error Error in user maintenance Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
12/9/2008 10:26:23 PM Error Error in user maintenance Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

[compunerdy]

I just started getting these over the last few days..

12/19/2008 9:13:38 AM Error Error in user maintenance Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
12/19/2008 9:13:38 AM Error Error in user maintenance Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.