Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

SEPM replication status: failed to connect

Created: 30 Oct 2012 • Updated: 11 Nov 2012 | 21 comments
cus000's picture
This issue has been solved. See solution.

Hi All,

 

some error that i notice from scm0 log:

 

ReplicationTask>> replicate: Communication Exception Error Code = -805240832 ErrorMsg Code = 130

 

com.sygate.scm.common.communicate.CommunicationException: No response from the remote server ErrorCode: 0xd0010000

 

strangely no big data in replication/inbox or outbox... only around 50mb.....

Comments 21 CommentsJump to latest comment

Ashish-Sharma's picture

Hi

Can you check the scm-server-0.log file located at  Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs

and check for https 415 error. In case its there paste the relevant portion and we will troubleshoot further.

Check for any recent changes in Firewall or Proxy

"Unable to connect to the server specified" error during the replication of Symantec Endpoint Protection Manager

http://www.symantec.com/business/support/index?page=content&id=TECH106224&locale=en_US

Thanks In Advance

Ashish Sharma

 

 

cus000's picture

No https 415 error found...

 

on fw side... i'm not sure...i doubt its fw issue as i'm able to telnet 8443 both side

pete_4u2002's picture

what is the SEPM version?

does teh data.zip gets transferred to other server? i believe it is timing out

cus000's picture

SEPM is ru6 mp2...

 

from the main SEPM it show replication as successful but remote SEPM shows as "failed to connect"

 

to verify check the replication/inbox content right?.

.. the main SEPM no issue... .zip file size about 10mb...

 

 

Based on above error i found a KB saying it might due to fw session timeout...but i don't think its logic for this case as the data not big....

pete_4u2002's picture

to verify check the replication/inbox content right?.

yes , on the other SEPM.

even though it might be 10 MB , it could be bandwidth at that moment of time that would have caused timeout.

 

if you feel the bandwidth is good, can you attempt for manual replication again and wait for results.

cus000's picture

Already tried manual replication but still fail....more horror below

 

I've somehow removed the replication partner and want to add back but it just stuck and fails....below the error

 

40 WARNING: Login: (rep login) ReplicationProcessAuthenticator>> authenticate: partner count=1
2012-10-31 16:47:49.440 WARNING: Login: (rep login) ReplicationProcessAuthenticator>> authenticate: checking #0 partner site=Site MY-MDP-VA-01, enable=false
2012-10-31 16:47:49.440 WARNING: Login: (rep login) ReplicationProcessAuthenticator>> authenticate: Failed to Login!! Login failaure!! remote ip=xx.xx.xx.xx

A. Wesker's picture

Hi,

Are you sure you put the correct credentials when you re-create the replication partnership ? On the recent logs you provided it seems to be incorrect.

Did the replication already work on both ways before ?

How big is your SEPM database on the both SEPM server ?

What data do you replicate ? Nothing checked (so by default group + policies) ? Do you replicate something else as well like logs and Live Update contents + Install packages ?

Could you check the replication logs and see when the replication start and when the replication stops and fails.

By curiosity, could you check on the replication logs and scm.server-0:log if you could find an error message like "Unable to lock process".

Maybe your "initial" replication issue was caused of Live Update was running on one of the SEPMs when the replication was tryng to be done.

Live Update, Auto-Upgrade and Replication use the same process. If Live Update suddenly starts to run when a replication is already running, Live Update will take the priority so your replication will fail.

Try to schedule Live Update on the both SEPMs to a fix period of hours (like from 11.00 AM to 11.00PM) then schedule the replications from 03.00 AM.

Note that once the schedules are changed, you need to run it once manually in order the schedule changes works.

 

Kind Regards,

A. Wesker

SameerU's picture

HI

Please check the connectivity between the another server.

Regards

 

cus000's picture

@A.Wesker -

-Yes, the credential is correct... we even changed the password to non-specialized character...

- We only replicate logs... no packages or content were replicated

- all the while it was working fine... i'm breaking the replication partner and wanted to readd it as a common troubleshooting step....but alas....

- this step was done during normal working time... our LU only running at midnight

 

@SameerU

- as stated in previous post... telnet test seems fine... no issue with port 8443

 

@pete

- no, the breaking and readd is just a simple troubleshooting step...previously was ok

 

pete_4u2002's picture

suggest to open a support ticket.

while adding replicaton partner did it throw any error?

cus000's picture

guys just 1 thing to double confirm...

 

is the replication "administrator id and password" asked in wizard is the same id and password with remote SEPM console that we want to replicate?

pete_4u2002's picture

yes.

Administrator Name The account name that is used to log on to the console with administrator user rights
Password Provide a password that is associated with the Administrator Name that is specified
 

http://www.symantec.com/business/support/index?page=content&id=TECH104986

cus000's picture

ok thx... then means no issue with credential... but error i mentioned in ealier post... it shows as invalid

 

40 WARNING: Login: (rep login) ReplicationProcessAuthenticator>> authenticate: partner count=1
2012-10-31 16:47:49.440 WARNING: Login: (rep login) ReplicationProcessAuthenticator>> authenticate: checking #0 partner site=Site MY-MDP-VA-01, enable=false
2012-10-31 16:47:49.440 WARNING: Login: (rep login) ReplicationProcessAuthenticator>> authenticate: Failed to Login!! Login failaure!! remote ip=xx.xx.xx.xx

 

i'm a bit lost here... do u guys think it's possible due to timeout?

pete_4u2002's picture

the earlier log, i feel it could be timeout. as a test can you just copy the data,zip manually on another SEPM and check the time taken.

I still suggest open a support ticket.

cus000's picture

sry forgot to mention case already opened.... they mentioned possible issue with fw timeout... still investigating though.....

 

what baffle me is our .zip in replication folder is not that big only below 50mb...

 

below is error n kb matched:

 

2012-10-30 18:22:55.924 WARNING: ReplicationTask-Site_MY-MDP-VA-01-2: ReplicationTask>> replicate: Communication Exception Error Code = -805240832 ErrorMsg Code = 130

http://www.symantec.com/business/support/index?page=content&pmv=print&impressions=&viewlocale=&id=TECH138108

 

SameerU's picture

Hi

Please check the communication

Regards

 

cus000's picture

Already telnet port... odbc connection also ok.

Unless i missed out something here?

Riya31's picture

Hi ,

Cancelled replication on both the site if running.

Restart SEPM service on both the site

then manually start replication without any logs.

 

 

cus000's picture

Hi Riya,

Done both, same no different...

cus000's picture

Dear All,

Seems fixed now.

Below are steps that works for my issue:

 

1) Break replication from both partner SEPM to primary SEPM.

2) Tried to re-add back replication partner.... failed...

3) Tried to ran management server configuration wizard... saw some error in 'data' folder regarding ACL..

4) Ran sepm repair as adviced by adv team...

5) rerun back management server config wizard... success

6) re-add back replication partner... success

7) run empty replication for testing (without any option ticked)... sucesss

8) scheduled logs replication from sepm partners to primary.... sucesss (as per previous setting)

 

 

regards

SOLUTION