Client: windows 1.8.1-128. (I’ve also seen this issue with 1.8.0 clients)
Intel Stick - Windows 10 Home
Server: 1.8.1
I’m finding players sitting in a state where it isn’t playing anything. When I open Watchdog, it contains the error below. It is randomly occurring.
System.IO.IOException: The process cannot access the file ‘C:\Users\Administrator\Documents\Xibo Library\status.json’ because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream…ctor(String path, FileMode mode, FileAccess access)
at XiboClientWatchdog.Watcher.Run()
Is there any consequence to that message? Ie does anything stop working as a result?
The part of the screen you highlight shows last log status so I’d assume there was an error accessing that file, but the watchdog should continue working regardless.
Hi,
The screen shot is this. I cannot get full size, because the error goes away when I connect the pc.
And this is the screenshot taken from cms.
When the error comes out, the windows bar shown, even there is a error, watchdog should not show error like this.
Thanks
Thank you for the screenshots. can you send a screenshot of the Status page? As mentioned previously, you can access the Status page by clicking the i key on your keyboard while Xibo is running.
Dear Dan,
Status page says nothing, because the error is shown by Watchdog, and it goes away when you click somewhere. Sorry cannot get more info for you.
This a full error message from Watchdog: System.IO.IOException: The process cannot access the file ‘C:\YDS\status.json’ because it is being used by another process. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream…ctor(String path, FileMode mode, FileAccess access) at XiboClientWatchdog.Watcher.Run()
Me too
This is annoying!
please do something about this.
Windows is way too stupid for making it to hide this kind of errors.
I am wondering,
why this is shown in the first place, screen looks very ugly while this is shown and goes nowhere with out rebooting it or restarting the player application.
Thanks Michael!
I am aware of this but the problem with it is,
we cannot hide the icon because we do not have CTRL+ALT+DEL for bringing up task manager, we need to somehow be able to terminate the WatchDog when required.
I am afraid the best solution would be to fix this issue.
Thanks for the detailed info!
However,
i still believe the best way is to fix the problem. Hiding the problem temporarily is okay but it is unfortunately not a solution.
I have also been having this issue for a while now. I recently upgraded the players and server to 2.0, but the screens still go black after a while. Have there been any developments on this?
Jschwa mentioned recently that they are also experiencing the same issue on CMS 2 and Windows Player version 2. Can you provide a screenshot of the Error that appears on your screen please when the screen is black? Is it the same as the error other users above have reported?