01-30-2013 06:34 AM
I tried to launch ACT! by Sage 2010 Version 184.108.40.206, Hot Fix 1 today and got the following error message. I could not find a solution online. Does anyboday have an idea how to fix this?
System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:28952.
Server stack trace:
at System.Net.Sockets.Socket.Connect(IPAddress addresses, Int32 port)
at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket(AddressFamily family)
at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew)
at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream)
at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)
Exception rethrown at :
at Act.Application.Act.Main(String args)
01-31-2013 06:53 AM
Welcome to the Sage ACT! Online Community!
Can you provide some additional information:
- Operating system
- Is database physically on this machine, or hosted (shared database)
- If shared, do other users have the same issue
- Service 'SQL Server (ACT7)' not started
- Service 'SQL Server Browser' not started (if shared database)
- Firewall blocking (exceptions: KB Article 25125)
01-31-2013 09:21 AM
Make sure SQL Server ( ACT 7 ) service is Started
Scroll down the list until you see it. Double click the item to modify/Start it.. Cheers - FSB
01-31-2013 10:51 AM - last edited on 02-01-2013 05:40 AM by gmartin
Thank you for taking the time to respond to my request. I started the SQL Server (ACT7) service. It was set to automatic. When I tried to launch the application, I received the same error message. Let me look at the other response I received from the Community and I will get back with you.
I noticed in your signature that you are the President of Fill Staff. I'm wondering if it would be feasible to work together?
[Edit: Removed personal information. Please use Private Notes for this type of communication; click on Community user name and select 'Send a Private Message' option.]
Best regards and, again, thank for your time and efforts!
01-31-2013 11:25 AM
Thanks for taking the time to respond to my request.
I'm using ACT! on a single PC running Windows 7 Pro SP1.
I must assume that the database is physically on this machine as the program was working a short while ago.
I'm using ZoneAlarm Anti-Virus and also have SpyShelter Personal and WinPatrol installed on my PC. Both of these programs had never before caused any conflicts with ACT!.
SQL Server (ACT7) had been set to Automatic, so I started the service but received the same error message when I tried to re-launch ACT! SQL Server Browser is currently set to 'Disabled'.
Please let me know if you need any additional informaiton and, again, thank you for your response.
01-31-2013 07:12 PM
Another respondant to this issue, Bill Williams, discovered that my ACT folder was not in the My Documents folder. We moved it but that did not clear up the problem. Bill suggested thtat I locate a download link for ACT! 2010 Diagnostic Tool. I couldn't find one in the Community. Have you any idea where or how I might acquire the download? I do not have an ACT! 2010 disk as I purchased a downloadable version of the applicaiton. Also, do you know if there are any free tools or ways to hack or reset passwords in ACT!?
01-31-2013 08:07 PM
ActDiag can be found here: http://kb.sagesoftwareonline.com/app/answers/detail/a_id/27607/
Just reading the thread, I'd be inclinded (and you may have already done these) make sure that you're logged in as a Windows Admin, run ACT! as Administrator.
I'd turn off AV & Firewalls (updates to them can interfere with SQL) temporarily to test, if it works, we've located the issue, then to fix it
At a guess, I'd say that possibly a Windows Update (to SQL) might have changed the SQL Port being used. ActDiag will show you which port is used (ActDiag | Server | Server Security | TCP/IP Port). Make sure that this port is allowed by the firewall.
02-01-2013 05:43 AM
To add to Ben's comments, I would also suspect the anti-virus software. Here is an article with exceptions to add to the a/v software: KB Article 25125
02-01-2013 08:34 AM
02-01-2013 08:37 AM