3.4.3 MxDB for SQL Server Installation and Administration Guide

Chapter 4: Troubleshooting 79

[-DistributorSecurityMode [0|1]] // set to 1 for SQL authentication

[-SubscriberLogin subscriber_login]

[-SubscriberPassword subscriber_password]

[-SubscriberSecurityMode [0|1]] // set to 1 for SQL authentication

For the merge agent job:

[-DistributorLogin distributor_login]

[-DistributorPassword distributor_password]

[-DistributorSecurityMode [0|1]] // set to 1 for SQL authentication

[-PublisherLogin publisher_login]

[-PublisherNetwork publisher_network]

[-PublisherPassword publisher_password]

[-PublisherSecurityMode [0|1]] // set to 1 for SQL authentication

[-SubscriberLogin subscriber_login]

[-SubscriberPassword subscriber_password

[-SubscriberSecur

ityMode [0|1]] // set to 1 for SQL

authentication

For the queue reader agent:

[-DistributorLogin distributor_login]

[-DistributorPassword distributor_password]

[-DistributorSecurityMode [0|1]] // set to 1 for SQL authentication

For the snapshot agent:

[-DistributorLogin distributor_login]

[-DistributorPassword distributor_password]

[-DistributorSecurityMode [0|1] ] // set to 1 for SQL authentication

For more information about Replication Agent Utilities, see the Microsoft

article “Replication Agent Utilities,” available at the following website:

http://msdn.microsoft.com/library/en-us/replsql/replmon_7qcz.asp

“Registry Replicator Undefined” Alerts

If messages stating that a registry replicator is undefined appear on the

PolyServe Management Console and in the Matrix Server logs, the

probable cause is that the Matrix Server registry keys are pointing to the

wrong database path. The error occurs when Matrix Server tries to probe

the incorrect path. (The registry keys are generated when the SQL Server

instance is virtualized.)