While trying to set up remote distribution on server PUBLISHER_NAME, I
get the above error when trying to specify the remote distributor.
(Error 21776: PUBLISHER_NAME not found in DistributionPublishers
collection on DISTRIBUTOR_NAME)
However, I have set up distribution on DISTRIBUTOR_NAME, and in the
Publishers tab of that window, I have checked the entry for
PUBLISHER_NAME. The alias for that server matches exactly the
PUBLISHER_NAME.
Do I need to restart the SQL Server for this entry to be acknowledged?
Is there some other step of configuration I am missing? Why doesn't the
PUBLISHER_NAME see that it's name is indeed on the authorized publisher
list for DISTRIBUTOR_NAME?
Thanks in advance for any help,
Jason
Its hard to say. Can you connect with your distributor and issue the
following commands for me. Post the results back here.
On your distributor
sp_helpdistpublisher 'RemotePublisherName'
On your remote publisher issue the following
sp_helpdistpublisher 'RemotePublisherName'
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
<iaesun@.yahoo.com> wrote in message
news:1112369037.970196.9940@.l41g2000cwc.googlegrou ps.com...
> While trying to set up remote distribution on server PUBLISHER_NAME, I
> get the above error when trying to specify the remote distributor.
> (Error 21776: PUBLISHER_NAME not found in DistributionPublishers
> collection on DISTRIBUTOR_NAME)
> However, I have set up distribution on DISTRIBUTOR_NAME, and in the
> Publishers tab of that window, I have checked the entry for
> PUBLISHER_NAME. The alias for that server matches exactly the
> PUBLISHER_NAME.
> Do I need to restart the SQL Server for this entry to be acknowledged?
> Is there some other step of configuration I am missing? Why doesn't the
> PUBLISHER_NAME see that it's name is indeed on the authorized publisher
> list for DISTRIBUTOR_NAME?
> Thanks in advance for any help,
> Jason
>
|||i'm very sorry for taking so long to get back to you. i was told to
stop setting up publishing and be a developer for a couple of weeks.
but that's over now, so i am back to this task.
firstly, thank you very much for your help, here are the results you
requested to see:
sp_helpdistpublisher 'RemotePublisherName' run on the distributor
reported:
"The remote server does not exist or has not been designated as a valid
publisher."
sp_helpdistpublisher 'RemoteDistributorName' run on the publisher
reported:
'RemoteDistributorName' is not configured as a Distributor.
however i have verified that on RemoteDistributorName that
RemotePublisherName is listed in the Publishers tab of the "Publisher
and Distrubutor Properties" window, and it is checked as a valid
publisher.
jason
Showing posts with label collection. Show all posts
Showing posts with label collection. Show all posts
Friday, February 17, 2012
Error 21776: [SQL-DMO] The name 'XXXX' was not found in the Users collection
Hello --
We have a SQL Server 2000 machine that has approximately 500 user databases.
Don't ask why -- I did not create this mess.
Anyway, we have about 200 users access the SQL Server as a DSS machine
using SA. We've finally weaned all users off of SA and each have their on
ID per customer.
Tonight, I was finally trying to change the "SA" password from within
Enterprise Manager and received the following message:
Error 21776: [SQL-DMO] The name 'XXXX' was not found in the Users
collection. If the name is a qualified name, use [] to separate various
parts of the name, and try again.
It looks like I'm receiving this message for every database we have.
I brought up another instance of Enterprise Manager and looked at each
database property and noticed that the owner of database was either "SA",
"NT user that happens to be logged into server most of the time", or some
other local SQL Server user.
How do I fix this problem?
All databases should simply belong to DBO and no one inparticular.
The problem is, I have multiple people that create databases and they all
log into the server differenently and use different steps in creating the
database.
Can I simply ignore these error messages?
If I do need to change the owner of all 500 databases, is there an easier
way than manually running sp_changedbowner?
--
...david
http://www.micro-mess.com
http://www.va-mustang.com
If you wish to reply to me personally, please remove
the "underline" from scandal_123@.cox.net. The is done to avoid SPAM!All databases need to be owned by a valid login or you may get errors in
Enterprise Manager. You can use a script below to generate a script that
changes database ownership to the login of your choosing.
SELECT 'EXEC ' +
CATALOG_NAME +
'..sp_changedbowner ''sa'''
FROM INFORMATION_SCHEMA.SCHEMATA
WHERE CATALOG_NAME NOT IN
(
'master',
'model',
'msdb',
'tempdb',
'distribution'
)
--
Hope this helps.
Dan Guzman
SQL Server MVP
"DavidM" <scandal_123@.cox.net> wrote in message
news:uYTjmAcxDHA.2448@.TK2MSFTNGP12.phx.gbl...
> Hello --
> We have a SQL Server 2000 machine that has approximately 500 user
databases.
> Don't ask why -- I did not create this mess.
> Anyway, we have about 200 users access the SQL Server as a DSS machine
> using SA. We've finally weaned all users off of SA and each have their on
> ID per customer.
> Tonight, I was finally trying to change the "SA" password from within
> Enterprise Manager and received the following message:
> Error 21776: [SQL-DMO] The name 'XXXX' was not found in the Users
> collection. If the name is a qualified name, use [] to separate various
> parts of the name, and try again.
> It looks like I'm receiving this message for every database we have.
> I brought up another instance of Enterprise Manager and looked at each
> database property and noticed that the owner of database was either "SA",
> "NT user that happens to be logged into server most of the time", or some
> other local SQL Server user.
> How do I fix this problem?
> All databases should simply belong to DBO and no one inparticular.
> The problem is, I have multiple people that create databases and they all
> log into the server differenently and use different steps in creating the
> database.
> Can I simply ignore these error messages?
> If I do need to change the owner of all 500 databases, is there an easier
> way than manually running sp_changedbowner?
> --
> ...david
> http://www.micro-mess.com
> http://www.va-mustang.com
> If you wish to reply to me personally, please remove
> the "underline" from scandal_123@.cox.net. The is done to avoid SPAM!
>
We have a SQL Server 2000 machine that has approximately 500 user databases.
Don't ask why -- I did not create this mess.
Anyway, we have about 200 users access the SQL Server as a DSS machine
using SA. We've finally weaned all users off of SA and each have their on
ID per customer.
Tonight, I was finally trying to change the "SA" password from within
Enterprise Manager and received the following message:
Error 21776: [SQL-DMO] The name 'XXXX' was not found in the Users
collection. If the name is a qualified name, use [] to separate various
parts of the name, and try again.
It looks like I'm receiving this message for every database we have.
I brought up another instance of Enterprise Manager and looked at each
database property and noticed that the owner of database was either "SA",
"NT user that happens to be logged into server most of the time", or some
other local SQL Server user.
How do I fix this problem?
All databases should simply belong to DBO and no one inparticular.
The problem is, I have multiple people that create databases and they all
log into the server differenently and use different steps in creating the
database.
Can I simply ignore these error messages?
If I do need to change the owner of all 500 databases, is there an easier
way than manually running sp_changedbowner?
--
...david
http://www.micro-mess.com
http://www.va-mustang.com
If you wish to reply to me personally, please remove
the "underline" from scandal_123@.cox.net. The is done to avoid SPAM!All databases need to be owned by a valid login or you may get errors in
Enterprise Manager. You can use a script below to generate a script that
changes database ownership to the login of your choosing.
SELECT 'EXEC ' +
CATALOG_NAME +
'..sp_changedbowner ''sa'''
FROM INFORMATION_SCHEMA.SCHEMATA
WHERE CATALOG_NAME NOT IN
(
'master',
'model',
'msdb',
'tempdb',
'distribution'
)
--
Hope this helps.
Dan Guzman
SQL Server MVP
"DavidM" <scandal_123@.cox.net> wrote in message
news:uYTjmAcxDHA.2448@.TK2MSFTNGP12.phx.gbl...
> Hello --
> We have a SQL Server 2000 machine that has approximately 500 user
databases.
> Don't ask why -- I did not create this mess.
> Anyway, we have about 200 users access the SQL Server as a DSS machine
> using SA. We've finally weaned all users off of SA and each have their on
> ID per customer.
> Tonight, I was finally trying to change the "SA" password from within
> Enterprise Manager and received the following message:
> Error 21776: [SQL-DMO] The name 'XXXX' was not found in the Users
> collection. If the name is a qualified name, use [] to separate various
> parts of the name, and try again.
> It looks like I'm receiving this message for every database we have.
> I brought up another instance of Enterprise Manager and looked at each
> database property and noticed that the owner of database was either "SA",
> "NT user that happens to be logged into server most of the time", or some
> other local SQL Server user.
> How do I fix this problem?
> All databases should simply belong to DBO and no one inparticular.
> The problem is, I have multiple people that create databases and they all
> log into the server differenently and use different steps in creating the
> database.
> Can I simply ignore these error messages?
> If I do need to change the owner of all 500 databases, is there an easier
> way than manually running sp_changedbowner?
> --
> ...david
> http://www.micro-mess.com
> http://www.va-mustang.com
> If you wish to reply to me personally, please remove
> the "underline" from scandal_123@.cox.net. The is done to avoid SPAM!
>
Error 21776: [SQL-DMO] The name 'XXXX' was not found in the Users collection
Hello --
We have a SQL Server 2000 machine that has approximately 500 user databases.
Don't ask why -- I did not create this mess.
Anyway, we have about 200 users access the SQL Server as a DSS machine
using SA. We've finally weaned all users off of SA and each have their on
ID per customer.
Tonight, I was finally trying to change the "SA" password from within
Enterprise Manager and received the following message:
Error 21776: [SQL-DMO] The name 'XXXX' was not found in the Users
collection. If the name is a qualified name, use [] to separate various
parts of the name, and try again.
It looks like I'm receiving this message for every database we have.
I brought up another instance of Enterprise Manager and looked at each
database property and noticed that the owner of database was either "SA",
"NT user that happens to be logged into server most of the time", or some
other local SQL Server user.
How do I fix this problem?
All databases should simply belong to DBO and no one inparticular.
The problem is, I have multiple people that create databases and they all
log into the server differenently and use different steps in creating the
database.
Can I simply ignore these error messages?
If I do need to change the owner of all 500 databases, is there an easier
way than manually running sp_changedbowner?
...david
http://www.micro-mess.com
http://www.va-mustang.com
If you wish to reply to me personally, please remove
the "underline" from scandal_123@.cox.net. The is done to avoid SPAM!All databases need to be owned by a valid login or you may get errors in
Enterprise Manager. You can use a script below to generate a script that
changes database ownership to the login of your choosing.
SELECT 'EXEC ' +
CATALOG_NAME +
'..sp_changedbowner ''sa'''
FROM INFORMATION_SCHEMA.SCHEMATA
WHERE CATALOG_NAME NOT IN
(
'master',
'model',
'msdb',
'tempdb',
'distribution'
)
Hope this helps.
Dan Guzman
SQL Server MVP
"DavidM" <scandal_123@.cox.net> wrote in message
news:uYTjmAcxDHA.2448@.TK2MSFTNGP12.phx.gbl...
databases.
We have a SQL Server 2000 machine that has approximately 500 user databases.
Don't ask why -- I did not create this mess.
Anyway, we have about 200 users access the SQL Server as a DSS machine
using SA. We've finally weaned all users off of SA and each have their on
ID per customer.
Tonight, I was finally trying to change the "SA" password from within
Enterprise Manager and received the following message:
Error 21776: [SQL-DMO] The name 'XXXX' was not found in the Users
collection. If the name is a qualified name, use [] to separate various
parts of the name, and try again.
It looks like I'm receiving this message for every database we have.
I brought up another instance of Enterprise Manager and looked at each
database property and noticed that the owner of database was either "SA",
"NT user that happens to be logged into server most of the time", or some
other local SQL Server user.
How do I fix this problem?
All databases should simply belong to DBO and no one inparticular.
The problem is, I have multiple people that create databases and they all
log into the server differenently and use different steps in creating the
database.
Can I simply ignore these error messages?
If I do need to change the owner of all 500 databases, is there an easier
way than manually running sp_changedbowner?
...david
http://www.micro-mess.com
http://www.va-mustang.com
If you wish to reply to me personally, please remove
the "underline" from scandal_123@.cox.net. The is done to avoid SPAM!All databases need to be owned by a valid login or you may get errors in
Enterprise Manager. You can use a script below to generate a script that
changes database ownership to the login of your choosing.
SELECT 'EXEC ' +
CATALOG_NAME +
'..sp_changedbowner ''sa'''
FROM INFORMATION_SCHEMA.SCHEMATA
WHERE CATALOG_NAME NOT IN
(
'master',
'model',
'msdb',
'tempdb',
'distribution'
)
Hope this helps.
Dan Guzman
SQL Server MVP
"DavidM" <scandal_123@.cox.net> wrote in message
news:uYTjmAcxDHA.2448@.TK2MSFTNGP12.phx.gbl...
quote:
> Hello --
> We have a SQL Server 2000 machine that has approximately 500 user
databases.
quote:
> Don't ask why -- I did not create this mess.
> Anyway, we have about 200 users access the SQL Server as a DSS machine
> using SA. We've finally weaned all users off of SA and each have their on
> ID per customer.
> Tonight, I was finally trying to change the "SA" password from within
> Enterprise Manager and received the following message:
> Error 21776: [SQL-DMO] The name 'XXXX' was not found in the Users
> collection. If the name is a qualified name, use [] to separate various
> parts of the name, and try again.
> It looks like I'm receiving this message for every database we have.
> I brought up another instance of Enterprise Manager and looked at each
> database property and noticed that the owner of database was either "SA",
> "NT user that happens to be logged into server most of the time", or some
> other local SQL Server user.
> How do I fix this problem?
> All databases should simply belong to DBO and no one inparticular.
> The problem is, I have multiple people that create databases and they all
> log into the server differenently and use different steps in creating the
> database.
> Can I simply ignore these error messages?
> If I do need to change the owner of all 500 databases, is there an easier
> way than manually running sp_changedbowner?
> --
> ...david
> http://www.micro-mess.com
> http://www.va-mustang.com
> If you wish to reply to me personally, please remove
> the "underline" from scandal_123@.cox.net. The is done to avoid SPAM!
>
Error 21776: [SQL-DMO] The name XXXX was not found in the Database collection.
Hi,
This is the error that I am getting after an unsuccessfuldatabase attachment.
Error 21776: [SQL-DMO] The name 'XXXX' was not found in the Databasecollection. If the name is a qualified name, use [] to separate various partsof the name, and try again.
Any ideas how can I delete that database?
Thanks
Kind regards,
Gift Peddie
|||Hi,
Yes I did try to move from one server to the current one, the solution was to restore it from an existing backup.
Just wondering if the operation fails, nothing should happen. Any way thanks for the ideas.
|||check if thislink helps.
Labels:
attachment,
collection,
database,
error,
microsoft,
mysql,
oracle,
server,
sql,
sql-dmo,
unsuccessfuldatabase,
xxxx
Subscribe to:
Posts (Atom)