Troubleshooting Web Console issues

• One possible reason could be that you have added a Connect:Server version that IBM Control Center Director does not support.
• Another possible reason could be that this Connect:Direct server is not configured to support IBM Control Center Director.

• See compatibility matrix to find out IBM Connect:Direct versions compatible with IBM Control Center Director. See, Compatibility Matrix.
• Ensure that initparms that are used to automate license metrics collection from Connect:Direct for UNIX/Windows are set.

  See, Configuring IBM Connect:Direct support for Control Center Director.

No value is populated in the Platform, Agent Port, Architecture, and CD Server Installation Location fields under the General tab in Servers > All Servers > View Server Details

• that is not configured properly to relay Connect:Direct Server properties to IBM Control Center Director
• that was added via Web Console
• version that is not supported by IBM Control Center Director

• Ensure that Connect:Direct servers in your deployment are configured to be dynamically discovered by Control Center Director

  See Configuring IBM Connect:Direct support for Control Center Director.

• Install/Upgrade to a Connect:Direct version that supports IBM Control Center Director. For more information see, see Compatibility Matrix.

• Were added via Web Console
• Server composition is not homogenous that is, they are running on different platform or architecture
• Version is not supported by IBM Control Center Director

• Ensure that Connect:Direct servers in your deployment are configured to be dynamically discovered by Control Center Director
• Ensure that server/server groups selected are a homogenous set in terms of platform and architecture
• Install/Upgrade to a CD version that supports IBM Control Center Director. For more information see, see Compatibility Matrix

This is because after an grade the role permissions are set to No Access for these functionality except for the admin role.

• One possible reason could be that upgrade is not supported for servers that are added via IBM Control Center Director Web Console
• Another possible reason could be that scheduling a Job to upgrade a server and/or server group is constrained by the Operating System and package version.
  Expected input for the following fields:

  • Operating System: Should match the OS for servers being upgraded.
  • Package Name: Should be a version higher than the current Connect:Direct server version.

• Select a Package name with a higher/equal package version
• Enter an Operating Server type that matches the Server and/or Server Group being upgraded

• One possible reason could be that the system running IBM Control Center Director is out of sync with the server time.
• Other possible reason could be that because IBM Control Center Director picks scheduling jobs every minute, the Web Console has not displayed refreshed data.

• Ensure that the time on system running ICC Director is in sync with your local time
• ICC Director Engine is up

• One possible reason could be that the package was possibly deleted from the designated directory while the job was still In Progress state
• Another possible reason could be that Agent is down
• Another possible reason could be that the Server for which the upgrade job was scheduled was deleted after the job was scheduled.

• Select another compatible package/Add a compatible package to the designated directory and schedule the job again
• Verify your Agent settings/configuration. For more information see, Configuring IBM Connect:Direct support for Control Center Director.

• View events related to packages in the event log files to isolate the issue.
• One possible reason could be Web Console is not displaying refreshed data. Auto sense feature enables ICC director to detect and process the packages after they are added/removed into the designated directory. It can take up to 15 minutes for the packages to show up under the Deployment view.
• Another possible reason could be that ICC Director was not configured correctly to define the directory where the Connect:Direct packages will be made available for auto-discovery.
• Another possible reason could be that the package name is not in the prescribed standard IBM format as downloaded from Fix Central.
• Another possible reason could be that you might have attempted to add a package that already exists in the designated directory possibly with a different name and/or same content. Packages once added to the designated folder cannot be replaced.

• Administrators, note that auto sense scheduler is configured by default to run every 15 minutes. To change this value, modify package.folderWatchDelayInSecs parameter in application.properties
• See Configuring Control Center Director.
• Go to Fix Central
• Remove the old package first and replace it with the new package.

Installing a new Connect:Direct server returns the following error:

CDAI050E Required parameter not provided: cdai_keystorePassword 

<Error: SPCLI> SPCG770E rc=8 Import error, label: 172.20.186.103 
- The Certificate validity interval has expired.>

Some problem occurred in downloading bundle/package. Look for the cause of failure, open <name.tar> in any editor to get the cause of failure and download the bundle/package again:

• Bundle download solution:
  • Control Center Director node should be up and running.
  • Check the download link is in active state and not archived or deleted.

• Package download solution:
  • If user has Load Balancer, then make sure that all the cluster nodes are using shared path for package. Refer Using RESTful APIs for Web Configurations.
  • Make sure that server.use-forwarded-for-with-proxy is set to true, when using load balancer.
  • Check if the package is available.
  • Make sure all the certificates used are valid.

Error: Attempt to connect to remote node <hostname/IP> failed. FRWL=N

curl: (7) Failed connect to 127.0.0.1:58083; Connection refused

<Error: Invalid admin userid.>

Admin user ID provided does not exist Connect:Direct UNIX.

• Port 1367 must be available.
• Check the /etc/hosts file and make sure if there is no entry like --> ::1 adcenter-01 localhost. If there is an entry, either remove it or comment the line and try installing again.

For more details, refer Customization Worksheet.

After upgrading from previous version Control Center Director to Control Center version 6.2 or later, all users are able to view/edit all Control Center Monitor functionality and can see a restricted user with DVG Manage permission.

• One possible reason could be that the user is trying to login using SEAS credentials. E-mails with account activation/password reset link are only sent if you login with a Control Center Director Account ID.
• Other possible reason could be that as a security consideration ICC Director does not display an error message when an incorrect account ID is entered by the user. The user assumes that the ID was validated, and an e-mail was sent.
• Another possible reason could be that your SMTP server configuration is incorrect.

• Attempt password reset procedure with SEAS ID.
• Attempt password reset procedure with a correct ICC Director ID or contact your administrator.
• See Configuring Control Center Director.

• Verify Certificate-based authentication configuration
• To download error logs for a failed upgrade job, go to: Deployments>All Jobs>View Job details> Click entry next to Failed field to display Failed pop-up>Click download button.

  Extract the log file to view contents. The log file could either be:

  1. A single file that implies failure even before the upgrade started with details.

  2. Multiple log files which implies that upgrade started but encountered an error.

  Look for following primary log file _UpgradeByInstallAgent.log that includes all OSAs sent during the upgrade.

  The last OSA records the upgrade status giving failure details with detailed information on where the error occurred and possible reasons that caused the error to occur.

  For further details on log files specific to Agent Upgrade issues, see _UpgradeAgent_cdaiLog.log.

  For Connect:Direct server upgrade issues, see _Upgrade_cdaiLog.log.

• Login via default super user i.e. admin

• Login by SEAS users i.e. by configuring external authentication server

1. Change property DEFAULT_USER_PASS_ENCRYPTED to false in InstallationInfo.properties file present under directory path //INSTALLATION-DIRECTORY//conf.
2. Access the database and delete the admin user ID from the system. Using given command:

   Delete from CC_USER where NAME =’admin’;

3. Now, simply run the config.bat and set the admin passphrase when “Config step: Default User 'admin' Configuration ...” prompt appears.

For all other databases, the search is case insensitive.

Delete this certificate. Now go to Venafi settings screen on Control Center and correct the Country value to US. Re-trigger the flow for generating Venafi certificate and it should work.

Auto-renewal or manual renewal is failing and the web logs contain below error:

2024-10-22 09:00:00.089 INFO CDRQA-073 — [ool-5-thread-26] s.ServerCertificateAutoRenewJobScheduler : Start certificateAutoRenewalJob1! at:2024-10-22T03:30:00.088873615 2024-10-22 09:00:10.550 ERROR CDRQA-073 — [ool-5-thread-26] c.a.c.a.s.VenafiCAImpl :

Error when connecting Venafi for certificate signing. Exception : {} feign.RetryableException: Connection reset executing GET https://api.venafi.cloud/v1/useraccounts at feign.FeignException.errorExecuting(FeignException.java:213)

When we are trying test connection, we get below error:

Invalid Venafi parameters 2024-07-04 03:51:23.397 ERROR bb477624-5dc3-428b-8df7-d8b291b39c67 CDWLT-045 — [qtp55741515-454] .c.c.a.s.CertificateAuthorityServiceImpl : Venafi authentication failed.

Exception : {} com.venafi.vcert.sdk.VCertException: feign.FeignException$Unauthorized: status 401 reading Cloud#authorize

Venafi certificate signing is failing, and the web logs contain the following error:

2024-07-04 22:08:34.789 ERROR b718049a-b32b-45cd-a8c0-0a885e17e727 CDWLT-045 — [tp55741515-4595] c.i.c.c.a.s.VenafiCAImpl : Error when connecting Venafi for certificate signing. Exception :

{} com.venafi.vcert.sdk.VCertException: status 404 reading Cloud#certificateDetails(String,String):

Unable to find certificate for key b79e1dc0-3a8c-11ef-8537-e59a38d8ac13 at com.venafi.vcert.sdk.VCertException.fromFeignException(VCertException.java:54)

at com.venafi.vcert.sdk.VCertClient.retrieveCertificate(VCertClient.java:219)