sql server replication: I have a situation where a customer has a SQL 2000 database at thier office
location, this is where they do data updates, it replicates to a SQL 2000
server located at a web hosting facility. Problem is there is a new IT guy
at the office location that has done something to the setup so that now the
database does not replicate. When at the office you can see the hosting
facility SQL in SQL Manager but you can not see the SQL server from the
office location in the hosting facility. The SQL ports are open on the
firewall, and we can telnet to the port but it does not replicate and we can
not see the server in SQL Manager from the hosting facility. What should I

Lee - check to see that the alias has not been removed - see (iii) here:
http://www.replicationanswers.com/InternetArticle.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

I made the change on the ALIAS on the pull network and opened port 21 inbound
on the Push network. Replication seems successful on one Agent but there
seems to be an invalid Column error on the other. I am having the database
guys look at that. But this may have fixed the problem.

The replication caused issues with the database. What I would like to do now
is remove everything and start from scratch. What things should I look for
first befoer removeing everything?
All we want to replicate is the data only, not schema or anything else.

Ok. I just got off the phone with Microsoft and I understand a lot now. Now
to test replication here is what we did:
Created a new database on the Publisher and added a table with columns and
data.
We then created a New Publication set. After creating this here is what
happened that has me stumped...
It created the database and the columns, but it did not replicate the data.
It gives and error: Generic Network error.

Lee - if you have plain transactional replication using
sp_removedbreplication on the subscriber and dropping the publication at the
publisher should be enough.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

Lee,
I'd enable logging (http://support.microsoft.com/?id=312292) and see if this
gives more info. Also start ping -t before syncing to test connectivity.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com