Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

No connection could be made because the target machine actively refused it 127.0.0.1:8019

SmartConnector Forum

Schneider Electric support forum about SmartConnector applications for integration of other building management systems (BMS) into EcoStruxure Building Operation.

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • EcoStruxure Building
  • SmartConnector
  • SmartConnector Forum
  • No connection could be made because the target machine actively refused it 127.0.0.1:8019
Options
  • Subscribe to RSS Feed
  • Mark Topic as New
  • Mark Topic as Read
  • Float this Topic for Current User
  • Bookmark
  • Subscribe
  • Mute
  • Printer Friendly Page
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Top Experts
User Count
JeffBowman
Sisko JeffBowman Sisko
164
ardak
ardak Schneider Alumni (Retired)
34
sesa180908_brid
Commander sesa180908_brid Commander
34
mike_meirovitz
Commander mike_meirovitz
21
View All

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Back to SmartConnector Forum
mike_meirovitz
Commander mike_meirovitz
Commander

Posted: ‎2022-10-16 11:55 PM

0 Likes
3
2113
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2022-10-16 11:55 PM

No connection could be made because the target machine actively refused it 127.0.0.1:8019

Hi,

 

Can someone explain the reason for this error:

No connection could be made because the target machine actively refused it 127.0.0.1:8019

I got 8,340 of this error in ~10 hours of SmartConnector run. See the attached log file.

 

Thank you.

 

Mike

Attachments
2022-10-17 Errors.log
Tags (1)
  • Tags:
  • english
Reply
  • All forum topics
  • Previous Topic
  • Next Topic
Replies 3
ahmet191
Ensign ahmet191
Ensign

Posted: ‎2022-11-12 07:26 AM

0 Likes
0
1902
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2022-11-12 07:26 AM

Hi,

 

I am not an expert and i couldn't look deep inside the log files but i would definetely check the firewall first. maybe shutdown for testing. second, i would change the port number also for testing. Maybe that one is already open or not closed in a right way. 

 

If i am guessing right, you are running ews server and is it have to be listening? I mean it is already a server. Then, it doesn't matter some client is connected or not. Thats why i am suspicious of server connection port and firewall. Like i said, i am not an expert. These are just my guesses but if you already solved this problem, could you please share the solution if it is okay

Tags (1)
  • Tags:
  • english
Reply
Daniel_Cerone
Lieutenant JG Daniel_Cerone Lieutenant JG
Lieutenant JG

Posted: ‎2023-07-25 05:56 AM

0 Likes
0
1617
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2023-07-25 05:56 AM

run a wireshark and see if there are any bottlenecks.

ensure the smartconnector service is running- it will refuse when not running.

check event viewer to see what may have occurred around the time of failure.

/dcer
Reply
markaldo
markaldo
Cadet

Posted: ‎2023-10-15 11:08 PM

0 Likes
0
1457
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2023-10-15 11:08 PM

Often, connectivity issues arise when something is hindering access to a specific port or hostname. This obstruction can be due to a firewall blocking the connection or the service-hosting process not listening on the designated port. This could result from the service not running, or it might be listening on an alternative port. Consequently, establishing a connection becomes impossible.

 

To diagnose the problem, you can try running the netstat -anb command from the command line to check if anything is listening on the intended port. If it returns no results, consider changing the port number. In Windows operating systems, you can use the netstat command via the command line (cmd.exe), while on Linux, you may need to use netstat -anp.

 

Occasionally, when the target machine 'actively refuses' the connection, it could be because the server's 'backlog' is full. In such cases, you might consider increasing the server's backlog, but it's also essential to implement retry logic in your client code to handle this situation. This is necessary because even with an extended backlog, the server could be handling numerous other requests on the same port at that time.



Reply
Preview Exit Preview

never-displayed

You must be signed in to add attachments

never-displayed

 
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of