JxNet Eventos
| Id | Ip | Url | Hora | Token | Versión | Error | |
|---|---|---|---|---|---|---|---|
| 3342 | 209.13.159.124 | https:--jxnet.sisem.net:443-account-LoginCloud | 2025-04-24T17:47:10.553Z | 8.2023.2612.3 | soporte@sisem.net | The server could not be contacted. - | |
| 3341 | 209.13.159.124 | https:--jxnet.sisem.net:443-account-LoginCloud | 2025-04-24T17:47:01.964Z | 8.2023.2612.3 | soporte@sisem.net | The server could not be contacted. - | |
| 3340 | 209.13.159.124 | https:--jxnet.sisem.net:443-account-LoginCloud | 2025-04-24T17:46:38.123Z | 8.2023.2612.3 | soporte@sisem.net | The server could not be contacted. - | |
| 3339 | 209.13.159.124 | https:--jxnet.sisem.net:443-account-LoginCloud | 2025-04-24T17:46:24.446Z | 8.2023.2612.3 | soporte@sisem.net | The server could not be contacted. - | |
| 3338 | 10.33.17.35 | http:--jxnet.intranet.osde:80-Jx3WebApp-account-LoginJx3 | 2025-04-24T17:22:54.675Z | 8.2023.2612.8 | soporte@sisem.net | The required anti-forgery cookie "__RequestVerificationToken_L0p4M1dlYkFwcA2" is not present. - | |
| 3337 | 10.60.114.62 | http:--jxnet.intranet.osde:80-Jx3WebApp-account-LoginJx3 | 2025-04-24T15:17:35.537Z | Produccion_361af1047fcefff6 | 8.2023.2612.8 | soporte@sisem.net | The provided anti-forgery token was meant for user "", but the current user is ".ASPXAUTH". - |
| 3336 | 10.247.121.136 | http:--jxnet.intranet.osde:80-Jx3WebApp-account-LoginJx3 | 2025-04-24T12:23:09.089Z | Produccion_4ebd6f6e6be9b700 | 8.2023.2612.8 | soporte@sisem.net | The provided anti-forgery token was meant for user "", but the current user is ".ASPXAUTH". - |
| 3335 | 10.248.245.64 | http:--jxnet.intranet.osde:80-Jx3WebApp-gestion-inbox-view | 2025-04-23T18:46:16.709Z | 8.2023.2612.8 | soporte@sisem.net | The provided anti-forgery token was meant for user ".ASPXAUTH", but the current user is "". - | |
| 3334 | 10.1.74.195 | https:--legales.supervielle.com.ar:443-Jx3WebApp-reportes-Reports-ReportFilters-178-ASUALL | 2025-04-23T18:08:18.980Z | PROD_53adbc815d72e166 | 8.2023.2612.0 | soporte@sisem.net | Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. - |
| 3333 | 10.248.123.163 | http:--jxnet.intranet.osde:80-Jx3WebApp-gestion-forms-asunto-asu-134877 | 2025-04-23T18:00:22.261Z | Produccion_8bab9e92d84b4f13 | 8.2023.2612.8 | soporte@sisem.net | A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.) - |