Running the Team Server Configurator should be a straightforward process. That said, you might get stuck and be unable to advance, so here is a list of the most common problems we see:
After installing the product, clicking on the Configure Team Server shortcut does not start the Configurator. It gets stuck Initializing Idera Team Server Configurator.
Cause: Not much is known about the cause of this issue, except that the configureTeamServer.bat files fails to run. On some occasions it is because of a privilege issue.
Steps to Fix This: Use the direct URL to the Configurator page, which follows the next format:
http://:/configurator/login
Assuming that an Oracle database is being used as repository and that everything is properly configured, there are instances where the customer might get ORA-12154 when testing the repository connection.
Cause: One of the requirements TeamServer has for the entries in the tnsnames.ora file for the Oracle client is that the Listener entry needs to be the same as the Service Name as per the following screenshot:
Steps To Fix This: Users will need to make the modification to the tnsnames.ora file manually or using the Oracle Net Configurator.
You are receiving an error message stating that the Keystore password for the certificate is wrong, even though the user is inputting the correct password.
Cause: We have a restriction for SSL certificates where the keystore password must be the same as the certificate password in order for it to work with Team Server.
Steps To Fix This: A new certificate will have to be issued which meets the above requirements of having the passwords match. Here are one way to do it using the CMD and OpenSSL:
1. Open command prompt by running as Administrator
2. Go to Open SSL directory--Extract certificates and key from the .pfx file
3.C:\OpenSSL\bin>openssl.exe pkcs12 -in ideracredentials.pfx -out ideracredentials.pem -nodes -password 123456789 MAC verified OK
4.C:\OpenSSL\bin>openssl pkcs12 -export -in ideracredentials.pem -out connect.keystore -name "etna" Enter Export Password: 12345678 Verifying - Enter Export Password: 12345678
5. Keystore is generated When trying to establish a connection the Repository Database you might get a message that states “Unable to Create database” or that the connection failed.
Cause: The cause of this issue is simple, the Database user connecting to the repository is lacking privileges to be able to create the Database on the MSSQL Server selected. It may also be that the user is trying to connect using Windows Authentication using the local Windows account, in which it will also be required that the account has the Log on as a Service in the Administrative Tools > Local Security Policy > Local Policies > User Rights Assignment menu.
Steps To Fix This: For the first cause, the DBA of the database will have to grant the privilege to the Database User, which can be done with a query similar to this one: GRANT CREATE ANY DATABASE TO LoginName; For the second cause, the System Admin will have to assign the proper policy to the Windows Account running Team Server
For the best possible outcome, please follow our step by step guide to Configure Team Server which can be found in:
Was this article helpful?
