Webinar (on-demand): OutSystems and Analytics Integration: A New Strategy to Reduce Costs

Discover everything you need to know about Hubway Connect

Try the product online without any installation or purchase commitment
Hubway Connect

Innovative ways to leverage your data for business outcomes

Find out how Hubway Connect can help you get more value from your OutSystems platform
Hubway Connect

Learn and expand your Hubway Connect knowledge

Deep dive in articles, videos and technical information to maximise its use
Hubway Connect

Start free and expand without surprises

Choose the Hubway Connect offer that best meets your needs and suits your budget
Hubway Connect

We are here to help. Let’s talk.

Connect with us via your preferred channel and we will be happy to answer your questions
Hubway Connect
  1. Home
  2. Knowledge Base
  3. FAQs
  4. Deploying a Project
  5. What are the possible errors that I may face while deploying the project?

What are the possible errors that I may face while deploying the project?

Hubway runs a series of validations before deploying a project.

Cause Error Message Action required
The version which is being deployed is not Hubway Connect runs a series of validations before deploying a project You can only deploy a published version of a project. Please publish the project version, or select a version that is already published. Publish the project and then deploy.
A user with the same username not found in the target environment Your username ([username]) does not exist in the destination environment. Please ensure you have access to the destination environment. Contact the UserManager to set up your username in the target environment.
The user in the target environment does not have DeployAdmin role You do not have permission to deploy projects in the destination environment. Please ensure your account has the DeployAdmin role in the destination environment. Contact the UserManager to grant DeployAdmin (HWSecurity) in target environment.
If a project with the same project name or service name already exists in the target environment, then the project cannot be deployed  “A project with the same name already exists”
or
“A project with the same service name already exists”.
Change the name of the Project/service.
A greater version of this project exists in the target environment The destination environment has a newer version than the version you are trying to deploy. Please deploy a newer version, or delete the newer version from the destination environment first. You can only deploy a higher version number than the one already deployed.
Espace name, entity name and attribute name are missing in the target environment The destination environment is missing entities or attributes needed for your project. Please ensure the following data is available in the destination environment:

  • Espace: [ESpaceName].
  • Entity: [EntityName].
  • ID.
Option 1: Create a new version, and remove the missing entities and attributes. Then deploy.

Option 2: Contact the Project team who owns the entities to deploy the latest version of their app module to the target environment.

The data types of the Entities do not match  Data types do not match for the Entities: <Entity Names>. Option 1: Create a new version, and remove the missing entities and attributes. Then deploy.

Option 2: Contact the Project team who owns the Entities to deploy the latest version of their app module to the target environment.

Role name does not exist in the target environment
Note that this one is a Warning not an error
We could not deploy the project as the group name is missing in the Production environment. Would you like us to create the relevant group names on your behalf? Click Yes if you would like the system to create the missing group name in the target environment.
Was this article helpful?

Related Articles

Need Support?

Can't find the answer you're looking for?
Contact Support