Jump to content

Database migration to SQL-Server 2008 R2


rblock

Recommended Posts

Hi,

 

I wanted to migrate from the build in SQL-Server CE version to SQL-Server 2008 R2. I set up a new special user for it and started the migration but I got an error and in the log file there is "Tcp transport error". Even if I use "sa" as user, the test shows me an o.k. but the migration fails. The error dialog shows the following.

 

The database {0} can't be created. Check the server log (plastic.server.log). Error: {1}   bei
Codice.CM.Data.BaseDataManager.ExecuteCreateDatabaseScript(String databaseName, String contentResourceName)
   bei Codice.CM.Data.BaseDataManager.CreateRepositoriesData()
   bei admintool.RepositoriesDatabaseCopier.CreateDestinationDb()
   bei admintool.DatabaseCopier.Start()
   bei admintool.DatabaseMigrator.MigrateDatabases()
   bei admintool.DatabaseMigrator.Start()

Does anybody knows what the problem here is?

 

Asking greetings

 

Reiner

 

Link to comment
Share on other sites

Hello,

 

Can you check if you can connect with same credentials using SQL Management Studio tool?.  Is your SQL Server in your same machine? 

A user reported a migration problem that was fixed indicating the path (http://www.plasticscm.net/index.php?/topic/1190-migrate-back-end-to-sql-server-2012/?hl=migration).

Can you indicate the path an also a prefix or suffix and check if it works?

 

Regards,

Carlos

Link to comment
Share on other sites

Hi Carlos,

 

the hints in the other thread didn't help. It was the latter one U wrote. I'd to give the path to the database directory, explicitly. At this system I use I'd this move to a folder on drive D: because I didn't want it on the system drive as it is suggested during installation of SQL-Server. At the moment the migration is running and I hope it will work afterwards. ;)

 

Hopefull greetings

 

Reiner

 

Link to comment
Share on other sites

Hi,

 

o.k. or better not o.k. I got a Migration failed error dialog.

 

It seems that it has problems with my rep_12 because at the moment I try to delete this db inside of SQL Server Management Studio and it has problems to delete it, too.

 

Is there any possibility to check and repair a rep?

 

 

Asking greetings

 

Reiner

Link to comment
Share on other sites

Hi Manuel,

 

lrep shows the following.

 

C:\Users\Administrator>cm lrep localhost:8087
 11 DokumentsPrivateS localhost:8087
 2 Softelier localhost:8087
 12 DocumentsPrivateO localhost:8087
 13 DocumentsBusinessO localhost:8087
 14 Siemens localhost:8087
 18 Tintschl localhost:8087
 19 Dokumentvorlagen localhost:8087
 21 DocumentsBusinessS localhost:8087
 22 Learning localhost:8087
 23 itms localhost:8087
 24 PMSERVICES localhost:8087

So it seems that rep_12 is DocumentsPrivateO and it is used.

 

Investigating greetings

 

Reiner

Link to comment
Share on other sites

Hi,

 

o.k. I found it. It was because the server has just 150 GB at drive D: and I missed to clean up unnecessary old files like backups. So the migration run out of space. I now cleaned it up during the migrations and it finished successfully. :rolleyes: 

 

 

Successful greetings

 

Reiner

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...