Client Log => Could Not Complete API Request
-
Hi,
I have the following error in the log file of my customers.
Since the installation of the RemoteAccess add-on:021-01-21 16:15:44,315 ERROR [50] ApiRequest - Could Not Complete API Request. The Response Produced An Error.ProvisionedComm/Policy/GetClientPolicies/ 2021-01-21 16:15:44,316 ERROR [50] ApiRequest - {"Value":"GSK+d5tIJ8SlzjXYPng5Ol4NfVGMoJDqzB7mq4oHSvjBPQczYerUmvFs0yLVe52FF7FnL4dC/aN538Pjceo5IQ=="} 2021-01-21 16:15:44,317 ERROR [50] ApiRequest - {"Message":"An error has occurred."} 2021-01-21 16:15:44,317 ERROR [50] PolicyRunner - Error Trying To Parse Policies. Aborting Trigger: Checkin
Thank you for your answer
-
Can you export the policy where you have enabled remote access and attach it?
-
Ok
Remote.txt [0_1611243740782_Remote.json](Envoi en cours 0%) -
sorry, I asked for the wrong thing. For the client in question, can you select Computers->View->Effective policy and add that?
-
No problem here it is
-
Everything looks good there. This client is definitely running 1.3.0? Seems that they would have to be to even checkin. Is this happening to all of your clients?
-
Yes on all my workstations.
And they are all in 1.3.0 -
Just to confirm, this worked fine until installing the remote access addon? That addon is totally independent of Theopenem and would not interfere. Has anything else changed? How are your IIS bindings setup for the com server? Are you using https?
-
All connections are in http
I changed the Toec-API port to 58888 and everything worked.
I installed the add-on and changed the remotely port to 58000.
Configured remote in toems-ui and restarted my VM. -
Can you attach your com server log? We may need to put it in debug mode, if nothing is there.
-
it is empty
-
In your toec-api web.config file towards the bottom, find the line that says
<root> <level value="INFO" /> <appender-ref ref="ClientApiLog" /> </root>
change it to:
<root> <level value="DEBUG" /> <appender-ref ref="ClientApiLog" /> </root>
-
Ok here is the file
ClientApi.log
New version of file -
I believe this issue is still the user processes monitor, only now it's crashing on the server instead of the client. I'm not sure if disabling that again will fix it though. I need to apply the same fix to the server as I did the client and I'll get back to you.
-
@theopenem_admin All right, thank you very much
-
Toems-Service.dll
Can you put this updated file in your toec-api\bin and toems-api\bin folder on all of your servers, it should ovewrite an existing file. I think this should fix the checkin issue, but I suspect if you try to pull reports for the processes it will still crash, I'll take care of that later. -
@theopenem_admin It's good more message in toec client logs
Thank you -
Hi @theopenem_admin
With version 1.3.1, I have the process feedback in ToemsUI.
Thanks a lot