HP StorageWorks Fabric Manager 5.x Administrator Guide (AA-RUQSF-TE, September 2005)

242 Troubleshooting
Stopping the Fabric Manager server on Solaris
Included in the Fabric Manager installation are scripts for starting and stopping the Fabric Manager
server. Normally you do not need to use these scripts, because the server starts automatically. However, for
troubleshooting you might need to stop and restart the server. To do this, change directory to
<FM_HOME>/server/bin and run ./s99fabman stop or ./s99fabman start.
Do not use the other scripts in this directory, such as stopFabricManagerServer.sh,
startFabricManagerServer.sh, and restartFabricManagerServer.sh; they are intended
for internal use only.
Changing printers in Fabric Manager
If you have multiple printers configured, selecting a non-default printer on the page setup dialog box in
Fabric Manager might crash the Fabric Manager client when you click OK. This occurs rarely on some
Windows hosts. To prevent the Fabric Manager client from crashing, do not change the printer from the
page setup dialog box. Either change the printer from the print dialog box or change the default printer in
Windows, and then close and relaunch the Fabric Manager client. Then print the selected views.
Changing the time in Fabric Manager
When running Fabric Manager server and client on the same or different machines, if the host time is
changed by a minute, the client and server ceases to communicate properly. They continue to
communicate, but not correctly. If the Fabric Manager client was open when the time was changed on the
host, then when the client is closed, no data is persistent in the server and a dialog box opens asking
whether you want to close the client without saving. The client and server are having a problem
communicating.
This communication problem can happen for multiple reasons; one common reason occurs when the host’s
time was being updated by an NTP server, then the host’s time could change from time to time. When the
system time is advanced on some Windows Platforms, the Fabric Manager server restarts. When this
happens, all the Fabric Manager clients close connection to the Fabric Manager server and must be
restarted as well. This is a fast restart, so normally, no damage occurs. However, if performance monitoring
is scheduled to run then, a round of data collection might be lost. Also, the clients have to be reconnected.
Normally, this happens only twice a year when time has to be advanced or decreased for the beginning
or end of daylight savings time.
Not enough system resources error
If the Excel window is minimized when the physical inventory report is being generated, a Not enough
system resources to display completely error occurs, and sometimes an Unhandled
Exception has occurred in your application Microsoft .Net FrameWork error is
displayed.
To avoid this problem, do not minimize the Excel window until Fabric Manager finishes generating the
physical inventory report.