When you remotely display the Solaris Management Console on the Solaris 8 7/01, or 10/01 operating environment, opening a dialog box in the console causes the console, including the open dialog box, to hang.
Workaround: Use the Solaris Management Console on your local system to connect to, and manage, a system running the Solaris 8 7/01, or 10/01, operating environment. Follow these steps.
Close the hung console window.
Start the Solaris Management Console on your local system.
Select Open Toolbox from the console menu.
Click the Server Toolbox tab and select, or enter, the name of the remote system you want to manage.
Click the Open button.
You can now use the console to manage the remote system.
The WBEM HTTP service in the Solaris 8 operating environment does not automatically start. If you want to use HTTP to connect to WBEM, you must manually start the WBEM HTTP service.
Workaround: To manually start the WBEM HTTP service, follow these steps.
Become superuser.
Stop the WBEM server if it is running.
# /etc/init.d/init.wbem stop |
Set your classpath to include the following .jar files.
# CLASSPATH=/usr/sadm/lib/wbem/cimapi.jar:/usr/sadm/lib/xml.jar: \ /usr/sadm/lib/wbem/cimom.jar # export CLASSPATH |
Start the HTTP service.
# java com.sun.wbem.client.HttpService & |
Start the Common Information Model (CIM) Object Manager service.
# /usr/sadm/lib/wbem/wbemconfig & |
If a Solaris provider generates indications and the class name is set to uppercase, the event delivery fails.
Workaround: Use uppercase characters to define indication class names.
If you run the flarcreate command with both the -e and -E options an error is encountered. The following message is displayed.
ERROR: Options -D and -f are mutually exclusive |
The message should read as follows.
ERROR: Options -E and -e are mutually exclusive |
Workaround: Ignore the error message. Do not use the -e and -E options together.
After selecting Help -> Information from the Front Panel, a list of obsolete files is returned. The correct file is S8FCSreleasenotes.
The following error message is displayed when memory is low:
CIM_ERR_LOW_ON_MEMORY |
Workaround: To reset the CIM Object Manager Repository, follow these steps.
Become superuser.
Stop the CIM Object Manager.
# /etc/init.d/init.wbem stop |
Remove the JavaSpaces log directory.
# /bin/rm -rf /var/sadm/wbem/logr |
Restart the CIM Object Manager.
# /etc/init.d/init.wbem start |
You lose any proprietary definitions in your datastore. You must recompile the MOF files that contain those definitions by using the mofcomp command. For example:
# /usr/sadm/bin/mofcomp -u root -p root_password your_mof_file |