Frequently Asked Questions (FAQ) and Solutions to Common Problems

In short

Limited performance in beA Desk is usually due to too many saved messages, large attachments, or insufficient memory. There are recommended limits for the number of stored messages.

Situation

beA Desk responds slowly or shows general performance issues.

Cause

Possible reasons include: - too many saved messages - large attachments - insufficient memory (especially on terminal servers)

For optimal performance, the following recommended limits apply:

Solution

• Regularly export, archive (e.g., in LEXolution.DMS), and remove messages from beA Desk that are no longer needed
• Check available memory, especially in terminal server environments

Note
If the recommended limits are consistently exceeded, the performance of beA Desk may continue to deteriorate.

In short

Error "F001" means that a message could not be delivered to the recipient's intermediary. The message must be resent.

Situation

Error "F001" appears when sending a message.

Cause

The message could not be delivered to the recipient's intermediary.

Solution

1. Move the message to the Drafts folder
2. Resend the message
3. Additionally: delete the failed message from the Outbox in the beA Web Client

Note
The failed message should also be removed from the Outbox in the beA Web Client to avoid duplicates.

Why is a message in the "Send Error" folder?

In short

If a message ends up in the "Send Error" folder, it could not be sent due to invalid data, missing permissions, or technical issues.

Situation

A message is in the "Send Error" folder and was not sent.

Cause

The message could not be sent due to: - invalid data - missing permissions - technical issues

Solution

Open the error log for the message to determine the exact cause.

Note
The error log usually provides the key information needed for troubleshooting.

Why can't I select a recipient?

In short

The recipient search only works when connected to the BRAK server.

Situation

When composing a message, no recipient can be selected.

Cause

The recipient search requires an active connection to the BRAK server.

Solution

Check your connection to the BRAK server and restore it if necessary.

Note
Recipient search is not available in offline mode.

Note
If an address was previously saved as a favorite (pinned) during an earlier address search, it is also available in offline mode. It can then be selected as a recipient in a draft without needing to search for the address again.

How are messages transferred to the DMS?

In short

Messages are transferred to the DMS as a .beamsg archive, optionally including attachments as separate files.

Situation

Messages from beA Desk are to be imported into a downstream DMS such as LEXolution.DMS.

Details

Messages are transferred as: - .beamsg archive - plus attachments as separate files (optional)

Note
Which attachments are additionally archived separately is defined via the export assistant within beA Desk.

How are messages processed in Input Management?

In short

Messages are transferred to Input Management as .beamsg files, where attachments are extracted, processed, and automatically classified and assigned.

Situation

Messages from beA Desk are to be further processed in Input Management.

Details

Messages are: - transferred as .beamsg - attachments are extracted and processed - automatically classified and assigned

Note
Automatic classification and assignment is based on the rules configured in Input Management.

Are all contents processed in Input Management?

In short

No. Certain content types are not processed by Input Management.

Situation

Not all parts of a message are further processed in Input Management.

Cause

The following contents are not processed: - digital signatures - certificates - encrypted attachments - delivery receipts

Note
These contents remain part of the message but are not analyzed by Input Management.

Why is more memory needed?

In short

For each active user session, beA Desk starts its own KSW interface instance, so memory usage increases with the number of active users.

Situation

The memory usage of beA Desk appears higher than expected, especially with multiple active users.

Cause

A separate KSW interface instance is started for each active user session.

Typical memory usage: - approx. 500 MB per user - may temporarily exceed 1 GB depending on message size

Note
Especially on terminal servers with many simultaneous user sessions, available memory should be sized accordingly.

Can beA Desk be used on a terminal server?

In short

Yes, beA Desk is fully supported in terminal server environments.

Situation

You want to check if beA Desk can be used in a terminal server environment.

Details

beA Desk is fully supported in terminal server environments.

Note
With multiple simultaneous user sessions, memory requirements per session should be considered (see "Why is more memory needed?").

What happens when you close beA Desk?

In short

Closing the window does not fully exit the application. beA Desk continues running in the background (tray).

Situation

After closing the beA Desk window, the application is still active.

Cause

Closing the window does not fully exit the application – beA Desk continues running in the background (tray).

Solution

To fully exit: - use the tray icon → select "Exit"

Note
Unless you select "Exit" from the tray icon, beA Desk will remain active in the background.