Cannot drop article ''TABLE60'' from publication ''DB_Comp''...

[ Merge Replication ]
I work with a software that the act deletion and creation of the table
and deletion and creation and change of the field by the users happens
so much.
for deletion of the table using this command :
sp_dropmergearticle @.publication='DB_Doc',
@.article = 'TABLE65',
@.force_invalidate_snapshot=1
, but after execute this command displayed below message :
"Cannot drop article 'TABLE65' from publication 'DB_Doc' because its
snapshot has been run and this publication could have active
subscriptions."
how can i drop the table in active merge replication with T-SQL(System
Stored Procedure)?
thanks.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
As far as I know, you can't. The best you can do is synchronize all
subscribers until no change is applied, drop the publication, change the
table on the publisher and subscribers, readd the publication and do a
nosync initialization.
Rgds,
Paul Ibison

Cannot drop an article.

Win 2000 / SQL 2000
In EM, I cannot 'uncheck' an article in a publication. There is a push
subscription from the server that has the publication. Does this need
to be dropped first?
Is there an SP that will do this for me?
AHIA,
Larry...
Let me answer my own question....
sp_droparticle
http://msdn.microsoft.com/library/de...repl2_1qp1.asp
|||You'll need sp_dropsubscription if you've already subscribed.
Rgds,
Paul Ibison
|||Thanks Paul

cannot delete publication

We are using SQL Server 2005 Service Pack 2 on WIn2003.
We lost our distributor and I reinstall SQL Server in Distributor machine.
Now I am not able to delete publication and subscription from publisher and
subscriber.
Any help highly appreciated.
tried
sp_removedbreplication
Msg 3724, Level 16, State 2, Procedure sp_MSdrop_peertopeer_tables, Line 27
Cannot drop the table 'dbo.MSpeer_lsns' because it is being used for
replication.
Thanks
Or I get following error
OLE DB provider "SQLNCLI" for linked server "repl_distributor" returned
message "Communication link failure".
Msg 233, Level 16, State 1, Line 0
Named Pipes Provider: No process is on the other end of the pipe.
"Sandeep Shankar" <sandeeps@.dntg.net> wrote in message
news:%23t%23jvCv0HHA.4236@.TK2MSFTNGP06.phx.gbl...
> We are using SQL Server 2005 Service Pack 2 on WIn2003.
> We lost our distributor and I reinstall SQL Server in Distributor machine.
> Now I am not able to delete publication and subscription from publisher
and
> subscriber.
> Any help highly appreciated.
>
> tried
> sp_removedbreplication
> Msg 3724, Level 16, State 2, Procedure sp_MSdrop_peertopeer_tables, Line
27
> Cannot drop the table 'dbo.MSpeer_lsns' because it is being used for
> replication.
>
> Thanks
>
|||set the ignore_distributor =1 parameter
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
"Sandeep Shankar" <sandeeps@.dntg.net> wrote in message
news:%234MijUv0HHA.4004@.TK2MSFTNGP05.phx.gbl...
> Or I get following error
> OLE DB provider "SQLNCLI" for linked server "repl_distributor" returned
> message "Communication link failure".
> Msg 233, Level 16, State 1, Line 0
> Named Pipes Provider: No process is on the other end of the pipe.
>
>
>
>
> "Sandeep Shankar" <sandeeps@.dntg.net> wrote in message
> news:%23t%23jvCv0HHA.4236@.TK2MSFTNGP06.phx.gbl...
> and
> 27
>
|||I did put this parameter yesterday, but Now when I refresh 'Local
Publication' I get ' Failed to retrive data for this request.'
More info
A exception occurred while executing a transact- sql statement or batch
Lock request time out period exceeded
Thanks
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OPzWNA30HHA.4184@.TK2MSFTNGP06.phx.gbl...[vbcol=seagreen]
> set the ignore_distributor =1 parameter
> --
> 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
> "Sandeep Shankar" <sandeeps@.dntg.net> wrote in message
> news:%234MijUv0HHA.4004@.TK2MSFTNGP05.phx.gbl...
Line
>
|||You are getting some deadlocking occurring. Run dbcc opentran and see if
there are open transaction. evaluate whether you can kill them. Close down
all instance of EM, stop the agents and try again.
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
"Sandeep Shankar" <sandeeps@.dntg.net> wrote in message
news:ez9U3y40HHA.4652@.TK2MSFTNGP05.phx.gbl...
>I did put this parameter yesterday, but Now when I refresh 'Local
> Publication' I get ' Failed to retrive data for this request.'
> More info
> A exception occurred while executing a transact- sql statement or batch
> Lock request time out period exceeded
> Thanks
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:OPzWNA30HHA.4184@.TK2MSFTNGP06.phx.gbl...
> Line
>

Cannot delete merge publication

Hello...
I had a merge publication that I thought was removed...at least it does not
appear in Ent. Mgr under the list of Publications. However, in the
Replication Monitor the publication still exists. When I click on the
publication to delete or check its properties I get the mesage:
SQL Server could not retrieve information about publication 'My_Publication'
Error 21776: [SQL-DMO] The name 'My_Publication' was not found in the
MergePublications collection. If the name is a qualified name...'
I searched for that error code...but could not find anything that would help
me solve this problem.
if anyone has any ideas, it would be appreciated.
thanks
- dw
check sysmergepublications in the publications database. Do you find the
publication there?
If so you will need to delete it and the matching sysmergearticles columns.
Also delete the rows for this publication from
distribution.dbo.MSpublications
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
"dw" <dw@.discussions.microsoft.com> wrote in message
news:85F329D5-E863-41A5-8AB3-8BB008C98EC7@.microsoft.com...
> Hello...
> I had a merge publication that I thought was removed...at least it does
not
> appear in Ent. Mgr under the list of Publications. However, in the
> Replication Monitor the publication still exists. When I click on the
> publication to delete or check its properties I get the mesage:
> SQL Server could not retrieve information about publication
'My_Publication'
> Error 21776: [SQL-DMO] The name 'My_Publication' was not found in the
> MergePublications collection. If the name is a qualified name...'
> I searched for that error code...but could not find anything that would
help
> me solve this problem.
> if anyone has any ideas, it would be appreciated.
> thanks
> - dw

Cannot create subscriber on MSDE2000

I am very new at SQL replication. I set up a publication and distributor at
our SQL 2000 server. All went fine. Now I am trying to create a laptop
subscriber to use (I think) an anonymous subscription. I setup the laptop
with MSDE 2000 SP3. I now want to create a subscription while connected to
the network. I want to use the Windows Syncronizer to synch the database.
I cannot find out how to create the initial subscription database on the
laptop. When I try to manually configure the Windows Synchronizer, I get an
error "The process could not access database 'MCFIData' on server 'LAPTOP1'.
Database is invalid or cannot be accessed"
Well DUH...I was told that it would be created if it does not exist. Any
help would be appreciated. Thanks.
David
Ignore this. I did not have the SQL Agent running on the laptop with MSDE
2000 SP3. I'm not sure why, but there was no prompt for this option when I
installed MSDE. Also there was no instruction to do so on the documentation
for setting up MSDE to be a subsriber!
David
"David" <dlchase@.lifetimeinc.com> wrote in message
news:elqk$rE%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
>I am very new at SQL replication. I set up a publication and distributor
>at our SQL 2000 server. All went fine. Now I am trying to create a laptop
>subscriber to use (I think) an anonymous subscription. I setup the laptop
>with MSDE 2000 SP3. I now want to create a subscription while connected to
>the network. I want to use the Windows Syncronizer to synch the database.
>I cannot find out how to create the initial subscription database on the
>laptop. When I try to manually configure the Windows Synchronizer, I get
>an error "The process could not access database 'MCFIData' on server
>'LAPTOP1'. Database is invalid or cannot be accessed"
> Well DUH...I was told that it would be created if it does not exist. Any
> help would be appreciated. Thanks.
> David
>

Cannot create publication after SP1 upgrade

After upgrading SQL Server 2005 with the recent service pack, I am unable to create a publication. When I right-click on [INSTANCE]/Replication/Local Publications and select "New Publication...," the mouse cursor turns into an hourglass, but the wizard never shows up, nor is any error displayed.

There is a logged error that's been showing up that may or may not be related. The error message is "Replication-(null): agent (null) scheduled for retry. Could not clean up the distribution history tables."

Any ideas on how we can restore replication functionality on our SQL Server instance?

Can you run profiler before invoking New Publication wizard to trace which statement is causing the problem? What kind of publications do you have before upgrade to SP1? Is distributor on the same machine as publisher?

Thanks,

Zhiqiang Feng

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

|||I ran the profiler, and I'm getting some strange output. Apparently, the command "select * from sysdatabases where name=N'distribution'" is being run over and over again. Strangely enough, there is a row returned from that command that points to where our distribution database was located, but the database isn't shown under the system databases in Management Studio.

Before upgrading to SP1, we were using merge publications with the distributor on the same machine as the publisher.

|||

Can you send sp1 upgrade log files and profiler trace to me? I will send you a separate email.

Thanks,

Zhiqiang Feng

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

|||

From the sp1 upgrade log file, looks like you have run SP1 upgrade twice, the first time it runs, SQLDEV01 machine is treated as a distributor and distribution database is upgrade successfully(from what the log file says). The 2nd time the sp1 upgrade runs, it didn't treat this machine as distributor and didn't upgrade distribution database (also you mentioned distribution database is no longer marked as system database, which is suspicious, we need to figure out why). Did you notice any error during sp1 upgrade? Why you run sp1 upgrade twice? Did you drop distributor or change replication settings after first sp1 upgrade?

Please also email a profiler trace for the New publication wizard so we can further diagnose the issue. When using profiler, make sure select following options (and unselect any options not mentioned below):

Error and Warnings --> ErrorLog, Exceptions, User Error Message

Stored Procedures --> RPC Starting, RPC Completed, SP Starting, SP Completed, SP Stmt Starting

TSQL --> SQL: Batch Starting, SQL: Batch Completed, SQL: StmtStarting

Thanks,

Zhiqiang Feng

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

|||It's finally working! I suspect that all the problems stemmed from there being an inconsistency in the sysdatabases table. I ran "DROP DATABASE distributor" under the master database, and afterward, I was able to set up the distributor, publishers, and subscribers without any problems.

Thank you, Zhiqiang Feng, for your email assistance.