07/07/2004, 08:10
|
 | Colaborador | | Fecha de Ingreso: enero-2002 Ubicación: Centro de la república
Mensajes: 8.849
Antigüedad: 23 años, 3 meses Puntos: 146 | |
| Mira, buscando el error en internet encontre:
I looked for the solution to this bug for more time than I had to
spend. Problem A is that debugging under IIS is more than a little bit
of a hassle. Problem B is that it seems to be a bogus pointer or
corrupted memory that causes the access violation, and I wasn't able to
track it down.
Patches that fix the problem are very welcome, in the mean time,
changing the security model to "low" seems to be a valid workaround.
Esto es, en el IIS->Sitio Web Predeterminado->Propiedades->Directorio Particular-> Nivel de Proteccion cambiar a Bajo (IIS).
Saludos |