-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Safe Exam Browser (SEB) Not Starting #1078
Comments
Hi @dbuechel We are using this version. |
I will share it tomorrow as I don’t have my computer with me right now, but thank you for the information. |
@dbuechel Hi, For example, I quickly checked a sample computer and saw that it is empty. What do we need in this case? |
Thanks for the update. Could you please provide the complete log files of the affected session? There might be an issue to be fixed, but I'd need to verify this in context of the entire log file. |
@dbuechel Hi, I have attached the logs. |
v8_context_snapshot.bin is missing. It's not the best solution but if you replace it with the file from a working SEB install it will run. I've seen this happen many times(in 3.6, 3.7. 3.8), starting roughly in October, and I'm not entirely sure WHY but v8_context_snapshot.bin(or icudtl.dat) gets temporarily moved/renamed and not restored. If you check the registry you might find a "PendingFileRenameOperations" related to this. |
Hello Team,
I am encountering an issue with Safe Exam Browser (SEB) and would like to request assistance. Below are the errors I am receiving:
I have collected additional information regarding these errors, but I still need assistance with finding a solution. The issue arises when attempting to start the SEB client, which terminates unexpectedly during initialization. Additionally, I encounter an unexpected exception during the 'LazyInitializationOperation' and am unable to retrieve certain registry keys.
Could you please guide me on the steps I should take to resolve these issues?
Thank you!
The text was updated successfully, but these errors were encountered: