London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!

smithsson68@gmail.com
Apr 11, 2012
  11233
(8 votes)

Problems with XForms when upgrading to CMS 6 R2

It seems that many people have had problems when upgrading an EPiServer CMS site to 6 R2 with the last part of the upgrade script.

What this tries to do is read all the XForm definitions from the database, perform a html decode on the form name, and then save the definition back to the database. Why this has to be done is not relevant to this post.

What is relevant is that it often doesn’t work for various reasons. This part of the script is run in a separate transaction after the main upgrade transaction has completed. The reason for this is that it has to run in a separate application domain in the context of the website.

If your site doesn’t use XForms or if you know that there aren’t any forms that have names that required html encoding then you can just ignore this error. As mentioned above, the main upgrade has been committed and your site should be ready to go.

If however you do need to run this part of the script and it keeps failing then there is a simple workaround.

Here you will find an ASPX file which contains the same code as the script executes. Place it in your site, execute it (i.e. browse to it’s Url) and it will do the business. When it’s finished it will tell you how many XForms it’s upgraded. If for some reason it should fail or get interrupted, it is safe to run again as it will only upgrade those XForms that need it.

When all is done you can just remove the ASPX from the site.

Voilà

Apr 11, 2012

Comments

Apr 11, 2012 04:02 PM

Great stuff Paul, now we can upgrade databases without having to use EPiServer Deployment Centre - if you know where the SQL upgrade scripts are of course ;)

Dec 9, 2013 12:23 PM

Hello Paul,

The link you provided for your script does not work. Can you please update the link?

Thank you!

Jun 13, 2014 11:38 AM

Please update the link

Jun 17, 2014 02:50 PM

Hi
Could you please update the link?

thanks!

//Pawel

Nitin Walawalkar
Nitin Walawalkar Jul 11, 2014 01:46 PM

I am unable to download the aspx page from the link

Please login to comment.
Latest blogs
Natural Language Q&A in Optimizely CMS Using Azure OpenAI and AI Search

In Part 2, we integrated Azure AI Search with Azure Personalizer to build a smarter, user-focused experience in Optimizely CMS. We used ServiceAPI ...

Naveed Ul-Haq | Apr 25, 2025 |

Identifying Spike Requests and Issues in Application Insights

Sometimes within the DXP we see specific Azure App Instances having request spikes causing performance degredation and we need to investigate. I fi...

Scott Reed | Apr 25, 2025

Optimizely Frontend Hosting Beta – Early Thoughts and Key Questions

Optimizely has opened the waitlist for its new Frontend Hosting capability. I’m part of the beta programme, but my invite isn’t due until May, whil...

Minesh Shah (Netcel) | Apr 23, 2025

Developer Meetup - London, 21st May 2025

The London Dev Meetup has been rescheduled for Wednesday, 21st May and will be Candyspace 's first Optimizely Developer Meetup, and the first one...

Gavin_M | Apr 22, 2025

Frontend hosting for PaaS & SaaS CMS

Just announced on the DXP, we FINALLY have a front end hosting solution coming as part of the DXP for modern decoupled solutions in both the PaaS a...

Scott Reed | Apr 22, 2025

Routing to a page in SaaS CMS

More early findings from using a SaaS CMS instance; setting up Graph queries that works for both visitor pageviews and editor previews.

Johan Kronberg | Apr 14, 2025 |