Subscription failures consist of materialization and dematerialization failures. This section describes procedures you can use to troubleshoot these types of problems.
Before troubleshooting a subscription problem, always verify that data has failed to materialize or dematerialize by:
Using isql to log in to the replicate database
Executing a select command that selects the materialized or dematerialized columns from the replicate table
Also make sure that all tasks required for subscription materialization have been completed. Subscription materialization can fail if you have not completed:
Creating replication definitions or function replication definitions
Marking tables or stored procedures for replication
Creating connections to the destination databases
Creating articles, if you are using them
Creating and validating publications, if you are using them
Marking text, unitext, or image columns for replication, if you are replicating text, unitext, and image columns
Creating direct and indirect routes, if the destination database is connected to a Replication Server different from the primary database’s Replication Server
Creating logical connections, if you are using warm standby applications
