> 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/upcoming-release/help-center-index/faqs/installer-faqs/verification-code-error.md).

# Why am I getting the error "Please provide the correct verification code" in registration process while installing application?

### Description

[Registration](/upcoming-release/getting-started/installation.md#registration) is one of the steps in installation. At the time of registration, user is required to provide the verification code which was sent to his/her business email address. This error may be encountered during the validation of verification code.

### Solution

Verification Code is unique for each machine and installation path. The code generated for one machine or path won't work for a different machine or path.\
For e.x, during registration process of installation, the verification code is generated for System A and later the same verification code is used on System B for validation. In this case <code class="expression">space.vars.OIM</code> will throw an error: "Please provide the correct verification code".

This error will also occur if for the same machine the verification code is generated for some installation path (`folder A\folder B`) and later used for installing <code class="expression">space.vars.OIM</code> at another path (`folder C\folder D`).

So make sure that the verification code is generated for the same machine and path where <code class="expression">space.vars.OIM</code> is to be installed.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.opshub.com/upcoming-release/help-center-index/faqs/installer-faqs/verification-code-error.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
