Steema Central

I seem to be unable to get rid of the "Evaluation expired" - Message after installation of the liecensed version of v2.

Can someone please direct me to some documentation about how exactly to get rid of the evaluation version and to install the licensed version ?

Any help greatly appreciated.

Gerhard

Hi Gerhard,

Please read this thread about the same issue.

Don't hesitate to let us know if it doesn't help.

Thanks in advance.

The mentioned thread did indeed help.

Alas, the information is somewhat hidden. Some hints from the installation tool might be helpful. It should be able to detect the former presence of an evaluation version and then give that advice.

This would in my opinion greatly improve the user experience.

As well, someone might want to look into the issue of the installation tool not beeing able to remove existing Steema toolbox entries. I had to remove them manually from Visual Studio before the installer could complete without error. I might add, the the error message was not from the installer, but from windows, in cryptic wording and in no way helpful.

Also, the user experience could be improved here ... imho.

Regards,

Gerhard Heidkamp
CTO, InnoDyne

Hi Gerhard,

I'm glad to hear that helped.

Regarding your experience, please notice that cases as yours are infrequent and this may be due to your environment configuration. Could you please give use some more information about your environment and the error message you received?

Thanks in advance.

My Environment is Windows XP Prof SP2

The Error mesg I received regularly before I manually removed the Steema Toolbox entry in Visual Studion was :

Quoted from memory, I did not make a snapshot, sorry ...

"ToolBo(Tilde-Sign)X produced an error and has to be closed. Would you like to send an error report to Microsoft ? "

Hope this helps.

Hi Gerhard,

Thanks for your feedback.

This seems that the part of the installation that installs the components at the ToolBox failed for some reason. Here you can see a thread discussing about the same problem.

We are constantly working on enhancing our installers. So if there's anything we can do to prevent such errors we will try to do so.