JxNet Eventos

Id Ip Url Hora Token Versión Email Error
880 192.168.240.9 http:--jxnet.sisem.net-jx3CntCorp-account-login?ReturnUrl=-jx3CntCorp- 22/07/2020 01:34:40 p.m. 8.2020.529.1 soporte_tecnico@sisem.net Invalid License Key -
879 192.168.240.9 http:--jxnet.sisem.net-jx3CntCorp-account-login?ReturnUrl=-jx3CntCorp- 22/07/2020 01:33:02 p.m. 8.2020.529.1 soporte_tecnico@sisem.net Invalid License Key -
878 192.168.240.9 http:--jxnet.sisem.net-jx3CntCorp-account-login?ReturnUrl=-jx3CntCorp- 22/07/2020 01:31:47 p.m. 8.2020.529.1 soporte_tecnico@sisem.net Invalid License Key -
877 192.168.240.9 http:--jxnet.sisem.net-jx3CntCorp-account-login?ReturnUrl=-jx3CntCorp- 22/07/2020 11:47:02 a.m. 8.2020.529.1 soporte_tecnico@sisem.net Invalid License Key -
876 192.168.240.9 http:--jxnet.sisem.net-jx3CntCorp-account-login?ReturnUrl=-jx3CntCorp- 22/07/2020 11:46:20 a.m. 8.2020.529.1 soporte_tecnico@sisem.net Invalid License Key -
875 192.168.240.9 http:--jxnet.sisem.net-jx3CntCorp-account-login?ReturnUrl=-jx3CntCorp- 22/07/2020 11:42:57 a.m. 8.2020.529.1 soporte_tecnico@sisem.net Invalid License Key -
874 192.168.240.9 http:--jxnet.sisem.net-jx3CntOne-account-login?ReturnUrl=-jx3CntOne- 22/07/2020 11:42:39 a.m. 8.2019.1212.3 soporte_tecnico@sisem.net Infracción de Licenciamiento, llaves duplicadas. -
873 181.28.54.8 https:--mille.jxnet.cloud-gestion-inbox-view 22/7/2020 13:57:00 8.2019.1212.2 soporte_tecnico@sisem.net The provided anti-forgery token was meant for user ".ASPXAUTH", but the current user is "". -
872 192.168.240.5 http:--jxnet.sisem.net-crm-gestion-forms-persona-per-0 21/07/2020 05:31:52 p.m. CRM_cf362c839ee85f66 8.2020.529.1 soporte-Sisem_Team-CRM@sisem.net Index was out of range. Must be non-negative and less than the size of the collection.Parameter name: index -
871 10.216.94.200 https:--dwin0406-Jx3WebApp-gestion-forms-add-gendoc-1134195?asuId=72143 20/07/2020 12:27:36 p.m. PAU_d4b2bff852bc1812 8.2019.1212.2 soporte-TELECOM__Desarrollo___Pau-PAU@sisem.net An error occurred while receiving the HTTP response to https://dwin0406/Jx3Service/DocumentService.svc. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. - - The underlying connection was closed: An unexpected error occurred on a receive.