One of CMS services is not listening TCP port 50121
Updated: 21 May 2010 | 10 comments
Hello,
Which service should own listening socket for port 50121? Netstat does not show anyone listening there.
After the following error message given below, Symantec Installation Manager simply blocks and then fails installation when Stopping AeXSvc service. I have .net 3.5 without SP1. Any ideas?
Log File Name: C:\Program Files\Altiris\Notification Server\Logs\a.log Priority: 1 Date: 7/21/2009 7:14:55 AM Tick Count: 13100078 Host Name: ALTIRIS-CMS Process: w3wp (1700) Thread ID: 7 Module: w3wp.exe Source: Altiris.TaskManagement.ClientTask.* Description: BaseXmlCallback Exception: System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:50121 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Connect(EndPoint remoteEP) at Altiris.DotNetLib.Sockets.SecureRemoting.SecureRemotingClient.EstablishConnection() at Altiris.DotNetLib.Sockets.SecureRemoting.SecureRemotingClient.AttempSendRequest(String service, Hashtable input) at Altiris.DotNetLib.Sockets.SecureRemoting.SecureRemotingClient.SendRequestI(String service, Hashtable input) at Altiris.DotNetLib.Sockets.SecureRemoting.SecureRemotingClient.SendRequest(String service, Hashtable input) at Altiris.ClientTask.Server.HttpHandlers.WebClientApiManager.ProcessRegister(XmlTextWriter wr, NameValueCollection queryValues, Stream requestStream, Int32 contentLength) at Altiris.ClientTask.Server.HttpHandlers.Register.WriteResponse(XmlTextWriter wr) at Altiris.TaskManagement.Common.XmlHttp.BaseXmlXmlHttpCallback.WriteResponseRaw(XmlTextWriter xwr) at Altiris.TaskManagement.Common.XmlHttp.BaseXmlHttpCallback.ProcessRequest(HttpContext context)
discussion Filed Under:
Comments
Hello, The Task Server
Hello,
The Task Server (Altiris Object Host Service (atrshost.exe)) listening on 50121 and 50122, this is used by task server web talking to task server process, so is local only traffic. I don't have sure but you could try change this port... at Altiris.ClientTask.Remoting.config.
Best regards,
If the suggestion has helped to solve your problem, please mark the post as a solution.
Fábio Sanches
Altiris Consultant
check services
i have seen that as a reply port.
check all the altiris services also.
Same problem - No Client Connection to the Task Servers
I am facing a similar problem. No client can connect to a task server (we have 2).
They are have similar log entries: No connection could be made because the target machine actively refused it 127.0.0.1:50121
Netstat lists all the task Server ports listening but 50121.
Any Ideas?
Also similar problem - No Client Connection to task servers
Not during installation but clients have same log entries - No connection could be made because the target machine actively refused it 127.0.0.1:50121.
Very interested in solution, definitely don't have .NET 3.5 Sp1 installed.
R
Something to check
Do you have the default (or any) maintenance window enabled?
Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.
Task Server issue - Maintenance Window
Jim,
no, I don't have any Maintenance Windows set. Other interesting thing is that this has previously worked. Something has obviously changed, now just a question of finding what that "something" is :)
r
R
What I have seen (at least post SP2)
When at least one maintenance window IS NOT defined, all client communication will be rejected. I have seen (on the client side) HTTP 407 errors, plus the socket\communication rejection errors.
Now, the argument could be made that you should have a maintenance window, that's why they are there. If that's the case, then you shouldn't be allowed to disable the default one in the first place.
Our workaround was to enable the default window and set it from 6am to 6pm, 24 hour availability.
Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.
Very interesting
Jim,
that's great info, thanks.
Just to check, i'm going to adjust the default Maintenance Window to be :
- A 24 hour long maintenance window with
- A 24 hour duration
Is that right?
If you fix this, I owe you a cold one :)
r
R
yep that's correct
I've had some musings and discussions off board about this, but really as convienient and requested as maintenance windows are, if you don't need one, then the ability to toggle it off should either be supported (or prevented). IMHO.
Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.
Heartily agreed mate...
Couldn't agree more, they're just creating issues for themselves doing it this way.
After I set the window, things looked up briefly but then got dreaded 407 etc back. I thought my installation might be kaput though so I repaired the whole SMS suite. I think it's still bust as in "Site Server Settings - Task Service - advanced", I'm missing the "Task Service Installation" policy which I'm informed should be there.
SymSupport are looking at this so I'm hopeful for ideas from them.
Even tried adding in NS name (Netbios and FQDN) as manual exception in Tools - Internet options - Connections - LAN Settings - Advanced to prevent the whole "Proxy autentication...." errors but no joy
*Sigh* another fun day with ns7 :)
R
Would you like to reply?
Login or Register to post your comment.