Sage 100

I'm trying to register Sage Intelligence for Sage 100 2020 on a remote desktop.  The server is Windows 2012 and the Sage installation is Standard.  I keep receiving the following error when I try to perform the registration:

"The Alchemex Update Server could not be reached. Make sure that you are connected to the internet and that the server is reachable.

If you are connected to the Internet through a Proxy Server then please make sure that Alchemex has been configured for Internet Access via the Proxy Server.

Please see the topic 'Proxy Server Settings' in the Help File for more information."

I can ping Sage.com but the registration fails.  There is no proxy server and I have tried changing the DNS to no avail.

Any ideas?

------------------------------
Chuck Peddy
Smartbridge Partners
------------------------------

I recently troubleshot the same message. Have you looked at firewall settings?  I sent my client's IT consultant info from three KB articles.  From KB 59453: Access your firewall's advanced settings and add the BICore.exe program to the whitelist/safelist. Also make sure thatmasintell.na.sage.com is allowed through firewall inbound and outbound rules.  From KB 54145: open access to Sage.com.  The SageCity article referenced in a link in that article doesn't exist anymore.  From KB 78717: Remove Sage Intelligence from your blocked websites list.  The websites to add on the firewall are the following:
https://www.sageintelligence.com/Soft ware/ (htt ps://www.sageintelligence.com/Soft ware/)
http://www.alchemex.net/bibackoffi ceservice/ (htt p://www.alchemex.net/bibackoffi ceservice/)
IP address being:
Port 80
196.22.197.247
It is also possible that the firewall is blocking bilicensing.aspx. A change may need to be temporarily set to alert on the fi e types instead of block to allow computer to access bilicensing.aspx.

After I sent that info, he made adjustments and then I couldn't get past "Error: The download file (PLDONGLE.DLL) is not the expected size."  It took several attempts on their end and they escalated it up the chain.  It was finally resolved when he reported "The licensing call-home to Sage.com tries to pull a "bilicensing.aspx" from masintell.na.sage.com. I created a new allow rule out to the Sage URL that doesn't do any file blocking inspection."  The first guy must have ignored that when the KB articles were sent to him.

------------------------------
Mary Jo Krueger
Senior Software Consultant
CLA (CliftonLarsonAllen LLP)
------------------------------