just a quick check, match the assemblies in bin folder and the one referenced in your web.config
The files match and everything is working. The update seems to have gone through. But I'm stil curious if something crucial failed.
Is your application .NET 4? Then you need a special setting. The step that failed is supposed to unescape data in XForms and is run after the actual upgrade, which is why the site might seem fully upgraded. I ran into this myself but had no XForms on the site so I didn't care to do the upgrade again.
More info here: http://world.episerver.com/Blogs/Paul-Smith/Dates1/2011/3/Upgrading-CMS-6-R1-sites-compiled-against-NET-40/
Thats it! I don't use xforms either so I'll skip the step too. Great to know though.
I'm getting the same error message, and we are in fact using XForms. Our site is compiled against .Net 4, so I tried to run Deployment Center using 4.0 as Paul Smith suggested, but I'm still receiving the same error message about being unable to resolve dependencies.
Does anyone have any other suggestions?
I've received this message too, I just wanted to ask if there are repercussions of this further down the line - currently the site doesn't use xforms but it may in the future.. should I roll-back and re-upgrade?
We got this error when having 64-bit ImageVault assemblys in bin. We temporarily replaced them with the 32-bit DLL's during Deployment Center upgrade. The installation then went through without errors.
To answer Steven's question: That part of the upgrade only upgrade existing posts. If you don't have any, then don't sweat it :)
Hi, I get this stack trace when trying the upgrade:
Seems like it is a missing dll, but where and which? The site was started as a cms 6 so there shouldn't be any references to older stuff.