Chrome might be raising a popup and/or you might have some settings configured to disallow that. You also might have something like https only settings enabled and since the Sage service URL is not https, the browser might not allow you to connect to a site that redirects your connection.

You should test the URL in Chrome and potentially some different browsers to try to identify the problem. The URL is structured like the following:

http://services.sagesoftware.com/services.asp?sid=8&regid=<serialno>&trackingid=<trackingno>

You will need to replace <serialno> with your customer serial number found in SM Maintain Site, and the <trackingno> with a valid package tracking number.

It seems to forward to https://www.sage.com/en-us/?sid=8&regid=<serialno>&trackingid=<trackingno> which then just goes to the generic sage website.  This is at least as of 7/6/2023.  Not sure if it was working yesterday. 

I recall successfully testing this, but it's been a few weeks. Not sure if Sage changed something but it failed for me as well. Interestingly enough, the old URL still worked for me, so this probably requires you open a case unless Ramon or someone in Sage Support can comment here.

I can't post the URL any longer as the forum software keeps replacing it, but I think this was updated to sagesoftware.com in the 7.2 or 7.4 time frame. The URL is hard-coded in the source. To use the old one, simply replace sagesoftware.com with bestsoftwareinc.com.

 I sent a request to support earlier today but haven't heard back yet. 

Well, it looks like the URL is constructed in the sozdf001.frm source, but not sure if that helps since I'm not sure if Support cracks open source code any longer. If the sagesoftware.com URL no longer works, that is a change Sage made to their services API which might be the source of your problem.

Well, it looks like the URL is constructed in the sozdf001.frm source, but not sure if that helps since I'm not sure if Support cracks open source code any longer. If the sagesoftware.com URL no longer works, that is a change Sage made to their services API which might be the source of your problem.

It is indeed being constructed in sozdf001.frm an generates an URL of 

http://services.sagesoftware.com/services.asp?sid=DummyID&regid=Sage500SerialNo&trackingid=DummyTrackID

Where I have replaced the sid with a dummy value,a site specific serial number with a dummy value, and actual tracking number with dummy data (it was a USPS tracking number in my test)