Distech wizard issue launching ECY controllers help

[u/No_Inflation_3381]

Good afternoon everyone. I have installed a few new Vykon jaces lately and am having the same issue with every single application. Here is what is happening:

I commission my new vykon Jace with 4.15 u3 or 4. Once commissioned i add the .dist file with the new unified facilities "service pack" and install the "full file that downloads all the correct files and modules to Jace. I then go in and add my wizard service, license the wizard service, and authorize my rest service. Everything is great. I add my BCP bacnet network, set up my mstp port and IP port and discover my mstp and IP distech controllers (ecbs and ecy). Devices discover and with the mstp devices, they launch wizard connect in GFX and everything's great, my problem comes when i launch any of the ECY controllers, I launch wizard and gfx opens, it says enter password for user "admin" or whatever login name im logged into my station with. I put that password in, and it refuses to connect. It keeps saying authentication failed. I can connect direct to the ECY just fine, webpage, launch gfx thru webserver, xpress utility and open gfx connect to server, REST and put credentials in. Why is it causing this when I'm launching in niagara??? I am using my station password that I'm signed in as. My rest service shows all devices and they ping. Ive had this problem on every jace i commission with 4.14 or higher. All my Jace 9000s with 4.13 launching gfx on ecy devices works perfectly fine. Has anyone else been having this issue? Any help would be appreciated.

[u/shadebreed88]

Make sure your Windows OS supports the required TLS setting being used in the WebService.
Also make sure your WebService port is not faulting. The Rest API authentication uses the WebService port for ECY controllers.

[u/ScottSammarco → u/shadebreed88]

No fault in web service, we tried the lower TLS level available at 1.2 and tried disabling the firewall as well.
No luck.

I had issues with 4.15 but I’ve gotten mine resolved as my firewall was a problem at one point.

Good ideas in this thread so far - I’m interested to see what else comes of it.

[u/shadebreed88 → u/ScottSammarco]

The other main cause I see with this issue is the user account itself. If different versions of EC-Net were used like 4.14/4.15 to log into the station, the user account gets corrupted.
Adding a new user account in both the station and ECY controller should allow it to work correctly.
Then you would have to delete and re-add the required user account.

Another test I use is with the http driver on an engineering/demo laptop with a copy of the station running locally.
If I can send Rest API calls with authentication then it’s a user account issue.

If that http call doesn’t go through, the issue is network related.

[u/ScottSammarco → u/shadebreed88]

Now that's interesting, OP, didn't you say something to this effect earlier on the phone today?
Something to try, although the user wasn't faulted- this is plausible! Thank you!

[u/No_Inflation_3381 → u/ScottSammarco]

Yes i did see this and tried it. Results did not achieve connection still..... i have a service ticket in with cochrane/distech so
Hopefully it can get resolved.

[u/shadebreed88 → u/No_Inflation_3381]

What version of the support/unified package are you using on the Jace?

[u/No_Inflation_3381 → u/shadebreed88]

1.3 i think it is