Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
Error <error code> has occurred (internal ID 3230203). Contact Microsoft Technical for assistance.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Microsoft Exchange Directory service?
- Error: -1811 - See ME253309.
- Error: 1720 - See ME180795.
Error code: 1 = "Incorrect function" - As per ME182513, there may be multiple causes for this error:
- the system date is incorrect and set to a year beyond 2038
- anti-virus software was installed before the Exchange Server installation
- a later version of Web browser than the version that ships with Windows NT 4.0 is not installed
- you are not logged in using the Exchange Server service account.
Error code: 8 = "Not enough storage is available to process this command." - As per Microsoft, The system is low on Virtual memory. Increase the size of the Paging File to allow more free virtual memory for Exchange Server. See ME174176.
ME317656 indicates that this may also occur after you update your Trend Micro scan engine to version 5.500.
Error code: 14 = "Not enough storage is available to complete this operation." - see comments for Error code 8.
Error code: -510 = "JET_errLogWriteFail" - The error can be caused by a corrupted Edb.log file. See ME301505 for workaround.
Error code: -514 = Applicable to SBS 2000, this problem may occur if you renamed the Exchange 5.5 service account to something other than the default value of "Administrator." This causes Setup to send incorrect parameters to the Exchange 2000 portion of the integrated setup, which results in the inability to successfully upgrade the Exchange 2000 Server component. See ME294159.
Error code: 1911 = "The object specified was not found" - As per ME240789, This issue can occur if one or more dynamic-link library (DLL) files that are associated with the operating system are damaged, missing, or modified. To resolve this issue, reapply the current service pack for the operating system and any fixes that were previously installed.
Error code: 1719 = "There are no protocol sequences." - Verify database registry and add this key if missing (Only for Windows 2000):
You can start now MsExchangeDS service and all other Exchange Services.
|Private comment: Subscribers only. See example of private comment|
|Links: ME174176, ME180795, ME182513, ME240789, ME253309, ME294159, ME301505, ME317656, ME326858, Error code 1811|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated