| Details | |
| Product: | Exchange |
| Event ID: | 482 |
| Source: | ESE |
| Version: | 6.5.0000.0 |
| Message: | %1 (%2) %3An attempt to write to the file “%4” at offset %5 for %6 bytes failed after %10 seconds with system error %8: “%9”. The write operation will fail with error %7. If this error persists then the file may be damaged and may need to be restored from a previous backup. |
| Explanation | |
| An unexpected error was encountered while writing to the file specified in the message.
The most common error associated with Event ID 482 found in the Description of the Event is ESE Error -1808, which means that the disk is full. One cause of receiving this error is that the disk may actually be full, and the database or the current transaction log cannot be written to because the disk is full. Another cause for ESE Error -1808 is that the file system may be FAT32, which has a limit of 4 GB. Another error that is found in the Description of Event ID 482 is ESE Error -1022. If Exchange asks the operating system for a page in the database, and an error occurs instead of the page data being returned, a -1022 error (JET_errDiskIO) results. The -1022 error is a generic error that appears whenever a disk input/output (I/O) problem prevents Exchange from gaining access to a requested page in the database. The most common reason for a -1022 error is a database file that was severely damaged or truncated. |
|
| User Action | |
|
Review the disk and file to which you are trying to write. If the ESE Error is -1808, check to see if the disk where the database or logs reside is full. If it is, determine the root cause of why the disk filled up. Check the file system and make sure the file system is not FAT32. If the ESE Error is -1022 and the error is caused by database damage in the file system, you need to verify or repair the file system, and then restore Exchange from a backup. Although repairing the database is still an option, repair is less likely to be successful than with the other errors because a -1022 error often signals extensive damage. If the database is undamaged, another application may be holding files open and preventing the Information Store service from accessing them. In such cases, you might also see -1032 errors (JET_errFileAccessDenied). Restarting all of the Exchange services or restarting the server might remove the lock. If the ESE Error is not -1808 or -1022, for information about ESE error codes and what they mean, see 266361 XADM: Exstensible Storage Engine 98 Error Codes 0 to -1048 or 266367 XADM: Extensible Storage Engine 98 Error Codes -1051 to -999999 |
|
Tag: Return code
Writing message tracking log entry failed. No more tracking information will be logged until the service is restarted. The last error is {error code}.
| Details | |
| Product: | Exchange |
| Event ID: | 95 |
| Source: | MSExchangeCCMC |
| Version: | 6.0 |
| Component: | Connector for Lotus cc:Mail |
| Symbolic Name: | MSG_TRACKING_WRITE_FAILED |
| Message: | Writing message tracking log entry failed. No more tracking information will be logged until the service is restarted. The last error is {error code}. |
| Explanation | |
| The Exchange server component that writes the entries to the log file is the System Attendant. | |
| User Action | |
| Restart the System Attendant service. Examine the event log for related errors. | |
Related:
IMPORT.EXE/EXPORT.EXE could not run because a temporary file (OUTxx.TMP) could not be created or opened. The system error code is {error code}{error code}.
| Details | |
| Product: | Exchange |
| Event ID: | 85 |
| Source: | MSExchangeCCMC |
| Version: | 6.0 |
| Component: | Connector for Lotus cc:Mail |
| Symbolic Name: | MSG_IMPEXP_OUT_FILE |
| Message: | IMPORT.EXE/EXPORT.EXE could not run because a temporary file (OUTxx.TMP) could not be created or opened. The system error code is {error code}{error code}. |
| Explanation | |
| Insufficient system resources were available to complete the operation. These types of errors usually occur when the server is low in memory and other resources. | |
| User Action | |
| Free up resources by closing unneeded processes. Locate the specified message on disk and manually remove it. | |
Related:
process name (process id) Unexpected file system error error code encountered while opening the restore environment file.
| Details | |
| Product: | Exchange |
| Event ID: | 950 |
| Source: | ESE BACKUP |
| Version: | 6.5.6940.0 |
| Component: | Microsoft Exchange Extensible Storage Engine Backup |
| Message: | process name (process id) Unexpected file system error error code encountered while opening the restore environment file. |
| Explanation | |
|
This event indicates that a file system error occurred when Exchange Server tried to open the restore environment file. For example, this event may be generated when a file is trying to perform a write operation as part of the restore process. |
|
| User Action | |
|
The user actions required to resolve this error depend on the error code listed in the event. Examine the file system error message number for more information about the file system error. To do this, at a command prompt, type net helpmsg <file system error message number> to translate that into a more readable error. For example, if the error is 53, the net helpmsg command will return “The network path was not found.” This should prompt you to make sure that you can access the administrative shares. You should also search the Microsoft Knowledge Base for more information about the error. In this circumstance, your search of the Microsoft Knowledge Base may return Microsoft Knowledge Base article 318755, “HOW TO: Restore Administrative Shares That Have Been Deleted” (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=318755). |
|
Related:
An error occurred while performing an ASN.1 decode. Syntax server error code: error code, Primitive type: name, Error detected at offset value. Contact Microsoft Technical Support. [valuevaluevaluevalue] (14)
| Details | |
| Product: | Exchange |
| Event ID: | 45 |
| Source: | MSExchangeMTA |
| Version: | 6.5.0000.0 |
| Message: | An error occurred while performing an ASN.1 decode. Syntax server error code: error code, Primitive type: name, Error detected at offset value. Contact Microsoft Technical Support. [valuevaluevaluevalue] (14) |
| Explanation | |
| ASN.1 is an ISO/ITU data encoding standard that refers to Specification of Basic Encoding Rules for Abstract Syntax Notation One.
The fully encoded ASN.1 envelope is in the Microsoft Exchange Server APDU (Application Protocol Data Unit) logs, which are binary representations of communication among message transfer agents (MTAs) in different sites and between MTA and client applications within a site. APDU logs are enabled when the logging levels of the X.400 service and APDU categories are both set to Medium or greater after you select MSExchangeMTA on the Diagnostics Logging tab of the Server Properties dialog box. To create Bf*.log files, set the logging level of the APDU and X.400 categories to Maximum. These text logs are stored in the Mtadata directory. The current log is always named Bf0.log. Prior logs are named Bfx.log, where x increases as the age of the log increases. |
|
| User Action | |
| The bad data may be viewed in the APDU log in Mtadata\Bf0.log. Reload the ASN.1 template files from the Exchange server installation compact disc. For more information, see Knowledge Base articles Q168906 and Q163032. | |
Related:
An error occurred while performing an ASN.1 decode. Syntax server error code: {error code}, Primitive type: {name}, Error detected at offset {value}. Contact Microsoft Technical Support. [{value}{value}{value}{value}] (14)
| Details | |
| Product: | Exchange |
| Event ID: | 45 |
| Source: | MSExchangeMTA |
| Version: | 6.0 |
| Component: | Message Transfer Agent |
| Symbolic Name: | MTA00045 |
| Message: | An error occurred while performing an ASN.1 decode. Syntax server error code: {error code}, Primitive type: {name}, Error detected at offset {value}. Contact Microsoft Technical Support. [{value}{value}{value}{value}] (14) |
| Explanation | |
| ASN.1 is an ISO/ITU data encoding standard that refers to Specification of Basic Encoding Rules for Abstract Syntax Notation One.The fully encoded ASN.1 envelope is in theMicrosoft Exchange Server APDU (Application Protocol Data Unit) logs, which are binary representations of communication among message transfer agents (MTAs) in different sites and between MTA and client applications within a site. APDU logs are enabled when the logging levels of the X.400 service and APDU categories are both set to Medium or greater after you select MSExchangeMTA on the Diagnostics Logging tab of the Server Properties dialog box. To create Bf*.log files, set the logging level of the APDU and X.400 categories to Maximum.These text logs are stored in the Mtadata directory. The current log is always named Bf0.log. Prior logs are named Bfx.log, where x increases as the age of the log increases. | |
| User Action | |
| The bad data may be viewed in the APDU log in Mtadata\Bf0.log. Reload the ASN.1 template files from the Exchange server installation compact disc. For more information, see Knowledge Base articles Q168906 and Q163032. | |
Related:
Failed to start due to failure to set the current working directory. The system error code is {error code}{error code}.
| Details | |
| Product: | Exchange |
| Event ID: | 42 |
| Source: | MSExchangeCCMC |
| Version: | 6.0 |
| Component: | Connector for Lotus cc:Mail |
| Symbolic Name: | MSG_STARTUP_CWD |
| Message: | Failed to start due to failure to set the current working directory. The system error code is {error code}{error code}. |
| Explanation | |
| The working directory, Exchsrvr\Bin, was not set. | |
| User Action | |
| Verify that the directory is available and the appropriate access privileges are set. If the problem persists, reinstall the connector. | |
Related:
Failed to start due to failure to create a Microsoft Win32 event. Please reboot the server. The system error code is {error code}{error code}.
| Details | |
| Product: | Exchange |
| Event ID: | 40 |
| Source: | MSExchangeCCMC |
| Version: | 6.0 |
| Component: | Connector for Lotus cc:Mail |
| Symbolic Name: | MSG_STARTUP_CREATE_EVENT |
| Message: | Failed to start due to failure to create a Microsoft Win32 event. Please reboot the server. The system error code is {error code}{error code}. |
| User Action | |
| View other events in Event Viewer to determine the cause of the failure.For more information about the error code reference specified in the message, go to www.reskit.com. | |
Related:
The service could not be started due to a failed wait for a Win32 object. Restart the service and if the problem persists reboot the server. The system error code is {error code}{error code}.
| Details | |
| Product: | Exchange |
| Event ID: | 24 |
| Source: | MSExchangeCCMC |
| Version: | 6.0 |
| Component: | Connector for Lotus cc:Mail |
| Symbolic Name: | MSG_STARTUP_WAIT_OBJECT |
| Message: | The service could not be started due to a failed wait for a Win32 object. Restart the service and if the problem persists reboot the server. The system error code is {error code}{error code}. |
| User Action | |
| For more information about the error code reference specified in the message, go to www.reskit.com. | |
Related:
The service could not be started due to a thread creation failure. Restart the service and if the problem persists reboot the server. The system error code is {error code}{error code}.
| Details | |
| Product: | Exchange |
| Event ID: | 23 |
| Source: | MSExchangeCCMC |
| Version: | 6.0 |
| Component: | Connector for Lotus cc:Mail |
| Symbolic Name: | MSG_STARTUP_CREATE_THREAD |
| Message: | The service could not be started due to a thread creation failure. Restart the service and if the problem persists reboot the server. The system error code is {error code}{error code}. |
| User Action | |
| Review the other event messages in Event Viewer to determine the cause of the failure. | |