Community
Showing results for 
Search instead for 
Do you mean 
Reply

No Connection Could Be Made...

Accepted Solution Solved
Nickel Elite Contributor
Posts: 1,449
Country: USA
Accepted Solution

No Connection Could Be Made...

Client on 2010 Web on Server 2008.  Multiple times per day, end-users are receiving a message stating "No connection could be made because the target machine actively refused it 127.0.0.1".  There are a number of posts here as well as in the ACT! CC newsgroups but no one has posted a solution.  The temporary workaround is to just restart IIS but then the issue comes up again a few hours or at most a day later.  Anyone know of a more permanent solution?

 

-----------
Marshall Knapp
AspenTech Consulting Group, Inc.
Act! Certified Consultants - Diamond Level
866-880-4ACT (4228)
www.aspen-tech.com

Accepted Solutions
Solution
Accepted by topic author mknapp
‎09-25-2015 03:20 AM
Nickel Elite Contributor
Posts: 1,449
Country: USA

Re: No Connection Could Be Made...

Received this from the client last week:


"I found some information on the ASP.net forum like you suggested and did
the following to resolve this Act logon error message:  No connection could
be made because the target machine actively refused it 127.0.0.1:47654

 We added a few exclusions for the ACT server to Trend AntiVirus.

C:\Windows\IIS Temporary Compressed Files
C:\Windows\system32\w3wp.exe

C:\act and C:\inetpub already existed in exclusion list

Users have not received this error msg. since making this change. Thanks for
your help!"

-----------
Marshall Knapp
AspenTech Consulting Group, Inc.
Act! Certified Consultants - Diamond Level
866-880-4ACT (4228)
www.aspen-tech.com

View solution in original post


All Replies
Platinum Super Contributor
Posts: 5,275
Country: USA

Re: No Connection Could Be Made...

One thing we've found that can cause this issue is the Act!/Outlook integration.  To determine if that is the culprit: on the server open a Task Manager and on the Processes tab locate the 'W3WP.exe' service and watch it's memory usage.  Also check the Event Viewer for Out of Memory errors with W3WP. 

If you are seeing the memory increase every few seconds, it can be the Act!/Outlook integration attempting to attach 'failed' messages. 

 

If these match your situation, you can have your end users clear out their Failed to Attach messages using the 'Attach to Act! progress' icon in the system tray (clean out the 'Not Attached Messages' tab).

 

Or you can go into the Act! Historyqueue folder located at:

XP: C:\Documents and Settings\*user*\Application Data\ACT\ACT for Web\HistoryQueue

Vista/Win7: C:\Users\*user*\AppData\Roaming\Act\Act for Web\HistoryQueue

and delete all messages within this folder.

Greg Martin
Sage
Solution
Accepted by topic author mknapp
‎09-25-2015 03:20 AM
Nickel Elite Contributor
Posts: 1,449
Country: USA

Re: No Connection Could Be Made...

Received this from the client last week:


"I found some information on the ASP.net forum like you suggested and did
the following to resolve this Act logon error message:  No connection could
be made because the target machine actively refused it 127.0.0.1:47654

 We added a few exclusions for the ACT server to Trend AntiVirus.

C:\Windows\IIS Temporary Compressed Files
C:\Windows\system32\w3wp.exe

C:\act and C:\inetpub already existed in exclusion list

Users have not received this error msg. since making this change. Thanks for
your help!"

-----------
Marshall Knapp
AspenTech Consulting Group, Inc.
Act! Certified Consultants - Diamond Level
866-880-4ACT (4228)
www.aspen-tech.com
New Member
Posts: 9
Country: United States

Re: No Connection Could Be Made...

[ Edited ]

Dear Sage,

 

Are you going to fix this error or provide an ample workaround? I can't tell 20 or 30 users to "keep an eye" on their waiting to be attached messages because if one misses to "clear" the server crashes for all.

 

Thank you,

 

Alex

Nickel Elite Contributor
Posts: 1,449
Country: USA

Re: No Connection Could Be Made...

Alex,

Sage recently released ACT! 2010 SP1 Hotfix 2.  This hotfix does address some performance issues with Outlook and may help in this scenario.  Worth a shot.

-----------
Marshall Knapp
AspenTech Consulting Group, Inc.
Act! Certified Consultants - Diamond Level
866-880-4ACT (4228)
www.aspen-tech.com
New Member
Posts: 9
Country: United States

Re: No Connection Could Be Made...

[ Edited ]

Such a detailed KB Sage offered for this one:

http://kb.sagesoftwareonline.com/cgi-bin/sagesoftwareonline.cfg/php/enduser/std_adp.php?p_faqid=2599...**&p_li=&p_topview=1

 

They forgot to mention (as of today) that after HFX EXE installation you have to log on to console to complete the process - the last step (omitted form KB and from HotFX wizard) is to update the database (otherwise HTTP connection will simply time out)! It takes about 10-15 minutes to complete the undocummented last step.

I don't  hold my breath for this one. I tend to get emotional when it comes to troubleshooting/using ACT!

After installation i've discovered that  one of the old issues is still present: there is a version mismatch between WEB interface(ACT! by Sage Premium for Web 2010  Version: 12.1.169.0) and console (ACT! by Sage Premium for Web 2010 Version 12.1.181.0, Hot Fix 2). While I was checking hfx version, I got GDI+ error in console session and web session simply crashed on me asking to contact administrator. I just don't understand this kind of development.

 

Thank you for the tip, Marshall.

 

Alex.

New Member
Posts: 9
Country: United States

Re: No Connection Could Be Made...

[ Edited ]

Hotfix lists Outlook Integration as one of the problems addressed. Fool me once...

I've installed it and it immediately started to crash the web service. 2 reps were helping me troubleshoot for 2 days. They basically stared at the screen and looked at the event log errors. That is it! It took them approx. 4 hours to tell me they need speak with "product specialist". And what do they do exactly? Gather data? I thought they were the specialists...  Fool me twice... My comment about disabling Outlook integration was ignored. In the meantime users are in standby. They are not extremely productive when in idle, I must say. I could not wait for more nonsense tomorrow, so I've disabled Outlook Integration myself. Now I'm back in business. Act web is up and running.

 

New Member
Posts: 5
Country: United Kingdom

Re: No Connection Could Be Made...

[ Edited ]

I've spent hours and hours just trying to find an approach to debug this message. WP3 process is fine, outlook integration has not been setup, sharing has been enabled, . . . . . etc etc

 

Still receiving the same:

 

Error validating user. No connection could be made because the target machine actively refused it 127.0.0.1:47654

 

I have database X which I can log into to Administrate the web site. In the web administration dialogue I added Database Y.

 

Database Y had it's pasword changed by the client. Either client is mistaken about the password been set or something is corrupt. So I can no longer even remove database Y from the web administration.

 

I'm used to logging into SQl Server and being able to set permissions on Databases not sure why this isn't easily available from Sage. I noticed in one post that there is the actDiag approach but I've now reached the stage I'm wary of setting the SA password without testing first as I've noticed so many problems on backups etc unless you know sage under the hood.

 

Can somebody please confirm that I can set the SA password via ActDiag without any gotchas. Having done that can I then administrate using something like SQL Server Studio Manager and set passwords for the locked database. I still don't understand why a database has to be sent to Sage Professionals to be 'unlocked' which is what one post indicates.

 

I don't think the locked database is related to the above error message but at least I can then rule that out.

 

Act version is Act! Premium For Web 2010 with hotfix 4 applied, Windows 2003 Standard.

 

Any reply would be appreciated. I had a problem when first setting up as I wanted it to be run from an existing domain, I was pointed to a knowledge base and performed the copy of the relevant files and permissions but no joy. So, I contacted Sage who said I would need to speak to Microsoft. I said I am wiling to open a ticket and pay for support but I was told that they do not handle support for IIS - I joke not, I was amazed by that response. I figured a workaround by using a fixed IP address.

 

Anybody around who can restore a confidence in this product?

 

New Member
Posts: 5
Country: United Kingdom

Re: No Connection Could Be Made...

Solution found: I changed the ASP.NET user account but, . . . it doesn't seem sufficient to just change that, I could be wrong (tried lot's of options)  may require a service restart and\or IIS restart, I wasn't in the mood any more so I just rebooted the server - that guaranteed flushing the whole lot. Didn't make sense that firewall was a problem as it had already gone through to reach that block. There is no need to open additional firewall ports. I have seen posts explaining that adding another user as an Admin and then logging in then out etc etc, has solved - this may also have contributed to the solution.

 

HTH