SSIS Scale Out worker is not showing up in Worker Agents

Published Jan 15 2019 05:42 PM 940 Views
First published on MSDN on Dec 01, 2017


Understanding of the issue:

Adding the scale out worker to the master shows successful but this does not show up in the SQL Server integration services – Manage Scale Out (ISManager). Also, this will not be added in [SSISDB].[internal].[worker_agents]

Adding SSIS worker completes in the wizard as below



After this finished, if we check the ISManager or worker_agents it is not showing up.



We can find the logs for both master and worker in below locations

Master: <path>:\Users\[account]\AppData\Local\SSIS\ScaleOut\Master

(Example: C:\Users\SSISScaleOutMaster140\AppData\Local\SSIS\ScaleOut\Master)



Worker: <path>:\Users\[account]\AppData\Local\SSIS\ScaleOut\Agent

(Example: C:\Users\SSISScaleOutWorker140\AppData\Local\SSIS\ScaleOut\Agent)



Things to verify for this issue:

  • The port is open


We need port that is being used by Master service to be open in Firewall on the master machine. By default, the port is 8391.

Possible error in worker error log if the port is not open:

System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at https://Master.domain.com:8391/ClusterManagement/ that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond <MasterIP>:8391

at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)

at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)

--- End of inner exception stack trace ---

at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)

at System.Net.HttpWebRequest.GetRequestStream()

at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()



  • Validate certificates in certificate store


Worker server: Worker machine needs to have master certificate in its trusted root and the local worker certificate in personal.

If Master certificate is not present, we can find the copy of the certificate in master machine in DTS\Binn location (Example: C:\Program Files\Microsoft SQL Server\140\DTS\Binn\SSISScaleOutMaster.cer)

We need to copy it from this location and install the certificate on worker



Master server: Master server needs to have master certificate as well as the worker certificate in its trusted root.

If the worker certificate is not present we can find it in DTS\Binn location of worker server (Example: "C:\Program Files\Microsoft SQL Server\140\DTS\Binn\SSISScaleOutWorker.cer" )

Note: By default, when we try to add the worker, it will try to make appropriate changes to the worker config file as well as install the certificates



  • Validate worker configuration


Worker config file location: \DTS\Bin\ WorkerSettings.config

Example: C:\Program Files\Microsoft SQL Server\140\DTS\Binn\WorkerSettings.config



Possible error in worker log if configured to incorrect master name:

Error when sending agent heartbeat.

System.ServiceModel.EndpointNotFoundException:

There was no endpoint listening at https://wrongmaster.domain.com:8391/ClusterManagement/ that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: The remote name could not be resolved: 'wrongmaster.domain.com'

at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)

at System.Net.HttpWebRequest.GetRequestStream()

at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()



  • Verify if the Master end point and certificate thumbprints are mapped properly


"MasterEndpoint": "https://masterserver.domain.com:8391",
"MasterHttpsCertThumbprint": "<Master Certificate Thumbprint here> ",
"WorkerHttpsCertThumbprint": "<Worker Certificate Thumbprint here>",


To get the certificate thumbprint,

DoubleClick on certificate -> Details -> Thumbprint



Make sure the config file is corrected and restart the worker service.

After all the above settings are verified, we have to add the worker from ISManager again.

If the issue is still present, check if the worker service is running under domain account, in that case, we can try changing it to local system and see if that works. After adding the worker, we can change the account back to domain account and restart the worker service.



Additional information:

If we are having issue with the master service itself not shown online or getting error saying master service is not installed on this server, we can check the master configuration to map it to correct instance

Master config file location:

<path>:\Program Files\Microsoft SQL Server\140\DTS\Binn\MasterSettings.config
"PortNumber": 8391,
"SSLCertThumbprint": "<Master certificate thumbprint>",
"SqlServerName": "<masterserver\\instancename >",
"CleanupCompletedJobsIntervalInMs":43200000,
"DealWithExpiredTasksIntervalInMs":300000,
"MasterHeartbeatIntervalInMs":30000,
"SqlConnectionTimeoutInSecs":15
By changing the server name here, we can map the master to different instance.



Author: Chaitra Hegde – Support Engineer, SQL Server BI Developer team, Microsoft

Reviewer: Krishnakumar Rukmangathan – Support Escalation Engineer, SQL Server BI Developer team, Microsoft

%3CLINGO-SUB%20id%3D%22lingo-sub-319037%22%20slang%3D%22en-US%22%3ESSIS%20Scale%20Out%20worker%20is%20not%20showing%20up%20in%20Worker%20Agents%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-319037%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3EFirst%20published%20on%20MSDN%20on%20Dec%2001%2C%202017%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20Understanding%20of%20the%20issue%3A%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Adding%20the%20scale%20out%20worker%20to%20the%20master%20shows%20successful%20but%20this%20does%20not%20show%20up%20in%20the%20SQL%20Server%20integration%20services%20%E2%80%93%20Manage%20Scale%20Out%20(ISManager).%20Also%2C%20this%20will%20not%20be%20added%20in%20%5BSSISDB%5D.%5Binternal%5D.%5Bworker_agents%5D%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Adding%20SSIS%20worker%20completes%20in%20the%20wizard%20as%20below%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F68616iF0F16F79446FB1E9%22%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20After%20this%20finished%2C%20if%20we%20check%20the%20ISManager%20or%20worker_agents%20it%20is%20not%20showing%20up.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EWe%20can%20find%20the%20logs%20for%20both%20master%20and%20worker%20in%20below%20locations%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Master%3A%20%3CPATH%3E%3A%5CUsers%5C%5Baccount%5D%5CAppData%5CLocal%5CSSIS%5CScaleOut%5CMaster%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20(Example%3A%20C%3A%5CUsers%5CSSISScaleOutMaster140%5CAppData%5CLocal%5CSSIS%5CScaleOut%5CMaster)%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Worker%3A%20%3CPATH%3E%3A%5CUsers%5C%5Baccount%5D%5CAppData%5CLocal%5CSSIS%5CScaleOut%5CAgent%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20(Example%3A%20C%3A%5CUsers%5CSSISScaleOutWorker140%5CAppData%5CLocal%5CSSIS%5CScaleOut%5CAgent)%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Things%20to%20verify%20for%20this%20issue%3A%20%3CBR%20%2F%3E%3CUL%3E%3CBR%20%2F%3E%3CLI%3E%3CSTRONG%3E%20The%20port%20is%20open%20%3C%2FSTRONG%3E%3C%2FLI%3E%3CBR%20%2F%3E%3C%2FUL%3E%3CBR%20%2F%3E%20We%20need%20port%20that%20is%20being%20used%20by%20Master%20service%20to%20be%20open%20in%20Firewall%20on%20the%20master%20machine.%20By%20default%2C%20the%20port%20is%208391.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Possible%20error%20in%20worker%20error%20log%20if%20the%20port%20is%20not%20open%3A%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CEM%3E%20System.ServiceModel.EndpointNotFoundException%3A%20There%20was%20no%20endpoint%20listening%20at%20%3CA%20href%3D%22https%3A%2F%2FMaster.domain.com%3A8391%2FClusterManagement%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2FMaster.domain.com%3A8391%2FClusterManagement%2F%3C%2FA%3E%20that%20could%20accept%20the%20message.%20This%20is%20often%20caused%20by%20an%20incorrect%20address%20or%20SOAP%20action.%20See%20InnerException%2C%20if%20present%2C%20for%20more%20details.%20---%26gt%3B%20System.Net.WebException%3A%20Unable%20to%20connect%20to%20the%20remote%20server%20---%26gt%3B%20System.Net.Sockets.SocketException%3A%20A%20connection%20attempt%20failed%20because%20the%20connected%20party%20did%20not%20properly%20respond%20after%20a%20period%20of%20time%2C%20or%20established%20connection%20failed%20because%20connected%20host%20has%20failed%20to%20respond%20%3CMASTERIP%3E%3A8391%20%3C%2FMASTERIP%3E%3C%2FEM%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CEM%3E%20at%20System.Net.Sockets.Socket.DoConnect(EndPoint%20endPointSnapshot%2C%20SocketAddress%20socketAddress)%20%3C%2FEM%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CEM%3E%20at%20System.Net.ServicePoint.ConnectSocketInternal(Boolean%20connectFailure%2C%20Socket%20s4%2C%20Socket%20s6%2C%20Socket%26amp%3B%20socket%2C%20IPAddress%26amp%3B%20address%2C%20ConnectSocketState%20state%2C%20IAsyncResult%20asyncResult%2C%20Exception%26amp%3B%20exception)%20%3C%2FEM%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CEM%3E%20---%20End%20of%20inner%20exception%20stack%20trace%20---%20%3C%2FEM%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CEM%3E%20at%20System.Net.HttpWebRequest.GetRequestStream(TransportContext%26amp%3B%20context)%20%3C%2FEM%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CEM%3E%20at%20System.Net.HttpWebRequest.GetRequestStream()%20%3C%2FEM%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CEM%3E%20at%20System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()%3C%2FEM%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%3CUL%3E%3CBR%20%2F%3E%3CLI%3E%3CSTRONG%3E%20Validate%20certificates%20in%20certificate%20store%20%3C%2FSTRONG%3E%3C%2FLI%3E%3CBR%20%2F%3E%3C%2FUL%3E%3CBR%20%2F%3E%20Worker%20server%3A%20Worker%20machine%20needs%20to%20have%20master%20certificate%20in%20its%20trusted%20root%20and%20the%20local%20worker%20certificate%20in%20personal.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20If%20Master%20certificate%20is%20not%20present%2C%20we%20can%20find%20the%20copy%20of%20the%20certificate%20in%20master%20machine%20in%20DTS%5CBinn%20location%20(Example%3A%20C%3A%5CProgram%20Files%5CMicrosoft%20SQL%20Server%5C140%5CDTS%5CBinn%5CSSISScaleOutMaster.cer)%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20We%20need%20to%20copy%20it%20from%20this%20location%20and%20install%20the%20certificate%20on%20worker%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Master%20server%3A%20Master%20server%20needs%20to%20have%20master%20certificate%20as%20well%20as%20the%20worker%20certificate%20in%20its%20trusted%20root.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20If%20the%20worker%20certificate%20is%20not%20present%20we%20can%20find%20it%20in%20DTS%5CBinn%20location%20of%20worker%20server%20(Example%3A%20%22C%3A%5CProgram%20Files%5CMicrosoft%20SQL%20Server%5C140%5CDTS%5CBinn%5CSSISScaleOutWorker.cer%22%20)%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Note%3A%20By%20default%2C%20when%20we%20try%20to%20add%20the%20worker%2C%20it%20will%20try%20to%20make%20appropriate%20changes%20to%20the%20worker%20config%20file%20as%20well%20as%20install%20the%20certificates%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%3CUL%3E%3CBR%20%2F%3E%3CLI%3E%3CSTRONG%3E%20Validate%20worker%20configuration%20%3C%2FSTRONG%3E%3C%2FLI%3E%3CBR%20%2F%3E%3C%2FUL%3E%3CBR%20%2F%3E%20Worker%20config%20file%20location%3A%20%5CDTS%5CBin%5C%20WorkerSettings.config%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Example%3A%20C%3A%5CProgram%20Files%5CMicrosoft%20SQL%20Server%5C140%5CDTS%5CBinn%5CWorkerSettings.config%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Possible%20error%20in%20worker%20log%20if%20configured%20to%20incorrect%20master%20name%3A%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CEM%3E%20Error%20when%20sending%20agent%20heartbeat.%20%3C%2FEM%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CEM%3ESystem.ServiceModel.EndpointNotFoundException%3A%20%3C%2FEM%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CEM%3E%20There%20was%20no%20endpoint%20listening%20at%20%3CA%20href%3D%22https%3A%2F%2Fwrongmaster.domain.com%3A8391%2FClusterManagement%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwrongmaster.domain.com%3A8391%2FClusterManagement%2F%3C%2FA%3E%20that%20could%20accept%20the%20message.%20This%20is%20often%20caused%20by%20an%20incorrect%20address%20or%20SOAP%20action.%20See%20InnerException%2C%20if%20present%2C%20for%20more%20details.%20---%26gt%3B%20System.Net.WebException%3A%20The%20remote%20name%20could%20not%20be%20resolved%3A%20'wrongmaster.domain.com'%20%3C%2FEM%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CEM%3E%20at%20System.Net.HttpWebRequest.GetRequestStream(TransportContext%26amp%3B%20context)%20%3C%2FEM%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CEM%3E%20at%20System.Net.HttpWebRequest.GetRequestStream()%20%3C%2FEM%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CEM%3E%20at%20System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()%3C%2FEM%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%3CUL%3E%3CBR%20%2F%3E%3CLI%3EVerify%20if%20the%20Master%20end%20point%20and%20certificate%20thumbprints%20are%20mapped%20properly%3C%2FLI%3E%3CBR%20%2F%3E%3C%2FUL%3E%3CBR%20%2F%3E%20%22MasterEndpoint%22%3A%20%22%3CA%20href%3D%22https%3A%2F%2Fmasterserver.domain.com%3A8391%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmasterserver.domain.com%3A8391%3C%2FA%3E%22%2C%20%3CBR%20%2F%3E%20%22MasterHttpsCertThumbprint%22%3A%20%22%3CMASTER%20certificate%3D%22%22%20thumbprint%3D%22%22%20here%3D%22%22%3E%20%22%2C%20%3CBR%20%2F%3E%20%22WorkerHttpsCertThumbprint%22%3A%20%22%3CWORKER%20certificate%3D%22%22%20thumbprint%3D%22%22%20here%3D%22%22%3E%22%2C%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20To%20get%20the%20certificate%20thumbprint%2C%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20DoubleClick%20on%20certificate%20-%26gt%3B%20Details%20-%26gt%3B%20Thumbprint%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F68617i420BDB0D016CD3A9%22%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Make%20sure%20the%20config%20file%20is%20corrected%20and%20restart%20the%20worker%20service.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20After%20all%20the%20above%20settings%20are%20verified%2C%20we%20have%20to%20add%20the%20worker%20from%20ISManager%20again.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20If%20the%20issue%20is%20still%20present%2C%20check%20if%20the%20worker%20service%20is%20running%20under%20domain%20account%2C%20in%20that%20case%2C%20we%20can%20try%20changing%20it%20to%20local%20system%20and%20see%20if%20that%20works.%20After%20adding%20the%20worker%2C%20we%20can%20change%20the%20account%20back%20to%20domain%20account%20and%20restart%20the%20worker%20service.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EAdditional%20information%3A%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20If%20we%20are%20having%20issue%20with%20the%20master%20service%20itself%20not%20shown%20online%20or%20getting%20error%20saying%20master%20service%20is%20not%20installed%20on%20this%20server%2C%20we%20can%20check%20the%20master%20configuration%20to%20map%20it%20to%20correct%20instance%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Master%20config%20file%20location%3A%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CPATH%3E%3A%5CProgram%20Files%5CMicrosoft%20SQL%20Server%5C140%5CDTS%5CBinn%5CMasterSettings.config%20%3CBR%20%2F%3E%20%22PortNumber%22%3A%208391%2C%20%3CBR%20%2F%3E%20%22SSLCertThumbprint%22%3A%20%22%3CMASTER%20certificate%3D%22%22%20thumbprint%3D%22%22%3E%22%2C%20%3CBR%20%2F%3E%20%22SqlServerName%22%3A%20%22%3CMASTERSERVER%3E%22%2C%20%3CBR%20%2F%3E%20%22CleanupCompletedJobsIntervalInMs%22%3A43200000%2C%20%3CBR%20%2F%3E%20%22DealWithExpiredTasksIntervalInMs%22%3A300000%2C%20%3CBR%20%2F%3E%20%22MasterHeartbeatIntervalInMs%22%3A30000%2C%20%3CBR%20%2F%3E%20%22SqlConnectionTimeoutInSecs%22%3A15%20%3CBR%20%2F%3E%20By%20changing%20the%20server%20name%20here%2C%20we%20can%20map%20the%20master%20to%20different%20instance.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EAuthor%3A%20%3C%2FSTRONG%3E%20Chaitra%20Hegde%20%E2%80%93%20Support%20Engineer%2C%20SQL%20Server%20BI%20Developer%20team%2C%20Microsoft%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20Reviewer%3A%20%3C%2FSTRONG%3E%20Krishnakumar%20Rukmangathan%20%E2%80%93%20Support%20Escalation%20Engineer%2C%20SQL%20Server%20BI%20Developer%20team%2C%20Microsoft%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%3C%2FMASTERSERVER%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-319037%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20MSDN%20on%20Dec%2001%2C%202017%20%26nbsp%3BUnderstanding%20of%20the%20issue%3AAdding%20the%20scale%20out%20worker%20to%20the%20master%20shows%20successful%20but%20this%20does%20not%20show%20up%20in%20the%20SQL%20Server%20integration%20services%20%E2%80%93%20Manage%20Scale%20Out%20(ISManager).%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-319037%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntegration%20Services(SSIS)%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3C%2FMASTER%3E%3C%2FPATH%3E%3C%2FWORKER%3E%3C%2FMASTER%3E%3C%2FPATH%3E%3C%2FPATH%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Jan 15 2019 05:42 PM
Updated by: