Socket is closed error in Data Services Management Console 4.1(Vmware ESX)

[Former Member]

I execute a job from the Console .(Vmware ESX)

-Socket is closed error is thrown in Data Services Management Console when executing job or adding a schedule or exporting execution command

-get error "Exception thrown when trying to communicate with Job Server:ETLSERV:3500. Socket is closed"

- Job Server and Web Server are on the same machine.

-The Job Server is running.

-----------------------------------------------------------------------------------------

Server : x86

VMWare : ESXI 4.1.0.8000380

OS : Window Server 2008 R2 Enterprise Edition 64 bit

IPS : SBOP INFORMATION PLAT SVCS 4.0 SP04 WINDOWS (64B)

Data Integrator : SBOP DATA SERVICES 4.1 WITH SP01 WINDOWS (64B)

--------------------------------------------------------------------------------------------------------------

[Former Member · Accepted solution]

Hi Tongwilai,

Try assigning a new port in the port configuration of the servers for the repository (uncheck "set to auto assign").

Regards,

Mubashir Hussain

[Former Member · Accepted solution]

Hi Mubashir Hussain,

please specify which ports number that use for config which server is shown below (for example : 3500 ,3501)

1.AdaptiveJobServer

2.AdaptiveProcessingServer

3.CentralManagementServer

4.EIMAdaptiveProcessingServer

5.InputFileRepository

6.OutputFileRepository

[Former Member · Accepted solution]

CentralManagementServer(right click) -->  properties -->  Request port

[Former Member · Accepted solution]

What should I use port number?

*** I've changed to 6400 but it seems that port collisions.

thank you

[Former Member · Accepted solution]

Hi Tongwilai,

By default the Name Server port is assigned to port 6400.

What you are changing is Request port.

Technically, Name Server port and Request port should be different. Hence they collide if you use same !!

Use some unused port for request port  and check!!

Regards,

Mubashir Hussain

[Former Member · Accepted solution]

I have tried changing the port 6400 and then I joined CMC is not an error.

[Former Member · Accepted solution]

To what port number did you change?

and

Did you change request server?

[Former Member · Accepted solution]

I test port 6400 and Now I can not Log on to CMC

[Former Member · Accepted solution]

Go to Central Configuration Manager--> Right click on Server Intelligence Agent --> Properties --> 'Configuration' tab --> if it says 'CMS belongs to cluster name servername:6400' ?

If so then its fine check in 'Startup' tab-->If the port is 6400??

Revert back!!

[Former Member · Accepted solution]

thank,Mubashir Hussain

Now I configuration change port 6400 to 6412

I can log on CMC but error "Exception thrown when trying to communicate with Job Server:ETLSERV:3500. Socket is closed"

It ' same Problem

[Former Member · Accepted solution]

Hi Tongwilai,

Do as shown in the following screen shot

Regards,

Mubashir Hussain

[Former Member · Accepted solution]

I can't do it. It 's same error

[Former Member · Accepted solution]

Is there any anti virus installed??

Or any firewall exists between Web Server and Job Server??

[Former Member · Accepted solution]

1. There is no anti-virus installed

2. Job Server is running

3.Install IPS and Data service same server

Now ,

Request Port:: 6422

Name Server Port : 6412

[former_member213365]

In my case, this error came up because there were multiple entries in the AL_MACHINE_INFO table. This was after upgrading from 4.2 SP08 to 4.2 SP13 in a fresh install, not an inplace upgrade.

When running a job from Designer, it worked fine. Running the same job from the Management Console, the "Job Server" drop down list box had two entries. It defaulted to the 'wrong' one which was listed at localhost instead of the server name.

I removed the two entries in AL_MACHINE_INFO that were wrong (after saving the data). After that, running jobs from the Management Console no longer threw a "socket is closed" error.

[Former Member]

Hello Tongwilai,

I've faced the same problem before few days-

If you're able to run the same job from Data Services designer then just try selecting different job server here-

and then execute.

Regards,

Gokul

[boga]

Hi ,

I have got the same problem and solution details as below :

Step 1 : Create the new job server with different port no like 3510 (default port - 3500).

Step 2 : we  can get these error message -

Error Message :UNABLE to Update the repository <bods@sai__bods>. Error: Error executing the sql, error message is: <Unable to find CA certificates for the job server. Ensure that the CA certificates for the job server exist in the LINK_DIR/ssl/trusted_certs folder.>

Step 3 : execute the below steps:

1.Stop Data Services service.

2.Copy DS_IntermediateCA_<hostname>_cert.crt and DS_Root_CA_<hostname>_cert.crt from LINK_DIR/ssl/CA to LINK_DIR/ssl/trusted_certs folder

3.Run LINK_DIR/bin/SetupJava Keystrore.bat for Windows Installation or LINK_DIR/bin/SetupJava Keystrore.sh for non Windows installation.

4.Resync the repositories.

5.Start Data Servucices service.