EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB41947: " SLSocket55@OldServer, ErrorCode=2310, ErrorMessage=TCP/IP, connection reset by peer. " Error message in Event Viewer caused by SequeLink in Microsoft Windows Server 2003 Enterprise Edition


Community Admin

• Strategy


Error messages may occur in the Windows Event Log after changing the machine hosting the Sequlink service from OldServer to ActualServer.

SYMPTOM:
The following error messages may occur in the Windows Event Log after changing the machine hosting the Sequlink service from OldServer to ActualServer.  Notice the references to both machine names in the error Computer and Description entries:


Log Name: Event Viewer Application.evt
Source: SLSocket55
Date: 11/09/2012 16:40:00
Event ID: 0
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: <ActualServer>
Description:
The description for Event ID 0 from source SLSocket55 cannot be found. Either 
the component that raises this event is not installed on your local computer 
or the installation is corrupted. You can install or repair the component on 
the local computer.
If the event originated on another computer, the display information had to be 
saved with the event.

 
The following information was included with the event:
SLSocket55@<OldServer>,ErrorCode=2310,ErrorMessage=TCP/IP, connection reset by peer
 
CAUSE:
The error messages are generated due to references in the SequeLink configuration file to the previous machine name.   In this specific case the configuration file swandm.ini had a entry referencing the old server machine name.
 
 
ACTION:
Search for the old server name in the swandm.ini file and update those entries to the new server name.   This file is located in: C:\Program Files\DataDirect\slserver55\cfg\swandm.ini
Here is a sample file which has references to the previous server name (aka OldServer)

Type=2
ServiceHost=<OldServer>
ServiceType=0
ServiceIdentification=SL5_Agent
ServiceDescription= Agent service
ServiceDebugLogPath=C:\Program Files\DataDirect\slserver55\logging
ServiceDebugLogLevel=3
ServiceEventTraceSize=1000000
ServiceAdminAuthMethods=1
ServiceAdminAuthMethods0=Anonymous
ServiceMinThreads=8
ServiceMaxThreads=64
ServiceExecPath=C:\Program Files\DataDirect\slserver55\bin\swagent.exe
ServiceEvQShmMonitorSize=32000
ServiceMessageFile=C:\Program Files\DataDirect\slserver55\bin\swagentmsg.dll
ServiceEventTraceLocation=C:\Program Files\DataDirect\slserver55\tracing
ServiceAdministrator=1
ServiceAdministrator0=everyone
ServiceRegisterTCPPort=1
ServiceName=SLAgent55
ServiceConnectInfo=tcp://Win200332b921m.19995


Comment

0 comments

Details

Knowledge Article

Published:

April 4, 2017

Last Updated:

April 4, 2017