Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Cant find remote Service


Cant find remote Service

Author
Message
Simha24
Simha24
SSC-Enthusiastic
SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)

Group: General Forum Members
Points: 106 Visits: 319
Hi Guys,
I am new to service broker tech. But many errors are triggering and saying remote service not pickingup.and my Error log is increasing haveily.


Description:
The query notification dialog on conversation handle '{66D0DCEF-F261-E111-8B0D-0026557FD35C}.' closed due to the following error: '<?xml version="1.0"?><Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8490</Code><Description>Cannot find the remote service 'SqlQueryNotificationService-04fbdb53-5e63-4ba2-b048-e5421866cb9f' because it does not exist.</Description></Error>'.

what i need to trouble shoot. Is box restarting will give solution for this.
becauses we havent restart our box from 2010 onwards. what is permanent fix for this....
Nils Gustav Stråbø
Nils Gustav Stråbø
SSCrazy
SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)

Group: General Forum Members
Points: 2013 Visits: 3575
Ok, so you haven't rebooted this server since 2010, means you haven't patched anything. NOT GOOD!!

Regarding you problem; this is a know bug, and MS shipped a fix in 2008.http://support.microsoft.com/kb/958006
janetkeith
janetkeith
Grasshopper
Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)

Group: General Forum Members
Points: 10 Visits: 65
Well, I have a brand new box/install: (thus, your response of "you haven't rebooted since 2010 won't hold water...")

Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64) Jun 28 2012 08:36:30 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

My logs are FULL of this message regarding "service broker and conversation handle closing..cannot find the remote service...because does not exist.. code 8490...blah blah"

This is an OTS application that is installed on an application server that uses service broker.

I've been researching WHY I am getting these error messages to no avail. All I seem to find is "it's a bug.."

The application is not working properly yet and am still trying to figure out with the vendor where the issue is and am trying to figure out why I am getting this BUG that appears to have been fixed lightyears ago...

Just wanted to state: your response was pretty useless.
Nils Gustav Stråbø
Nils Gustav Stråbø
SSCrazy
SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)

Group: General Forum Members
Points: 2013 Visits: 3575
Look yourself in the mirror and ask how useful or polite it is to answer a post 15 months later with a rude comment. You won't get much help around here with that kind of attitude.
blehner
blehner
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 6
Do you happen to use SqlDependency to communicate with the Service Broker? I ask because I have been fighting to resolve the same error in my application. This happens when the SqlDependency is stopped and there are unfired dependencies still registered with the database. So far, it has sounded like this is a known issue with SqlDependency. I am currently looking for a way to remove these, and so far I have come up with running the following before starting a new SqlDependency:

KILL QUERY NOTIFICATION SUBSCRIPTION ALL;

It would be more effective once I work through how to determine which ones are orphaned and only kill those. Note you will need sysadmin privileges to execute the above command.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search