Specifications

SpectroSERVER (VNM)
Known SpectroSERVER Anomalies in SPECTRUM 6.5
SPECTRUM Software Release Notice Page 79
Solution: The Alarm Manager receives its alarms from SpectroSERVER’s
landscape. When an attempt is made to connect to the Archive Manager to
get the events associated with the selected alarm, that connection is routed
to the “default service” which is SpectroSERVER. SpectroSERVER
supports the default, but the requests will fail. However, the connection to
the server as the event service (default) is up/established - thus, the
connection dialog shows the green connection to events. The default
service is in place as all service was previously defaulted to
SpectroSERVER.
Problem 4: When you start SpectroSERVER on the Solaris platform and
stop processd then restart processed, the SpectroSERVER does not
reconnect making it impossible for clients to be launched. Although
Control Panel shows a SpectroSERVER is running, when a SpectroGRAPH
is launched you will receive the error message:
Could not find any SpectroSERVERs. The Location Server may
be improperly configured, there may be no SpectroSERVERs, or
the host configuration access privileges may be improperly
configured.
Solution: Avoid stopping processd without first stopping the
SpectroSERVER. This is will be addressed in a future release of
SPECTRUM.