Discussions about product bugs & problems!
Note: This is no replacement for the Official ETM Support!
paramesh1985
Posts: 81 Joined: Thu Sep 25, 2014 6:03 am
WinCC OA WibuKey Error
Post
by paramesh1985 » Mon Jul 24, 2017 4:37 pm
Hi,
We are using VMware for our WinCC OA testing; all the vmwares are stored in to Esxi Server.
we inserted all the WinCC OA dongles in ESXi server and assigned each dongle to the individual VMWare.
But we are facing one strange behaviour after assignment dongle is listed under Computer->Device manager-> USB controller
but its not showing in the Wibu Key Control panel as well project administrator.
After we enabling and disabling the usb port its showing.
Second issue: After we restarted the vm ware we are loosing again the dongle information but its listed in the device manager.
Here i have attached the screenshot for your reference.
Attachments
killer007
Posts: 4 Joined: Wed Mar 13, 2019 6:35 am
Re: WinCC OA WibuKey Error
Post
by killer007 » Thu Apr 25, 2019 10:20 am
Hi,
I got nearly the same issue with a ESXi 6.7U1 Host.
But i got a different Error on opening the WibuKey Control Panel and it is also not shown in the Project Adminstration.
The Workaround with disabling / enabling the USB port on ESXi does not help with this behaviour
BR Daniel
leoknipp
Posts: 2928 Joined: Tue Aug 24, 2010 7:28 pm
Re: WinCC OA WibuKey Error
Post
by leoknipp » Thu Apr 25, 2019 4:03 pm
If you get an error when calling WibuKey functions or tools we cannot tell you what the cause for the error is.
WinCC OA integrates WibuKey as 3rd party software for dongle licensing functionality.
Please take into account that licensing via USB dongles is not supported for VMWare ESXi servers.
According to the information in the WinCC OA Documentation VMWare ESXi Version 6.0 and 6.5 is supported.
Best Regards
Leopold Knipp
Senior Support Specialist
killer007
Posts: 4 Joined: Wed Mar 13, 2019 6:35 am
Re: WinCC OA WibuKey Error
Post
by killer007 » Tue Jun 25, 2019 8:09 am
Hi,
Thanks Leu!
The call of
Code: Select all
esxcli system module set -m=vmkusb -e=FALSE
and a reboot had done the trick on ESXi 6.7U1 also.
BR Daniel