Resolution:
Description:
= = = = = = =
List of things to be checked to avoid this fatal error.

Environment:
= = = = = = =
Windows.

Resolution:
= = = = = =
The FATAL: Exiting on non-retryable disk error is generated when the shared storage device that stores the
EMS data files goes down or does not respond or there is an issue with locking.  For this particular "error: 33",
according to Microsoft spec (http://msdn2.microsoft.com/en-us/library/ms681382.aspx) ,  the ERROR_LOCK_VIOLATION 33
(0x21) is thrown when the process cannot access the file because another process has locked a portion of the file.

In the code of EMS , server just do the WriteFile() call. It means that what EMS does is ask the Operative System to write the
messages in disk.  The error is returned from the operating System, in this case for Windows.   Looks like there is some locking issues to access the db files.  So please check if there are any other utilities like backup run in the background takes the lock. If that is the case, backup utilities should be run on the files which are are not EMS server's DB files.  EMS locks only DB files and configuration and other files can be backed up with no issues.

Reference:
= = = = = =
(http://msdn2.microsoft.com/en-us/library/ms681382.aspx

Keywords/Tags:
= = = = = = = = =
disk error

Possible causes of the error " FATAL: Exiting on non-retryable disk error: 33" inEMS server log