Common errors

This page provides an overview of common errors.

Teacher application

Common errors and warnings are visible in the web application for teachers (https://dashboard.exams.schoolyear.app).

”Your organization has reached its limit of concurrent Secure Apps sessions at the planned time slot.”

This warning prevents teachers from planning an exam that will exceed the available quota.

Possible causes:

1. There is not enough quota to serve the number of students configured in the exam.
2. There are other exams planned in an overlapping time slot which together with the new exam would exceed the available quota.
3. You misconfigured the available quota.
4. You misconfigured the quota calculation in the AVD Add-on.

1 & 2: In the first two situations, the message prevents the user from doing something that will result in a deployment failure. The scheduling tool is working as it is supposed to. If your users often run into this issue, you can request a quota increase in Azure and adjust the Schoolyear quota configuration to reflect the new quota limit.

Note that quotas are reserved from the moment the deployment job of an exam starts until the end of the deletion job. This means that two exams planned back-to-back are considered overlapping and cannot use the same quota.

3 & 4: If you do have enough quotas to plan the exam but still get this warning, you probably misconfigured the quotas. In the “Quota” section of the Schoolyear Admin Console, you can configure how much quota there is available in total to Schoolyear AVD. Check if this number reflects the number of quota you have available in your Azure Subscription.

In the AVD Add-on, you can configure per App how Schoolyear should calculate how much quota should be reserved for an exam. The required quota is usually dependent on the number of students that participate in the exam. Therefore, you can configure a formula in which “n” is the number of students.

”Failed to get resources for Safe Exam Workspace. Please refresh the page and try again.”

This error indicates a wildcard certificate problem. If you are currently running the first technical test, it usually fails because one of the first three requirements listed below is not met. If you run into this issue after successfully testing for a while, the certificate has most likely expired.

Certificate requirements:

1. The certificate must include the full chain: the leaf, any intermediaries, and the root certificate.
2. The certificate should be a wildcard certificate for the correct subdomain. It should therefore be *. + the dns zone configured in the add-on, e.g. syproxy.contoso.com. In this example, that results in *.syproxy.contoso.com.
3. The certificate must be signed by a trusted Certificate Authority (CA).
4. The certificate should not be expired.

Resolution:

1. Verify that the full certificate chain is present in the deployed certificate(it includes the root certificate).
2. Confirm that the certificate is issued for the correct subdomain (*.syproxy.contoso.com).
3. Confirm the expiry date of the certificate is after today’s date.
4. Confirm you uploaded a .pfx file to the Azure keyvault.

If you are still having trouble resolving the error, contact support and we will try to help.