Problem upgrading from 2.14 to 2.53: KeyError: _Real

I have tried repeatedly to upgrade a Plone site (2.14, Zope
2.87, Python 2.35,
Windows XP) to Plone 2.52 or 2.53 running in a completely
separate Zope
installation, by dropping in Data.fs.

After migration attempt I get the error KeyError: '_real'
(see traceback below).
It also appears in the ZMI left-hand column!

Do I need to "clean" the Data.fs somehow? 

Thanks for any help.

Dan

________

Exception traceback

Time 	2007/07/25 19:29:42.734 GMT-7
User Name (User Id) 	dan (dan)
Request URL 	
http://localhost:8080/Plone/portal_migration/upgrade
Exception Type 	KeyError
Exception Value 	'_real'

Traceback (innermost last):

    * Module
Products.CMFQuickInstallerTool.QuickInstallerTool, line 322,
in
	installProduct
      __traceback_info__: ('PlonePAS',)
    * Module Products.ExternalMethod.ExternalMethod, line
225, in __call__
      __traceback_info__: ((<PloneSite at /Plone>,),
{}, None)
    * Module C:Program FilesPlone
2DataProductsPlonePASExtensions
	Install.py, line 846, in install
    * Module C:Program FilesPlone
2DataProductsPlonePASExtensions
	Install.py, line 701, in migrate_root_uf
    * Module
Products.PluggableAuthService.Extensions.upgrade, line 202,
in 
	replace_acl_users
    * Module
Products.PluggableAuthService.Extensions.upgrade, line 194,
in 
	_upgradeLocalRoleAssignments
    * Module
Products.PluggableAuthService.Extensions.upgrade, line 186,
in 
	descend
    * Module
Products.PluggableAuthService.Extensions.upgrade, line 186,
in 
	descend
    * Module
Products.PluggableAuthService.Extensions.upgrade, line 146,
in 
	descend
    * Module ZODB.Connection, line 732, in setstate
    * Module ZODB.Connection, line 786, in _setstate
    * Module ZODB.serialize, line 604, in setGhostState
    * Module ZODB.serialize, line 597, in getState
    * Module ZODB.serialize, line 469, in _persistent_load
    * Module ZODB.serialize, line 506, in load_persistent
    * Module Products.CMFCore.DirectoryView, line 458, in
__setattr__

KeyError: '_real'





_______________________________________________
Setup mailing list
Setuplists.plone.org
http://
lists.plone.org/mailman/listinfo/setup

Dan Thomas wrote:
> I have tried repeatedly to upgrade a Plone site (2.14,
Zope 2.87, Python 2.35,
> Windows XP) to Plone 2.52 or 2.53 running in a
completely separate Zope
> installation, by dropping in Data.fs.
> 
> After migration attempt I get the error KeyError:
'_real' (see traceback below).
> It also appears in the ZMI left-hand column!
> 
> Do I need to "clean" the Data.fs somehow? 
> 
> Thanks for any help.
> 
> Dan

Dan,
   Not sure when you mean this happened- during, or after,
migration 
attempt. If the migration itself failed, all bets are off
about what 
will get served when attempting to look at the site AFTER
that.

To make progress here's some ideas:

Before attempting portal_migration, make sure nothing is
broken in ZMI.

Are all 3rd-party products in the new site compatible with
Plone 2.5.3? 
Get the new versions if required, before attempting
migration.

Before attempting portal_migration make sure you don't have
"rogue 
customisations" floating around. Any customised
versions of old versions 
of templates,scripts etc can cause problems, so you have to
compare 
everything you've customised and re-apply customisations
where 
necessary. This kind of audit is essential when migrating.

As for "cleaning the Data.fs", well you could
first do a catalog clear 
and rebuild from ZMI->portal_catalog->Advanced. This
wouldn't hurt, and 
while it takes a while to run, helps in certain
circumstances.

Regards,
Nick


-- 
Nick Davis
Web Application Developer
University of Leicester
http://www2.le.ac.uk


_______________________________________________
Setup mailing list
Setuplists.plone.org
http://
lists.plone.org/mailman/listinfo/setup

Many thanks to Nick for a thoughtful reply. As it turned out
a PloneCal
folder (empty!) was the culprit. I discovered it by
exporting each Plone
instance from 2.14 and importing into Plone 2.53 in turn,
and one of them
generated the same '_real' error as the migration attempt
had. Then I
imported content folders from that one instance, and again
got the error on
one folder. Then took a guess that PloneCal in that folder
was the cause,
and after confirming it with yet another import, deleted the
folder from
Plone 2.14, and a normal migration could proceed. A bit
tedious, but it
revealed the defective content. 

Dan


Nick Davis-3 wrote:
> 
> Dan Thomas wrote:
>> 
>> After migration attempt I get the error KeyError:
'_real' 
>> It also appears in the ZMI left-hand column!
>> 
> 
> To make progress here's some ideas:
> 
> Before attempting portal_migration, make sure nothing
is broken in ZMI.
> 
> Are all 3rd-party products in the new site compatible
with Plone 2.5.3? 
> Get the new versions if required, before attempting
migration.
> 
> Before attempting portal_migration make sure you don't
have "rogue 
> customisations" floating around. Any customised
versions of old versions 
> of templates,scripts etc can cause problems, so you
have to compare 
> everything you've customised and re-apply
customisations where 
> necessary. This kind of audit is essential when
migrating.
> 
> As for "cleaning the Data.fs", well you could
first do a catalog clear 
> and rebuild from ZMI->portal_catalog->Advanced.
This wouldn't hurt, and 
> while it takes a while to run, helps in certain
circumstances.
> 
> 

-- 
View this message in context: htt
p://www.nabble.com/Problem-upgrading-from-2.14-to-2.53%3A-Ke
yError%3A-_Real-tf4149114s15482.html#a12011023
Sent from the Installation, Setup, Upgrades mailing list
archive at Nabble.com.


_______________________________________________
Setup mailing list
Setuplists.plone.org
http://
lists.plone.org/mailman/listinfo/setup