Hi Ally

Let's start with the basics first. Open the link below for a detailed guide on setting up the Freedom Service. 

https://za-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=200825153334273&page=1&position=1&q=freedom%20service%20setup%20guide

If after carefully applying ALL the steps in this guide and you still need any further assistance, please don't hesitate to get back to us on Sage City on this forum.

Kind Regards

Bennie 

Hello Bennie,

The provided link for Setup Guide was careful followed which I ended up to that error.

Regards,

Ally

Hi Ally

Noted.

In that case, please confirm the following:

1. Are you specifically working on the main Evolution Server PC where the Freedom Service has been installed on?

2. If yes, on the server PC, go to Computer | Manage  | Service and Applications  | Services.

Is the Evolution Freedom Service Host running?

4. Regardless if running, restart it

5. Close and re-open the Evolution company on the server,

6. Now test of your query has bene resolved or not

7. If still a problem: Consider the following fact:
We know that VPN connections may interfere with the Service Manager. Therefore, please test this if running on a any kind of VPV connection:

  a) Closing the Evo company on the server

  b) Turn off the VPN 

  c) Working directly on the server PC, not via the VPN connection, test if your Freedom Service query has now been resolved. 

Please provide feedback 

Kind Regards

Bennie 

Hello Bennie,

1. Yes, on the main server.

2. Restarted the service but still the same case.

6. No VPN is used on the server.

Firewalls turned off and Antivirus uninstalled.

If I enter connection string for another computer freedom service on the network it works but not the one locally within the server.

Regards,

Ally

Hello Bennie,

1. Yes, on the main server.

2. Restarted the service but still the same case.

6. No VPN is used on the server.

Firewalls turned off and Antivirus uninstalled.

If I enter connection string for another computer freedom service on the network it works but not the one locally within the server.

Regards,

Ally

Thanks Ally

So just to confirm:
On the main server PC you observe first the first error above and then directly afterwards the second error?

On the main server If I click Auto locate I get the first error, when I manually set the connection string and click finish it gives the second error.

Thanks Ally

Please apply the steps in'NO CONNECTION COULD BE MADE BECAUSE THE TARGET COMPUTER ACTIVELY REFUSED IT’ CENTRAL SEARCH ERROR.pdf the attached guide on how to fix your query 

Hello Bennie,

I have tried that too but still the same error.

Regards

Hi Ally

In that case, please do the following:

Formally log this query by opening the link below, but request that the new query incident gets sent for my attention so I can then formally contact you and continue on this query for you.

https://app.smartsheet.com/b/form/4c5023eeaff24b05839f55753b05c465

Noted I'm on it, thanks.

Hi Ally

I received the new incident query and will now continue on that platform, moving of from Sage City, to address your query.

Kind regards

Bennie 

Hi Bennie, sorry to chime in on this post but was it something simple you did to rectify this error ? I'm having a similar issue also with the Database Name automatically being added to the end of Freedom Service URL when pushing Auto Locate (I also added evolution as a DEP Exception as per the attached PDF above). 

Hello RyanJ,

If I may ask, what operating system are you using? If it's Windows 10 Pro, can you check the version number? I'm facing this issue on windows 10 Pro version 2004.

Regards,

Ally

Hi, it's Windows 10 Home that I'm using

Go to Settings > System > About. Then check the version number as seen on below image

 Windows 10 Home 2004 

It's the same version number 2004 as I do face the problem with. Let us wait to hear from Bennie as he is working on this hypothesis.

Hi Ryan 

Yip, the query I'm busy dealing with for Ally: he is also running Windows 10 Pro Version 2004. We are currently investigating specifically if ver 2004 could be the reason for your query. I should hopefully be done with the testing at around Mon next week.

Can you please enquire agian then about my findings?

Kind Regards

Bennie