dco application is not communicating to the Domain controller server

[DCIM_Support]

This question was originally posted on DCIM Support by shihabudheen on 2018-12-12

---

We are facing some issue with remote access ( application is not communicating to the active directory ) after DCO software up gradation from 8.1.0 to  8.2.12  , so we cannot log in to the application with our user accounts . we have logged through the local user and tried to configure authentication server set up as per the below links

http://sxwhelpcenter.ecostruxureit.com/display/UADCO8x/Configuring+authentication+servers+used+for+m...

 http://sxwhelpcenter.ecostruxureit.com/display/UADCO8x/Setup+an+AD+%28Active+Directory%29+Server

but the application is not communicating to the Domain controller server it is showing the error “serverValidationErrorLoginSetup”.

kindly help

(CID:137110833)

[DCIM_Support]

This comment was originally posted on DCIM Support by Jef Faridi on 2018-12-12

---

Hi shihabudheen,

Do I understand correctly that the remote authentication was working for you in 8.1?

If you were using the encryption (port 636) for the integration, probably (only guessing) there might be certificate change(s) on your AD server, then you could try to edit the Authentication server settings, re-enter the credentials and push Ok (to update the trust between the DCO and AD servers).

If you could provide the following data, then I will see what I can find:

1- screen captures of the configuration/settings, similar to image 1 and 2 from this guide: Setup an AD (Active Directory) Server

2- Screen capture illustrating where/how you see the error message

3- DCO server logs

4- client application.log file (usually located in C:\Users\<user name>\.isxo\8.2.12*\Operations\application.log)

5- copy of the latest backup file

I will send you an invite to my =S= box shortly, so the data safely can be provided/uploaded, thanks. 

Kind regards

(CID:137110891)

[DCIM_Support]

This answer was originally posted on DCIM Support by Jef Faridi on 2018-12-13

---

Hi Shihabudheen,

I have received your data yet, but it is most likely language related,  

the Authentication server settings feature in web-client is not localized, so most likely you might be running with non-English language. 

In web client, go to your profile > Language, and change it to English:

And then begin your authentication server settings.

Kind regards

(CID:137111873)

[DCIM_Support]

This comment was originally posted on DCIM Support by shihabudheen on 2018-12-14

---

we had selected language English 

(CID:137112305)

[DCIM_Support]

This comment was originally posted on DCIM Support by shihabudheen on 2018-12-14

---

(CID:137112307)

[DCIM_Support]

This comment was originally posted on DCIM Support by Jef Faridi on 2018-12-17

---

Hi,

According to your screen capture (from authentication server settings), client language was/is non - English - it is being translated incorrectly.

Kind regards

(CID:137725682)

[DCIM_Support]

This comment was originally posted on DCIM Support by shihabudheen on 2018-12-14

---

remote authentication was worked properly in 8.1 

yes we are using the port 636 and there is no certificate issue in AD ( no changes in AD certificates , kindly note that we have used the same AD in 8.1 

we are getting frequent error message when we are opening thin client through local user 

screen 

(CID:137112290)

[DCIM_Support]

This answer was originally posted on DCIM Support by shihabudheen on 2018-12-16

---

1. This issue has been resolved by setting up server authentication through the DCE , we can access the DCO application with our user accounts now  

(CID:137112603)

[DCIM_Support]

This comment was originally posted on DCIM Support by Jef Faridi on 2018-12-17

---

Hi Shihabudheen,

Apparently the ssl communication may need to be updated. It seems your client is set to non English language - to be able to use the authentication server settings you would need to switch the client language to English.

Kind regards

(CID:137725680)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.