SEB error with Moodle 4.3.2 & IIS

[AhmadSMS]

hello all,
while our students (around 90 stds) running their online exams, with some students (10-20 std), the SEB keep leaving the exam automatically with the following errors (as shown in attached screenshots) ...

in the client log file shows error:
ERROR: Client application has unexpectedly terminated with exit code -532462766 !

it happened several times for each students, but not all of them..!
we r using SEB 3.7.0 & Moodle 4.3.2 & Windows Server 2019 with IIS
SEB is configured manually with default settings + a Key to start the exam..

any ideas or hints?
what does this error code mean - 532462766 ?

[AhmadSMS]

the error at log file is here:
`2024-05-23 11:41:09.843 [12] - DEBUG: [RuntimeHost] Received message 'SimpleMessage -> Ping', sending response 'SimpleResponse -> Acknowledged'.
2024-05-23 11:41:10.824 [22] - DEBUG: [ClientProxy] Sending message 'SimpleMessage -> Ping'...
2024-05-23 11:41:10.826 [22] - DEBUG: [ClientProxy] Received response 'SimpleResponse -> Acknowledged' for message 'SimpleMessage -> Ping'.
2024-05-23 11:41:10.826 [22] - INFO: [ClientProxy] Pinged host, connection is alive.
2024-05-23 11:41:50.360 [05] - ERROR: Client application has unexpectedly terminated with exit code -532462766!
2024-05-23 11:41:50.362 [05] - INFO: ### ------------------------------------- Session Stop Procedure ------------------------------------- ###
2024-05-23 11:41:50.364 [05] - INFO: Reverting kiosk mode 'CreateNewDesktop'...
2024-05-23 11:41:50.367 [05] - INFO: [DesktopMonitor] Stopped monitoring desktop 'YcMkcXrfLt' [4684].
2024-05-23 11:41:50.386 [05] - INFO: Switched back to original desktop 'Default' [308].
2024-05-23 11:41:50.391 [05] - INFO: Closed custom desktop 'YcMkcXrfLt' [4684].
2024-05-23 11:41:50.392 [05] - INFO: Finalizing service...
2024-05-23 11:41:50.396 [05] - INFO: ### --------------------------------------- Session Terminated --------------------------------------- ###
2024-05-23 11:42:10.846 [22] - DEBUG: [ClientProxy] Sending message 'SimpleMessage -> Ping'...
2024-05-23 11:42:10.850 [22] - WARNING: [ClientProxy] Communication channel has faulted!
2024-05-23 11:42:10.861 [22] - ERROR: [ClientProxy] Failed to ping host!

Exception Message: There was an error writing to the pipe: The pipe is being closed. (232, 0xe8).
Exception Type: System.ServiceModel.CommunicationException

Server stack trace:
at System.ServiceModel.Channels.StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)
at System.ServiceModel.Channels.StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout, BufferManager bufferManager)
at System.ServiceModel.Channels.FramingDuplexSessionChannel.OnSendCore(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.TransportDuplexSessionChannel.OnSend(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.OutputChannel.Send(Message message, TimeSpan timeout)
at System.ServiceModel.Dispatcher.DuplexChannelBinder.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at SafeExamBrowser.Communication.Contracts.ICommunication.Send(Message message)
at SafeExamBrowser.Communication.Proxies.BaseProxy.Send(Message message) in C:\Users\appveyor\projects\seb-win-refactoring-xo6eb8owbvycfge8\SafeExamBrowser.Communication\Proxies\BaseProxy.cs:line 132
at SafeExamBrowser.Communication.Proxies.BaseProxy.TestConnection() in C:\Users\appveyor\projects\seb-win-refactoring-xo6eb8owbvycfge8\SafeExamBrowser.Communication\Proxies\BaseProxy.cs:line 163

Inner Exception Message: The write operation failed, see inner exception.
Inner Exception Type: System.IO.IOException

at System.Net.Security.NegotiateStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.NegotiateStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at System.ServiceModel.Channels.StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)

Inner Exception Message: There was an error writing to the pipe: The pipe is being closed. (232, 0xe8).
Inner Exception Type: System.ServiceModel.CommunicationException

at System.ServiceModel.Channels.PipeConnection.WriteHelper(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout, Object& holder)
at System.ServiceModel.Channels.PipeConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)
at System.ServiceModel.Channels.BufferedConnection.WriteNow(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout, BufferManager bufferManager)
at System.ServiceModel.Channels.BufferedConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)
at System.ServiceModel.Channels.ConnectionStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at System.Net.Security.NegotiateStream.StartWriting(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.NegotiateStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)

Inner Exception Message: There was an error writing to the pipe: The pipe is being closed. (232, 0xe8).
Inner Exception Type: System.IO.PipeException

at System.ServiceModel.Channels.PipeConnection.StartSyncWrite(Byte[] buffer, Int32 offset, Int32 size, Object& holder)
at System.ServiceModel.Channels.PipeConnection.WriteHelper(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout, Object& holder)

2024-05-23 11:42:26.590 [05] - DEBUG: [Process 'SafeExamBrowser.Client.exe' (1740)] Process has terminated.

2024-05-23 11:42:26.615 [22] - INFO: Initiating shutdown procedure...
2024-05-23 11:42:26.615 [22] - INFO: Stopping communication host...
2024-05-23 11:42:26.616 [22] - DEBUG: [RuntimeHost] Communication host is closing...
2024-05-23 11:42:26.622 [22] - DEBUG: [RuntimeHost] Communication host has been closed.
2024-05-23 11:42:26.623 [22] - DEBUG: [RuntimeHost] Terminated communication host for endpoint 'net.pipe://localhost/safeexambrowser/runtime/d73606b3-6006-4105-b6f6-39f80d4fadbb'.
2024-05-23 11:42:26.623 [22] - INFO: Application successfully finalized.

Application terminated at 2024-05-23 11:42:26.632`

Note, number of students around 90, and few of them had faced this error...

[dbuechel]

The red lock screen appears in case the last session with a particular configuration resp. start URL has not been terminated normally.

The unrecoverable application error appears to occur due to an issue with the inter-process communication of SEB's application components. You'll need to make sure that it isn't suppressed or otherwise negatively impacted by e.g. an anti-virus software or your system configuration. You may find some information related to the issue in the application log of the Event Viewer system application.

[AhmadSMS]

thank u dbuechel for the respond,,
Note, number of students around 90, and just few of them had faced this error...
this issue just appered after we update our SEB to 3.70.882
while we was running fine with a previous version 3.7.0.661
and as i noted before, it occur for few of our users, while the rest users running their exam just fine with SEB..!

we did a test to back to 3.7.0.661, and then we faced a new issue with red screen ... cursor configuration...
#896 (comment)

[Dezzhx]

Hello
Wondering if you have had any luck in solving the issue?
We are having by the looks of things the exact same issues both on student and our machines. We have hundreds of students in many different classrooms on private and our machines with similar but different configs both on win 10 and 11 doing tests daily and we are not able to pin point the solution.
Pushing the newest update seems to help but its too early to say.
As of now we have made a choice to avoid SEB when possible.
Taking into account the number of users and computers the issues do appear on a small % of our systems but still enough to disrupt normal operations.
When trying to reproduce the issue in the lab we have not been successful - different SEB configs on different machines, different SEB versions.
Until last week we were using version 3.6 since 02.01.2024. with none of these specific issues.

[dbuechel]

If you're referring to the inter-process communication issue, then no, that is for the time being a known issue (see #824). We were until now unable to reproduce the issue ourselves, which is a precondition to be able to investigate and potentially fix it.

[steveorulez]

Hello,

we just started our exam sessions (all BYOD) and we had the same exact error on 40+ students in different exams.

In the past session (February 2024) we never had any of these errors.

The crash can happen random, scrolling, clicking on next question or clicking the question number on the right side.
The same student on an exams might crash 2 times and on another exam never.
Most of the time the crash happened only once and after restarting his attempt no more errors.
Sometimes it's impossible to continue because SEB keep crashing and we have to provide a laptop.

The red screen is easy to solve, just insert the password and the student can continue, this will happen when you re-start SEB after the crash.

At the moment we did not find any solution to solve the complete crash, we had it on 3.7.682 (the only picture I took) but also on older versions.

From today i will take pictures to all errors and compare the versions.

christian

[dbuechel]

That's most likely due to #883.