Ekrem:
I checked the job that failed and found the following errors:
Step Name (Job Outcome):
The job failed. The Job was invoked by User DOMAIN\Username. The last step
run was Step 3 (Detect nonlogged agent shutdown).
Step Name (Run Agent):
Login failed for user 'Server\Servername$'. The process could not connect
to subscriber 'Server B'. The step failed.
Does that help at all?
[quoted text, click to view] "Diane" wrote:
> I am in SSMS and have set-up replication (I think). I have connected Server A
> and Server B in SSMS via SSMS Object Explorer. Server B is at another
> location and is connect via VPN I believe.
>
> Server A has the database I want to replicate somewhere else. I have setup
> Server A to be Distributor and Publisher. I have created a snapshot
> publication. I have set-up Server B as the subscriber via Push method on
> Server A. I have set this publication to be replicate on demand.
>
> On Server A, when I highlight the subscription and select 'View
> Syncronization Status' and then select 'Start', the Agent starts and then I
> get the following message:
>
> "The process could not connect to Subscriber 'Server B' "
>
> What can I do to resolve this? I am new to setting this up and am unsure
> what to try next. Any help would be greatly appreciated.
>
> Regards,
Do I need to do some type of Server Registrtion in order to get this to work?
[quoted text, click to view] "Diane" wrote:
> I am in SSMS and have set-up replication (I think). I have connected Server A
> and Server B in SSMS via SSMS Object Explorer. Server B is at another
> location and is connect via VPN I believe.
>
> Server A has the database I want to replicate somewhere else. I have setup
> Server A to be Distributor and Publisher. I have created a snapshot
> publication. I have set-up Server B as the subscriber via Push method on
> Server A. I have set this publication to be replicate on demand.
>
> On Server A, when I highlight the subscription and select 'View
> Syncronization Status' and then select 'Start', the Agent starts and then I
> get the following message:
>
> "The process could not connect to Subscriber 'Server B' "
>
> What can I do to resolve this? I am new to setting this up and am unsure
> what to try next. Any help would be greatly appreciated.
>
> Regards,
Both the publisher and subscriber would be ideal to have the SQL Server
service and agent started with the same domain account. Right now the login
is not a valid login on the subscriber.
[quoted text, click to view] "Diane" <Diane@discussions.microsoft.com> wrote in message
news:DB2DF787-8D60-40B2-8527-5338816DB9CF@microsoft.com...
> Do I need to do some type of Server Registrtion in order to get this to
> work?
>
> "Diane" wrote:
>
>> I am in SSMS and have set-up replication (I think). I have connected
>> Server A
>> and Server B in SSMS via SSMS Object Explorer. Server B is at another
>> location and is connect via VPN I believe.
>>
>> Server A has the database I want to replicate somewhere else. I have
>> setup
>> Server A to be Distributor and Publisher. I have created a snapshot
>> publication. I have set-up Server B as the subscriber via Push method on
>> Server A. I have set this publication to be replicate on demand.
>>
>> On Server A, when I highlight the subscription and select 'View
>> Syncronization Status' and then select 'Start', the Agent starts and then
>> I
>> get the following message:
>>
>> "The process could not connect to Subscriber 'Server B' "
>>
>> What can I do to resolve this? I am new to setting this up and am unsure
>> what to try next. Any help would be greatly appreciated.
>>
>> Regards,
>> Diane
Don't see what you're looking for? Try a search.
