I have upgraded our environment to RC Server 10.0.0.0618 and it has work well in 50% or our environment. Unfortunately, those servers where it did upgrade, the setting were not kept. On these servers, I had to uninstall RC and reinstall .0618 version. After installation, I am able to configure the LDAP, common.properties, trc.properties, user groups, target groups and create a token with no issues. The only thing is that they linking between the Target Group and the User Group keeps coming undone. I reset it and a few minutes later, it comes undone again.
Is there anything that I need to do in order to keep this linking active to get these servers up and running and functioning properly?
In the meantime, since they are VM’s I had to restore the servers to a previous date. Any assistance will be greatly appreciated.
About the upgrade you didn’t mention how you performed it. From your description it seems like that the upgrade turned to a fresh install. This is what happens when you perform the upgrade in a not supported way. Note that the upgrade is still not supported in silent mode and the console/command-line mode is disabled so you can’t even use the Server wizard on the BESConsole. You need to manually download the server installer (maybe using the Fixlet 90 or 91 of the RC site depending on the OS) and manually run it from the graphical session.
About the group issue it seems like you are using local user group instead of the LDAP one. When an LDAP synchronization is run all the local group and users created on the RC server will be deleted and the related links with Target groups will be reset too. So make sure that you are using LDAP groups to create links with Target groups. Also validate the LDAP configuration with the LDAP Wizard (Admin -> LDAP Configuration Utility) and make sure that all the wanted groups are shown in the Group search box.
The way I performed the upgrade was manually by downloading the trc_server_setup.exe. Once downloaded on the RC server, I run the exe as an administrator. The exe run through it’s process like it does when it is a fresh install and upgrades it. When the upgrade completes, I run through the process to ensure all the configurations are set and that is when the problems begin.
Our environment is set up via LDAP and not local ID’s. I am aware that when LDAP is setup and syncs, it will wipe out all the local id’s created. The local ID’s would remain if there was no LDAP server set.
So after the upgrade, I verify the configs. First step, is to check that the LDAP settings are set. When I go to the setup, the alternate server connection is missing. I add it again and click on Test Connection. Sometimes the test is successful and others, it fails. When I test the Group 2 connections, it fails on those where the LDAP connection works. No matter what I do, I cannot get the LDAP server connections to work. That is when I proceed to uninstall RC, reboot and reinstall.
Upon reinstallation, I proceed to setup all the configs, to include LDAP. Once the setup is complete and I link the Target Base to the User Base, after sometime, it looses that link.
As mentioned, the upgrade worked on 50% or our environment. It is that bottom 50% I need to fix. Since these are VM’s I have had to revert those servers back two weeks so that they are able to use the old 9.1.4.0612 version.
By the way, I have a support ticket in already but they were not able to figure this out. They want me to recreate the issue but I cannot afford to bring down another environment.
This is strange. This might be caused by a corrupted ldap.properties file.
Do you have the Connection password encrypted or in clear text ?
Other customers reported that if the password is not encrypted and contains some specific special characters then this may lead to a file corruption during an upgrade.
If the LDAP configuration is not working after the upgrade probably the already imported user groups contained in the database are not in sync with the LDAP server and probably the RC server detect these as “local” groups. This may lead to a deletition of some links between User groups and Target groups.
There are currently no known problem for upgrades from version 9.1.4.0612.
The strangest thing is that it work on half of our environment. Even taking the files from a working server, modifying them and copying the over does not work.
Yes, the ldap password is encrypted.
I get that the configuration contained in the db is not in sync but when I uninstall the RC and reinstall it (10.0.0.0618 version) it still occurs. That is the intriguing part. Maybe the issue is .0618 (or .0518 which I tried as well).
The strangest thing is that it work on half of our environment. Even taking the files from a working server, modifying them and copying the over does not work.
Note that it’s not recommended to copy the properties files from an old version to a newer one. The new versions may introduce new property and changes in the default values. So you can reuse the same properties file only as reference or to reinstall the same version of RC server.
Also if you reinstall the server the encrypted properties values like the Connection Password won’t be decrypted correctly because the encryption key has changed. In this case you need to blank such properties before the reuse of the file. This is not need of course in case you perform an upgrade.
I get that the configuration contained in the db is not in sync but when I uninstall the RC and reinstall it (10.0.0.0618 version) it still occurs. That is the intriguing part. Maybe the issue is .0618 (or .0518 which I tried as well)
When you reinstalled the RC server did you reconfigure the LDAP properties and related synchronization ? Is the connection test working ? Are you using LDAPS ?
I understand the copy and paste is not best practice but it is what I was asked to do by support on the ticket I submitted. I tried this on the a clean server where I backed them up and also copied them to a different server. Prior to doing so, I edited the property files before copying the over to the different server.
After installation .0618, after uninstalling first, of course I reconfigure the ldap setting. This has to be done in order for me to be able to see and lync the Target Group to the User Group. Otherwise, I would not be able to see the User Group.
I understand the copy and paste is not best practice but it is what I was asked to do by support on the ticket I submitted. I tried this on the a clean server where I backed them up and also copied them to a different server. Prior to doing so, I edited the property files before copying the over to the different server.
As I said it’s ok if you perform the copy of the files on a RC server installation of the same version. Of course you need to pay attention to the encrypted properties and all the properties which are specific of the installation like hostnames, URL etc …
This is also stated in the linked doc :
When you complete the upgrade verify that the new version is installed, manually edit the new properties files. Update the values with the values that are in your backed up properties files. Restore your recording files and certificates if applicable
As I said this is not normally needed if the upgrade is performed. Maybe if you migrate a server or you have some special settings like SSO but this is not something which need to be done normally. In your case is the upgrade problem which forced you to do so. So this bring us to your main problem which is the upgrade.
After installation .0618, after uninstalling first, of course I reconfigure the ldap setting. This has to be done in order for me to be able to see and lync the Target Group to the User Group. Otherwise, I would not be able to see the User Group.
This is a second problem and you need to provide the installation log along with the RC server log to the support team once you reproduced the problem otherwise they can’t do much without further information. Having a remote and showing the problem while is reproducible would also help.