Administer > Administer Service Management > Studio > Notifications > Direct access to Service Management via email > Direct access to Service Management troubleshooting and limitations

Direct access to Service Management troubleshooting and limitations

The following issues may arise when using direct access to Service Management via email. Be advised that in certain cases, the user may receive an email indicating that an error occurred:

Issue Cause Solution

Direct access to Service Management is not working. The following email notification is received:

Requesting support using email is currently disabled.

To create a new request, log in to the Service Portal.

The tenant setting to enable direct access is set to Off.

Set the tenant setting to enable direct access to On:

  1. From the main menu, select Administration > Configuration > Service Portal Settings > Feature Settings.
  2. In the Enable request creation and actions from email field, select On.

The following email notification is received:

We could not process your email because the email address does not belong to an authorized email domain.

To create, track, or update a request, log in to the Service Portal.

The user's email domain is not defined as a permitted domain.

Make sure the user's email domain (for example, microfocus.com) is defined in the endpoint:

  1. From the main menu, select Administration > Utilities > Integration > Endpoints > Configure > Advanced connection configuration > Authorized email domains.
  2. Enter the user's email domain.

The task to create a request via email fails. The following email notification is received:

We could not create your request because we need more information, which may be system-related. For details, contact your system administrator.

To create a new request, log in to the Service Portal.

The creation of a request fails due to validation errors.

Fine-tune the request creation process:

Make sure all users have an entitled default offering and that the default offering consists of default values for all mandatory request fields, OR that a request that has only a title and description can be created.

The task to create a request via email fails. The following email notification is received:

You do not have the necessary permissions to create this request via email. Please contact your system administrator.

To create a new request, log in to the Service Portal.

The creation of a request fails because a user does not have correct permission to create a request.

By default, the Service Portal User role has permission to create requests. If a user cannot create requests, the user may either not be defined in Service Management or does not have the Service Portal User role.

Create the user in Service Management and assign them the Service Portal User role or the request-creation permission.

A user cannot perform an action in an email. The following email notification is received:

We could not process the email for request #123456 <title>.

To track or update the request, log in to the Service Portal.

This occurs when a user attempts to execute an action from an email when the record is no longer in the correct lifecycle phase. For example: a user marks a comment as a solution after the request has been closed. Review the request and verify that it is in a phase where it can be updated.

The following email notification is received:

We could not process this email because it has expired.

To track or update the request, log in to the Service Portal.

Service Management failed to process an email action because the token contained in the email expired (too many days passed since the user received the email that contains the action link).

If permitted, extend the default token expiration time in the email endpoint configuration:

  1. From the main menu, select Administration > Configuration > Service Portal Settings > Feature Settings.
  2. In the Specify email validity time frame field, select the desired time frame.

The following email notification is received:

We could not process the email because the action has already been performed.

To track or update the request, log in to the Service Portal.

Service Management failed to process an email action because the token contained in the email was already used (the user already performed the action).

None.

The following email notification is received:

.We could not process your email. The email's security token may have been altered. Try to send it again by clicking the same action link/button.

To track or update the request, log in to the Service Portal.

Service Management failed to process an email action because the token is invalid or may have been altered.

Make sure that the bottom part of the incoming email that contains the security token is not changed.

Contact Support if the problem persists for multiple users.

The following email notification is received:

We could not process your email. You may not be a registered Service Management Automation user. Contact your system administrator.

To verify that you are a registered user, try to log in to the Service Portal. If you are a user, make sure to use the same email address that is listed for you in the system when you send emails.

A user with the sender's email address was not found in Service Management.

Make sure the user's email address is correctly specified in the People module in Service Management (Main menu > Administration > Master Data > People).

Contact Support if the problem persists for multiple users.

The following email notification is received:

We could not process your email. The sender’s email address does not match the email address of the user who received the original email. Emails that were forwarded from other email addresses cannot be processed.

To create, track, or update a request, log in to the Service Portal.

The sender of the email and the user in the email's token do not match. This might occur if a user forwarded the email containing a token to someone else.

None.

Contact Support if the problem persists for multiple users.

The following email notification is received:

We could not process your email because the email address does not belong to an authorized email domain.

To create, track, or update a request, log in to the Service Portal.

The email received from the email server might be corrupted. Check the support inbox to see if any of the received emails were corrupted.
New emails are not processed. There might be problems with the On-Premise Bridge email integration task.

In the endpoint configuration dialog box, check if the last SyncEmailTask failed. If so, check the \\<OPB_folder>\product\log\email-integration\email-integration.log and \\<OPB_folder>\product\log\controller\controller.log files.

The new task will start at the next cycle (at xx:00 or xx:30).

The integration task does not start after configuring the endpoint. Email integration tasks run every 30 minutes (at xx:00 and xx:30); therefore, it may take up to 30 minutes until the mail polling task begins. None.
The user changed the email integration configuration but the changes are not applied immediately. The new configuration will be applied after a maximum of 30 minutes. To apply the configuration immediately, click Stop and then Start in the endpoint toolbar.