To Troubleshoot Directory Service Control Center Access

If there is any problem accessing Directory Service Control Center, use the following procedure on the host where you installed Directory Service Control Center using native packages.

You must be root to perform this procedure.

1. Verify that Directory Service Control Center has been initialized properly.

   Native Packages:

   root# /opt/SUNWdsee/dscc6/bin/dsccsetup status *** DSCC Application is registered in Sun Java (TM) Web Console *** DSCC Agent is registered in Cacao *** DSCC Registry has been created Path of DSCC registry is /var/opt/SUNWdsee/dscc6/dcc/ads Port of DSCC registry is 3998 ***

   Zip Distribution:

   $ install-path/dscc6/bin/dsccsetup status *** Sun Java (TM) Web Console is not installed *** DSCC Agent is registered in Cacao Cacao uses a custom port number (11168) *** DSCC Registry has been created Path of DSCC registry is /var/opt/SUNWdsee/dscc6/dcc/ads Port of DSCC registry is 3998 ***

   On Windows, run the following command to check the status of DSCC:

   C:\install-path\dscc6\bin>dsccsetup.exe status

   The default installation path for native packages on Solaris operating systems is /opt/SUNWdsee. For the default installation path on your operating system, see Default Paths.

   If you find any initialization problems with DSCC, fix them using the dsccsetup(1M) command.

2. Native packages installation. Check the status of Java Web Console and start using the smcwebserver command if not already running.

   root# /usr/sbin/smcwebserver status Sun Java(TM) Web Console is stopped root# /usr/sbin/smcwebserver start Starting Sun Java(TM) Web Console Version 3.0.2 ... The console is running.

   On Windows, run the following command to check the status of Java Web Console and start, if required.

   C:\install-path\share\webconsole\bin>smcwebserver status C:\install-path\share\webconsole\bin>smcwebserver start

3. If you see errors that pertain to the DSCC agent, check the Common Agent Container.

   The cacaoadm(1M) man page describes the error codes that the command returns. For the exact location of this command on your system, see Command Locations.

   You must run the cacaoadm command as root for native packages installation and as the user who performed the installation for zip installation.

   root# /usr/sbin/cacaoadm status default instance is DISABLED at system startup. Smf monitoring process: 26129 Uptime: 0 day(s), 3:16

   After installing Directory Server, the Common Agent Container starts automatically. However, when you reboot, you might have to start the Common Agent Container manually as follows.

   # cacaoadm start

   On Windows, check the status of Common Agent Container using the following command:

   • Native packages

     C:\install-path\share\cacao_2\bin>cacaoadm status

   • Zip distribution

     C:\install-path\dsee6\cacao_2\bin>cacaoadm status

   For more information about the Common Agent Container, see Sun Java Enterprise System 5 Monitoring Guide.