WAS v8.5 > Troubleshoot > Troubleshooting Service integration > Problem solving for messaging engine file storesDiagnose problems with accessing file store files
Diagnose the causes of problems with accessing files in the file store and examine possible causes to the problems. Compare your symptoms with those listed in the following table and examine the possible solutions:
Symptom Cause Solution The messaging engine fails to start and writes error messages CWSIS1579E and CWSIS1583E. The log file for the file store is locked by another process and cannot therefore be opened by this messaging engine. The messaging engine has tried again to connect to the log file but has reached its retry limit and stopped.
- Check that no other instance of this or any other messaging engine is running that uses the same set of file store files.
The messaging engine stops unexpectedly and writes message CWSIS1590E. The file store has encountered an unexpected problem and has had to stop to ensure that it has a reliable copy of its data on disk. If configured to do so, the messaging engine will failover to a new instance and attempt to re-start.
- Check your server logs for any error messages output before message CWSIS1590E to see if they explain the shutdown.
- If the file store files are accessed across a network, check that a connection between the messaging engine server and the file server is available.
When the service integration message store tries to place a message and finds the file store full, the exception that occurs results in the creation of a large FFDC record. The messaging engine writes messages CWSIS1574E and CWSIS1575E. When message delivery fails because the file store is full, an FFDC record is created with the entire content of the file store. This makes the FFDC record too large, and the record occupies a large amount of disk space on the system. If you get a large FFDC record as a result of the file store becoming full, we can delete the FFDC record.