Skip to main content

I sometimes see an error message when trying to re-license after an update (which I've been doing a lot recently to get customers up to 3003).

"This web address is for US and Canadian customers of RBC.  Please click OK and click the indicated URL to continue."

This is from https://rbc.rocketsoftware.com/authprod.asp.  I usually wait a day or two (but not ten!) and go through the process again and it usually seems to work.  I could be entering the details a different way the 2nd time?  The customers work with the VAR to get the license details, so I'm one step removed from requesting and managing the serial numbers, they just call me when they need help.

Anyone else seen this, or have advice on what I'm doing wrong?



------------------------------
Ian McGowan
Principal Consultant
Rocket Forum Shared Account
------------------------------

I sometimes see an error message when trying to re-license after an update (which I've been doing a lot recently to get customers up to 3003).

"This web address is for US and Canadian customers of RBC.  Please click OK and click the indicated URL to continue."

This is from https://rbc.rocketsoftware.com/authprod.asp.  I usually wait a day or two (but not ten!) and go through the process again and it usually seems to work.  I could be entering the details a different way the 2nd time?  The customers work with the VAR to get the license details, so I'm one step removed from requesting and managing the serial numbers, they just call me when they need help.

Anyone else seen this, or have advice on what I'm doing wrong?



------------------------------
Ian McGowan
Principal Consultant
Rocket Forum Shared Account
------------------------------

Ian,

In the background traffic from the RBC servers is directed to one of two servers depending on which part of the world you are in and how you login to RBC. The message and link are directing you to US version of the servers. If RBC detects a problem with the licence details these messages can appear and the detailed that have been entered need to checked and corrected, hence the VAR has to work with us to correct whatever the problem is.

If they are having problems with licencing they need to contact their VAR rather than yourself.

Are you aware that you do not need to restart UniData to apply licence changes ? As long as the Device Licence Count is not changed, after entering a new auth code you can use the command '$UDTBIN/stopsmm -r', this forces UniData to reread the auth code without having to do a restart of UniData.

When available one single command at ECL such as LICENSEUDT - N "who you are" -E "youremail" -R "Reason for Relicense" -C "Company" -A will talk to RBC, get the Auth Code, Report any errors and log the license attempt on our side.

We have also completed the first round of testing of an automated relicence program which talks directly to the RBC server to get an auth code, which can be run from ECL (and the .NET 6 version is also in it's testing phase).

Regards,

 



------------------------------
Jonathan Smith
UniData ATS
Rocket Support
------------------------------

Ian,

In the background traffic from the RBC servers is directed to one of two servers depending on which part of the world you are in and how you login to RBC. The message and link are directing you to US version of the servers. If RBC detects a problem with the licence details these messages can appear and the detailed that have been entered need to checked and corrected, hence the VAR has to work with us to correct whatever the problem is.

If they are having problems with licencing they need to contact their VAR rather than yourself.

Are you aware that you do not need to restart UniData to apply licence changes ? As long as the Device Licence Count is not changed, after entering a new auth code you can use the command '$UDTBIN/stopsmm -r', this forces UniData to reread the auth code without having to do a restart of UniData.

When available one single command at ECL such as LICENSEUDT - N "who you are" -E "youremail" -R "Reason for Relicense" -C "Company" -A will talk to RBC, get the Auth Code, Report any errors and log the license attempt on our side.

We have also completed the first round of testing of an automated relicence program which talks directly to the RBC server to get an auth code, which can be run from ECL (and the .NET 6 version is also in it's testing phase).

Regards,

 



------------------------------
Jonathan Smith
UniData ATS
Rocket Support
------------------------------

Thanks Jonathan - that helps with understanding what's happening.  I have multiple VDI's that I log into, and I think it matters which country you're coming from.

The usual URL is:

https://rbc.rocketsoftware.com/authprod.asp

But the international URL below worked for me (after making sure to enter the same version shown on the confprod screen).

https://rbcint.rocketsoftware.com/authprod.asp
Thanks for the tip on stopsmm -r, that's really handy to know.  And the future license enhancements sound great, It usually works in the end, but the current authorization process can be finicky :-)


------------------------------
Ian McGowan
Principal Consultant
Rocket Forum Shared Account
------------------------------