Question

Photo of Davey Blackburn

0

Runtime Error/Server Error in '/' Application

3

Hey,

I updated Rock this morning with the new update and then tried to go to the URL we have set for our database login (people.myresonateindy.com). I keep getting a "Runtime Error" that pops up (see image below). Does anyone else have this problem? Is it a Rock issue or an issue with my hosting?

 

Screen Shot 2014-09-29 at 10.11.55 AM.png

  • Photo of Steve Hughes

    1

    Hi all,

    I experienced the same issue when refreshing after applying the 0.13 update.  Also hosted on Arvixe.  And also definitely not a SQL expert!

    I'll run thru what I did to get back up & running.  Thankfully it's fairly simple, as that's all I'm capable of ;-)
    So, after chasing the trail from a few suggestions in these forums posts as well as a little more googling, this is what worked for me...

    And to be fair, as previously suggested on https://github.com/SparkDevNetwork/Rock/issues/544 it appears that the issue lies with a couple of stored procedures that have their owner/schema listed as the [UserName] rather than [dbo].  Not sure why or how this happened, but my access was restored by reassigning two stored procedures to dbo ownership.

    ___________
    In my example below, my databasename = StMattsRock
    and my username = RockAdmin
    -------------------

    Access your Rock installation via SQL Server Management Studio 2012.  Within the Object Explorer, expand the Databases branch & navigate to the name of your database.  As shown below, expand from there and under "Programmability" you'll find "Stored Procedures".  For me, the last two Stored Procedures in the list had their schema set to username.xxxxxxxxxxxx
    We need to change these ones to be dbo.xxxxxxxxxxx   like the rest of them.

    rockrms1.jpg

    To change the Schema of these Stored Procedures to dbo:

    1. Open a New Query.
    2. Type: ALTER SCHEMA dbo TRANSFER username.storedprocessname
      ie use your own username - for me it was RockAdmin
      The first storedprocessname for me was spCore_PageViewNullPageId.
      Therefore I entered: RockAdmin.spCore_PageViewNullPageId
    3. Execute the query to apply

    Repeat for other stored procedures.  Therefore, I opened a new query & executed this: ALTER SCHEMA dbo TRANSFER RockAdmin.spFinance_ContributionStatementQuery

    It's worth noting that whilst my installation of RockRMS came back online once these schemas were changed, the Object Explorer did not update to reflect these changes until I restarted the program.

    I hope that walk-thru helps someone out there.

    (Interestingly, after applying the update to 0.14 the error message returned for a couple of minutes.  However a hard refresh a few nervous minutes later proved that this update was actually successful.)

  • Photo of Nick Airdo

    0

    By any chance are you hosting with Arvixe?  We've seen a case where an Arvixe hosting client had a stored procedure that was not in the dbo schema. If you're comfortable with running SQL in SQL Server Management Studio, run this in a query window replacing the "RockDB" (in USE RockDb) with the name of your database:

       USE RockDb
   GO
   SELECT * FROM sys.procedures WHERE object_id = OBJECT_ID(N'dbo.spFinance_ContributionStatementQuery')

    It should return a single row.

    Also, run this SQL to see the last database migration that successfully ran:

       SELECT TOP 1 [MigrationId] FROM [dbo].[__MigrationHistory] ORDER BY MigrationId DESC

    For Rock McKinley v0.14 it should return "201409241226361_PersonDuplicateConfidence".

    Other than that, you can try carefully editing the web.config enabling the RemoteOnly as shown in the screenshot and also look at any recent entries in the App_Data\Logs\RockExceptions.csv

    • Keith Pavia

      Keith Pavia

      I got the same error when upgrading to 0.13 and to 0.14. Both times I had to go it and restart the server and the service pools. Both times it came back up after aseveral minutes. We are using Arvixe. However the 0.14 update removed our Ad Blocks on our home page, even though I thought the notes said that it would not do that until after 0.14 update.


      I am restoring my web site now, to get it back to 0.12. Bummer....


      Nick, I am back to 0.12. The results of your first query for me is: "No Results". The results of the second query is: 201408221117347_AddPersonDuplicateFinderProc


      Why would Arvixe not have this stored procedure? And, what do I need to do to fix it?

      • Jim Michael

        Jim Michael

        Keith- I'm pretty sure the note on the upgrade page warned that Ad Blocks WOULD go away if you update, and even provided a work-around to get them back if necessary. This is the danger of implementing beta software before it's fully baked. That's not to say we shouldn't all be poking at it and figuring it out (which is why we're all here, after all), but until 1.0 arrives we can't assume things won't change... sometimes dramatically.
        As for the Arvixe issue, I cannot say what causes it, but it sure seems to be a common theme on that platform in the way the db is getting set up or rights are being applied. It looks like other have figure out the fix, so no need to repeat here. I've been immune to all of these issues as I'm hosting locally, and have had exactly zero issues with any upgrade.

      • Photo of Davey Blackburn

        0

        Hey Steve and Nick,

        Thank you for your answers! This is super helpful! We do host with Arvixe and I had one of the Spark Developers walk me through this, but I'm sure your responses will help others with this same problem! Thank you again!