04-11-2017 07:49 AM
We are struggling with the same issue. In our customer' case, a new firewall has been implemented and the problem now occurs when the customer enables HTTPS traffic (Act! works fine if ALL HTPS traffic is allowed)
Quite reasonably, the customer has asked what ports/services need to be opened/unblocked in the new firewall in order to allow them to enable HTTPS.
Swiftpage Tech support have logged on to a User's PC and investigated, concluding with a recommendation to delete the registrationdata.xml (Program Data) which removed the error message but presented a new error message when registration was attempted again. Swiftpage then advised re installation of Protexis, which made no difference.
Note that this issue affects all Users, so these particular steps on a single User's PC seemed a bit futile to us!
Our client has verified that Ports 1690 and 443 are open for outbound traffic.
Swiftpage are unable to offer any further advice or suggestion.
Not sure where to go from here. Any ideas?
Env: Act! v19.1 Premium, Update 2; Windows 2012 Server with Windows 10 Workstations (50+).
04-11-2017 07:58 AM
You have mentioned port 1690 and 443, i would like to confirm Port 80 and 8080 have been unblocked also.
and if possible to add exceptions for applications please ensure: PsiService_2.exe has been added.
04-11-2017 08:28 AM
This issue can occur if the network uses a proxy server. You will need to make sure the proxy server is configured to unblock Port 443 and allow access to license.ntitles.net.
You can run the following test using command prompt on a machine to test if it can reach the licensing server via it's required port:
telnet license.ntitles.net 443
You should get a blank screen if the connection is successful, otherwise an error will be shown.
04-11-2017 08:38 AM
Thanks Gary, but 'been there, done that'
04-12-2017 05:50 AM
07-11-2017 01:00 AM - edited 07-11-2017 01:02 AM
We have a client that is never allowed to have their servers connected to the internet. They would breach the HMRC regulations that they have to work under if they did so.
(ACT was installed and licence activated off site before server went live on system)
Is there any way out of this as they are now getting the message?
07-11-2017 03:23 AM
07-11-2017 03:33 AM
It is a perpetual licence so I thought it odd we were getting the message as well.
07-11-2017 03:47 AM
10-08-2017 03:24 PM