Can't connect...

Can't connect...

avatar

Hello,

can't connect at user from RDM Wayknow.

At RDM I've stored connection for user laptop:
1) Unique ID
2) sub-connection as source ID

When I double-click at user entry it should connect at user laptop, but get info about "not found"
Then I did try use sub-connection.. they same info... not found...

I called to user and he run manually wayknow client from desktop. First... source ID was different.. but I check Unique ID and was the same like I have in RDM stored as user entry.

Logs from servicenow (user computer) and wayknow rdm as an attachement.

--
KriS

All Comments (2)

avatar

Hi Kris

Thanks for the bug report, and we are sorry for the inconvenience. That is exactly the kind of situation that using the Unique ID for addressing is supposed to prevent. It's not clear exactly why the ID "bookmark" was not updated when the users Wayk ID changed, but we are going to look into this.

Do you still have the parent entry (the Unique ID one) in RDM? If so, could you export it and send it to us by PM or at wayk@devolutions.net? Or, if you knew the Unique ID, that would also be helpful.

Thanks and kind regards,

Richard Markievicz

avatar

you can see the unique ID of the way now instance via help -> about Wayk now (or whatever it might have been changed to if branding is applied).

there you could check if the unique id might have changed e.g. due to some problems with the certificate associated to it.