---
schema_version: "1"
id: cd5efc38ab7013e1689a857dd4c84ad994c2a62a442ba923a979772fd6adf1b4
title: Troubleshooting Registration Issues
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/gateway/latest/troubleshoot-reg.md
canonical_url: https://docs.mulesoft.com/gateway/latest/troubleshoot-reg
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 64e693934ed362bf0b92a23355135dfc38ee6a74310086659e9a05a1fd7cbd0d
description: MuleSoft Documentation Site
release: "1.14"
latest: true
---
---
product: Omni Gateway
version: 1.14
is-latest-version: true
---

# Troubleshooting Registration Issues

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

When registering Omni Gateway, you might encounter issues caused by incorrect access permissions,
and so on. The following topics provide possible causes for registration issues and describe how to
troubleshoot:

- [Performing Registration as a User Without Necessary Access Permissions](#no-permissions)

## Performing Registration as a User Without Necessary Access Permissions

Executing the registration command without having correct permissions can result in an error:

Couldn't execute register command successfully: rpc error: code = Internal desc = handler returned
neither error nor response message

### Cause

This issue occurs when the credentials that you provide for registration do not have the required
permissions.

### Solution

To resolve this error, perform the following steps:

1.  Navigate to **Access Management** as the organization administrator.

2.  Select **Users** from the main menu.

3.  Select the target organization user from the **Users** menu.

4.  From the **Permissions** tab, select **Runtime Manager**.

5.  Specify the environment in which to apply your permissions.

6.  Select the following from the **Select access** dropdown menu:

    - _Manage Servers_

    - _Read Servers_

7.  Click the **+** button.

Re-running the registration command should now result in success.

## See Also

- [Known Issues](https://help.salesforce.com/s/issues)