Specifications

SpectroSERVER (VNM)
Known SpectroSERVER Anomalies in SPECTRUM 6.0.3
SPECTRUM Software Release Notes Page 99
get the events associated with the selected alarm, that connection is routed
to the “default service” which is the SpectroSERVER. The 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 the
SpectroSERVER.
Problem 6: When you attempt to stop the MySQL service on Windows
2000 the service will not stop. This problem is due to a bug in the current
version of MySQL server.
Solution: A fix is in progress and will be made available as soon as it is
developed. As a workaround perform the following:
1. In a bash or DOS shell, navigate to the MySQL binary directory in
$SPECROOT/SS/DDM/mysql/bin.
2. Bring up the Services Manager and attempt to stop the MySQL service.
3. When you see the message in the Service Control popup message box,
“Windows is attempting to stop the following service on <local computer>
MySQL”, type in the bash or DOS shell window the following command:
mysqlshow
4. When a Microsoft Management Console message box appears with the
message, “Could not stop the MySQL service on <local
computer>....” dismiss the message box with the OK button. The
Services Manager window should now indicate that the MySQL service is
no longer running.
Problem 7: 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.