Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
AI OnAI Off
Migration problems, error in table name?
I searched all the stored procedures of both databases and there is no reference to tblPagetype without capital T in neither the source nor the destination database.
#26287
Dec 01, 2008 13:46
Seems to be a bug when form properties are validated, can't find it lowercased elsewhere in the code. I'll report it.
The obvious, but the most work, is to switch to a case-insensitive database. But, you may want to try to add a view named tblPagetype that basically does a SELECT * FROM tblPageType, that could work.
Dec 01, 2008 15:03
It's a bug in the migration tool, not in any of the EPiServer versions?
I tried to add the tblPagetype view, but then I had the same problem with tblPageTypeDefinition. After adding another view it starts to complain about column names instead: property, pkid, description. All lower case. I can not find any reference to the misspelled table in the database, the lowercase pkid is however used in the stored procedures editFormPostingList, usrKeywordFind, usrFindPersonalizedProperty and editSaveKeyword.
I suppose I can't do very much but to move the data to a case-insensitive database? Or when can I expect the bug to be fixed?
Dec 02, 2008 6:38
Yes, I suggest that you move over the database to a case-insenstive database for now. Its a bug in the Migration Tool.
Dec 02, 2008 9:30
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
In the first step of migrating a site from 4.62 to 5R2 i get this error:
Validation of the configuration files failed. General errors: Validation failed: Invalid object name 'tblPagetype'
I notice that the table is actually called tblPageType (with capital T), could this be the problem? Where does the migration tool find the faulty table name?