unattended access fails with error msg
hello. I setup the unattended access and I can get it to work just fine until the client reboots....
Once the client reboots, wayk now (on the client) gives me an error that the "unattended service started late" once I restart the app we are good again.
so how do I get the service to start earlier? so the unattended access will work...
Thanks in advance....the client is a win 7 machine btw
All Comments (2)
Hello
Service startup can be delayed for a few reasons, but it sounds uncommonly slow if you are able to log into the machine and launch wayknow.exe before the service has started.
Can you start by sending us the service log from that machine? Open Wayk Now and choose "Help > Export Diagnostics", then send us the resulting .zip file either by a PM or to wayk@devolutions.net.
Thanks and kind regards,
Richard Markievicz
Hello
Thank you for sending over the log information.
It seems the machine is running Windows 7 Embedded? Is that correct?
I see some irregularities in the logs that you sent; for example the most recent start for both the unattended service component and the Wayk Now client is virtually simultaneous. The service should be started automatically, with the system, and - as a GUI application - the Wayk Now client might be started sometime later, by the user, within Explorer. That both would start simultaneously seems odd, and would probably be hard to achieve without automating somehow...
It doesn't directly explain the issue you're seeing. Can you tell us more about how the system is configured or built? We don't have much in-house knowledge of embedded Windows - I see it contains the full Win32 API, but also that it can be heavily customized (and indeed, doesn't seem to be available as a standalone ISO - it seems a custom image must be created for deployment).
The output of `sc qc wayknowservice` may also tell us something.
Thanks and kind regards,
Richard Markievicz