Konica Minolta BIZHUB C30P - Manual (Page 117)

MetaConsole 2.3 including PageScope EMS Plug-Ins
page 103
Toubleshooting Unicenter
To Enable Logging
To help solve problems with MetaConsole for Unicenter, it can be helpful to capture a log of what
the snapin is doing. This is especially the case if Technical Support must be contacted for assis-
tance. To determine what is wrong, Technical Support will require a log from the MetaConsole
Unicenter SnapIn server (on Windows) or the RunUniSnapIn program (on Solaris). To obtain this
log, change the LogToFile option in console.properties (see “Configuration Text Files for
Unicenter” on page 99) from false to true and then stop and restart the MetaConsole server and
the MetaConsole Unicenter SnapIn service/RunUniSnapIn program. (For details, see “Starting and
Stopping the Client” on page 85.) After the client has been running for a few minutes, open the file
console.log using a text editor and see if anything has been logged. Make a copy of this file to
provide to Technical Support. Both console.properties and console.log are in the Uni directory
which is in the installation directory.
Discovered Devices Is Not in the Service Provider’s Submap in 2-D (Windows Only)
To ensure that all devices on the server provider’s submap are visible, right-click the background
of the service provider’s window and, on the Arrange Objects menu that appears, click an ar-
rangement type.
When a device is added to a service provider while the 2-D Map is running, the service provider’s
window is open and there is already a device in the window. For this reason, the new device maybe
placed on top of the existing device icon and the old device may no longer be seen. Resizing the
window, zooming in and out or closing and reopening the window will not reveal the hidden icon.
You must use the Arrange Objects procedure (see above) in order to remedy this situation.
The MetaConsole Devices Icon Is Not in the 2-D Map (Windows Only)
Depending upon your version of Windows, access either the Control Panel or Administrator’s Tools.
From there, verify that the MetaConsole for Unicenter SnapIn service exists and is running. If the
service is missing, uninstalling and reinstalling MetaConsole is the safest way to remedy the prob-
lem. Be sure to explicitly select the MetaConsole for Unicenter SnapIn during installation. If the ser-
vice exists but is not running, stop and restart it.
If the 2-D Map is already up when MetaConsole for Unicenter adds the root MetaConsole object,
the object is not shown nor are any of its subordinate objects. Stop and restart the 2-D Map to view
the root MetaConsole object.
The 2-D Map does not show instances of any classes that are added after the 2-D Map is already
running. If any operation takes place that involves classes while the 2-D Map is running, the 2-D
Map must be stopped and restarted. The 2-D Map should be started after the MetaConsole server
and the MetaConsole Unicenter SnapIn.
If the 2-D Map is run after you stop and restart the MetaConsole server and the MetaConsole
Unicenter SnapIn and the MetaConsole Devices icon still do not appear, obtain a log and contact
Technical Support (see “To Enable Logging” above).
The MetaConsole Devices Node Is Not in the Topology View of Unicenter Explorer (Windows)
Depending upon your version of Windows, access either the Control Panel or Administrator’s Tools.
From there, verify that the MetaConsole for Unicenter SnapIn service exists and is running. If the
service is missing, uninstalling and reinstalling MetaConsole is the safest way to remedy the prob-
lem. Be sure to explicitly select the MetaConsole for Unicenter SnapIn during installation. If the ser-
vice exists but is not running, stop and restart it.