Issues creating Snapshot after setting up Replication

Version 2

    Verified Product Versions

    LANDESK Management Suite 9.6LANDESK Management Suite 2016.x

    Error

    You might run into the following error message after configuring Replication for the first time:

     

    Message
    2016-07-27 15:53:52.22 Microsoft (R) SQL Server Snapshot Agent
    2016-07-27 15:53:52.22 [Assembly Version = 11.0.0.0, File Version = 11.0.6020.0 ((SQL11_PCU_Main).151020-1526 )]
    2016-07-27 15:53:52.22 Copyright (c) 2008 Microsoft Corporation.
    2016-07-27 15:53:52.22 The timestamps prepended to the output lines are expressed in terms of UTC time.
    2016-07-27 15:53:52.22 User-specified agent parameter values:
    2016-07-27 15:53:52.22 --------------------------------------
    2016-07-27 15:53:52.22 -Publisher SQLServer
    2016-07-27 15:53:52.22 -PublisherDB ChildDatabase
    2016-07-27 15:53:52.22 -Publication LDMS_ChildDatabase
    2016-07-27 15:53:52.22 -Distributor SQLServer
    2016-07-27 15:53:52.22 -DistributorSecurityMode 1
    2016-07-27 15:53:52.22 -XJOBID 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
    2016-07-27 15:53:52.22 --------------------------------------
    2016-07-27 15:53:52.22 Connecting to Distributor 'SQLServer'
    2016-07-27 15:53:52.31 The replication agent had encountered an exception.
    2016-07-27 15:53:52.31 Source: Replication
    2016-07-27 15:53:52.31 Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentSqlException
    2016-07-27 15:53:52.31 Exception Message: The remote server "SQLServer" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers. 
    2016-07-27 15:53:52.31 Message Code: 14080
    2016-07-27 15:53:52.31
    

     

    Resolution

    This error typically means that there are issues with your ldms_snapshot user in SQL Server for your child cores. Here are two possible outcomes that can happen in this situation:

    (It's recommended to check and validate all 3)

    Incorrect Server Roles

    Though Microsoft documentation states that you should only need db_owner fixed user mapping, I've found that the sysadmin Server Role is also some times necessary to successfully create a snapshot:

    Incorrect User Mapping

    Ensure that your User Mappings look like the following:

    ldms_distribution:

    child database:

    Incorrect Credentials

    Navigate to Security > Credentials > Right Click on the ldms_snapshot user > Properties and update the password information there.

     

    References

    MSDN Documentation:

    Replication Agent Security Model