The Service Broker protocol transport cannot listen on port 1433 because it is in use by another process. ![]() In fact, I see this message in my errorlog: I haven't worked much with endpoints for Service Broker, but from what I can make out configuring a Service Broker endpoint to use 1433 (when that port is used by a default instance) is incorrect. Get the error with state 12 just like you did. I realise now that I had a brainfart - I made my login attempt from the local machine. I made an attempt last night with creating a Service Broker endpoint, but when I tried to log in with a low-priv user it worked. Great to hear that you were able to solve the problem! TSQL Local Machine- 2 1 -4 SHARED_MEMORY 2 -TSQL- 0 STARTED 0 ![]() I do know when I use the user that doesn't work, I can't pull back database using the browse. I checked the Connection Properties earlier and didn't notice anything. ![]() I would like to figure out the issue instead of just reinstalling the server.
0 Comments
Leave a Reply. |