Last post Dec 15, 2008 09:00 PM by hooligannes97
Dec 08, 2008 03:47 PM|dwfreeman|LINK
Our main server has dotnetnuke installed on it as a tool/framework for the main website that was built by a consultant. I am totally unfamiliar with it and our administrators are only slightly familiar. The server box also hosts several other applications
that we are in the process of developing in house. The smaller applications are built with NET or plain ASP and have nothing to do with dotnetnuke.
Occassionally, one of the smaller NET applications will fail with an error message that suggests the server cannot load something called for in the dotnetnuke web.config file. This suggests the dotnetnuke web.config and the application's web.config are somehow
being chained together even though the smaller app does not use dotnetnuke. Is this proper behavior and is there a means to avoid the problem? It seems the only way to fix it when it crashes is to reboot IIs.
Dec 15, 2008 09:00 PM|hooligannes97|LINK
This forum is inactive. all activity was moved to
www.dotnetnuke.com, if you need help you may contact me offline.