2000 Replication job wont run on 2005

  • I have a Replication job which runs great on SQL Srvr 2K, but it fails on 2005 with the following message:

    "The step is improperly defined and so could not be run.  The step failed."

    The step I am trying to run is:

    -Publisher [TESTSERVER] -PublisherDB [testdb] -Distributor [TESTSERVER] -Publication TestingSnapshot -DistributorSecurityMode 1

    The Type is "Replication Snapshot"

    Run as : "SQL Agent Service Account"

    Any input is appreciated.

    Thanks

    Anik

  • I don't see the -ReplicationType flag in your command. Perhaps it is optional in SQL 2000 but required in 2005. I'm guessing on this one. Try adding the flag to the command: -ReplicationType 1


    My blog: SQL Soldier[/url]
    SQL Server Best Practices:
    SQL Server Best Practices
    Twitter: @SQLSoldier
    My book: Pro SQL Server 2008 Mirroring[/url]
    Microsoft Certified Master: SQL Server, Data Platform MVP
    Database Engineer at BlueMountain Capital Management[/url]

  • Now the step is:

     

    -Publisher [TESTSERVER] -PublisherDB [testdb] -Distributor [TESTSERVER] -Publication TestingSnapshot -DistributorSecurityMode 1 -ReplicationType 1

    Still fails with the same message! I tried on two different installs - same message.

    Is there a sample setup script somewhere that I can use as a template? May be I am setting up the Publisher incorrectly?

    I took the exact same script that runs on 2K and copied it to 2K5 for testing - only changed the server names.

     

  • Have a look at msdb..sysjobsteps.

    The server column of the step in question is probably NULL. Change it to whatever your target server is and it should work.

  • i would script out the publication and run the script on the distributor to create the publication from scratch. or create it from scratch

  • By adding server and database_name in sysjobsteps the replication step started to work properly. Thanks for the help.

    Branko

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply