4.1.0 HP PolyServe Software for Microsoft SQL Server administration guide (T5392-96074, October 2010)

Connection error with Windows authentication
When connecting to a SQL Server instance using local Windows authentication, you
may receive the following error:
Login failed for user '(null)'. Reason: Not associated with
a trusted SQL Server connection.
This error is addressed in the following Microsoft Knowledge Base article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;840219
Windows authentication fails with SQL Server replication
When replication is set up using SQL Server tools, by default the replication agents
are configured to use Windows authentication. However, if at any time the replication
agent runs on the same machine as the replication distributor or publisher, the agent
will fail to connect to those instances. This situation occurs because of a SQL Server
problem described in the following Microsoft Knowledge Base article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;840219
To work around this problem, you will need to modify the steps in the replication job
to use SQL authentication instead of Windows authentication. Add the following
options:
For the log reader agent:
logread [-?]
-Publisher server_name[\instance_name]
-PublisherDB publisher_database
[-DistributorLogin distributor_login]
[-DistributorPassword distributor_password]
[-DistributorSecurityMode [0|1]] // set to 1 for SQL authentication
[-PublisherSecurityMode [0|1]] // set to 1 for SQL authentication
[-PublisherLogin publisher_login]
[-PublisherPassword publisher_password]
For the distributor job:
[-DistributorLogin distributor_login]
[-DistributorPassword distributor_password]
[-DistributorSecurityMode [0|1]] // set to 1 for SQL authentication
[-SubscriberLogin subscriber_login]
Troubleshooting138