Error Log Messages

In reviewing the error log, you may see one or more of these messages.

Error message text Explanation

Failed to obtain TransactionDispenserInterface: XACT_E_TMNOTAVAILABLE This message is an informational error message indicating that the Microsoft Distributed Transaction Coordinator (MS DTC) service is either currently not running on the server, or is currently unavailable. For more information about MS DTC, see your Microsoft Distributed Transaction Coordinator documentation.

Error message text	Explanation
Failed to obtain TransactionDispenserInterface: XACT_E_TMNOTAVAILABLE	This message is an informational error message indicating that the Microsoft Distributed Transaction Coordinator (MS DTC) service is either currently not running on the server, or is currently unavailable. For more information about MS DTC, see your Microsoft Distributed Transaction Coordinator documentation.
`Warning: Server cursor memory usage: %d pages. If this message repeats, see the Error Log Messages topic in Troubleshooting.`	For example: `Warning: Server cursor memory usage: 531 pages. If this message repeats, see the Error Log Messages topic in Troubleshooting.` Either too many cursors have been created and left open, or have not been deallocated. It is recommended that a cursor be closed and deallocated as soon as it is no longer needed. For more information, see Cursors. In time-critical situations, the system administrator may need to terminate those connections that have not been closing or deallocating cursors using KILL.
`Warning: SQL cache memory usage: %d (pages). If this condition persists, see the Error Log Messages topic in Troubleshooting.`	The SQL Server cache consumes memory and holds ad hoc and prepared SQL text. This message occurs if the SQL Server cache exceeds a certain number of pages of server memory. For example, this error occurs if one or more clients are preparing large numbers of SQL statements without performing corresponding unprepare operations. This lack of corresponding unprepare operations can be due to poor application design, an application bug, or repeated creation of prepared SQL text. This message will be printed again if server memory changes significantly and if the memory consumption of the SQL Server cache remains high. Either warn the suspected clients that server memory is at a low level, or terminate suspected connections using KILL.

Warning: Server cursor memory usage: %d pages. If this message repeats, see the Error Log Messages topic in Troubleshooting.

For example:

Warning: Server cursor memory usage: 531 pages. If this message repeats, see the Error Log Messages topic in Troubleshooting.

Either too many cursors have been created and left open, or have not been deallocated. It is recommended that a cursor be closed and deallocated as soon as it is no longer needed. For more information, see Cursors.

In time-critical situations, the system administrator may need to terminate those connections that have not been closing or deallocating cursors using KILL.

Warning: SQL cache memory usage: %d (pages). If this condition persists, see the Error Log Messages topic in Troubleshooting.

The SQL Server cache consumes memory and holds ad hoc and prepared SQL text. This message occurs if the SQL Server cache exceeds a certain number of pages of server memory. For example, this error occurs if one or more clients are preparing large numbers of SQL statements without performing corresponding unprepare operations. This lack of corresponding unprepare operations can be due to poor application design, an application bug, or repeated creation of prepared SQL text.

This message will be printed again if server memory changes significantly and if the memory consumption of the SQL Server cache remains high.

Either warn the suspected clients that server memory is at a low level, or terminate suspected connections using KILL.

Error Log Messages

See Also