Corporate Site | Register |

R2i DotNetNuke® Forum

R2i wants you to have the opportunity to ask questions, post reviews, help others or just rant and rave about DotNetNuke® or any of the R2i Modules and Skins. Our team spends hour upon hour, day after day, working on custom DotNetNuke® modules and services; please feel free to ask us anything.
 
Unanswered Active Topics Forums Search Members
Forums > DotNetNuke > Tips and Tricks
Running into machine.config errors? (line 198 or thereabouts)
Last Post 14 Jul 2005 10:14 PM by kevinmschreiner. 0 Replies.
Printer Friendly
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages Informative
kevinmschreinerUser is Offline
Advanced Member
Advanced Member
Posts:729

--
14 Jul 2005 10:14 PM  
When IIS is running an installation of DNN, it stores the runtime libraries in a separate location in order to optimize the utilization of these files. Occasionally updates to your site libraries, like installing new modules can corrupt the runtime library references in memory because the dll's in your website directory are not the same version, or are missing from the cache.

When this occurs, the easiest thing to do is stop IIS, and restart it. Rarely will this fail to correct the issue, but when it does, you may need to clear the cache of files for your website. Stop IIS, and possibly the ASP.NET worker process (aspnet_wp.exe). Then delete the directory located in your windows installation -

Ex: C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\YOUR SITE NAME.

This will clear out the runtime cache. Now when you start IIS again - it will pull the entire library from your website.

Happy Nuking!
You are not authorized to post a reply.
Forums > DotNetNuke > Tips and Tricks
Active Forums 4.1
 

New York, NY • Baltimore, MD • Vienna, VA • St. Louis, MO • Seatle, WA • 410.327.0007 • info@R2Integrated.com

Bookmark & Share Bookmark and Share
© 2012 R2integrated. All Rights Reserved.