When the EU HUB tries to deliver alerts or messages to an OBP endpoint and receives an error, an “exception” is recorded.
Below you will find an overview of each exception type, its likely cause, and guidance on how to resolve it.
⚙️ 1. Message Security Exception
Description:
This exception usually occurs in WCF applications when there is a mismatch or misconfiguration between the security settings of the EU HUB and the OBP’s system (for example, certificate configuration, authentication schemas, or encryption methods).
How to resolve:
Verify that your security configuration and ensure you have correctly referenced the signing certificate on the receiving endpoint to ensure you are able to accept the signed message successfully.
Check whether the correct certificate chain is installed and valid.
As there can be multiple root causes, please raise a ticket with EMVO so that our technical team can assist you case by case.
🔐 2. Security Token Validation Exception
Description:
This exception occurs when the EU HUB attempts to deliver an alert to an OBP endpoint that is using an expired or invalid client certificate.
How to resolve:
Register a new endpoint using a valid certificate via the
ProcessProductServiceSubscriptionrequest.Activate the new endpoint using the
ProcessProductServiceSubscriptionRollrequest to make it your primary connection.Once complete, verify that alerts are being received successfully in your new endpoint.
🧰 3. Helpers Service Exception
Description:
This exception is typically triggered when the only endpoint registered in the OBP’s configuration uses an outdated schema version.
How to resolve:
Register a new endpoint with a valid schema version via the
ProcessProductServiceSubscriptionrequest.Activate it using the
ProcessProductServiceSubscriptionRollrequest to ensure it becomes the active endpoint.Confirm that your system can receive alerts using the new schema.
🚫 4. Endpoint Not Found Exception
Description:
This occurs when the EU HUB cannot reach the OBP’s alert endpoint — for example, if the endpoint service was down, misconfigured, or temporarily offline when the HUB attempted delivery.
How to resolve:
Ensure that your client endpoint service is running and accessible from the internet.
Check firewall, DNS, and URL configurations.
Since there may be several causes, please log a support ticket with EMVO if the issue persists.
📈 5. Server Too Busy Exception
Description:
The OBP’s endpoint is overloaded and cannot accept new incoming requests from the EU HUB.
How to resolve:
Verify your system performance and capacity.
Increase resources or optimize queue management to handle higher alert volumes.
Consider reviewing your alert-processing logic to avoid bottlenecks during high traffic periods.
⏱️ 6. Timeout Exception
Description:
This occurs when the EU HUB sends an alert but does not receive an acknowledgment from the OBP’s system within the allowed time.
How to resolve:
Check that your client endpoint correctly acknowledges every alert received from the EU HUB.
Review network latency and response times.
If the alert has been received but not confirmed, ensure your client sends a proper acknowledgment message to prevent retries.
🔄 7. Protocol Exception
Description:
This can result from incompatible communication bindings, an incorrect endpoint address, or misaligned configuration parameters between the OBP’s system and the EU HUB.
How to resolve:
Verify that your endpoint configuration strictly follows the latest EMVO Interface Control Document (ICD).
Double-check the endpoint URL and protocol bindings.
As several technical scenarios can lead to this exception, it may require individual troubleshooting through the EMVO Helpdesk.
📬 Need Help?
If your organisation continues to experience any of the exceptions above, please contact us at
📧 helpdesk@emvo-medicines.eu, providing:
Your Org ID
Exception type
Timestamp or log snippet
A brief description of your setup and recent changes
Our technical support team will review your case and guide you through the necessary steps.