I am upgrading one of our websites from 5.0 to 5.4 through successive upgrades of each released version between the two. Each upgrade completes successfully and I can fully browse the site with no problem. When I upgrade from 5.3 to 5.4 the upgrade completes successfully in the Project Manager, but when I attempt to go to Administration or to browse the site, the browser just spins away until the connection terminates. I've restarted IIS, checked permissions and even rebooted the server to no avail. Upon checking the Application event log on the server, I get the following error showing up. It appears it is killing the site's w3wp.exe process for some reason...
"Application Error" Event ID 1000
Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc00000fd
Fault offset: 0x0000000000054f61
Faulting process id: 0xe6c
Faulting application start time: 0x01ce1b6dd02224d7
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 50ed196a-8761-11e2-b0bd-000c29c73b0a
Here are also subsequent messages that appear:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Anyone have any idea why this is happening just with the 5.3-5.4 upgrade?
Here is additional info gathered by debugging it:
"StackOverflowException was unhandled
An unhandled exception of type 'System.StackOverflowException' occurred in mscorlib.dll
Make sure you do not have an infinite loop or infinite recursion.
Not sure why 5.4 has triggered this. Everything was fine with the 5.3 upgrade earlier today...
Yes, we do have a few custom content modules. How does that affect it? Especially when I can successfully upgrade the site through all versions up to 5.3? We aren't doing anything special or fancy, Just some simple content modules.
We don't have any custom module code like that. We pretty much just defined custom modules using the Module Builder and are using fairly basic widget templates. There also is nothing LanguageData based.
I have not encountered this problem after an upgrade from 5.3 to 5.4. Do you by any chance have any content based custom modules?
Would it be possible to go through custom module code and look for this line:
This was valid for custom modules built before the module builder, since you do not have such, the issue is entirely different. Would it be possible to open a support ticket and send us the generated error logs so that we can investigate the issue in detail.
Thank you in advance.
Steve is correct. This has been logged for fixing. Check your ContentViewConfig file for <config:lazy, create a backup of the file, remove the lazy config entries, save the file and try again.
I am glad to hear that you managed to resolve the problem. I hope this information will be helpful for other users who are experiencing the same symptoms.
I realize this post is fairly old, however, I am running into the same issue. The differences between my project and the one listed above are following:
1) there are no references to <config:lazy/> in the ContentViewConfig
2) There appear to be references in the LibrariesConfig and NewsConfig, but these are for the backend pages. I've tried removing it but no effect.
3) We are getting the error upgrading the site to 6.0, not 5.4
4) The configs are actually stored in the database, not in the Filesystem.
Would any of these make sense as reasons why we would be receiving the System.StackOverFlowException error? If not are there any other configs or Sitefinity issues which would cause this error?