Home » Support » Telligent Evolution Platform » Telligent Community » Discussions » Error with Job Scheduler - Only one usage of each socket address permitted

Error with Job Scheduler - Only one usage of each socket address permitted

Open Support Ticket

Call Support:
Direct: (214) 420-1337
Toll Free: (877) 522-6334

Monday through Friday
8 a.m. to 6 p.m. Central (GMT-6)

Join our Community
Details
  • 3 Replies
  • 0 Subscribers
  • Postedover 1 year ago
Options

Error with Job Scheduler - Only one usage of each socket address permitted

This question is not answered
Adam Seabridge
Posted by
on Fri, May 11 2012 11:46 AM

Hi , I am using TC 6.1 and everything is working apart from the Job Scheduler. Its starts up fine but then throws this error:

2012-05-11 11:43:04,905 [1] ERROR Telligent.JobScheduler.JobsManager [(null)] -

System.Net.Sockets.SocketException (0x80004005): Only one usage of each socket a

ddress (protocol/network address/port) is normally permitted

  at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress

socketAddress)

  at System.Net.Sockets.Socket.Bind(EndPoint localEP)

  at System.Net.Sockets.TcpListener.Start(Int32 backlog)

  at HttpServer.HttpListener.Start(Int32 backLog)

  at Telligent.JobScheduler.Hosting.JobsApplication.Initialize(SchedulerConfigu

rationElement config)

Scheduler started... press any key to exit

I looked here but this issue does not seem to be listed: telligent.com/.../20960.job-scheduler-installation-and-troubleshooting.aspx

I am guessing it is trying to run on a port that is already in use. If so How do I resolve this?

Thanks

Adam
All Replies
  • Bruno Lopes
    Posted by
    on Fri, May 11 2012 12:18 PM

    Hey Adam, I also faced that issue, and I believe it's the "status service". If you open the tasks.config you have a "statusService" node that can have a port property. Change that to another port, and do the same on the corresponding community website. Afterwards you should be able to start the job scheduler
  • Adam Seabridge
    Posted by
    on Fri, May 11 2012 5:59 PM

    Thanks Bruno. I haven't ever had to do this before and have at least 8 instances of the Task Service running on our development server. I managed to get it to start after I changed the port to 8099 in both the tasks.config and communityserver.config in the site. What is strange though is that I can't get content to index. I will need to look into this further as It doesn't make sense why content is not being indexed as even if I reset the search index it doesn't index.

    Thanks for your assistance with this anyway.

    Adam
  • Bruno Lopes
    Posted by
    on Fri, May 11 2012 6:11 PM

    Are those others also 6.0? 5.6 didn't need this.

    When you start the scheduler, you can connect to that port via a browser and see when the tasks were run, and some status info that might be useful.