[Can't use AD integration]

21 hours ago, AuMonroe said:

This! I can define a Mapped AD group to admin permission set, but when I try and login I get "Login Failed"

I am using DOMAIN\username

if I use a bad password or username on purpose the error is still "login failed"

How can I go about troubleshooting this?

Complete ESET SMC newb here, so be gentle hahaha

 

TIA

AuMonroe, if your ESMC server is a virtual appliance, you need access to the server's terminal

1. Open the virtual appliance console (from your hypervisor), login with the administrator's password
2. Then you can either
   • Enable remote access : this will give you the option to SSH into your ESMC server
   • Exit to terminal
3. Browse to the /var/log/eset/RemoteAdministrator/Server/ folder. The trace.log file should be there.

Dont forget to disable the remote access if you enabled it

[Can't use AD integration]

For my part, it looks to be a memory allocation error : 

2019-02-01 12:36:02 Error: ConsoleApiModule [Thread 7f9026fdd700]: 142 Error while sending AuthenticateUser request [UserName=DOMAIN\user] boost::process::detail::posix_start: fork(2) failed: Cannot allocate memory
2019-02-01 12:36:02 Error: ConsoleApiModule [Thread 7f9026fdd700]: Untranslatable CInterModuleException: boost::process::detail::posix_start: fork(2) failed: Cannot allocate memory
2019-02-01 12:36:02 Error: CServerSecurityModule [Thread 7f90b77fe700]: boost::process::detail::posix_start: fork(2) failed: Cannot allocate memory
 

The ova image was configured with 4 GB of ram, I ended up boosting it to 10 GB because of errors I first got when I tried to migrate from ERA 6.5 to ESMC 7.

I am monitoring the virtual machine's memory usage right now and I can see that its using 7.56GB of memory.

Maybe a JVM setting I missed?

 

[Can't use AD integration]

I have the same issue