Resolving problems with business cards

If business cards are not displaying user information as expected, first check the server configuration, then the client, and finally, the business cards themselves.

To check the server configuration, verify that the storage repository, such as LDAP used with the Sametime server is configured correctly. A configuration problem is the most likely cause of problems with business cards. For more information, see Setting up business cards.

If the configuration is correct, next verify that the business card information on requested from the clients is working correctly. For this, trace the UserInfo servlet flows to verify that the UserInfo servlet is working correctly. The UserInfo servlet runs on the server retrieves business card information on request from clients and responds to client requests. To determine if there are errors on the exchange of information, enable the UserInfo Debug trace.

If the UserInfo servlet on the server is responding correctly, enable client-side tracing to determine what is happening on the client. Follow the instructions in Logging and tracing on the Sametime Embedded and Connect clients. For Web clients, review the Proxy service logs and capture a browser HTTP Archive (HAR) file to review the business card information received.

Parent topic: Troubleshooting

Enabling the UserInfo Debug trace on Docker

If a debug.env doesn't exist in the directory where the installation package was decompress, you must create it.
Add the following line to the debug.env file.
```
STI__debug__USERINFO_DEBUG_LEVEL=5 
```
Add the debug.env in the community section of the docker_compose.yml file.
Save the file.
Start the Sametime server to apply the changes and enable the trace.
```
docker compose up -d
```

Enabling the UserInfo Debug trace on Kubernetes

Edit the values.yaml file, changing the enableCommunityDebug property from false to true. Save this change.
Edit sameteime-community-logging ConfigMap, and add the following line to the data section.
```
STI__debug__USERINFO_DEBUG_LEVEL: "5"
```
For example:
```
kubectl edit cm sametime-community-logging
```
Apply your changes to the environment.

Verify that you are in the helm directory and run the following command to apply changes. Specify the Sametime deployment name for your environment. The default for Sametime Premium version 12 is sametime.
```
helm upgrade sametime\_deployment\_name .
```
Note: Be sure to include the dot at the end. It is part of the command.

If you are unsure of your deployment name, issue the helm list command to find the name. If you upgraded from an earlier Sametime release, the default name is sametime-meetings.
Restart the pods with the changes. Use the kubectl scale command to scale the pods to zero and then to one that have been changed. You must run the commands for each pod that the change affects.
1. Run the following command to scale the pod to zero.
  
  Scale the pod to zero, where pod_deployment_name is the pod name.
```
kubectl scale deploy pod\_deployment\_name --replicas=0
```
2. Run the following command to scale the pod to one.
```
kubectl scale deploy pod\_deployment\_name --replicas=1
```