Unable to reach TIE Server via DXL

[kblowe]

I have a DXL connection & everything is connected to DXL on the ePO server and all clients, but my TIE Server Topology has a DXL Connection Error:

Error		[-]
Unable to reach TIE Server via DXL. McAfee ePO can't connect to TIE Server. Possible cause: - TIE Server is transitioning between operation modes. It won't connect until this process is complete. Wait a few minutes, and refresh the page to see the latest status. - TIE Server upgrade is running. On Secondary servers, this process might involve a full database sync with the Primary server, which might take several minutes. Check /tmp/reconfig-tie.log to monitor the progress. - No service registered on DXL Fabric for this TIE Server. Check service status on the appliance. - No DXL brokers available for connecting McAfee ePO and TIE Server. Check connection status of DXL Client for ePO. - Verify that DXL Topology settings and DXL Fabric are configured correctly. I ran restarted DXL BRoker services, ran numerous commands; reconfig-ma, reconfig-network, reconfig-cert etc. but nothing seems to fix this issue. The test connection from ePO to the TIE Database was successful as well. What am I not doing? Need some assistance before I decide to stand up another TIE server.

[bbarnes]

Hello kblowe,

The initial setup of your first TIE server does involve a few behind the scenes steps that must be completed before the server itself would report online.. I would recommend contacting support and some quick log review may point to the actual cause of the problem.

Some items you can check:

- Ensure the TIE Server Management extension is checked into ePO.

-Ensure you see the TIE server in the system tree and that all products are showing up as installed.. 

-The system should automatically inherit the TIESERVER tag in ePO, without this it will not show up.

One of the following log  files may give you a hint as to what is going on:

/tmp/reconfig-tie.log

/var/McAfee/tieserver/logs/tieserver-start.log

Thanks, 

Brian

[kblowe · Accepted solution]

I figured out what was behind this issue. The sudo or sudoer permissions were corrupted inadvertently. I ended up running some chmod commands to fix the issue. After the sudo permissions were fixed. restarted TIE server, ran TIE ePO server task and the error mentioned in this thread was rectified. Thanks.