Apr 7, 2011 at 9:04 AM
Edited Apr 7, 2011 at 9:40 AM
- If you use IIS, have you tried defining the user on the application pool itself
It work fine but it's not what i'm looking ^^
but it show us that the problem come from an impersonation troubleshoot.
- If you run in a brand new web application using the same we.config impersonate section, and connection string, does it work ?
It work fine in default branch
but i always get the error on a clean 1.X install .
so it seem to be a regression ! :(
i'll post a workitem in the issue tracker:
EDIT: All work fine when i use the old global.asax before the implementation of warmupstarter (revision 3980) and i remove the WarmupHttpModule