> For the complete documentation index, see [llms.txt](https://docs.opshub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opshub.com/v7.226/help-center-index/troubleshooting-index/errors-index/microfocus-error-solutions/oh-microfocus-012651.md).

# OH-Micro Focus ALM/QC-012651

## Description

When user encounters OH-Micro Focus ALM/QC-012651, then following error message will appear:

'OH-Micro Focus ALM/QC-012651 : Rest request processing Error : `<status_code>` `<name of the status code>` for the request `<request URL>`'

**Example:**

OH-Micro Focus ALM/QC-012651 : Rest request processing Error : 403 Bad Request for the request <http://10.13.28.82:8181/qcbin/authentication-point/authenticate>

## Cause

* This error may occur when the user mentioned in the system configuration form is not present as a project user in Micro Focus ALM/QC for the project being used in the integration.

## Solution

* To add the user as a **Project User** in Micro Focus ALM/QC, please refer: [Add a project user in a project](/v7.226/connectors/micro-focus-alm-qc.md#add-project-user-in-project)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.opshub.com/v7.226/help-center-index/troubleshooting-index/errors-index/microfocus-error-solutions/oh-microfocus-012651.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.