JxNet Eventos
| Id | Ip | Url | Hora | Token | Versión | Error | |
|---|---|---|---|---|---|---|---|
| 6125 | 10.24.63.28 | http:--jxnet.intranet.osde:80-Jx3WebApp-gestion-inbox-view | 2025-12-16T17:03:11.215Z | 8.2023.2612.8 | soporte@sisem.net | The provided anti-forgery token was meant for user ".ASPXAUTH", but the current user is "". - | |
| 6124 | 10.60.29.27 | http:--jxnet.intranet.osde:80-Jx3WebApp-gestion-forms-asunto-asu-123736 | 2025-12-16T16:33:52.838Z | Produccion_880c8a22197093c3 | 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 specified network name is no longer available.) - |
| 6123 | 192.168.0.66 | http:--neodesa:20130-Jx3APP-administracion-inbox-view-AMTPDIA | 2025-12-16T16:24:07.496Z | OSDEDESA_a43452a9db90f864 | 8.2023.2612.8 | soporte@sisem.net | DESCRIPCION - |
| 6122 | 192.168.0.66 | http:--neodesa:20130-Jx3APP-administracion-%3CJX_COL%3E%3CJX_L4%3E16-12-2025%3C-JX_L4%3E%3C-JX_COL%3E?_=1765902114071 | 2025-12-16T16:21:58.987Z | OSDEDESA_a43452a9db90f864 | 8.2023.2612.8 | soporte@sisem.net | Se detectó un posible valor Request.Path peligroso en el cliente (<). - |
| 6121 | 192.168.0.66 | http:--neodesa:20130-Jx3APP-administracion-inbox-view-AMTPDIA | 2025-12-16T16:21:26.715Z | OSDEDESA_a43452a9db90f864 | 8.2023.2612.8 | soporte@sisem.net | Invalid column name 'hola'. - |
| 6120 | 192.168.0.186 | http:--neodesa:20125-Jx3APP-gestion-Forms-Add-tar-1518341 | 2025-12-16T15:55:40.570Z | CLARODESA_3cee18d56bd1fb6a | 8.2025.2104.0 | soporte@sisem.net | El tipo de contenido text/xml; charset=utf-8 no era compatible con el servicio http://127.0.0.1:20125/Jx3SVC/DocumentService.svc. Es posible que los enlaces del cliente y el servicio no coincidan. - - Error en el servidor remoto: (415) Cannot process the message because the content type 'text/xml; charset=utf-8' was not the expected type 'application/soap+xml; charset=utf-8'.. |
| 6119 | 192.168.0.186 | http:--neodesa:20125-Jx3APP-gestion-Forms-Add-tar-1518341 | 2025-12-16T15:55:10.856Z | CLARODESA_3cee18d56bd1fb6a | 8.2025.2104.0 | soporte@sisem.net | El tipo de contenido text/xml; charset=utf-8 no era compatible con el servicio http://127.0.0.1:20125/Jx3SVC/DocumentService.svc. Es posible que los enlaces del cliente y el servicio no coincidan. - - Error en el servidor remoto: (415) Cannot process the message because the content type 'text/xml; charset=utf-8' was not the expected type 'application/soap+xml; charset=utf-8'.. |
| 6118 | 192.168.0.186 | http:--neodesa:20125-Jx3APP-gestion-Forms-Add-tar-1518341 | 2025-12-16T15:49:55.677Z | CLARODESA_3cee18d56bd1fb6a | 8.2025.2104.0 | soporte@sisem.net | El tipo de contenido text/xml; charset=utf-8 no era compatible con el servicio http://127.0.0.1:20125/Jx3SVC/DocumentService.svc. Es posible que los enlaces del cliente y el servicio no coincidan. - - Error en el servidor remoto: (415) Cannot process the message because the content type 'text/xml; charset=utf-8' was not the expected type 'application/soap+xml; charset=utf-8'.. |
| 6117 | 192.168.0.186 | http:--neodesa:20125-Jx3APP-gestion-Forms-Add-tar-1518341 | 2025-12-16T15:49:28.748Z | CLARODESA_3cee18d56bd1fb6a | 8.2025.2104.0 | soporte@sisem.net | El tipo de contenido text/xml; charset=utf-8 no era compatible con el servicio http://127.0.0.1:20125/Jx3SVC/DocumentService.svc. Es posible que los enlaces del cliente y el servicio no coincidan. - - Error en el servidor remoto: (415) Cannot process the message because the content type 'text/xml; charset=utf-8' was not the expected type 'application/soap+xml; charset=utf-8'.. |
| 6116 | 192.168.0.186 | http:--neodesa:20125-Jx3APP-gestion-Forms-Add-tar-1518341 | 2025-12-16T15:49:07.429Z | CLARODESA_3cee18d56bd1fb6a | 8.2025.2104.0 | soporte@sisem.net | El tipo de contenido text/xml; charset=utf-8 no era compatible con el servicio http://127.0.0.1:20125/Jx3SVC/DocumentService.svc. Es posible que los enlaces del cliente y el servicio no coincidan. - - Error en el servidor remoto: (415) Cannot process the message because the content type 'text/xml; charset=utf-8' was not the expected type 'application/soap+xml; charset=utf-8'.. |