Question

Photo of Ron Young

0

Install on Azure error on external web page 1

Is there an answer for this or a work around? 


ERROR: There was a problem getting content... Show Details Unterminated string. Expected delimiter: ". Path '[1]', line 5, position 1.

I deleted the installation and reinstalled same issue. I had done a test install on local Hyper-v guest machine and it works perfectly.


Any Thoughts

Thanks

Ron Young


So this is install as a VM on Azure Windows Server 2012 with SQLExpress 12, Also this only appear to happen on page 1 (external home page) and the page 346 (blog) everything else appears to be working fine. 

Installation
  • Michael Garrison

    Please let us know how Rock is installed on Azure- is it in a VM or a WebApp container? SQL Server or Azure DB? I'm not familiar with this error, but a little more information might spark something in someone else ;-) If you're willing, sharing the domain or address you've got it installed on might help, too

  • Photo of Daniel Hazelbaker

    2

    Richard, (And Ron if you are still having this problem), Try the following:

    On the page(s) that are having this error, click the Block Editor icon in the admin bar at the bottom of the screen (it's the one with 4 small squares together). Edit the settings of each Content Channel block by using the Pencil icon for the block. Click Save without making any changes to save the block. I believe that will fix the problem. This happened to somebody else recently and this was the fix. We don't know what the actual root cause was though.

    BTW because this is on the external site you need to make sure you are logged in to the external site so you can get to the admin bar.

    • Gladson Jacob

      I had the same issue on a new install I did on Azure. I did what Daniel suggested and that solved my issue.

  • Photo of Ron Young

    0

    So this is install as a VM on Azure Windows  Server 2012 with SQLExpress 12, Also this only appear to happen on page 1 (external home page) and the page 346 (blog) everything else appears to be working fine.  sorry this is appearing as an answer, No sure how to add to the question 

    Ron Young

  • Photo of Richard Krvaric

    0

    I get the same error... 

    I just did a brand new install - I've been asked to help assist with a new site for church.

    I have a VM with Windows Server 2012 R2 installation, with SQL Server Express 2016 (this is a test/play site). Install went fine, I upgraded Rock to the latest, and this is what the first page looks like. 

    error1.PNG

  • Photo of Sheen An Goh

    0

    Hi,

    I also faced a similar issue and had the exact same problem. Does anyone know how to fix this? :)


    • Daniel Hazelbaker

      Sheen,
      Yes. It should be the same process. Edit the block settings for the two blocks causing that error and click Save. You don't need to make any changes, just open the editor modal and then save and that should take care of it.

  • Photo of Sheen An Goh

    0

    Hi Daniel,


    Thank you for your answer! It took me some time to find the admin bar, haha. I didn't know you must go to the bottom of the browser for the admin bar to appear.

    The issue is resolved now, thank you!

  • Photo of Peter Schott

    0

    Thanks, Daniel. Realized I needed to log in w/ some login that could edit the site and followed the instructions. Worked to get those working on my 6.2 site. Any idea why this is happening? Trying to run on an Azure WebApp and an Azure SQL DB. This is the only oddity I came across so far.  (The WebApp is a total test - I realize that's not necessarily best practice and/or supported.)

    • Daniel Hazelbaker

      Not yet. I need to get a full Windows Server + SQL and then figure out a way to do a custom build of the installer. The migration that populates that data looks perfectly fine, so I think I need to find a way to have the installer log the contents of those rows after every migration runs so I can find out what is changing them to be malformed data - though it only seems to be on new installs.


      I'm also wondering if the new installer is maybe using a new version of NewtonsoftJson that is having issues. Needles to say it's going to be a pretty complicated bug to dig into and find :(