November Happy Hour will be moved to Thursday December 5th.

CMS 4.62 to CMS 5 Migration Tool Error : Object reference not set to an instance of an object.

Vote:
 

Managed to overcome a NUMBER of other errors thrown up by the migration tool but stumped on this one..

 

Seems to fall over when converting DynamicProperties?. What is the best way to debug this?

 

[16/02/2010 08:36:26][Error] Failed to convert links, reason:Object reference not set to an instance of an object.
   at EPiServer.DataAccess.DynamicPropertiesDB.LoadTree()
   at EPiServer.DataAbstraction.DynamicProperty.ListTree()
   at EPiServer.Migration.ConvertLinks.UpdateDynamicProperties()
   at EPiServer.Migration.ConvertLinks.StartConverting()
[16/02/2010 08:36:26][Warning] Failed to convert links therefore migration is stopped. Check that target site is running and then run migration tool again and choose continue existing process
[16/02/2010 08:36:26][Information] Migration stop requested
[16/02/2010 08:36:26][Warning] Some pages failed during migration. See C:\EPiServer\Sites\TemporarySite\MigrateLinksErrors.txt for detailed information
[16/02/2010 08:36:26][Information] Migration stopped


Object reference not set to an instance of an object.
   at EPiServer.DataAccess.DynamicPropertiesDB.LoadTree()
   at EPiServer.DataAbstraction.DynamicProperty.ListTree()
   at EPiServer.Migration.ConvertLinks.UpdateDynamicProperties()
   at EPiServer.Migration.ConvertLinks.StartConverting()

 

-- Lee

#36983
Feb 16, 2010 10:24
Vote:
 

Can you check that your CMS 5 site is running without any errors?

#36985
Feb 16, 2010 12:02
Vote:
 

Yes

#36986
Feb 16, 2010 12:30
Vote:
 

Both the old CMS 4 site and the new CMS 5 site work fine before the migration process..

#36997
Feb 16, 2010 16:11
Vote:
 

Do you have any dynamic properties of a custom property type? If yes, do you get a succesfull migration if you remove them?

#37009
Feb 16, 2010 22:44
Vote:
 

I will try this later, cheers

#37023
Feb 17, 2010 11:47
Vote:
 

Cheers Frederik.

Removing any DynamicProperties whose types were CustomProperties then retrying the migration tool worked for me!

Thanks.

-- Lee

#37073
Feb 19, 2010 10:09
Vote:
 

I usually create library project(s) that contains classes for all custom properties registered in the EPiServer 4 site and add it to the bin folder for the EPiServer 5 site before migration.

The only thing the class need to do is to inherit from the correct base class to get the right data type. It must of course has the same namespace and class name and the assembly name must also match.

The benefit from this extra work is that it prevents the Migration Tool from createing renamed dummy properties for you (that you have to rename manually later).

It could possibly also work to solve this problem too.

#37100
Feb 19, 2010 19:28
Vote:
 

So if you just use the same assembly name, namespace, class, and type, the migration tool will use that as the property type for custom properties?

#37105
Feb 19, 2010 22:54
Vote:
 

Yes, the migration tool checks first if custom properties are available on the target site and if not creates dummy custom properties and change the assembly and class name in the database to match the generated code.

#37107
Feb 19, 2010 23:02
Vote:
 

Very cool! Wish I'd known that before.. Learn something new every day! Thanks for sharing Fredrik! :).

#37108
Feb 19, 2010 23:03
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.