Jump to content
Dataton Forum
Fisejs

Updateing Watchpax - license key can`t be found

Recommended Posts

Hello,

I am trying to update watchpax2 from version 6.1.5 to 6.1.6.

 

The watchout gives the message about different versions and if I want to update.

I click ok.

The watchpax displays this message:

 

"The WATCHOUT license key can`t be found.

Re-trying automatically in a few seconds."

 

If I click "Retry" (with the keyboard connected to watchpax) nothing happens.

I tried to swith watchpax on and off, restart watchout etc, but with no result.

 

Thank you for any help,

Jakub

 

 

 

Share this post


Link to post
Share on other sites

Hi,

 

Just leave it to automatically finish all the update process.

 

You don't have to connect keyboard, no need for any extra click.

Share this post


Link to post
Share on other sites

Have you tried to just let it run until the progress bar on the production computer has finished?

 

We have seen this message too but normally the upgrade will work fine. 

Share this post


Link to post
Share on other sites

 'Retrying automatically...' means just that: automatically. No need to retry manually, and no need to connect a keyboard. In fact, doubt if a keyboard works with Watchpax owing to the locked-down and embedded Windows.

 

Patience is the key. By powering it down and up again mid-way through the process, all bets are off.

 

Thomas Leong

Share this post


Link to post
Share on other sites

Hello,

the problem was static ip address setup-ed in start-up script (192.168.1.200). Watchpax changed it to 192.168.1.221 after first unsuccessful attempt to update (and I let it do everything automatically for the first few attempts). When I switched it off after some time, it started up with the 200 address again and than changed it to 221 - so the WO production didn't see it and so on.

 

Now when I noticed this ip change, I went offline and in wo production changed the display-watchpax ip address to 192.168.1.221. Than I went online. The watchpax asked me again about the update and really updated it self. And as a bonus changed the ip address again to 192.168.1.200. So I changed the ip address in production computer once again to 200 and it works.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×