Invisible Replications

We have
Database A.
Database A Training
Database B
"Database A Training" was a copy of "Database A" 6 months ago.
Since then "Database A Training" has had replications set up to "Database B".
Last night a collegue decided that "Database A Training" needed updating and
so backed up "Database A" and then restored that backup over the top of
"Database A Training".
When I open the new "Database A Training" all the replications are gone.
This is not a problem as we were thinking of dispensing with most of them
anyway and the one I wanted is easy to recreate.
However when I now go to Replication Monitor all the old replications are
still showing and one of them is showing the big red X (OK, white X in red
circle) that shows something has failed.
When I right click - Delete I get the following message.
"SQL Server Enterprise Manager could not retrieve information about
publication 'XYZ'.
Error 21776: [SQL-DMO]The name 'XYZ' was not found in the TransPublications
collection. If the name is a qualified anem, use [] to separate various
parts of the name, and try again.
All I want to do is delete them and learn why this happened. I don't care
about recovering any information about them.
Your help is, as always, appreciated.
Derek
is this merge or transactional?
The best thing to do here is to restore the database again, this time using
the keep_replication switch. Then drop the publication using the GUI.
I'd also check the metadata tables to see if there is anything lingering
there.
You'll probably find some rows in syssubscriptions and sysmergesubscriptions
which you can delete.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Derek" <Derek@.discussions.microsoft.com> wrote in message
news:4FBE6B8B-8083-45DB-BD3F-6D9ACC1B8FE1@.microsoft.com...
> We have
> Database A.
> Database A Training
> Database B
> "Database A Training" was a copy of "Database A" 6 months ago.
> Since then "Database A Training" has had replications set up to "Database
B".
> Last night a collegue decided that "Database A Training" needed updating
and
> so backed up "Database A" and then restored that backup over the top of
> "Database A Training".
> When I open the new "Database A Training" all the replications are gone.
> This is not a problem as we were thinking of dispensing with most of them
> anyway and the one I wanted is easy to recreate.
> However when I now go to Replication Monitor all the old replications are
> still showing and one of them is showing the big red X (OK, white X in red
> circle) that shows something has failed.
> When I right click - Delete I get the following message.
> "SQL Server Enterprise Manager could not retrieve information about
> publication 'XYZ'.
> Error 21776: [SQL-DMO]The name 'XYZ' was not found in the
TransPublications
> collection. If the name is a qualified anem, use [] to separate various
> parts of the name, and try again.
> All I want to do is delete them and learn why this happened. I don't care
> about recovering any information about them.
> Your help is, as always, appreciated.
> Derek
|||Transactional. I'll let you know how this goes.
"Hilary Cotter" wrote:

> is this merge or transactional?
> The best thing to do here is to restore the database again, this time using
> the keep_replication switch. Then drop the publication using the GUI.
> I'd also check the metadata tables to see if there is anything lingering
> there.
> You'll probably find some rows in syssubscriptions and sysmergesubscriptions
> which you can delete.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Derek" <Derek@.discussions.microsoft.com> wrote in message
> news:4FBE6B8B-8083-45DB-BD3F-6D9ACC1B8FE1@.microsoft.com...
> B".
> and
> TransPublications
>
>
|||syssubscriptions and sysmergesubscriptions didn't show anything.
However when I restored an old copy of the training database (that had the
replications), I could then delete them all.
Thanks for all your help.
Derek
"Derek" wrote:
[vbcol=seagreen]
> Transactional. I'll let you know how this goes.
> "Hilary Cotter" wrote:

Invalid Instance Name while trying to install MSDE

I am running XP SP2. I have downloaded MSDE (SQL Sever 2000) to put on my
laptop for training purposes. When I try to load the setup program I get an
error message saying "The Instance Name Specified Is Invalid" and then when I
acknowledge the message the install exits. I have searched for and tried to
understand the post that seem to relate to my problem but I am just not
knowledgable enough to understand what to do. If someone would please tell me
(in baby steps) how to fix this problem so I can install MSDE then I would
really appreciate it. If you need ANY additional information please feel free
to contact me and I will respond immediately. Your time and attention is very
much appreciated.
Thank you for your help...premium001
Read into the readme file in your extracted folder.
If there is an instance of SQL Server already installed, the MSDE should be
named.
"premium001" wrote:

> I am running XP SP2. I have downloaded MSDE (SQL Sever 2000) to put on my
> laptop for training purposes. When I try to load the setup program I get an
> error message saying "The Instance Name Specified Is Invalid" and then when I
> acknowledge the message the install exits. I have searched for and tried to
> understand the post that seem to relate to my problem but I am just not
> knowledgable enough to understand what to do. If someone would please tell me
> (in baby steps) how to fix this problem so I can install MSDE then I would
> really appreciate it. If you need ANY additional information please feel free
> to contact me and I will respond immediately. Your time and attention is very
> much appreciated.
> --
> Thank you for your help...premium001
|||hi,
premium001 wrote:
> I am running XP SP2. I have downloaded MSDE (SQL Sever 2000) to put
> on my laptop for training purposes. When I try to load the setup
> program I get an error message saying "The Instance Name Specified Is
> Invalid" and then when I acknowledge the message the install exits. I
> have searched for and tried to understand the post that seem to
> relate to my problem but I am just not knowledgable enough to
> understand what to do. If someone would please tell me (in baby
> steps) how to fix this problem so I can install MSDE then I would
> really appreciate it. If you need ANY additional information please
> feel free to contact me and I will respond immediately. Your time and
> attention is very much appreciated.
as <zhaounknown> already wrote, please read the proviede ReadmeFile... it
explains you have to provide a set of parameters to the setup.exe boostrap
installer..
typically you have to provide the SAPWD="your strong password" as you are
forced to protect "sa" login ...
you can specify if you like to enable network connections
(DISABLENETWORKPROTOCOLS=0), if you like to permit standard SQL Server
authenticated connections (SECURITY MODE=SQL) as the default does not permit
them to be authenticated, or if you like to install a named instance
(INSTANCENAME="the name").. and please enable verbose logging of the
installation task providing the /L*v "c:\Msde.txt" parameter, which results
in an about 2Mb text file you can inspect for
RETURN VALUE 3
entries indicating troubles... about 10/20 lines before and/or after each
entry some (sometime cryptic) description of the problem will be logged..
so, if you like to install a named instance (named "MSDE") with enabled
networkprotocols and enabling SQL Server authenticated connections you have
to provide something similar to
C:\MSDERelaA\>setup.exe INSTANCENAME="MSDE" SECURITY MODE=SQL
DISABLENETWORKPROTOCOLS=0 SAPWD="your strong password" /L*v "c:\Msde.txt"
all on the same line from the command promt
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply