F
Frank Meulblok
Guest
This doesn't look like a .NET dll call, but like a call to an unmanaged C dll. Quite a different beast. Although, if it's really just defining the external procedure (=declaring the DLL entry point) that triggers the session crash, I'd suspect the .dll itself fails to load for some reason or the other. Windows Event log and/or Process Monitor tool may provide more details on why that fails.
Continue reading...
Continue reading...