Episerver Migration 4.62 to CMS5 r2 on SQL Server 2008

I wish that I had great things to say regarding running a migration using SQL Server 2008 but I don’t.

Strike One: I couldn’t run a simple EPiServer CMS5 installation to the sql server. I kept getting this error:

Error – User ’dbo’ does not have permission to run DBCC TRACEON

After some searching I came to the conclussion that the only thing one could do to override this is to give my user sysadmin rights. Something that not many customers fancy giving away.  But it did actually work and the insallation was successful.

Strike Two: With a fresh epi5 site installed and my original site upgraded to 4.62b and ready to rock, I started to run the migration tool. The Result? ”Migrating Data…” And nothing else. It didn’t really start the job and just died there. I even gaved it 12 hours (over the night) and nothing happened. I still had sysadmin rights so that wasn’t it.

Strike Three: With not much patience left I tried to do a workaround, i.e to backup the Databases and restored them on a 2005 machine, then do the migration and then back to the 2008 machine. The problem is that SQL Server doesn’t have backward compatibility 🙁

So basicly I’m going to reproduce everything on the 2005 machine and work from that one. Once done, I’ll do a backup and then restore that to the sql server 2008 and have the final product running on that one. Not the best solution.

I’ve a case open @ EPiServer and who knows, maybe they have a solution for this. I’ll be sure to post it once I get it.

*EDIT*
Well, once I was doing all the work on the SQL Server 2005 machine, I encountered an error doing the migration itself. It was complaining about DTC transactions. Then it hit me, that the same thing might be whats wrong with the migration to the SQL Server2008. So I added the following settings and voilá! it worked!

I did notice that they had info about this on their Migration tool info page but the error itself never came up when doing the migration, except when I tried to run it against SQL Server 2005.

Hope this helps someone out 😛

5 kommentarer

  1. I’m on a migration process right now and I got some similar problems as you describe. The migration was from version 4.60 to 5.2. I got problems through all steps. First off, upgrading from 4.60 to 4.62B which on every attempt hanged sql server 2005 causing an automatic reboot. Finally,I fixed this by running all sql conversion scripts manuallt on my local dev machine and then restoring it back on the server (where my migration sites resided).

    Everything fine.. till next breath. Migration tool running fine but suddenly stops, times out into a nice latch 4 sql exception and sql server 2005 stops responding with locked up databases. All this causing another fine deep dive into log analysis and google fishing. After some headache trying to find a solution I backed up the ******* database, moving it to dev machine again.

    My strategy now was to run the migration tool on the server but converting the database remote on my dev machine. I ran the tool and it looked really good this time. Just some steps further .. till .. MSDTC exception running wild. Well, after some time resolving the issue using DTSPing after enabling MSDTC transaction on both machines I was still without luck. And then it hit me. My sql connection string was set up with my dev machine IP adress as source. But after some (many) thoughts I realized that instead of using this IP as endpoint, the MSDTC handling was looking up my dev machine NETBIOS name. Pinging this name from my server showed that dns wasnt synced correctly. A fine ipconfig /flushdns took place .. and OH YEAH! Migration Tool runs across all steps and FINALLY: Migration Complete.

    Well, nice experience and now there’s some bad ass code migration in progress 😉

    Happy migration y’all!

    (Ps. Dont know yet why the server always hanged during these steps because of some latch-4 exceptions)

  2. thats quite a trip mate! 🙂 crazy that it was using the NETBIOS name. Let me know how the rest of the migration works out for you.

  3. hello!,I really like your writing so much! share we keep up a correspondence extra approximately your article on AOL? I need a specialist on this space to solve my problem. Maybe that’s you! Having a look ahead to look you.

Lämna ett svar

Denna webbplats använder Akismet för att minska skräppost. Lär dig hur din kommentardata bearbetas.