While our production portal is no longer down, we do still appear to have major issues.
Our event log has gone crazy and now stands at over 500,000 rows. I am just about to archive these to address any possible performance issues.
Just this morning we have had over 18,000 General Exception errors logged - the majority of which report this error:
System.Exception: Unhandled Error: ---> System.IO.FileLoadException: Could not load file or assembly 'DOTNETNUKE' or one of its dependencies. Access is denied. File name: 'DOTNETNUKE' at System.RuntimeTypeHandle._GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, Boolean loadTypeFromPartialName) at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark) at System.RuntimeType.PrivateGetType(String typeName, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark) at System.Type.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) at System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) at System.Web.Configuration.HandlerFactoryCache.GetHandlerType(HttpHandlerAction handlerAction) at System.Web.Configuration.HandlerFactoryCache..ctor(HttpHandlerAction mapping) at System.Web.HttpApplication.GetFactory(HttpHandlerAction mapping) at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig) at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. --- End of inner exception stack trace
Now our sever guys have checked, double checked and triple checked the server permissions and are convinced that they are OK and that nothing has been changed for weeks now.
So why are these errors being thrown up now?
We haven't released any new code to our production portal.
So what could be causing all these errors?
What else could of changed that we are missing?
Any help or suggestions would be very gratefully received.