Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Catastrophic failure-DotNetNuke 4.7 Web farmingCatastrophic failure-DotNetNuke 4.7 Web farming
Previous
 
Next
New Post
12/7/2007 9:10 AM
 

hi, I have managed to set up DotNetNuke in the Web farming environment and installed successfully.  But when I try to browse my site I get the following error:

Server Error in '/' Application.
--------------------------------------------------------------------------------

Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Runtime.InteropServices.COMException: Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 

Stack Trace:


[COMException (0x8000ffff): Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))]

[FileLoadException: Could not load file or assembly 'Microsoft.JScript, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))]
   System.RuntimeTypeHandle._GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, Boolean loadTypeFromPartialName) +0
   System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark) +72
   System.RuntimeType.PrivateGetType(String typeName, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark) +58
   System.Type.GetType(String typeName) +48
   System.CodeDom.Compiler.CompilerInfo.get_IsCodeDomProviderTypeValid() +9
   System.Web.Compilation.CompilationUtil.GetRecompilationHash(CompilationSection ps) +1800
   System.Web.Configuration.CompilationSection.get_RecompilationHash() +68
   System.Web.Compilation.BuildManager.CheckTopLevelFilesUpToDate2(StandardDiskBuildResultCache diskCache) +741
   System.Web.Compilation.BuildManager.CheckTopLevelFilesUpToDate(StandardDiskBuildResultCache diskCache) +46
   System.Web.Compilation.BuildManager.RegularAppRuntimeModeInitialize() +418
   System.Web.Compilation.BuildManager.Initialize() +235
   System.Web.Compilation.BuildManager.InitializeBuildManager() +228
   System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags) +310

[HttpException (0x80004005): Could not load file or assembly 'Microsoft.JScript, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +3426839
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +88
   System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +149

 


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

 
New Post
12/7/2007 1:46 PM
 

If you refresh the page are you able to open it? I am seeing the exact error that apparently occurs when the app pool restarts (or possibly the error is causing the app pool to restart?). I have been unable to resolve it.

I've updated .NET Framework but still no joy.

 
New Post
12/10/2007 5:09 AM
 

It does seem intermittent. I'm surprised no one else has had the problem.

 
New Post
12/10/2007 5:18 AM
 

mmmm, i'm thinking its a permissions problem now

 
New Post
12/10/2007 12:24 PM
 

I still suspect this is a permissions problem and I tried to fix it by giving the domain account I am using in my configuration modify access to the .net framework root folder on both of my web servers but the problem still persists

this is basically my setup-within a domain I have two web servers, and SQL Server and a file server.  The two web servers use a network share with in IIS to the file server which contains all of the DotNetNuke files and I use a domain account within IIS to connect to the share.  The same domain account has access to those files and I can sometimes get DotNetNuke to render fine within a browser, sometimes with errors within modules and other times I just get the full blown error above.

I wonder if it's a permissions problem with the application pools in IIS as they are using the network service identity so is the fact that a remote file share is being used causing problems?

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Catastrophic failure-DotNetNuke 4.7 Web farmingCatastrophic failure-DotNetNuke 4.7 Web farming


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out