4.1 Busted our install
So, we have 2 issues after upgrading to 4.1. We've been messing with it all day to get to this point.
Issue 1: Site won't run using IIS. It only works (sort of, using the internal server in the Sitefinity Project Manager)
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. |
|
|
I got the first error as well. I changed security permissions to allow "Network Service" full control over the App_Data directory and the error was resolved. I hope this helps a bit...
Thanks so much. That fixed the IIS issue. Now I'm just left with the 2nd issue.
Can't help with that second one, that looks nuts :)
FYI
I received this error locally when developing through VS2010. We use
Team Foundation Server. I needed to have the App_Data folder checked out
to fix this issue.
Hi Kyle,
Sorry for the bit late reply.
Do you see the 2nd error on all front end pages or just on some of them? We will have to isolate the issue and check if it is caused by the template or some of the controls.
Please let us know if you have any further findings.
Need to fix this guys
Come on guys, I have wasted 4 hours on this already 4.1 is broken. The initial release wasn't tested for custom master page files either. The default template is almost useless as well because there are no easy ways to create full width footers and headers on top of it. Please Please Please.
Thanking you for for fixing the boldness ( so it is nolonger italic, too) in the forums promptly!
Hello Jwize,
We've fixed some problems that might have caused the layouts to break, in the latest internal build. I suggest you trying with it, and send us the whole project and the database, if things go wrong or do not work again. We will fix it locally and return it to you with further information.
Kind regards,****************************** How to Fix *******************************
Make sure ALL files and ALL folders in App_Data are NOT read-only and have given NETWORK SERVICE FULL PERMISSON (I found even removing read-only from App_Data did not auto remove read-only from the Configuration folder)
Stop your site in IIS
Stop the App_Pool
Start the App_Pool
Start the site in IIS
************************** Note ******************************
This is how I resolved this issue for me on Windows Server 2003 using IIS6.