Hi Sebastian,
How is the certificate under https 443 binding? Is valid?
And... the 443 port shows as ' listen' on server?
IIS logs shows some relevant info about this?
Hello Uiliam!
I dont really know how to enable DS debug logs but I found 2 folders under Airwatch/Logs on the DS server. One log named DeviceServicesLogs.txt and DeviceManagement.txt
When I open them they only show logs up to 2018-11-28 at around 14:00 and that's about the time our servers crashed and there are no logs after that.
If I check the logs in the Console at the time the servers went down it says:
2018-11-28 15:09:21 SYDSRVAWCS01 daeaad63-3513-4e3b-aa01-8537d0e4da51 (1) Info **************************************************************** WanderingWiFi.AirWatch.Console.Web.Global
2018-11-28 15:09:21 SYDSRVAWCS01 daeaad63-3513-4e3b-aa01-8537d0e4da51 (1) Info * Starting WanderingWiFi.AirWatch.Console.Web 9.3.0.0 WanderingWiFi.AirWatch.Console.Web.Global
2018-11-28 15:17:47 SYDSRVAWCS01 50c68b54-b5b6-4400-92f4-1a81b3003fc8 (7) Error Object reference not set to an instance of an object. WanderingWiFi.AirWatch.Console.Web.Controllers.LogoutController
2018-11-28 15:17:48 SYDSRVAWCS01 3ffea47c-6c4e-4bb3-a0c3-7a7e71820255 (8) Error Object reference not set to an instance of an object. WanderingWiFi.AirWatch.Console.Web.Controllers.LogoutController
2018-11-28 15:38:17 SYDSRVAWCS01 88fa515b-08a2-49c8-8347-7f7d12518d1e (8) Info Stopping WanderingWiFi.AirWatch.Console.Web 9.3.0.0 WanderingWiFi.AirWatch.Console.Web.Global
2018-11-29 06:58:11 SYDSRVAWCS01 88773f0f-180a-432e-998f-f375a8302d49 (1) Info ***************************************************************
I have enabled logging on Device Services now under Diagnostics > Logging. But the problem is still that ' DeviceServicesLogs.txt' stopped logging 28/11 at 14:00 when the servers crashed. So even though I have enabled the DSlogging it's not updating the .txt file.
I also tried doing a restoration on the Device Server from the day before the server went down and it was working but the issue is still the same with the older backup.
Im thinking it's maybe some communication error between the devices and the mdm server. But I tried pinging the mdm server and it's external IP adress from an external network and it works.
Hi Sebastian,
How is the certificate under https 443 binding? Is valid?
And... the 443 port shows as ' listen' on server?
IIS logs shows some relevant info about this?
Definitely could be the certificate. Otherwise, not sure how your environment is setup, but in my organization I don't manage the load-balancer or firewall configuration. If you don't either, you'll probably want to present this to your data network team to see what changes were made recently that would cause 443 to be blocked.