Error Codes 3000–3999
Last updated on
This article documents the most common error codes in the range 3000–3999. If you encounter an error code that is not documented here, use the More Help menu to contact our support team.
3003
OMSRuntime cannot read a required file.
OMSRuntime will try to connect to DinkeyOMS to tell it about an update code that has just applied or failed to apply. If OMSRuntime could not connect to DinkeyOMS then it creates a receipt file and tries to connect again later and when it is next started.
Look for this file in the C:\ProgramData\Microcosm directory. The file will have the word receipt in it. What are the file permissions? What size is the file? Please contact Microcosm to try to resolve this problem.
3020
OMSRuntime could not determine the init system type (e.g. systemd, Upstart, OpenRC). This error can occur when OMSRuntime is installing or uninstalling itself as a daemon on Linux.
Please contact Microcosm with details of your operating system. e.g. Linux distribution name and version, Linux kernel version, etc., to help us find a solution.
3048
OMSRuntime has detected that the system date is incorrect. Set the system date and time to the correct values, including daylight saving time and time zone settings.
3049
OMSRuntime error creating named-pipe used for communication. The extended error will give the Linux system error why this call is failing.