error on API call from devices
-
Yes that is correct the checking time is 180, that makes sense.
can you remind me how to put the client in debug?
thank you
-
Set the log level to debug
https://docs.theopenem.com/tutorials/toec-arguments/#2-command-line-options -
ok enabled Debug, now will wait to make sure all info is populating, also all apps are installing as normal. So not sure why i have that error for an API call error.
-
ok seems to have sorted itselfout. Apologize for this inconvinient.
-
OK i did some more depth checking, Now the login and system as super slugish (we have a 64gb ram and raid 5 ssd drives nvme with a 10gb NIC, so I know it is not a problem with my system.
I am attaching the two full logs for review as I do not know where the issue is at. The settings and all have not changed and the connection to the DB are fine.Toems-API application logs.log FrontEnd - toem-UI.log
if anybody has any idea let me know.
-
How many clients do you have and what os are you using?
-
@theopenem_admin os win 10 and right now arround 33
-
That's your problem. Windows 10 only supports 20 concurrent connections. Os limitation. It's also mentioned in the getting started docs.
-
@theopenem_admin Yeah i just saw this So we are wprking to change this into a server grade system.
Now I do I migrate all so then I do not break theopenem? and my systems can work together? or just all into one server?
Can I export the DB? or how?
thank you
-
I don't have any migration docs right now. You would need to install on the new server then export the database from the old server and import to the new. You will also need the db encryption key from the web.config file. I can try to make a guide for this, but not sure when.