Switch to the Bing Ads Community
Switch to the Microsoft Advertising Community
Grow your business by advertising on Bing, Yahoo! Search and our syndicated search partners!
Trouble logging in? Need help with managing your account?
Contact Bing Ads Support now.
Oops! We've encountered an error. Wait a few minutes and try again.
Details: Error 1205, level 13, state 47, Procedure CreateKeywordBackup, Line9, Message: Transaction (Process ID 59) Was deadlocked on lock resources with another process and has been chosen as the deadlock victim.
Sounds like the MSN hamster fell off the wheel...
This error occurs when Microsoft® SQL Server™ encounters a deadlock. A deadlock occurs when two (or more) processes attempt to access a resource that the other process holds a lock on. Because each process has a request for another resource, neither process can be completed. When a deadlock is detected, SQL Server rolls back the command that has the least processing time and returns error message 1205 to the client application. This error is not fatal and may not cause the batch to be terminated.
Please refer to the following link for more information:
I hope this helps!
Muñeca Aldarondo - Support Specialist
So you send me to a Microsoft SQL debugging page? I'm not a developer for adcenter desktop, I can't fix this...
Every other click triggers this error. I don't care if the error is fatal or not, It makes the software unusable.
Can you try the following and let me know if that makes a difference:
Open file Microsoft.AdvertisingDesktop.exe.config and change the following 2 settings to false:
<add key="EnableRuleEngine" value="false" />
<add key="EnableDashboard" value="false" />
The file is in %LOCALAPPDATA%\Microsoft adCenter.
This is trying to pinpoint what's causing this (since I cannot repro).
You may want to change the values back to true after testing this change. Let me know how that works.
I tried the above and got a couple different errors:
#1205, level 13, state 47, Procedure CreateKeywordBackup, Line9, Message: Transaction (Process ID 62) Was deadlocked on lock resources with another process and has been chosen as the deadlock victim.
# 309981046 "The join order has been enforced because a local join hint is used."
That would rule out that it's caused by either these:-(. Unfortunately I'm unable to repro to pinpoint the cause.
- Does this error happen only at startup of Desktop or after you leave the machine idle for a while?
- if you repeat the change you made does the error go away 2nd attempt?
- Are you using the latest Desktop version?
I've been able to repro this issue today sporadically and will try to find cause and find a fix for next release.
Sorry for any inconvenience. For now best to retry the operation or restart Desktop.
I've found the cause is that 2 duplicate update requests are send to DB and one will fail as expected. So 1 update will succeed and the error can be ignored. I suspect the issue does not occur when you use the lower edit pane instead.
We'll fix this in future release.