Forum Replies Created
-
Posts
-
Hi Volker,
I’ll try it later today, thanks!
FYI: I also tried to deploy the latest image for the 5070 W10 IoT thin client provided by DELL. (WIN10_5070_March2019). I downloaded the .exe-file, copied it to the WMS repository (..\repository\osImages\zipped) and let WMS do it’s thing. The image is now available in WMS but also cannot be deployed. Same problem as stated in my first post.
Hi Volker,
thanks for your input. I checked the reg entry. It’s “number only” with a “.” in between. I tried removing the dot and recapturing the image. Capturing works as before but deploying still does not.
Even with W10 IoT-devices I cannot deploy captured OS images. App policies seem to work though. I successfully updated Merlin on two devices.
Regards
Philipp
“I went back to the Groups & Configs tab but nothing is displayed, would be good at minimum to see all devices with a local exception (and an option to reset it to default)?”
I’m looking for this as well.
Hi MoPositive,
I updated to WMS 1.4 this week and also had issues concerning memcached.
The log file shows a lot of warnings:
2019-08-20 07:36:31.359 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for wms_QueueLockCache_3. 2019-08-20 07:36:31.406 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for wms:globalType:. 2019-08-20 07:36:31.406 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for wms:globalType:. 2019-08-20 07:36:31.406 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for wms_QueueLockCache_29. 2019-08-20 07:36:31.421 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for wms:globalType:. 2019-08-20 07:36:31.421 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for wms:globalType:. 2019-08-20 07:36:31.437 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for wms_QueueLockCache_30. 2019-08-20 07:36:31.515 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for wms:globalType:. 2019-08-20 07:36:31.531 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for wms:globalType:. 2019-08-20 07:36:31.531 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for wms:globalType:.After seeing your post I checked the registry:
Old value was: <path to executable> -d runservice -p 11211 -l <server name> -U 0
As you can see, the port number is already specified. However, it didn’t work. So I just changed the order of the string to:
<path to executable> -d runservice -l <server name> -U 0 -p 11211
Oddly enough, after restarting the memcached-service, everything works fine.
Thanks a lot for pointing me in the right direction!
Thanks SanderR! Quite old thread but even with the new WMS 1.2 HF1 the problems you stated in your first post still seem to exist. Your workaround via advanced ini options worked like a charm, though. 🙂
