Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Service Broker / March 2006

Tip: Looking for answers? Try searching our database.

Error 15404

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Richard - 10 Mar 2006 02:38 GMT
When running the commands below, I receive this message:  An exception
occurred while enqueueing a message in the target queue. Error: 15404,
State: 19. Could not obtain information about Windows NT group/user
'MyLoginDomain\MyUserName', error code 0xea.

DECLARE @h uniqueidentifier --conversation handle
DECLARE @msg xml; --will hold the message

BEGIN DIALOG CONVERSATION @h
FROM SERVICE s1
TO SERVICE 's2'
ON CONTRACT [Ctract];

SET @msg = '<hello/>';
SEND ON CONVERSATION @h
MESSAGE TYPE [sendmsg]
(@msg);

My Windows account is on the root domain, I'm a local admin and a member of
the sysadmin role, I log into SQL Server using Windows authentication, the
SQL Server service is running using my account, and my computer account is a
child domain account, but I don't know if that makes a difference.  I don't
receive that error when logged into an account that is from the same domain
as the computer account (it's someone else's account, so I can't continue to
use it).

I've found quite few blogs, etc, on this error, but nothing to lead me to a
fix yet.  Any ideas?  Something to do with domain trusts?
Remus Rusanu [MSFT] - 10 Mar 2006 04:58 GMT
0xea is ERROR_MORE_DATA. I'll see if I can find more info what could cause
this problem. Personally, I suspect this is caused by a large token, i.e.
one of the involved accounts is member of a many groups in the domain. A
tool like tokensz.exe could be used to confirm or invalidate this.

Assumming that the s1 service is owned by dbo, to fix the problem simply
change the owner of the database from 'domain\user' to a SQL login (i.e.
SA).

ALTER AUTHORIZATION ON DATABASE::[dbname] TO [SA];

or use  sp_changedbowner

In the case when s1 is now owned by dbo but by a different user, change the
owner of the service to an user that is based on a SQL login, using
ALTER AUTHORIZATION ON SERVICE::s1 TO [some-user-created-from-a-sql-login]

Signature

This posting is provided "AS IS" with no warranties, and confers no rights.

HTH,
~ Remus Rusanu

SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx

> When running the commands below, I receive this message:  An exception
> occurred while enqueueing a message in the target queue. Error: 15404,
[quoted text clipped - 24 lines]
> I've found quite few blogs, etc, on this error, but nothing to lead me to
> a fix yet.  Any ideas?  Something to do with domain trusts?
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.