Description | If a consolidated FSE system or FSE server has a power failure, external FSE clients are not |
| automatically reconnected to the server after it is restarted. |
Explanation | n/a |
Workaround | Stop all FSE processes on the FSE server and all external FSE clients. Restart the services on the |
| FSE server first, then restart the processes on the external FSE clients. |
| Note that an unexpected power failure of the FSE server may result in a condition where you |
| cannot stop the FSE client processes with the fse |
| operating system tools to terminate all FSE processes. |
| Linux specific |
| Use the kill command to terminate the FSE processes. |
| Windows specific |
| Use Task Manager to terminate the FSE processes. |
| If the above action does not stop the FSE processes, you must restart the host of the problematic |
| FSE client to restart the FSE processes. |
Description | After installation of an FSE server, the FSE processes are not started automatically. When you |
| try to start them manually, the following error is reported: |
| fse.exe Component not found |
| (Windows FSE server specific) |
Explanation | Because of a problem with software packaging, a dynamic link library is missing in the |
| |
Workaround | Uninstall the FSE server and install a consolidated FSE system afterwards. |
HP StorageWorks File System Extender Software user guide 243