44
Views
7
Comments
Solved
[ServiceStudio]Can not Connect to environment.
Service Studio Version
11.10.20 (Build 41467)

Hi here,

I can not connect to My Personal environment and Another on-premise environment from today.

(Yestoday is ok).

OS Version:Windows10 Enterprise(1909)

Service Studio Version:11.10.20(build 41467)


And i tried on another laptop with same Service Studio Version ,two environment it are all ok.



Solution

Hi,


First of all thank you for reporting this issue and providing workarounds.


We released a new Service Studio version, 11.10.20.41551, which should solve this issue. If possible try to update your version and tell us if it worked.


Thank you!

mvp_badge
MVP
Solution

fixed the problem by reinstall the version of:

Service Studio Version:11.10.19(build 41208)

Hi Ming,

I don't know why its happening in personal environment. But in the on-premise environment, this insecure connection warning is due to the "SSL" certificate. Once we installed "SSL"  certificate this warning wont occur.

This is strange but from today Morning I am also having the same error.

Tried different Environments and different machines. Also tried different networks and premises VPN.

Same error as Ming.

Service Studio Version:11.10.20(build 41467)
Platform :11.10.3 (Build 27323)

 

mvp_badge
MVP
Solution

fixed the problem by reinstall the version of:

Service Studio Version:11.10.19(build 41208)

Fixed for me as well.
I cleared Cache from TEMP folder and restarted my laptop.

Works well with the same Service Studio version which I installed previously.
(Still don't know the reason for this)

@Palak Patel ... exactly which TEMP folder did you clear?

I found and fixed it!

The OutSystems Settings.xml file somehow was changed to be <HasSSL>false</HasSSL>

Check out the screenshot below - I simply changed to true, saved Settings.xml and restarted OutSystems Service Studio.

Solution

Hi,


First of all thank you for reporting this issue and providing workarounds.


We released a new Service Studio version, 11.10.20.41551, which should solve this issue. If possible try to update your version and tell us if it worked.


Thank you!

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