Replication Problem

High I hope someone can help me.

I'm trying to set-up replication between us and a business client.
We have a VPN into their network on 1 account set against 1 userid.
We then have a SQL SERVER acocunt on their Sql Server 7 machine.

We are running Win2000 and SQL Server 2000 Enterprise Std.

The publication has been set-up and looks okay
so has the pull subscription on our server.

When running the replication though I'm getting the following error.

The process could not connect to Distributor 'NXTIMSVR'.

Any ideas would be appriciated.

CliveWhere is your Distributor reside at? how was the account setup in the Distributor?|||Originally posted by joejcheng
Where is your Distributor reside at? how was the account setup in the Distributor?
The distributer is a the remote client site, I do not know how the distributer was set-up for we have just been asked to look after a section of their data.
Is there something that I could ask them to check.|||The first thing you have to make sure is that your publisher has to be able to access the Distributor. The ID that you setup your publication is the one you need to check. Then your subscirber has to be able to pull in information from the Distirbutor, so it need to be able to access the Distributor also.|||The publisher can see the distributer, its the PULL subscriber that is not connecting to the distributer.

Clive

Replication Options

Hello,
New to SQL Replication.
Have SQL 2000 and wanted to replicate my business & core databases to a
server at another site to increase availability.
Is SQL replication able to keep my business application running without end
users ever knowing that one of the serves went down or are there manual steps
to be taken to get end users reconnected if I lose or down one of the SQL
servers?
Which type of replication is best suited for this?
Also, my WAN bandwidth is around 768 K upto about 1 M max betweeen sites.
Will these speeds support SQL replication ok?
Thanks much,
Mark
Paul,
Thanks for the info. Seems I'm a bit limited. I read that log shipping
requires SQL 2000 Enterprise, and I don't have it!
I quess one of the forms of Replication or an upgrade to SQL 2005 may be my
only options.
Thanks much,
Mark
"Paul Ibison" wrote:

> Hi Mark and welcome to the group
> For DR, you might want to look at log shipping. In SQL Server 2005 there is
> database mirroring which is similar but offers automatic failover that you
> mention, but this isn't there in log shipping and there willbe some final
> tweaking to get things ready, and then you'll need to point the client apps
> at the new server. Have a look here for a little more info:
> http://www.replicationanswers.com/Standby.asp, and BOL for the final steps
> needed in log shipping to bring up the standby server.
> HTH,
> Paul Ibison
>
>
|||Paul,
Could I just do a manual database transfer of a full backup every night to
the standby server, and just send a copy of the transaction logs to the
standby server say every hour without using Replication?
Any reason not to do it this way?
Thanks,
Mark
"Paul Ibison" wrote:

> Hi Mark and welcome to the group
> For DR, you might want to look at log shipping. In SQL Server 2005 there is
> database mirroring which is similar but offers automatic failover that you
> mention, but this isn't there in log shipping and there willbe some final
> tweaking to get things ready, and then you'll need to point the client apps
> at the new server. Have a look here for a little more info:
> http://www.replicationanswers.com/Standby.asp, and BOL for the final steps
> needed in log shipping to bring up the standby server.
> HTH,
> Paul Ibison
>
>
|||You can do log shipping in other editions, but it is a bit more difficult as
it isn't out of the box. At the end of the day you just need jobs to back up
logs on one server, copy to a network share on another server then a third
job to restore there (no recovery). Procedures to make this setup are on the
SQL Server resource kit and on some websites so you can use someone else's
scripts if you don't want to make your own.
Cheers,
Paul Ibison
|||Exactly - you can roll your own log shipping. Just be sure to restore using
NO RECOVERY and the rest is pretty straightforward.
Cheers,
Paul Ibison