Log in to AnswerLog in to Follow
Joe Tan
69Views
9Comments
Solved
Unable to connect to environment after Platform Server Upgrade
Question
Service Studio
Service Studio Version
11.10.4 (Build 36716)
Platform Version
11.10.1 (Build 23852)

Hi,

I am currently unable to connect to the enterprise environment from my service studio 11 after platform server upgrade to 1. I am getting the error: There was an error connecting to <my environment name> - SendFailure. Attached is the screenshot of the error. I have a feeling it has got to do with https connection as secure connections is not set up in the environment security. 

Any ideas what is causing this issue and how to solve this issue.

Regards,

Joe

LoginToEnvError.PNG

0
0
on 11th Jan
Joe Tan
Solution

Hi, 

I managed to login to my enterprise environment via http connection and using the IP address instead of my hostname

Regards,

Joe

See solution in context
0
0
on 13th Jan
Daniël Kuhlmann
mvp_badge
MVP

That sounds like a DNS that is missing an entry to your environment 

0
0
on 13th Jan

Hi I am facing exactly the same issue with my enterprise environment. Can you share more exactly how you deal with this? did you enter IP address in the Environment parameter?

0
0
on 15th Apr

Hi Joe,

Are you trying to connect your personal environment or the licensed one? Please confirm.

Thanks & Kind Regards,

Sachin

0
0
on 11th Jan

Hi Sachin,

I am trying to connect to an enterprise environment.

Regards,

Joe

0
0
on 11th Jan

Replying to Joe Tan's comment on 11 Jan 2021 07:57:01

Please refer the below links - 

If you still get the error, I would suggest you to please contact OutSystems Support (support@outsystems.com) to look into the issue.

0
0
on 11th Jan
Daniël Kuhlmann
mvp_badge
MVP

Hi Joe,

Are you able to connect to Service Center and LifeTime?

Regards,

Daniel

0
0
on 11th Jan

Hi Daniel,


I am able to connect to Service Center. LifeTime was not installed as we are not using the services in LifeTime. Is LifeTime a must for outsystem 11?

I used a self signed certificate as SSL certificate as this is a development environment. The cert is only for server authentication.

Regards,

Joe

0
0
on 12th Jan
Joe Tan
Solution

Hi, 

I managed to login to my enterprise environment via http connection and using the IP address instead of my hostname

Regards,

Joe

0
0
on 13th Jan
Daniël Kuhlmann
mvp_badge
MVP

That sounds like a DNS that is missing an entry to your environment 

0
0
on 13th Jan

Hi I am facing exactly the same issue with my enterprise environment. Can you share more exactly how you deal with this? did you enter IP address in the Environment parameter?

0
0
on 15th Apr

Hi, I am facing the exact same problem. Did you replace the environment with the IP address of the server?

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