Showing posts with label pcs. Show all posts
Showing posts with label pcs. Show all posts

Sunday, March 25, 2012

Cannot drop the table "xyz" as it is being used for replication

I have a replication setup running on 2 Win2K Server PCs with SQL
Server 2000.
Both the PCs have a common DB installed on them.
The setup takes care of starting one PC as primary and other as
backup.
It also starts the SQL replication (transactional), where both the PCs
are configured as publisher, distributor and subscriber.
Now the replication service creates a publication ONLY ON
PRIMARY and a subscription ONLY ON BACKUP. The replication starts.
When a switch-over of primary and backup is done, the existing
publication and subscription are deleted. A new publication is created
on new PRIMARY and a new subscription on the new BACKUP. Again,
replication works without a problem.
HOWEVER, sometimes, (I'm not able to reproduce & it is very
infrequent) on a switch-over I get thee error--"Cannot drop the table
"xyz" as it is being used for replication." The table is the one I
used for replication. Also, the primary keys exist on this table in
this case even though it's a part of subscription. The only solution
till now is to delete the entire replication on both machines and
re-create it.
I'm not using this DB anywhere else for any other purpose. Any
clues, why am I getting this problem occasionaly?
Thanks in advance.
Nelabh,
it's sometimes the case that some replication metadata is left hanging
around in system tables. sp_removedbreplication usually fixes these issues,
or the more granular sp_MSunmarkreplinfo may also be of interest.
HTH,
Paul Ibison

Friday, February 10, 2012

Cannot connect SQL Server via Internet from Widows 2003 Server

I have a SQLServer 2000 connection problem from a Windows 2003 and Windows
2000 Servers. But it is no problem from other windows XP PCs. Any idea!!!
The Error Message is :
SQL Server registration failed because of the connection failure displayed
below.
ConnectionOpen (LoadNetlibs())Hi
You probably do not have the correct rules in the firewall, although opening
the ports may not be the best of things to do! Use of a VPN would provide
some protection.
For more about the rules needed see http://support.microsoft.com/kb/287932
John
"BMW" wrote:
> I have a SQLServer 2000 connection problem from a Windows 2003 and Windows
> 2000 Servers. But it is no problem from other windows XP PCs. Any idea!!!
>
> The Error Message is :
> SQL Server registration failed because of the connection failure displayed
> below.
> ConnectionOpen (LoadNetlibs())
>
>