WebSpeed Messenger 10.1B Licenence has exiped

[JamesBowen]

Hi All

The solution to my problem might be obvious but I'll ask it anyway. I downloaded the Linux 32bit WebSpeed Messenger from "PSDN Product Downloads" and when I tried to install the Messenger I get an Error message stating that the license has expired. The license was obtained from the "License Memorandum" Page.

Now correct me if I am wrong, but I thought that the WebSpeed messenger was free and why would the license have an expiry date on it?

Also does anyone know if the latest version of the WebSpeed Messenger is backward compatible with 10.1B WebSpeed Broker?

Tomorrow I will make a quick call to Progress Tech Support for a solution.

Many Thanks

James.

 

[Casper]

I am using probably the same license as you do and our messengers are still running.

Can it be that you might have some environment variables (DLC,PROCFG)set on the machine which does some tricks with your license?

I think the messengers should be backward and forward compatible. Haven't tried it though.


Casper.

 

[JamesBowen]

I raised a quick tech support call and they are confused as well. Only explination that the can think of is that the HP-UX tar ball was mixed up with the Linux tar ball. I even re-downloaded the Linux 32 bit tar ball again, but not luck.

But any way I had crack at installing the latest 10.2A Messenger and seams to work with 10.1B Webspeed.

 

[Casper]

If you want I can make the 10.1B tarball I got, but if the 10.2a works for you maybe that isn't necessary.

Casper.

 

[JamesBowen]

Tech support asked for a step-by-step screen shot on the 10.1B Messenger being installed. Which I started to do, but soon as it got to the accepting the license it work for the first time. I was dumb-strucked. I spent about hour and half just trying to install the messenger and then it just worked.

I have been using the same tar ball and the same license codes. However I do also have 10.2A Messenger installed at the same time, so there could be some reason to it.

Anyway problem has now gone but with no real explanation.