Error 21776 SQL DMO - nothing found on technet

Question

Error 21776 SQL DMO - nothing found on technet

jvElecenter

SSCarpal Tunnel

Points: 4502
More actions
June 23, 2004 at 9:09 am

#84824

Hi
I can't c the publication under publications anymore, but it's still on the replication monitor. When I ask it's properties, then I receive the follwoing error :
SQL Server Enterprise Manager could not retrieve information about publication ‘X’.

Error 21776 SQL-DMLO The name Essent was not found in the transpublications collection. If the name is a qualified name, us [] to separate various parts of the name and try again.
When I want to add a new publication i get an error that there still is a subscription so that it can't be created.
Can anyone offer any help ? It's SQL 2000, SP 3.
Thx
Jef

JV

Viewing 15 posts - 1 through 14 (of 14 total)

You must be logged in to reply to this topic. Login to reply

TriggerMe SSChampion Points: 11752 More actions · Answer 1

Yes! I have seen this before. It's because you tried to remove replication inappropriately or you truied to restore the Database when it was marked for replication. What you have to do is remove replication all together and start again!

Kindest Regards,

RHale SSC Enthusiast Points: 182 More actions · Answer 2

These stored procs will remove lingering replication systems settings on both the subscriber and the publisher's sides of replication.

Run on Subscriber Server.

Run sp_RemoveDBReplication "[Subscriber Database Name]"

Run on Publisher Server.

Run sp_RemoveDBReplication "[Publisher Database Name]"

============================
Richard S. Hale
Senior Database Marketing Developer
Business Intelligence
The Scooter Store
RHale@TheScooterStore.com
DSK: 830.627.4493

jvElecenter SSCarpal Tunnel Points: 4502 More actions · Answer 3

Hi it seemed to work, but it didn't.

The strange thing is, I can't see the publication in the replication folder, but I can see it in the replication monitor.

How can that be ?

Thx

Jef

JV

jl SSC Veteran Points: 228 More actions · Answer 4

JV,

Did you solve the problem? I am having same issue...

Jenny

Matthew Koo Grasshopper Points: 10 More actions · Answer 5

Yes, I had this exact same problem also and fixed it using Old Hand's solution of removing all replication and setting up everything again.

archana krishnan-380527 SSC Veteran Points: 207 More actions · Answer 6

I also faced the same issue last week and as usual did a proper cleanup of replication and reset it back again. This did the trick.

Infact even before this error, my publisher was marked as a Distributor (Dunno why!!) because of which I was unable to drop replication also

After some testing etc, I found that in msdb..MSdistributiondbs , the name of Distributor was actually the name of my Publisher. I took a chance to update this name with the name of Distributor db after which I was able to drop replication atleast..

I hope it helps others.

jchen-398834 SSC Enthusiast Points: 184 More actions · Answer 7

Hello All,

I got this error 21776 from security login Of EM. When I only tried to give the user access database and role from property, the error 21776 poped out. Anyone can help?

Thank,

Jchen

jvElecenter SSCarpal Tunnel Points: 4502 More actions · Answer 8

Try this one :

http://www.cryer.co.uk/brian/sqlserver/error21776.htm

Did you copy the database ?

Good luck !

JV

jchen-398834 SSC Enthusiast Points: 184 More actions · Answer 9

JV,

Thank you for your link, I learned some from there.

Jchen

jchen-398834 SSC Enthusiast Points: 184 More actions · Answer 10

I tried to trace to table, but the textdata field size is limited, it couldn't collect whole select script or exec sproc informations. Is any way I can reset textdata size for profiler trace?

Jchen

Carlos-221009 Grasshopper Points: 19 More actions · Answer 11

Hi, I'm having the same problem getting the error 21776 SQL-DMLO The name XXXX was not found in the transpublications collection. If the name is a qualified name, us [] to separate various parts of the name and try again.

I tried Run sp_RemoveDBReplication "[Publisher Database Name]" but nothing happened.

How could you solve that? What is the "Old Hand's solution" ??

Thanks in advance

Hasib - MCP SSC Veteran Points: 216 More actions · Answer 12

Try deleting user account and then recreating it. Do this with SQL rather than via Enterprise Manger. The following sequence cured the problem on the server where it was observed (although it is not clear at which point the problem went away):

use MASTER

go

exec sp_revokedbaccess 'ACCOUNT'

exec sp_revokelogin 'DOMAIN\ACCOUNT'

go

use DATABASE

go

exec sp_revokedbaccess 'ACCOUNT'

exec sp_revokelogin 'DOMAIN\ACCOUNT'

exec sp_grant login 'DOMAIN\ACCOUNT'

exec sp_defaultdb 'DOMAIN\ACCOUNT','DATABASE'

exec sp_grantdbaccess 'DOMAIN\ACCOUNT', 'ACCOUNT'

go

where ‘ACCOUNT’ is the name of the user account, ‘DOMAIN’ is the name of the NT domain in which the account is defined and and ‘DATABASE’ is the name of the database that the user is to have access.

Roy Ernest SSC-Dedicated Points: 38780 More actions · Answer 13

Hasib - MCP (8/6/2009)
Try deleting user account and then recreating it. Do this with SQL rather than via Enterprise Manger. The following sequence cured the problem on the server where it was observed (although it is not clear at which point the problem went away):
use MASTER
go
exec sp_revokedbaccess 'ACCOUNT'
exec sp_revokelogin 'DOMAIN\ACCOUNT'
go
use DATABASE
go
exec sp_revokedbaccess 'ACCOUNT'
exec sp_revokelogin 'DOMAIN\ACCOUNT'
exec sp_grant login 'DOMAIN\ACCOUNT'
exec sp_defaultdb 'DOMAIN\ACCOUNT','DATABASE'
exec sp_grantdbaccess 'DOMAIN\ACCOUNT', 'ACCOUNT'
go
where ‘ACCOUNT’ is the name of the user account, ‘DOMAIN’ is the name of the NT domain in which the account is defined and and ‘DATABASE’ is the name of the database that the user is to have access.

I fail to understand what a user account has got to do with a replication issue. This seems to be an issue with not removing replication properly.

-Roy

1987.santhosh Newbie Points: 7 More actions · Answer 14

Hi,

Even I have observed the same problem. I got this problem in SQL server 2000, after changing some attributes using SQL Server Client 2005(Especially database access values). Can anyone get me the official link from microsoft for this problem

Thanks in advance..

Santhu..