Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Cant find remote Service Expand / Collapse
Author
Message
Posted Thursday, March 22, 2012 7:25 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 6:45 AM
Points: 94, 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....
Post #1270832
Posted Thursday, March 22, 2012 8:23 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 6:32 AM
Points: 1,890, Visits: 3,472
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
Post #1270891
Posted Thursday, June 27, 2013 1:33 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, July 9, 2013 9:03 AM
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.
Post #1468317
Posted Thursday, June 27, 2013 1:54 PM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 6:32 AM
Points: 1,890, Visits: 3,472
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.
Post #1468337
Posted Friday, July 12, 2013 7:13 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, July 17, 2013 9:37 AM
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.
Post #1473005
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse