Set Enable broker failure to use with SignalR

Question

0.00/5 (No votes)

See more:

Hello All.......

I am new in Asp.Net Web development..........

I want to generate database change notification using SignalR, for this, I am using SQL Server 2008 R2.

I am getting failure with following command

ALTER DATABASE SignalRDummy SET ENABLE_BROKER.

It says

"Msg 1205, Level 13, State 68, Line 1
Transaction (Process ID 58) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed."

I have tried

SET DEADLOCK_PRIORITY LOW;

It doesnt work.

Thanks in advance.

Regards.

Posted 13-Aug-15 21:01pm

Member 3153152

Updated 2-Jan-23 17:47pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

MMMMMD · Answer 1 · 2023-01-02T17:47:00

Solution 1

hi, using this query for solve your Problem:
ALTER DATABASE SignalRDummy SET ENABLE_BROKER WITH ROLLBACK IMMEDIATE

Posted 2-Jan-23 17:47pm

MMMMMD

Comments

Dave Kreskowiak 3-Jan-23 0:05am

Considering the database was locked at the time the statement was run, executing your statement would have fallen to the same error.

Also, this was asked seven years ago.