The information area
All messages of the Administration are collected in the information area: the button with the exclamation mark on the right of the status bar. Red means unread messages, green that you have read them all.
- New messages also appear at the bottom right of the screen and disappear after five seconds. Messages with priority have a red heading and remain until you close them.
- A click on the information area opens the list of all messages since the Administration was started, each row with the time and the first line. A double-click shows a message again.
- Multiple servers: the information area collects the messages of all added servers. Under Details, each message names its server.
- Repetitions: the same message from a server appears only once within 24 hours, unless it has priority.
- While nobody is logged in, the server keeps messages for administrators and sends them at the next login.
Some messages offer the appropriate next step right away, as a button with an icon; the tooltip shows the text:
| Button | Effect |
|---|---|
| Open server settings | opens the server configuration |
| Report an error | opens the feedback form |
| Open mailbox settings | opens the mailbox concerned |
| Open link, Open folder, Play audio | opens the target named |
| Microsoft365 login | logs a mailbox in to Microsoft 365 |
| Start Microsoft365 DeviceCode login, Copy code | logs a mailbox in to Microsoft 365 with a device code. The Administration copies the code to the clipboard by itself when the message arrives. |
Error messages of the server
The server collects errors in the server and in the Routing Services and reports them to all logged-in administrators. The heading names the severity and the type of the error, for example Error: Recording error. Below it are the details, the time of the first occurrence (First time) and, for repetitions, the last time (Latest) and the number (New occurrences). The times are in Coordinated Universal Time (UTC).
So that the same errors do not keep appearing, the server combines them: it
reports a new type of error after about one minute, further errors of the same
type no earlier than after the Admin error inform time — in the server
configuration on the Server tab, twelve hours by default. With 00:00:00,
you turn these messages off. If nobody is logged in, the server keeps errors
for up to 24 hours. If a message combines events of different severities, the
most severe one applies — error before warning before information: the
heading names it, and the inform time depends on it.
| Message | Meaning and remedy |
|---|---|
| Connection to port 6007 failed | The agents named cannot reach the server on their second connection. Open TCP port 6007 between the workstations and the server. |
| SpeechService failed! | The Azure speech services failed during a call. Check the Azure key and the credit. |
| External database failure, SSH connection failure | A flow could not reach an external database, possibly via SSH. Check the connection under External databases. |
| Email / fax Error | An email or a fax could not be sent, for example because there was no recipient or no mailbox. Check the mailbox and the SMTP settings. |
| Recording error, Voice message recording has failed! | A recording or a voicemail could not be recorded or saved. Check the storage location of the recordings and the access permissions for it. |
| Recognition error | In a chat or an email, the recognition found nothing, for example no matching boilerplate. |
| General Flow error | A flow is incomplete, or its error handling failed. Check the flow. |
In addition, the Routing Service reports errors from a conversation immediately, with the type of error as the heading and the details of the conversation and the flow. The same cause then appears twice: immediately and later in the collected message.
If saving or deleting a flow or saving license limits fails, you learn about it immediately, and you are the only one who does — with Saving flow failed!, Delete flow failed! or Saving license limits failed!. If the phone number of a flow collides with another one, the server reports Conflict with FlowMappingNumber! and saves the flow without this mapping.
Other notices
| Message | Meaning |
|---|---|
| Azure AI Configuration — Azure AI is not configured. | No Azure key is entered for the server. The message lists what is therefore unavailable: transcription, speech recognition in flows and media cases with a text part. Open server settings leads to the key. |
| PBX error | The Routing Service is not logged in to the phone system. The details name the state of the login. |
| SQL server performance to low | SQL Server cannot keep up with writing the statistics. Check the load and the reachability of SQL Server. |
| Licenses — Please check your licenses | Something is wrong with the licenses of the server, see Licenses. |
| Information with a version number | Your Administration is older than the server. Install the matching version. |
| Tracking data entry count, Synchronization completed | Master and standby are synchronizing their data: how many entries and roughly how long it will take, then the end — once each for the configuration and the statistics. |
| Synchronization — Synchronisation in progress, please start new synchronisation when this synchronisation has terminated. | You started a synchronization while another one was still running. |
Serious database errors
If the server has serious problems with SQL Server, the Administration opens a separate window:
- SQL Failure — the server could not write data to the database.
- SQL Writer Stopped — SQL Server is so slow that the server has stopped writing the statistics. Until the problem is fixed, statistics data is lost.
Fix the cause on SQL Server and then restart the myContactCenter servers, as the message requests. The Administration adds further messages of the same kind to the open window.