SQL Replication Publisher 2000 with Subscriber and Distributor 2008


I am trying to setup Replication between SQL 2000 and SQL 2008.

I'm trying replication topology:
Publisher SQL 2000 SP4
Distributor and Subscriber SQL 2008
This topology should work according to docs.
But the snapshot agent fails to start I get login error. The distributor cannot connect to publisher. See attached.
We are testing with domain admin account so security should not be an issue.

I tried another topology to get more information
Publisher SQL 2000  SP4
Distributor SQL 2008
Subscriber SQL 2005 SP2
We get same error.

This topology worked
Publisher SQL 2005 SP2
Distributor SQL 2008
Subscriber SQL 2005 SP2

Then I read in the article:

Using a SQL Server 2005 or SQL Server 2008 Distributor with a Publisher Running SQL Server 2000
SQL Server 2005 and SQL Server 2008 can be used as a remote Distributor for Publishers that are running SQL Server 2000. To change agent properties in this scenario, execute the following stored procedures at the Distributor. These procedures let you change properties that were introduced in SQL Server 2005:
sp_MSchange_snapshot_agent_properties (Transact-SQL)
sp_MSchange_logreader_agent_properties (Transact-SQL)
sp_MSchange_distribution_agent_properties (Transact-SQL)
sp_MSchange_merge_agent_properties (Transact-SQL)

And from there I'm a little lost I must say. I am not a DBA :l
What properties would I have to change to allow the topology with SQL 2000 Publishing? (If this is the solution at all)

Any ideas?

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

lcohanDatabase AnalystCommented:
Why can't you keep the Distribution on the same SQL as the Publisher I mean on the SQL 2000 SP4?
carlosmonteAuthor Commented:
We don't want to put more load on the SQL 2000.
That is why my topology has to be the one I explained.
lcohanDatabase AnalystCommented:
I thought that would be the answer but how then you tested
This topology worked
Publisher SQL 2005 SP2
Distributor SQL 2008
Subscriber SQL 2005 SP2

and why the SQL 2000 which BTW is long ago not supported can't be upgraded to a more recent supported version? And let me guess <1try:)> the application/system using the back end SQL database(s) cannot be modified for some (misteriously or too much not worth it effort...) reason so...

My guess the error you'r getting is because the NT login THEPALACEUS\PALACE57$ (I gues this is the SQL 2008 Agent startup account) does not have sufficient rights in your SQL 2000 (maybe does not even exists) for whatever reason so Distribution Agent SQL job running as that NT login can't connect back to SQL 2000.

Another option may be to try to create a SQL Login and use it instead of NT login like described here:
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

When you build the replication you should choose your own login if it has the proper permissions instead of the instance default login.
carlosmonteAuthor Commented:
I'm trying different topologies for testing.
I know SQL 2000 is 15 years old and not supported. But it is a requirement for us. We cannot upgrade it. not my fault :/ It is not that we are lazy and don't want to upgrade to newer version.
The 2008 Agent startup account as I mentioned is the DOMAIN/ADMIN (so access to everything). And I double checked right now that this user has explicit access to publication DB, distribution db and Subscription DB as db_owner.
We tried SQL login too.
We have decided to use a SQL 2005 server for distribution although it is not what we wanted but it works.
Thanks for the comments

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
carlosmonteAuthor Commented:
Issue was not resolved with comments and had to find an alternate which is the route i'm taking to fix the issue.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.