EMS 7.4.4 Web Server 500 Error after migration

[SteveJW]

In my test environment, I migrated from FortiEMS client 7.2.2 to 7.4.4.
We deployed EMS on a Hyper-V VM.
I didn't encounter any issues during the migration.
I want to start the console now, but I'm getting the error below.

I think it has something to do with the certificate, among other things.
How can I remove it and/or configure/import a new certificate?

[SteveJW]

I just checked my logs, but besides numerous other errors, I still see the same socket errors in various logs.
Despite the errors, I can now access the console after my second migration test.
So I would check for other errors.
I think the default port should be 5432.

I have a ticket open with support regarding the numerous errors in various logs.
The only response so far has been to adjust the resources in my VM.
https://docs.fortinet.com/document/forticlient/7.4.3/ems-administration-guide/358374/system-requirem...

I'm currently not having any issues with version 7.4.4, but this is a test environment with two endpoints.
I want to make sure the errors in the logs don't cause any vague issues in the near future when I start migrating to production.

[SteveJW]

I forgot to mention this earlier, but the final response from Fortinet support is:

Regarding "encrypted columns update: 60%", no similar cases or reports found.

I'll perform the migration in production next week.
I'm curious to see what the output will be.
I'll create a new post here if I encounter any issues.

I forgot to ask.
Can I perform the migration during business hours if users are also connected to the EMS server?

[AEK]

Any upgrade that impacts the production we avoid doing it during business hours.