Switching Express-C server from Derby to SQLServer
I have installed Rational Team Concert EXPRESS-C in Windows XP SP3 successfully and it is running. Is it possible to switch from the Derby database to another DBMS such as SQLServer, Oracle or DB2?
When I try to re-do the server setup up to use SQLServer I am able to successfully connect to the SQLServer database but Create Tables fails. Here is the error message:
CRJAZ1173I Service "com.ibm.team.repository.service.internal.IDatabaseCreationRestService" is not available.
When I try to re-do the server setup up to use SQLServer I am able to successfully connect to the SQLServer database but Create Tables fails. Here is the error message:
CRJAZ1173I Service "com.ibm.team.repository.service.internal.IDatabaseCreationRestService" is not available.
6 answers
I have installed Rational Team Concert EXPRESS-C in Windows XP SP3 successfully and it is running. Is it possible to switch from the Derby database to another DBMS such as SQLServer, Oracle or DB2?
When I try to re-do the server setup up to use SQLServer I am able to successfully connect to the SQLServer database but Create Tables fails. Here is the error message:
CRJAZ1173I Service "com.ibm.team.repository.service.internal.IDatabaseCreationRestService" is not available.
Hi
Have you followed all the steps to use SQLServer? Once that works (and apologies if that is what you did and you get the error message), you should be able use repotools to move your existing database to SQLServer.
Also - check your Express-C version number. 2.0.0.2 definitely supports SQLServer, 1.x did not.
anthony
Have you followed all the steps to use SQLServer? Once that works (and apologies if that is what you did and you get the error message), you should be able use repotools to move your existing database to SQLServer.
Also - check your Express-C version number. 2.0.0.2 definitely supports SQLServer, 1.x did not.
anthony
I followed all the steps and the setup page connects to SQLServer successfully (when you try the Test button). I also tried to use repotools --createTables from the command line and got the same errors. I am using the latest RTC version 2.0.0.2. I also tried the regular EXPRESS download and got the same errors.
Have you followed all the steps to use SQLServer? Once that works (and apologies if that is what you did and you get the error message), you should be able use repotools to move your existing database to SQLServer.
Also - check your Express-C version number. 2.0.0.2 definitely supports SQLServer, 1.x did not.
anthony
I followed all the steps and the setup page connects to SQLServer successfully (when you try the Test button). I also tried to use repotools --createTables from the command line and got the same errors. I am using the latest RTC version 2.0.0.2. I also tried the regular EXPRESS download and got the same errors.
Hmm - so one more obvious check - what version of SQLServer are you using. If this is a supported version, then I am not sure why this is happening. If no one else has any good ideas, I suggest you raise a defect here on jazz.net.
Apologies I did not have a quick answer for you.
anthony
Have you followed all the steps to use SQLServer? Once that works (and apologies if that is what you did and you get the error message), you should be able use repotools to move your existing database to SQLServer.
Also - check your Express-C version number. 2.0.0.2 definitely supports SQLServer, 1.x did not.
anthony
I followed all the steps and the setup page connects to SQLServer successfully (when you try the Test button). I also tried to use repotools --createTables from the command line and got the same errors. I am using the latest RTC version 2.0.0.2. I also tried the regular EXPRESS download and got the same errors.
Hmm - so one more obvious check - what version of SQLServer are you using. If this is a supported version, then I am not sure why this is happening. If no one else has any good ideas, I suggest you raise a defect here on jazz.net.
Apologies I did not have a quick answer for you.
anthony
I am using SQL Server 2005 Express. I was thinking this may be a licensing limitation with EXPRESS-C, but it appears that is not the case