SafeCom replication failing
SafeCom replication is failing on "add server" or "repair replication" server.
One possible cause for this is that the account running the SQL service is running with local authority rather than as a network service. If the account running the SQL service does not have access to the target SQL data folder, it will not be able to create the replication correctly.
To test if this is the case, open SQL Management Studio and connect to the Primary SQL server.
- Find the replication section and right-click.
- Select the option for the replication monitor.
- Expand the 'My Publishers' field and drill down to the target server and replication entry (sccoreTrans).
- On the right hand pane, select the Agents tab and review the status there.
There is a screenshot attached (Replication monitor.png) to this article showing this error.
Option 1: Change the account running the SQL service to one that has access to the target folder.
Example target folder (default: C:\Program Files\Microsoft SQL Server\MSSQL_xxx.xxx\MSSQL\DATA)
Option 2: Change the folder permissions on the target server so that the account has access. If the account is a local account, you may need to use the 'everyone' group in the permissions for the folder.
Note: This configuration is the responsibility of the customer and should not be configured by tech support.
Replication monitor.png (123 KB)