MSSQL on Windows: XML: XML document could not be created because server memory is low. Use sp_xml_removedocument to release XML documents

Microsoft.SQLServer.Windows.EventRule.DBEngine.XML___XML_document_could_not_be_created_because_server_memory_is_low._Use_sp_xml_removedocument_to_release_XML_documents_1_5_Rule (Rule)

When you execute sp_xml_preparedocument , a parsed XML document is stored in the internal cache of SQL Server 2000. The MSXML parser uses up to one-eighth the total memory available for SQL Server. There is not enough memory in the portion of cache allocated to MSXML to open the document specified in the sp_xml_preparedocument statement. This may be because the specified document is very large or because documents already in that memory space do not leave enough space for the new document.

Knowledge Base article:

Summary

When you execute sp_xml_preparedocument , a parsed XML document is stored in the internal cache of SQL Server 2000. The MSXML parser uses up to one-eighth the total memory available for SQL Server. There is not enough memory in the portion of cache allocated to MSXML to open the document specified in the sp_xml_preparedocument statement. This may be because the specified document is very large or because documents already in that memory space do not leave enough space for the new document.

For more information about parsing XML documents, see "sp_xml_preparedocument" and "sp_xml_removedocument" in Docs Online.

Resolutions

Execute sp_xml_removedocument to remove documents from memory. Verify that your code always calls sp_xml_removedocument when you have finished processing a document. Your code should account for the possibility that a connection or transaction is interrupted between the sp_xml_preparedocument and the sp_xml_removedocument calls. To accomplish this, you may need to store open document handles in a table where you can reference them if a batch is interrupted.

Overridable Parameters

Name	Description	Default Value
Enabled	Enables or disables the workflow.	Yes
Interval (seconds)	The recurring interval of time in seconds in which to run the workflow.	300
Priority	Defines Alert Priority.	1
Severity	Defines Alert Severity.	1
Synchronization Time	The synchronization time specified by using a 24-hour format. May be omitted.
Timeout (seconds)	Specifies the time the workflow is allowed to run before being closed and marked as failed.	200
Timeout for query execution (seconds)	The workflow will fail and register an event, if the query execution takes longer than the specified period.	60
Timeout for database connection (seconds)	The workflow will fail and register an event, if it cannot access the database during the specified period.	15

Element properties:

Target

Microsoft.SQLServer.Windows.DBEngine

Category

EventCollection

Enabled

True

Alert Generate

True

Alert Severity

Warning

Alert Priority

Normal

Remotable

True

Alert Message

MSSQL on Windows: XML: XML document could not be created because server memory is low. Use sp_xml_removedocument to release XML documents

{2}

Comment

Mom2017ID='{136A2E5E-A460-4FAE-8587-D72C945E89EB}';MOM2017GroupID={467ECC75-C5DA-42BD-955C-A73BBB51AF74}

Member Modules:

ID	Module Type	TypeId	RunAs
_F6DA1507_12AF_11D3_AB21_00A0C98620CE_	DataSource	Microsoft.SQLServer.Windows.DataSource.EventCollectionFiltered	Default
GenerateAlert	WriteAction	System.Health.GenerateAlert	Default

Source Code:

<Rule ID="Microsoft.SQLServer.Windows.EventRule.DBEngine.XML___XML_document_could_not_be_created_because_server_memory_is_low._Use_sp_xml_removedocument_to_release_XML_documents_1_5_Rule" Target="SqlDiscW!Microsoft.SQLServer.Windows.DBEngine" Enabled="true" ConfirmDelivery="true" Remotable="true" Comment="Mom2017ID='{136A2E5E-A460-4FAE-8587-D72C945E89EB}';MOM2017GroupID={467ECC75-C5DA-42BD-955C-A73BBB51AF74}">

  <Category>EventCollection</Category>

  <DataSources>

    <DataSource ID="_F6DA1507_12AF_11D3_AB21_00A0C98620CE_" Comment="{F6DA1507-12AF-11D3-AB21-00A0C98620CE}" TypeID="Microsoft.SQLServer.Windows.DataSource.EventCollectionFiltered">

      <MachineName>$Target/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/MachineName$</MachineName>

      <NetbiosComputerName>$Target/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/NetbiosComputerName$</NetbiosComputerName>

      <InstanceName>$Target/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/InstanceName$</InstanceName>

      <ConnectionString>$Target/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/ConnectionString$</ConnectionString>

      <InstanceVersion>$Target/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/Version$</InstanceVersion>

      <InstanceEdition>$Target/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/Edition$</InstanceEdition>

      <MonitoringType>$Target/Property[Type="SqlDiscW!Microsoft.SQLServer.Windows.DBEngine"]/MonitoringType$</MonitoringType>

      <SqlExecTimeoutSeconds>60</SqlExecTimeoutSeconds>

      <SqlTimeoutSeconds>15</SqlTimeoutSeconds>

      <TimeoutSeconds>200</TimeoutSeconds>

      <IntervalSeconds>300</IntervalSeconds>

      <SyncTime/>

      <EventDisplayNumber>6624</EventDisplayNumber>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="GenerateAlert" TypeID="Health!System.Health.GenerateAlert">

      <Priority>1</Priority>

      <Severity>1</Severity>

      <AlertMessageId>$MPElement[Name="Microsoft.SQLServer.Windows.EventRule.DBEngine.XML___XML_document_could_not_be_created_because_server_memory_is_low._Use_sp_xml_removedocument_to_release_XML_documents_1_5_Rule.AlertMessage"]$</AlertMessageId>

      <AlertParameters>

        <AlertParameter1>$Target/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/MachineName$</AlertParameter1>

        <AlertParameter2>$Target/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/InstanceName$</AlertParameter2>

        <AlertParameter3>Event ID: $Data/Property[@Name='EventID']$. $Data/Property[@Name='Message']$</AlertParameter3>

      </AlertParameters>

      <Suppression>

        <SuppressionValue/>

      </Suppression>

    </WriteAction>

  </WriteActions>

</Rule>