How is your experience with the OutSystems Community?
17
Views
3
Comments
Error encountered when deploying
Question

When deploying an application, error message 'There was an error preparing settings due to a connection issue with target environment.' appears. 

Related to this, there is https://success.outsystems.com/support/troubleshooting/incident_models/incident_models_outsystems_11/error_encountered_when_deploying_using_a_user_with_username_containing_the_plus_character/,

so I checked the username, but the username I logged in is 'admin', which does not seem related to whether it contains a '+' sign or not. What could be other causes and solutions for this?



2019-11-11 17-10-24
Manish Jawla
 
MVP

Hi @SungGeun Song ,

Can you make sure there is no space in your user name? or can you try to edit your user name & try again.

Or do you have any other user with same permission?

If not do you have permission to create a new one and try with that new user?

Regards,

Manish Jawla

2026-08-11 07-57-21
Dennison

Hi @SungGeun Song , 

Kindly check the username "admin" is from source environment or target environment while deploying. 

Thanks,

Dhanasingh Dennison T

2021-07-09 10-51-04
Leyviston Martins

Building on what Manish and Dennison mentioned , this error usually points to a connectivity/auth issue between LifeTime and the target environment's Deployment Service, not just the username format itself. A few quick things worth checking:

- Deployment Service running? Confirm the "OutSystems Deployment Service" is up on the target front-end(s).

- Credentials valid on the target side? Even if "admin" looks fine, check if the password expired/changed recently in that specific environment (LifeTime and the environment can get out of sync).

- SSL cert / firewall: if the target's cert is expired or not trusted by the LifeTime server, or a firewall is blocking the deployment port, you'll get this exact generic message.

The LifeTime error message itself is pretty vague — I'd check the Event Viewer on the target server and the Deployment Service logs there, they usually show the actual root cause (timeout, auth failure, cert issue, etc.). If you can paste that, easier to pin down.

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.