Konica Minolta BIZHUB C30P - Manual (Page 118)

Configuring MetaConsole
page 104
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 (Solaris)
Determine if the RunUniSnapIn program is running by using the ps command. If it is running, stop
it and restart it. For details, see “Starting and Stopping the Client” on page 85.
If it is not running, change directories to the Uni directory (located in the MetaConsole directory)
and type ./RunInoSnapIn. If there is no Uni directory or the program is not in the directory, unin-
stalling and reinstalling MetaConsole is the safest way to remedy the problem. Be sure to explicitly
select the MetaConsole for Unicenter SnapIn during installation. If, after running the program from
the command line, the process still does not show up, obtain a log and contact Technical Support
(see “To Enable Logging” above).
If the Unicenter Explorer is run after you stop and restart the MetaConsole server and the RunUni-
SnapIn program and the MetaConsole Devices node still do not appear in the Topology view,
obtain a log and contact Technical Support (see “To Enable Logging” above).
The Wrong Icons Appear for Nodes in the Topology View of Unicenter Explorer
If Unicenter Explorer is already running when the snapin is started, the default icons many show for
some MetaConsole nodes. Topping and restarting Unicenter Explorer may correct this.
Old MetaConsole Classes or Objects Exist
If you upgrade from an earlier version of MetaConsole for unicenter, you should uninstall the old
version of MetaConsole first then recreate the repository before installing the new version of Meta-
Console. Ordinarily, uninstalling MetaConsole removes the old MetaConsole classes and objects
from the repository, but recreating the repository guarantees that no old classes or objects, that
might cause a conflict, remain.
The Browser Fails to Run for “Configure” or “Show Device Details” Menu Items
The Configuration and Show Service Details menu items are acted upon by launching a web
browser with the appropriate URL. This is implemented by calling a script file called launchurl.bat.
This script file is installed where it can be found on the path. On windows, the script file is a batch
file that runs a program called rundll32.exe to call a function in a DLL call url.dll. This call starts
the default browser if it is not running and passes the URL to the default browser. On Solaris, the
script file assumes that the browser is compatible with Netscape 6.2.3. It looks to see if a process
is running that includes the text “netscape” and if there is one it uses the “-remote” command line
option supported by newer versions of Netscape. If there is not such a process, then the script starts
netscape. In both cases, it assumes that Netscape can be run by calling the version of netscape
found first on the path. If these assumptions are not correct, then the launcurl.bat script needs to
be changed to adapt. Of course, care must be taken in changing the script file, though no copied
code should need to change.