Question

Photo of Chris Rivers

0

Error downloading Rock

4

Hey guys, 

I downloaded Rock 3.0 yesterday and after download tried to log back in and get this error. Any idea what I might need to do here? 

Rock Error .png

  • Photo of Jon Edmiston

    0

    Looks like either a compatible version of the System.Runtime.Caching assembly is not in the server's GAC or the application is using a .net Client Profile instead of the Full .net version.  You could try to try a different .net version.  Not sure what options are availble other than 4.5.2.  You could try 4.5.1 if that's available (nothing less than this though). 

    Either way though I agree with Cody above. You should consider moving from GoDaddy as they don't specialize the enterprise level hosting of .net environments.

  • Photo of Trey Hendon III

    0

    Hey Chris,

    Just to make sure, is it possible your server settings got changed from .Net 4.5 to .Net 4.0?

    -Trey

  • Photo of Chris Rivers

    0

    Trey, my server settings are .NET 4.5. Any other ideas? 

  • Photo of Chris Rivers

    0

    Jon, 

    I'm using Godaddy as my hosting environment. I'm using their "Ultimate Windows Hosting with Plesk" plan. Here are my hosting settings (http://screencast.com/t/YEaUvcdbObt7) 

    Rock image one.png

    • Cody Tindall

      Cody Tindall

      Not a solution to your problem as much as a warning. I just switched from Godaddy's Ultimate hosting to an in-house server. The website performance over all was sluggish (not unbearable but definitely slow to respond) and that caused problems with updating. The reason we switched had to do with the database size cap. If I remember correctly the database tops out at 250mbs and there is no way to increase this without upgrading to a VPS or hosting the database somewhere else. Scanning our checks/envelopes is probably the main reason we maxed out the database but regardless 250mb is not a long term option. Its easier to start planning the switch now than for Rock to be dead in the water until you adjust. With that said, I would take a look at your webconfig file and make sure there isn't something out of place there. If you have a backup of your site I would consider rolling back to that and maybe just trying the upgrade again.