Re: Updating Subsciber Replication Error

From: Hilary Cotter (hilary.cotter_at_gmail.com)
Date: 08/31/04 

Date: Mon, 30 Aug 2004 22:25:52 -0400

I take it you are using queued updating? If so are you using MSMQ or the SQL
database as the queue?

I suspect that your Subscriber is having a hard time figuring out where the
subscriber is. Can you do a select @@servername on your subcriber and
publisher and post them here.

Can you also query sysservers on your subscriber and publisher

select srvid, srvname from sysservers where srvid in (0,1) 

-- 
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"lancemc5" <lancemc5@discussions.microsoft.com> wrote in message
news:E936DFD6-34D2-4DDD-8579-756AABAE8D6F@microsoft.com...
> I have a couple of servers in my test region that I am trying to configure
in
> an Updating Subscriber replication configuration.  I am able to set up the
> publisher without issue.  The distributor is on the same server as the
> publisher.  I can create a subscription to the second server.  When
updating
> a column for a publication, the row updates to the subscriber without a
> problem.  However, when updating the same column on the subscriber, I
receive
> the following error message:
> Could not locate entry in sysdatabases for database 'central'  No entry
> found with that name.  Make sure that the name is entered correctly.
> The 'central' database is the publishing database on the first server and
> would not have an entry in the sysdatabases table on the subscriber.  Does
> anyone know why I am getting this message.
> Thanks,
> -- 
> Lance McCaskey

Relevant Pages

  • Re: transactional replication problem
    ... If the distribution agen can't connect to the subscriber, ... Looking for a SQL Server replication book? ... > server B. Problem is with only one database. ...
    (microsoft.public.sqlserver.replication)
  • Transation replication with updateable subscribers
    ... I have a main database that I need to distribute a copy of to another server ... The Subscriber will be a SQL server 2000 std edition ... was supposed to create a publication that was a transactional publication ...
    (microsoft.public.sqlserver.replication)
  • Re: Subscriber Transaction Logs Too Large
    ... I would advise you to put the subscriber database into bulk ... in full recovery model and dump the log every 15 minutes or so. ... Director of Text Mining and Database Strategy ... Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)
  • Re: reinstall of the subscriber server
    ... database, rather you need to shut down the distribution agent. ... Looking for a SQL Server replication book? ... > log reader agent and I don't need to shut it down for what I am planning ... I noticed that if I want to delete a subscriber database, ...
    (microsoft.public.sqlserver.replication)
  • Re: SQL2000 - Merge Replication - Timeout error
    ... The timeout is in your publisher and distributor server, ... Then, update the database statistics. ... Run profiler on the subscriber to see what is going on? ...
    (microsoft.public.sqlserver.replication)