Question

Photo of Jonathan Carlson

0

Microsoft .NET Framework exception in w3wp.exe after installation

3

I'm working on an internal server installation.  I was able to install Rock 2.0 but when I get to the "Complete.aspx" page, I get an error message pop up each time I go to that page.

IMG_1240.JPG

When I click "Flip the Switch" I get a 403 error because it's trying to view my external webpage which doesn't have any files set up as the default file for it to view yet:

IMG_1241.JPG

Any idea what's going on or what I could do to fix this?

Thanks!

  • Photo of Daniel Healy

    2

    I think I can help since I just experienced this same issue.

    I'll get straight to the meat here - Make sure you are viewing this from a web browser on the loca server!

    I had this configured for external access already and was attempting to do the install from an external location. However, when I click "Flip the switch" I get the EXACT same error as you. You need to access this from the local server. If you can't because it's already setup for a hostname within IIS, you should install the DNS role and add your desired domain and subdomain to the list so your local access to that site's address will resolve locally.

     

  • Photo of Rock RMS

    0

    There are quite a few mentions on Google for this issue (https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=the%20just%20in%20time%20debugger%20was%20launched%20without%20necessary%20security%20permissions). You might try working through them. That said it seems like your server configuration might be a little atypical. Looks like it might have Visual Studio installed and interacting with IIS. If you plan on using Rock in production I'd recommend starting with a fresh install of Windows Server. Our internal hosting guide will take you from fresh install to a successful Rock install (http://www.rockrms.com/Rock/Book/1/31).

  • Photo of Jonathan Carlson

    0

    Thanks Daniel! That helped a lot.  That was basically the problem with that.  I had to edit my host file and add a name for my site and then add that name to the bindings for my site in IIS.  That allowed me to access it locally on the server.  

    After solving that I ran into a few other issues that might help others.  I used some special characters like $ and & in my database creator password and that caused an error message saying that it was unable to parse the Web Connections Configuration file.  I resolved that by removing those special characters.  

    Also, I had another error that the CustomErrorModule was locked, and I resolved that by going into my Configuration Manager in IIS and unlocking the httperror group.  

    I'm finally online!  Thanks very much!!