Topics created by mzprays

I ended up adding MaximumPoolSize=25; to the connectionString for all of the Toec-API instances and everything seems happy now. Increasing the max connections would have likely had the same effect, but I'm not seeing all the connections utilized even at peak checkin times. HeidiSQL is a great troubleshooting tool.

I did some digging and it appears bootType is being incorrectly detected as legacy, so the script is formatting the drive as MBR. $env:firmware_type contains the correct value, EFI. I found that the boot type is determined using Confirm-SecureBootUEFI, interpreting a failure to run as legacy boot. This system does not support secure boot, causing Confirm-SecureBootUEFI to crash, although it does use UEFI. Is there a reason Confirm-SecureBootUEFI is used instead of $env:firmware_type for the boot type?

It's correct. There is no virus. It's because Toec can elevate and impersonate users but obviously that's intentional. It's used for the new Winget functionality. The virus scanner is complaining about this file.

https://github.com/jdolny/Toec/blob/master/Toec-Services/ServiceRunAs.cs

@mzprays https://docs.theopenem.com/changelog/version-history.html#154-6-2-23 ah, nevermind

Nevermind, it fixed itself.

Have you tried putting that entire command in the command field instead of using the arguments field?

Solved, my network adapter was set to NAT in VirtualBox
https://forum.theopenem.com/topic/237/image-upload-always-hangs-at-9-86

Alright, thanks. I'll continue as is for now and see if the connections becomes a problem.