More in this section
Forums / Deployment / Upgrading to sitnity 3.7 SP4 - getting "Data is Null."

Upgrading to sitnity 3.7 SP4 - getting "Data is Null."

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.
2 posts, 0 answered
  1. Divyesh
    Divyesh avatar
    1 posts
    04 Sep 2008
    19 Nov 2010
    Link to this post

    Hi there,

    Basically we downloaded "Sitefinity_3_7_2136_standard_patch" last week and patched my development machine with the SP4 by just applying the patch directly to the project bit-by-bit and everything is fine, site works ok on my local machine.

    However we have another development server where users are actually using the site, adding contents to the site having different roles etc. The issue is, we are not able to upgrade that machine to 3.7 SP4.

    The Issue is after applying patch to that development server we are getting "Data is Null. This method or property cannot be called on Null values" error. Surprisingly the database on my machine is copied from development server couple of days before patching my machine.

    Than we tried upgrading as Gabe Sumner's video suggests using 3.7 SP4 blank project but as soon as it connects to the database we are getting the same error and we think it is to do with database.

    we check some tables and the scemaversion value in tables are 2096 where is in my local machine the value in same variables are 2136.

    What is that we need to do to upgrade the database or site?
    We will appreciate your quick response.

    Thank you.


  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    12 Sep 2017
    19 Nov 2010
    Link to this post
    Hi Div,

    The database should be automatically and internally upgraded. We check the assemblies version in your bin and perform an upgrade or downgrade depending on the version value.

    1. Could you check whether you have two or more projects with different version connection to the same database? This will cause ugrade and downgrade over the database each time you make a request from one of the websites and this alters the schema version which could cause the issue you have

    2. Here is a link with our detailed upgrade instructions that you can review once again.

    3. If the problem persists, could you send the entire stack of the error?

    Sincerely yours,
    Ivan Dimitrov
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
2 posts, 0 answered