Try Now
More in this section

Forums / Migrating from 3.x to the latest Sitefinity version / Migration of sitefinity framework 3.7 to 4.2

Migration of sitefinity framework 3.7 to 4.2

3 posts, 0 answered
  1. Suman
    Suman avatar
    3 posts
    18 Aug 2011
    19 Aug 2011
    Link to this post

    We have already done a project on sitefinity using 3.7 framework.Now,we want to convert it into 4.2 framework.We have done the

    a)copied the Migrationservice.svc file to the root of  our website EvolvedMe.

    b)copied the Telerik.Sitefinity.Migration.dll  and Telerik.Sitefinity.MigrationContracts.dll to the /bin folder of website.

    c)Edited the web.config file according to the instructions given in the dashboard of the sitefinity4.2 website.

    d)entered the sitefinity3.7 project URL.

    But after entering the URL a message is showing that the connection is failed.

    Now,Please tell me how can I get out of this problem?

    Thanks & Regards,
  2. Georgi
    Georgi avatar
    3583 posts
    10 Oct 2016
    22 Aug 2011
    Link to this post
    Hello Suman,

    Can you please let us know what the message is? Perhaps it will give us a hint so that we know how to proceed.

    Thanks in advance. 

    the Telerik team

    Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's DevProConnections Awards. We are competing in mind-blowing 20 categories and every vote counts! VOTE for Telerik NOW >>

  3. SelAromDotNet
    SelAromDotNet avatar
    912 posts
    18 Jul 2012
    22 Aug 2011
    Link to this post

    Try accessing the migration service directly on the 3.7 site by going to http://yoursite//MigrationService.svc after you've uploaded the svc file. This should show you an error (if you have CustomErrors off in web.config) if there is a problem with the 3.7 configuration.

    If the page loads correctly (it should look like the attached image) there might be a problem with the 4.2 site communicating with the 3.7 site. In that case, check the error log inside the app_data folder of the 4.2 site for more information.
3 posts, 0 answered