Troubleshooting Duet Client Central Diagnostics (CCD) Issues
On my Duet Client Central Diagnostics (CCD), I talked about the Duet Client Central Diagnostics (CCD) feature and its great advantages. But sometimes you might face issues that prevent you from seeing a user status in the CCD user interface, or the user results will not be updated.
In this blog I’m going to guide you step by step on how to overcome such cases.
To begin with, let’s verify that we covered the basics:
- Are the CCD settings configured correctly?
Browse to http://duethost:port/duet/diag, select the “Test Management” tab and verify that the fields are filled and that there are no error messages.
- Are the tests loaded into the CCD?
In Duet 1.5 SP1 and SP2, each test has a corresponding XML file that needs to be copied to the Tests shared folder. To verify that the tests are configured correctly, check that you see the tests list in the “Test Management” tab:
- Is the CCD client component installed on the Duet client? (In Duet 1.5 SP3 it is installed as part of the Duet client installation.)
- Was the user logged-in to his machine after the CCD installation?
The CCD component will start to run on the client after the user log in. There is also a 15-minute delay before the CCD process starts its actual work.
- Has the CCD task “Update CCD Test Results In DB” been run recently?
This task parses the tests results in the shared folder and stores them into the database. You can check the task status and schedule on the “Scheduled Tasks” tab in the Duet Administration environment (http://duet:port/duet).
In case the problems were not resolved with the steps above, let’s drill down even further on the server configuration to provide other suggestions :
- Check that the user has write permissions to the results shared folder used by the CCD.
- Verify that there is no user limit defined on the shared folder:
- Check that the CCD settings Web service is not failing.
Go to the Web service navigator (http://duet_host:port/wsnavigator), select the CCD_Management*, and test the getCcdManagmentData operation by entering the User ID of the user you don’t see. Verify that the test list is returned as part of the response. If you don’t get the test list in the result, check the J2EE trace logs to understand what went wrong.
* If you don’t see the CCD_Management on the Web services list, select CCD_WS and test the GetCcdSettings operation.
By following the steps I mentioned so far, you should be able to catch the problem. But if you still facing it, this means that something in the client side prevents the results from being updated.
In this case, log in to the client and verify that the SAP.Office.CCD.Scheduler.exe process is running for the user. This process is responsible for executing the tests and sending the results to the server. If the CCD scheduler process is running, the last thing left for you to check is the client’s event viewer log (application logs). Filter for the sources: “Duet CCD Scheduler” and “Duet Client Support Tool” to see the exact error and cause for the problem.