This is deep, I have been working it for months, hope someone understands and can help.  Ready.

I have DNN 4.03 running on 2003 server and SQL 2000. Port forwarding requires the Default Web site to point to my DNN Web.  But, I have a Web Service developed in VS 2005 running in a Virtual Directory underneath it. I have separate Application pools but no matter what I do the web service inherits the web.config from the root default web site (I have beat my head bloody on this for weeks).  I get this strange error: This application was precompiled with personalization turned off, but it appears to have been turned on after the precompilation, which is not supported.

It appears to be a conflict with the DNN Web.config because if I point the Default Web site somewhere else (this removes the DNN web config from the inheritance chain) it works great.  I have tried putting some "Clear" statements in my web service web.config to get around it but nothing seems work.

Stry, I can fix it temporarily by changing the Default Web home directory, testing the web service (runs perfectly), and then change the Default Web back to DNN.  This works for awhile, but eventually IIS remembers that is doesn't like it and I start getting the error again.

I have tried a redirect from the Default Web site to a Virtual Directory for DNN.  I think this should be the answer but could not get it to work. (this would again take the DNN web.config out of the inheritance path but may hide the web service)

I have also tried to isolate the web.configs using "Location" tags in the DNN web.config but I could not get that to work either.

I also spent a day or two getting  the Microsoft "Web Admin Tool" working.  Nice idea, but a total waste of time.

All in all this attempt to upgrade from DNN 2.X to DNN 4.03 and Windows 2003 has been a nightmare and a wonderful learning experience.  I won't even get into the tightened security in 2003 IIS.  So if anyone is an IIS/2003/DNN/Web.config expert, please throw me a bone before I throw my web server into the parking lot.

P.S. I'm going to 4.1 as soon as it hits the streets.  Maybe that will fix it.

Thanks,

Jeff  

---

Trusmart Technologies Corp.

thanks!  i have been trying to figure this out too.  you just saved me at least a days worth of headache.  i pasted in your code and things started working immediately.  question though, what does the ftbwebresource.axd line do in the web.config?

Just wanted to let you know that your post also helped me solve my issue. I'm not running a DNN site right now, but I did get the "Profile appears to have been enabled after compilation" error, after I enabled the Profile system in my main root site. Like you, I didn't think this would affect my other child sites, because they are supposed to be isolated in their own app pool processes. But all my sites do use the same database for their Membership system, so that could have something to do with it.

Anyway, just wanted to say thanks! You saved me who-knows-how-much downtime. These are the only lines I had to add to my child sites' web.configs:







Once I added that to each child website, it fixed it right up!