Troubleshooting

Diagnose and resolve common issues with DSClient installation and operation.

---

DSClient cannot connect to CompReg

Connection Issues

Symptoms: Connection refused or timeout errors in DSClient logs

Solutions:

1. Verify CompReg is running: docker ps | grep compreg
2. Check network connectivity between containers
3. Verify RegDsClientHttpCompregHost URL is correct
4. Check firewall rules

---

Authentication errors

Authentication Failures

Symptoms: 401 Unauthorized errors in DSClient logs

Solutions:

1. Verify client credentials match:
   - RegDsClientHttpCompregClientId matches the created client
   - RegDsClientHttpCompregClientSecret matches the created secret
2. Verify user exists in CompReg with correct roles
3. Re-create the client secret if necessary

---

Database connection errors

Database Connectivity

Symptoms: Cannot connect to downstream database

Solutions:

1. Verify database is running and accessible
2. Check RegDSDBUrl is correct

3. Verify database user has required permissions

   • In Oracle systems, users may not have enough privileges. Run the following as SYS to grant the DSClient user the required privileges:

   GRANT CREATE SESSION, CREATE TABLE, CREATE SEQUENCE, CREATE VIEW, CREATE PROCEDURE TO DSDBUser;
   GRANT UNLIMITED TABLESPACE TO DSDBUser;
   

4. Check JDBC driver is available

---

No messages are being processed

Message Processing Issues

Symptoms: DSClient running but no data in downstream database

Solutions:

1. Verify downstream publishing is enabled in CompReg:
   - Check RegDownstreamPublishEnabled=true

2. Create a new registration to trigger message publishing

3. Check CompReg logs for publishing errors