Password issue while upgrading to jazz 4
Hi,
We are working on an upgrade from JAZZ 3.0.1.3 to JAZZ 4.0.6.
All preparation seems fine but while executing the upgrade script we get a message that an invalid password is provided while accessing the database.
· We are using CCM anden RQM.
· The database (SQL) is on the same server as the Jazz applications.
· JAZZ 3.0.1.3 works fine
· Access to the database with Microsoft SQL Server Management Studio is OK.
· JRE is upgraded to JRE 7
· sqljdbc4.jar is used
· We tried the upgrade form teh server
· We tried the upgrade from a remothe machine
I think it is a simple issue. Does someone have a possible solution for me?
2 answers
Thanks for the quick reply.
Below the details from the log file of the script showing the details and the script used. The database confirms that the wrong userid or password is provided.
========================================================================================
2014-04-28 09:29:08,003 Repo Tools
2014-04-28 09:29:08,019 java.version=1.6.0
2014-04-28 09:29:08,019 java.runtime.version=pwi3260sr15-20131017_01 (SR15)
2014-04-28 09:29:08,019 Provisioning using "C:\JazzTeamServerv4\server\conf\jts\provision_profiles".
2014-04-28 09:29:08,113 repotools-jts -addTables
2014-04-28 09:29:08,128 Jazz Foundation - Core Libraries, Version 4.0.6 (RJF-I20140130-1407)
2014-04-28 09:29:08,144
To submit questions about issues, go to the Jazz.net forum at https://jazz.net/forum.
To find more information about a message, see the CLM Messages Information Center at
https://jazz.net/help-dev/CLMErrorMessages/index.jsp.
2014-04-28 09:29:08,160 CRJAZ1363I Loading the configuration from "file:conf/jts/teamserver.properties".
2014-04-28 09:29:08,847 CRJAZ1779I This server is configured as a JTS.
2014-04-28 09:29:09,191 CRJAZ2558I Setting the local server rename state to false and the openServerDescriptionServiceTemporarily state to false.
2014-04-28 09:29:11,081 CRJAZ1365I The server is attempting to connect to the following database: "//nsrrepoj01:1433;databaseName=jts;user=xxxxxxxx;password=xxxxxxxx"
2014-04-28 09:29:11,550 CRJAZ2654E The server was unable to connect to the database because the database connection settings are invalid or because database is unreachable (SQLSTATE: S0001, SQLCODE: 18456). Verify the connection settings in your teamserver.properties file. See the Jazz Team Server log for more information.
com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'jtsUser'. ClientConnectionId:acd9a5ba-88b4-4894-b49f-8cb107a2cbbe
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)
at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:254)
at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:84)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:2908)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:2234)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$000(SQLServerConnection.java:41)
at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(SQLServerConnection.java:2220)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1326)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:991)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:827)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:1012)
at com.ibm.team.repository.service.db.provider.AbstractDbProvider.getConnection(AbstractDbProvider.java:203)
Comments
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m6/topic/com.ibm.jazz.install.doc/topics/t_s_server_installation_setup_sql.html
1 vote
Comments
Philippe Chevalier
JAZZ DEVELOPER Apr 28 '14, 11:02 a.m.Invalid password to the database may mean that the teamserver.properties is not providing the right user name and password. Cause: The updates of the configuration files is not being executed and that the process is trying to connect to the database using the default teamserver.properties files, which setup for the default connection to the Derby database, not your SQL server.
Which upgrade script are you executing? and what output did you get when the process executed the upgrade configuration files?